Routing
How MintCash picks a provider for each charge — the inputs the routing engine evaluates and the rules you can configure per merchant.
Every payment goes through a routing decision before it touches a provider. You send one request to MintCash; we decide which payment service provider (PSP) is the best fit for that specific charge, then forward it. From your application's perspective, the choice is invisible.
The decision
The routing engine evaluates the request against your merchant configuration and selects a provider. The decision is deterministic for identical inputs — if you replay the same charge under the same rules, you get the same provider.
What the engine considers
| Input | Examples |
|---|---|
| Geography | Customer country, issuer country |
| Card type | Brand (Visa, Mastercard, etc.), credit vs. debit |
| Currency | Charge currency vs. provider supported currencies |
| Merchant rules | Per-merchant priority list, allow/deny lists |
| Historical health | Recent success rate per provider for similar charges |
Rules are stored per merchant and evaluated server-side. You don't ship routing logic in your application — change a rule on our side and it takes effect on the next charge.
What you control
You can request changes to your routing configuration through your account manager. Common levers:
- Priority list — preferred provider order for a given geography or card type
- Allow/deny — block specific providers for specific corridors
- Currency mapping — which provider settles each currency
Routing is decoupled from the API
Adding, removing, or reprioritizing providers doesn't require code changes on your side. The API contract — request shape, response shape, webhook envelope — is the same regardless of who actually runs the charge.