Skip to main content

Multi-Provider Routing

NextAPI connects to multiple financial providers and routes each transaction to the most appropriate one. You do not choose the provider directly — NextAPI handles this automatically based on a set of routing factors.

Current providers​

NextAPI currently connects to 3 financial providers — a mix of banks and e-wallets — with more partners joining as the network grows.

Each provider connects to BancNet and can generate virtual accounts, QRPH codes, and initiate payouts. Having multiple providers means transactions are never dependent on a single institution — if one experiences issues, routing shifts to another automatically.

What each provider can do​

All providers support the same core capabilities:

  • Generate virtual bank accounts (unique account numbers per merchant/account)
  • Generate dynamic one-time QRPH codes
  • Generate static QRPH codes
  • View current balance
  • Initiate payouts to any Philippine bank or e-wallet

Routing factors​

NextAPI's routing engine considers several factors when selecting a provider:

1. Cost​

Each provider has a different cost structure for the same transaction type. NextAPI routes to the lowest-cost available provider for each transaction. Your net transaction cost is determined by your partner agreement with NextPay — the underlying provider rates are not passed through directly.

2. Strategic routing factors​

Routing balances cost, reliability, and strategic factors — it is not purely cost-optimized. This means the cheapest provider for a given transaction may not always be selected.

3. Reliability​

Provider uptime and success rates vary. NextAPI tracks real-time reliability and down-weights providers that are degraded. If a provider has elevated failure rates, transactions are routed away from it automatically.

4. Partner-specific rules​

For certain partner integrations, routing can be configured based on existing financial relationships between the partner and a specific provider.

Routing decision flow​

Transaction request received
        │
        ▼
Is any provider degraded?
  YES → exclude degraded provider(s)
        │
        ▼
Does a partner-specific rule apply?
  YES → route to designated provider
        │
        ▼
Is minimum volume commitment met?
  NO  → route to commitment provider
        │
        ▼
Select lowest-cost available provider

What this means for your integration​

Routing is transparent to your integration — you call the same API endpoints regardless of which provider handles the transaction. You will see the provider reflected in payout details and webhook payloads, but your code does not need to handle provider selection.

Things to be aware of:

  • Do not assume a specific provider in your reconciliation logic — the provider can change between transactions
  • Reliability varies — if a specific provider is experiencing issues, your payouts may take longer as NextAPI routes around it
  • Rates are dynamic — your net transaction cost may vary slightly between transactions of the same type

Observability​

The provider used for each transaction is included in payout and posting records. Use GET /v2/accounts/{id}/postings to see the full posting history with provider details.

Growing network

The number of connected providers continues to grow. Each new provider adds redundancy and improves routing cost efficiency across the network.