Product
One integration covering every method in our footprint, in both directions, with the routing and recovery layer that decides whether a payment succeeds or quietly fails.
107 methods · 70 of them payout-capable
01 · Pay-ins
Most users here do not hold a card that works cross-border. These are the categories that do.
Domestic cards are the smallest category in this footprint. That is why a card-first stack fails here.
In most of our footprint the wallet is the primary account, not a layer on top of one. A user with GCash or bKash may have no card at all — so wallet coverage is not an add-on, it is the market.
Instant account-to-account rails have reset entire markets. They clear in seconds, carry no chargeback exposure, and cost materially less than card interchange.
Central-bank QR standards collapse a fragmented wallet market into a single acceptance point. One integration reaches every wallet on the scheme.
Easy to dismiss and expensive to skip. For the unbanked cohort — still a large share in Mexico, Colombia, Egypt and Japan — this is the only way they can pay you online.
Local schemes that international acquiring does not reach. A card issued on RuPay, Elo, Troy, Meeza or JCB frequently declines cross-border and authorises domestically.
Available where it is lawful and sensible, and refused where it is not. Brazil's Resolution BCB 561 bars stablecoin settlement of cross-border remittances by eFX providers from October 2026 — we will tell you that before you build a plan around it, not after.
02 · Payouts
Most providers treat payouts as an afterthought bolted onto a collection product. For your users, the withdrawal isthe trust event — and returning funds to the instrument they deposited from is both the fastest route and the cleanest position to defend.
70 of our 107 methods move in both directions.
Funds return to the wallet they came from. Same rail, same identity, fastest path — and the cleanest position to defend if anyone asks how money moved.
Direct to local accounts on instant rails where they exist, batch where they do not, with per-recipient status rather than one opaque batch result.
Built for creator and affiliate schedules: thousands of recipients, one submission, individual outcomes you can act on.
03 · Platform
Connecting to a rail is the easy part. What decides your authorisation rate is what happens in the two seconds after a provider says no.
Without cascading, attempt one returns an error and the deposit is over.
A declined attempt re-routes to the next provider on the same method before the user sees an error — not after they have already closed the page.
Soft declines are retried against an alternative route with backoff. Hard declines are surfaced with a reason your support team can actually use.
Mobile-first checkout built for 3G and mid-range Android, because that is what traffic in South and Southeast Asia is genuinely running on. Method ordering is tuned per market.
Returning users pay in one step. Credentials are tokenised at capture, so neither your systems nor ours hold the instrument itself.
Every transaction carries a stable reference through settlement, so finance is not matching by hand at month end.
Add a market or a method by configuration, not by another engineering cycle. Webhooks for every state change.
04 · Security
How we hold and move data, described as architecture. We make no regulatory claims on this page and hold ourselves to the controls below regardless.
Sensitive credentials are tokenised at the point of capture. Your systems and ours hold references, not instruments, which keeps the breach surface small enough to reason about.
TLS on every hop, envelope encryption for stored records, key material in a managed HSM-backed store with rotation. No production secret is readable from an application log.
Sanctions and PEP screening on counterparties, with velocity and pattern monitoring above it. Alerts stop money rather than merely recording it.
Merchant balances are held separately from operating capital and reconciled daily. You can see what is yours, what has cleared and what is in flight.
Internal access to merchant data is role-scoped, time-bound and recorded. Every read of a transaction record is attributable to a person and a reason.
Routing degrades to the next provider rather than to a blank screen, and status reaches your dashboard before your support queue hears it from users.
Four questions about your business and your markets. If we are a fit, a payments lead responds within one business day with the methods and indicative pricing for your corridors.
We work with licensed operators and incorporated businesses. Corporate email required. We do not publish a general enquiries address.