Build payments
the Sovara way.
Simple, honest, and on your terms.
Sovara Core™ is the payments engine under Sovara Hub™ and Sovara One™. One API, one ledger and one set of rules, from your first test call to the deposit in the merchant's own bank.
Everything a payment needs, in one engine.
The API, the ledger, webhooks, the gateway connection, tenancy and the sandbox are one system. Every product on top of it reads the same records.
One API
A REST API with a TypeScript SDK, hosted checkout, payment links and a drop-in for your own pages.
One ledger
Double-entry, in integer cents. Posted entries never change. A correction is a new entry.
Signed webhooks
HMAC-signed events, retried with growing waits and replayable.
One partner tree
Sovara, ISOs, sub-ISOs, platforms, merchants and locations, kept apart by the database itself.
Charged exactly once
Every gateway call sits between two database transactions. An unclear answer waits for reconcile.
No card numbers
Card data goes straight to the gateway. The engine keeps a token and the last four digits.
Pick the product for who you are.
Sovara Hub™ and Sovara One™ both run on Sovara Core™, so a sale shows up for the merchant and in its ISO's book at the same moment. Buyers see Sovara Pay™ at checkout and on receipts.
For ISOs, sub-ISOs and connectors
The full ISO platform: your book and pipeline, boarding and underwriting, residuals and margins, and setup help for every merchant you bring. Residuals and margins are estimates until the processor's statements confirm them.
For merchants
The account where merchants run their payments: checkout and payment links, in-person sales, refunds, customers, orders and every fee, itemized and marked as estimates until the statement confirms them.
Build in the sandbox. Go live with the same code.
Test keys and live keys call the same API. Only the route changes: test keys reach a simulator, and live keys reach the gateway.
- An Idempotency-Key on every POST. A retry returns the first answer, never a second charge.
- Pinned API versions. The current version is
2026-12-01. - OpenAPI 3.1, llms.txt and an MCP endpoint for your tools and your AI assistants.
Example data
From the buyer's card to the merchant's bank. Never through us.
Sovara never holds merchant funds. Each location has its own merchant account, and the processor deposits straight to the merchant's own bank.
The buyer pays
On a checkout page, a payment link, Tap to Pay or a terminal. The merchant is named as the seller.
The gateway authorizes
Card data goes straight to the gateway. The engine records the intent before the call and the result after it.
The processor settles
The processor batches each merchant account's payments for the day. Fees stay estimates until its statement confirms them.
The merchant's bank is paid
Deposits go from the processor straight to the merchant's own bank. No Sovara company holds the money.
Try the engine in the sandbox.
Tell us what you're building. We'll set up test keys, test cards and the developer docs.