Live demo
Payment Gateway
- Create a checkout session as the merchant, then pay it as the buyer.
- Watch the routing rule pick a processor, and the cascade take over when one is down.
- The card is tokenized before the server sees it: SAQ A, or the hosted vault.
- Multi-processor routing
- SAQ-A or hosted vault
- Live interactive demo
How the demo works
- 1
Set the amount, the buyer's country and the routing rule.
- 2
Pay in the buyer panel: card, wallet or QR.
- 3
Follow the trace: route, attempts, capture, settlement.
Under the hood — what runs when you pay
Every click in the demo hits the real gateway API against a live sandbox acquirer.
The backend creates a session
POST /api/v1/sessions pins amount, currency, and region. The gateway resolves the processor — buyer and merchant never pick one.
The card never hits the server
SAQ-A tokenizes inside the processor secure fields; the hosted-vault path KMS-encrypts the PAN into an isolated CDE.
Geo-routed to a live sandbox
Each region routes to its own acquirer — real sandbox acquirers, with circuit breakers and retries.
Captured, settled, posted
Each money event posts a balanced double-entry ledger line; idempotency keys make every call exactly-once.
POST /api/v1/sessions
Create a checkout session; returns a one-time client_secret.
POST /api/v1/client/pay
Pay against a session with a processor token (SAQ-A path).
POST /api/v1/client/checkout
Hosted-vault submission: vault the PAN, then charge the token.
GET /api/v1/transactions/{id} · /settle
Poll the transaction, then clear the funds.
Tell us where
it breaks
Bring the part of your fintech stack that is hard right now. We start with a working consultation and scope to outcomes.