Routing
How MintCash picks a provider for each charge — the inputs the routing engine evaluates and the rules you can configure for your account.
Every payment goes through a routing decision before it touches a payment service provider (PSP). You send one request to MintCash; e 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 request shape, response shape, and webhook envelope are the same regardless of who runs the charge.
The decision
The routing engine evaluates the request against your merchant configuration and selects a provider.
What the engine considers
| Input | Examples |
|---|---|
| Geography | Customer country, issuer country |
| Card type | Brand (Visa, Mastercard, etc.), credit vs. debit |
| Route health | Recent success rate per acquirer 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
Changes to your provider configuration flow through your account manager — there's no self-serve API for it. Adding or switching providers requires no code changes on your side. 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.