GatePay sits between your platform and your acquirers. It scores every transaction for risk, sends it to the processor most likely to approve it, and cascades to the next one when a decline is worth retrying.
The cheapest acquirer declines with a retryable code, so the payment cascades and is captured on the second attempt — in one API call.
4023 issuer unavailable — retryable, so the payment cascades rather than failing.
The tenant console. Figures shown are illustrative.
Counted from the source, not from a brochure: currencies from the money module, integrations from the adapter registry, rails from the payout module. The last one is the declarative adapter generator — an acquirer’s specification becomes a working integration without a deploy.
How it works
None of them are hidden. Every routing decision is recorded against the payment, including the acquirers that were considered and why each was skipped.
Velocity, amount, blocklists, device signals and third-party fraud providers score the payment before any acquirer is contacted.
Eligible acquirers are ranked on live approval rate and processing cost. The payment goes to the one most likely to take it.
A soft decline moves to the next acquirer in milliseconds. A hard decline stops immediately, so a dead card is not retried into the ground.
Every candidate, every exclusion and every response code is written against the payment. Nothing about the decision is a black box.
Platform
Built for operators as much as integrators — the console is where MIDs are priced, limits are set, disputes are worked and reporting is pulled.
Run several processors and merchant accounts side by side. Add capacity, a currency or a region without touching your code.
Rules and heuristics run first, so a suspicious payment is held or declined rather than charged and then argued about.
A first-party script fingerprints the browser and classifies the network — datacentre, VPN, proxy, automation — and feeds the score.
Per-MID limits by card, by person or in aggregate, on a rolling window or resetting at a fixed local time in your own timezone.
A payment left in an unknown state is queried on a schedule until the acquirer answers, never assumed either way.
Separate access for operations, finance and support, with a record of who changed which MID and when.