Platform · Connectivity

Route every payment to the right rail.

A pluggable gateway engine that resolves the correct credentials and route for every transaction — per operator, per bank, per currency.

Routing

Smart routing, built in

The gateway engine sits between your operators and the rails — resolving credentials, matching rules and dispatching every transaction to the right provider.

Per-operator gateway configuration

Each brand carries its own gateway credentials and settings, fully isolated from every other operator on the core.

Bank & currency routing rules

Define which provider handles each bank and currency pair, so every transaction follows the path you intend.

Inbound bank-callback handling

Receive and verify bank callbacks reliably, then reconcile each one against the originating transaction.

Pluggable gateway providers

Add new providers behind a common interface — no rewrites, just configuration, so your rail mix can grow over time.

Dedicated gateway paths

Pin specific flows to dedicated routes for priority traffic, special bank arrangements or high-value transactions.

Outbound merchant callbacks

Notify merchants of every status change with templated, reliable callbacks and a full delivery log.

Resolution

One transaction, the right route.

For every payment, the engine resolves the operator's credentials, matches the bank and currency to a route, and dispatches to the provider — deterministically, every time.

Resolve operator credentialsLoad the right keys and config for the brand behind the transaction.
Choose bank/currency routeMatch the bank and currency to the configured routing rule.
Dispatch to providerHand off to the selected gateway and track the result.
Routing decisions
MYR · Bank A→ Aurora Pay
IDR · Bank B→ Nimbus
THB · Bank C→ Aurora Pay
SGD · Bank A→ Dedicated
Throughput by route
Lifecycle

How routing works

From the moment a transaction arrives, the engine walks a deterministic path — resolve, match, route and reconcile.

1

Transaction received

A payin or payout enters the engine, tagged to its operator.

2

Operator config resolved

Credentials and gateway settings for the brand are loaded.

3

Bank & currency rule matched

The right routing rule is selected for the bank and currency.

4

Routed to provider

The transaction is dispatched and the callback reconciled.

Reliability

Callbacks you can trust.

Both sides of the conversation are handled with care — inbound bank callbacks are verified, outbound merchant callbacks are templated, and every event is logged for full traceability.

Inbound bank callbacks verifiedEvery incoming callback is validated before it is acted on.
Outbound merchant callbacks templatedConfigurable request/response templates per merchant.
Full callback logsEvery attempt and delivery is recorded and searchable.
Callback events
Bank A → payin confirmedVerified
Merchant #M-204 notifiedDelivered
Bank B → payout settledVerified
Merchant #M-187 retryingRetry
Delivered
99.4%
In retry
0.6%

Route every payment with confidence.

Plug in your providers, define your rules and let the engine resolve the right route for every transaction.