Use case summary
Build routing rules in Corefy's visual editor using 100+ transaction attributes — issuer country, card brand, amount, currency, even your own metadata like risk scores or customer tiers. Each payment then goes to the provider most likely to approve it, at the best cost. You change the logic yourself in the dashboard, and it takes effect immediately.
- Payment Manager
Why one routing setup can't fit every transaction
E-commerce decline rates run as high as 15%, and a large share of those are wrong calls: false declines of legitimate customers cost merchants an estimated $443 billion a year globally. And 41% of consumers say they'll never return to a brand after a false decline.
When every payment follows the same path, each segment where that provider is weak keeps losing payments that a different route would have approved. Payment teams see this in their data. But when routing logic lives in code, redirecting traffic means a developer ticket, a sprint, and a release, so routing decisions get made rarely, on stale data, while the approval gap widens with every transaction.
How to send every payment down its best path
Corefy's routing engine decides the path for each transaction at the moment it's committed, following rules you define — no code involved.
- 1
Connect the providers you want to route between
Each connected provider account brings its supported methods and currencies into your payment scheme; these become the routes your rules choose between.
- 2
Build rules in the visual editor
Every rule is a readable condition: attribute, operator, value — 'issuer country is UK', 'amount is greater than €500' — combinable into groups with AND/OR logic. A JSON editor is there for teams that prefer it, with drafts and approvals so changes are reviewed before they touch traffic.
- 3
Use any of 100+ attributes
Geography and IP, card BIN, brand and type, amount, currency, date and time, provider availability and response times — and your own metadata: attach a risk score, loyalty tier, or first-deposit flag to a transaction and route on it, which turns your business context into routing logic no provider-side tool can see.
- 4
Pick a distribution strategy per rule
Use priority order, percentage split, balance-based distribution, or turnover caps to stay within provider limits or the optimal strategy, selecting the route by weighing conversion and cost dynamically instead of following a fixed list.
- 5
Let cost break the tie
Where two providers approve a segment equally well, route to the cheaper one — approval optimization and fee optimization in the same rule set.
- 6
Watch, then adjust in minutes
Analytics shows approval rates per route, method, and currency, so when a provider's performance shifts, updating the rule is a dashboard edit that takes effect without a developer queue or release window.
What you get
Every traffic segment gets the provider that approves it best, and the results show up in your overall rate.
More approvals from the same provider mix
Every traffic segment gets its strongest provider, so the weak spots of any single provider stop taxing your whole volume.
Lower processing costs without approval trade-offs
Cost-aware strategies route to cheaper providers wherever performance is equal — savings that compound at volume.
Routing decisions at the speed of the market
A provider degrades on Tuesday; the payment team reroutes your traffic the same day without engineering involvement.
Routing on your own business data
Attach metadata to transactions — risk tiers, VIP segments, deposit history — and use it in routing rules alongside standard attributes. Your business context becomes part of the routing decision, applied consistently across every provider you process through.
From 56.2% to 85.1% conversion
A PSP processing through multiple providers worked with Corefy to build routing schemes that send each transaction to the provider with the highest approval rate for that transaction type and to the cheapest one where approval rates tie. Their live rules go beyond standard attributes like card brand, geolocation, and amount, down to custom metrics such as the number of successful 3DS transactions on a specific card and card turnover per currency. Combined with cascading and checkout improvements, their payment conversion grew from 56.2% to 85.1% within a year.