Bring your merchants. Build on Sovara Core™.
Developer platforms, such as Sovara Golf™, connect to Sovara Core™ through Sovara Hub™. Restricted keys, signed webhooks and a sandbox that behaves like live. Each of your merchants keeps its own Sovara One™ account.
A payment in one call. Charged exactly once.
Amounts are whole cents. Every POST takes an Idempotency-Key, so a retry returns the first answer instead of charging again.
- Test keys route to the simulator. Same code, same responses, no real money.
- Test tokens for every outcome: approved, declined, timeouts, partial approvals.
- A test clock to move time forward instead of waiting.
# Take a test payment: $79.00, charged once even if you retry curl https://api.sovaraone.com/v1/payment_intents \ -H "Authorization: Bearer sk_test_…" \ -H "Idempotency-Key: order-SO-1001" \ -d '{"amount":7900,"currency":"usd","confirm":true, "payment_method":"tok_test_approved"}'
Designed for the day the network goes quiet.
Idempotent by default
Every POST needs an Idempotency-Key. The same key returns the same answer for seven days. A different body with the same key is refused.
Never a double charge
When the gateway doesn't answer, the payment goes "unknown" and only reconcile can move it. Nothing is sent again until we know what happened.
Signed webhooks
Every event is HMAC-signed, retried with growing waits and can be replayed. One versioned event catalog.
Restricted keys
Platform keys carry only the scopes you need, for only the merchants connected to you.
Card data never touches you
Card fields come from the gateway in a secure window. You get a token and what you need to show the card: brand and last four.
Typed and documented
A TypeScript SDK with generated types. An OpenAPI file checked against real responses on every release, and llms.txt.
Your merchants, each with its own account.
Each merchant on your platform is boarded by an ISO, by Sovara Pay™, or through your partner link. It keeps its own Sovara One™ account and its own merchant account, and stays the seller.
- Your ISO sees you as your own line in its book.
- The merchant sees your connection and what it can do, and can disconnect at any time.
- You get your merchants' events through your own connection.
Example data
An MCP server, restricted keys and a human in the loop.
Connect an AI assistant through our MCP server with a restricted key. Reads work right away. In live mode, money moves wait for a person to approve them.
- llms.txt and OpenAPI for tools that read docs.
- Scopes per key: read-only, draft, or exactly what you tick.
- An audit log of every action, by person or by assistant.
Example data
Try it before anyone signs anything.
Tell us what you're building. We'll set up a sandbox with test keys, test cards and the developer docs.
- Test mode is not billed and never touches real cards or money.
- Docs, OpenAPI, SDK and llms.txt included.
- Going live needs each merchant's own merchant account from a payments provider.
Building for a single merchant? Use that merchant's Sovara One™ account. The engine's developer site is sovaracore.com.