
By Daniel Karpilovsky, Head of Success, Payneteasy
The outcome of per customer payment routing is simple: trusted customers reach the route that suits them, risky ones are held to tighter rules, and you steer both from one payment orchestration platform instead of rebuilding rules for every provider.
Per customer payment routing means the routing engine looks at who is paying before it picks a route. Card BIN, issuer country and amount still matter. But they describe the transaction. Customer signals — verification status, history with each route, behaviour — describe the person. Two people with similar cards can deserve very different routes.
This guide is for payment and risk leads at PSPs (payment service providers), gateway operators and merchants in demanding verticals. It covers which customer signals to route on and where they sit in the rule order. It also shows how cascading should behave per customer level, which mistakes turn routing into risk, and how to measure the result. If you need the module-level view of customer tiers first, start with our overview of per-customer payment logic.
Per-customer payment routing vs per-transaction routing
Classic rules-based routing answers one question: which acquirer (the bank or provider that processes card payments for the merchant) is most likely to approve this card, in this currency, for this amount. That logic works on data that arrives with the authorisation request. Some engines add a short memory of the card — sending it back to the acquirer that approved it last time. But none of this tells the engine who the customer is. A first-time buyer and a verified customer paying with a new card look the same.
Per-customer routing adds a second layer of input. Before the engine compares acquirers, it knows the customer's level: new, verified or restricted. It knows how their past payments did on each route and which limits apply. The difference is easiest to see side by side:
| Transaction-level routing | Customer-level routing |
|---|
| Question it answers | Which route can approve this card? | Which route should see this customer? |
| Typical inputs | BIN, card type, issuer country, currency, amount | Trust level, KYC status, history per route, velocity, dispute record |
| How often inputs change | Every transaction | Over days and weeks, as the customer builds history |
| Where the data lives | In the authorisation request | In a customer registry or the merchant's CRM |
| Typical risk if misused | Sending traffic to a route that cannot accept it | Sending a risky customer to a route chosen for trusted ones |
Transaction attributes tell you which acquirer can approve this card. Customer history tells you which acquirer should see this customer.
The two layers do not compete. Good intelligent payment routing uses transaction attributes to find the routes that can technically approve, and customer signals to choose among them.
Five customer signals worth routing on
Most teams already hold these signals somewhere — in KYC tools, CRM fields or spreadsheets. The work is getting them to the payment layer in a form a routing rule can read.
- Trust level. New, Verified, VIP, Restricted, or your own scale. It usually reflects KYC status and payment history and is the single most useful customer input, because it summarises the rest.
- Track record on each route. A customer whose payments clear reliably on one acquirer and fail on another is telling you something no BIN table can. Route history per customer is what turns balancing from averages into specifics.
- Tenure and value. How long the customer has paid and how much. It justifies higher limits and premium routes, and it tells you whose false declines are the most expensive.
- Risk behaviour. Velocity, repeated failed attempts, card changes, dispute history. These signals are what move a customer down, and a level scheme without a way down leaves risk on routes chosen for trusted customers.
- Payment direction and type. A deposit, a withdrawal, a first payment and a repeat payment carry different risk and often belong on different routes. For payouts, the route decides how fast the customer gets paid, which matters as much as approval on the way in.
One filter before any signal goes into a rule: could you explain it to your acquirer's risk team? If routing on a signal would be hard to justify in a review, it does not belong in the routing logic.
Rule order: where the customer fits in the routing stack
A customer signal is powerful, which is exactly why it should not run first. A workable order looks like this:
- Eligibility. Which routes may accept this transaction at all — approved business types, currencies, countries, acquirer volume limits. Nothing downstream may override this step.
- Customer level. Narrow the eligible routes to those configured for the customer's level, with the level's own limits per day, week and month.
- Transaction attributes. Among the remaining routes, apply BIN, issuer country, card type and amount rules.
- Balancing and cost. Use observed performance, processing fees and volume commitments to pick the route — or split traffic between equivalent routes.
- Cascade policy. Decide which declines may cascade (move to the next route), how many hops are allowed and which routes are off-limits for this level.
Here is how it plays out. A new customer makes a first deposit. Eligibility leaves three routes. The New level narrows them to one: the route with the strictest screening, full 3-D Secure checks and low daily limits. After KYC and a run of clean payments, the customer moves to Verified. The same card now goes to the route that performs best for repeat customers, with higher limits. A dispute or a burst of failed attempts should move the customer to Restricted — by an operator’s decision or by your CRM sending the new level with the next transaction. The routing follows the level — no one edits a routing rule.
Route on who is paying only after you have routed on what is allowed.
Cascading per customer: retry only what the rules allow
Cascading — sending a declined payment to the next route — recovers sales when the first acquirer fails for reasons that another acquirer would not share. It also costs money and can create risk. Whether a decline is eligible for a retry depends on scheme rules, acquirer rules, the fraud score and your retry policy, and customer level is a sensible input to that policy:
| Decline type | Cascade? | Per-customer nuance |
|---|
| Technical: acquirer unavailable or connection error | Usually yes, to the next eligible route | Same for all levels — the problem was the route, not the customer |
| Timeout with no response | Only after confirming the first attempt did not authorise | Otherwise the customer can be charged twice |
| Issuer unavailable | Rarely useful if the issuer itself is down; can help if the outage sits on the acquirer’s side | Counts toward scheme retry limits |
| Generic soft decline | Sometimes, within scheme and acquirer rules | Reasonable for Verified and VIP; keep tight or off for New |
| Soft decline asking for authentication (Visa 1A; Mastercard 65 in Europe) | Retry with 3-D Secure, not on another route | Authentication data carries the acquirer named in the 3-D Secure request and cannot simply be reused on another route |
| Insufficient funds | Rarely useful — another acquirer meets the same balance | Better handled by a later retry policy than by a cascade |
| Hard decline: lost or stolen card, closed account, invalid card | No | Also a signal to review the customer's level |
| Declined by fraud screening | Not to a looser route | A cascade here moves risk; it does not recover a sale |
Card schemes also police retries directly. Visa groups decline responses into categories and treats some as “do not reattempt”; Mastercard returns Merchant Advice Codes, including “do not try again”. Both schemes can charge for excessive reattempts on the same card. A cascade policy that ignores these responses will pay for declines it was never going to recover.
Per-customer limits close the loop. A cap on how many attempts and how much volume one customer ID may generate per day stops a single customer — or someone testing stolen cards under one account — from walking the whole route list.
A cascade that sends a new customer's declined payment to your most permissive acquirer is not recovery. It is risk transfer.
Five ways per-customer routing goes wrong
- Levels that never move. Levels assigned by hand drift: yesterday's new customer is still “New” six months later and still pays for strict screening. Levels need rules for moving up and down: promotion can run on thresholds automatically, while demotion needs an owner — a risk analyst or your CRM, which can send the current level with every transaction.
- Routing around risk. Per-customer routing chooses among routes you are approved to use. Using it to send traffic onto an account that was not approved for that business, or to blur what a transaction is, breaks acquirer and scheme rules — and that is a compliance problem, not an optimisation.
- Breaking recurring payments. Merchant-initiated payments rely on the network transaction ID of the original customer-initiated transaction and on stored credentials. Not every acquirer accepts a reference created on another route, so check before a level change moves a customer's subscriptions — or route recurring payments separately and keep them on the route where they started.
- Ignoring authentication. In markets with strong customer authentication, whether a low-risk exemption can be requested depends partly on the acquirer's own fraud levels. The route changes how much friction a trusted customer sees — worth measuring, not assuming.
- Samples too small to read. Split traffic into ten levels across six routes and most cells hold a few hundred payments. Start with three or four levels and add more only when the data supports it.
How to prove it works: measure per level, per route
A blended approval rate hides exactly what per-customer routing changes. Read these per customer level and per route:
| Metric | Why it matters |
|---|
| First-attempt approval rate | Shows whether the chosen route was right before any cascade |
| Approval rate after cascade | Shows what the cascade policy recovers, and for whom |
| Cost per approved transaction | Processing fees plus the cost of declined attempts and retries |
| Dispute and fraud ratio | Shows whether trusted levels stay trustworthy on looser routes |
| Share of customers per level | Reveals frozen levels and promotion rules that are too strict |
| Payout success and speed | Withdrawals are part of the customer experience, not an afterthought |
To compare fairly, keep a control share of each level on your previous routing for a fixed period and compare like with like: same level, same issuer countries, same payment type. Assign the control share by customer, not by transaction, so the same customer stays on the same routing for the whole test. Comparing VIP customers on the new route with new customers on the old one only proves that VIP customers pay better. Look at the approval rate and the dispute ratio together — an uplift that arrives with more disputes is not an uplift.
How this runs on Payneteasy
On Payneteasy, customer levels live in the Customer Management System (CMS), a payment-aware customer registry inside the gateway. The building blocks map onto the stack above:
- Levels and limits. Levels per merchant account, set up separately for deposits and withdrawals. Each level defines which routes or gates are available, minimum and maximum amounts per currency, and daily, weekly and monthly limits on customer ID usage by count and amount.
- Two sources of truth. In Payment Gateway mode Payneteasy holds the customer records; in CRM/API mode your CRM sends the customer ID and level with each transaction and CMS mirrors it.
- Automatic level changes. Auto-leveling promotes customers one level at a time on thresholds you set, for deposits and withdrawals, in Payment Gateway mode. Moving a customer down is an operator’s decision there; in CRM/API mode your CRM sets the level in both directions.
- Routing by level. Each level has its own list of available routes and gates, so the level narrows the routing tree before rules by country, card type and amount apply. A separate CMS Trust Level routing type splits traffic by whether the customer already has an approved transaction. Balancing is based on accumulated processing statistics, with cascading across connected routes. Routes blocked by limits, filters or acquirer restrictions drop out before the chain is built, so eligibility always comes first.
- Route history per customer. Cascading strategies can reorder the chain by the customer's last result on each acquirer, and a gate that returned selected decline codes can be skipped for the same card for a set number of minutes.
- Cascade control. For each acquirer connection you choose which decline reasons continue the chain and which stop it, and an acquirer restriction applies Visa’s resubmission limits to declined recurring transactions.
- Reporting. Client level appears in transaction details and reports, and orders can be searched by client level and merchant client ID — the raw material for the measurement above.
The routing sits on a payment orchestration platform (one integration that connects and manages many payment providers) with more than 1,000 integrations and 130+ fraud filters. Payneteasy is the technology and control layer: you keep your acquirers, your merchant accounts and your risk decisions.
Intelligent payment routing on an orchestration platform: one integration, many providers
Intelligent payment routing only pays off if you can reach enough providers and change the rules without a new project each time. Payneteasy gives you smart routing and cascading across more than 1,000 integrations through one connection, so per customer payment routing becomes a rule you edit, not a connector you build. When a payment fails on one route, your routing rules decide whether the next provider gets a try, which is how you keep failed payments and the revenue they put at risk under your control.
- Machine-readable API. The Processing API is described in OpenAPI 3.1, so your engineers and tooling read the contract instead of reverse-engineering it.
- AI agents on live payment data. A read-only MCP server gives AI agents live access to payment data, so your team catches decline and routing issues sooner while control stays with you.
- 21 years in payments. Payneteasy has been building payment technology since 2005.
The routing layer is technology and control: you keep your acquirers, your merchant accounts and your risk decisions. See the orchestration platform and the white label gateway for how the pieces fit.
If you want to see how your current customer segments would map onto levels and routes, talk to our team — we will walk through your traffic and the rule order with you.
PSP
Offer your customers a top-level payment solution, increase your turnover and boost your business profit.
Merchants
Only one integration to consolidate all your payment providers to a unified management system.