One API. Every payment rail. Reconciliation that actually reconciles.

You're a fintech, a platform, or an operator who has outgrown a single PSP. You need to route across acquirers, handle 3DS, manage retries, settle to multiple destinations, and produce a daily reconciliation that finance trusts. Payments Central is the layer that handles all of that, so your team can ship product instead of payments plumbing.

Key features

• Acquirer-agnostic: route by cost, success rate, or geography.
• Card-present and card-not-present, real-time payouts, and account-to-account rails.
• Programmable settlement: split, hold, escrow, or sub-merchant payouts.
• Reconciliation engine with first-class export to your ledger.
• Webhooks, idempotency keys, and a sandbox that mirrors production behavior.

Why teams pick it

• Designed by people who have integrated payments at three previous companies and got tired of the same broken patterns.
• Pricing is interchange-plus and visible on the site — no "call us."
• Subsidiary of Red Mutex, so the support and engineering you get isn't a contractor in a queue.

Developer experience

curl -X POST https://api.paymentscentral.com/v1/payments \
  -H "Authorization: Bearer $PC_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"amount": 4999, "currency": "USD", "source": "tok_visa", "merchant_id": "mer_123"}'

SDKs in TypeScript, Python, Go, and Ruby. Full docs at docs.paymentscentral.com.