One API surface. Every corridor. Defined settlement.
Acceptance, processing, and multi-currency settlement run through a single integration point. No patchwork of regional processors, no opaque FX spreads.
Three layers. One integration.
The acceptance layer handles card networks, local payment methods, and alternative rails across 60+ markets. Processing normalizes authorization and routing in real time.
Settlement consolidates multi-currency positions into a single ledger entry per cycle. Your operations team reads one reconciliation file, not twelve.
All three layers are addressable through one versioned REST API with webhook delivery for every state transition. No polling, no proprietary SDKs required.
Settlement benchmarks
Funds arrive on schedule, not eventually.
T+1 standard
Settlement cycles are contractually defined per corridor — T+1 for most major markets, T+0 on select rails. The schedule does not flex with network congestion.
T+0 available
FX conversion prices at mid-market. The spread is declared in the API response before the transaction commits — no post-hoc adjustments, no margin buried in the rate.
Declared at auth
Ready to evaluate the stack?
Connect with the infrastructure team. Bring your corridor requirements, volume estimates, and current processor pain points — no slide decks unless you ask.