Multi-gateway routing
Each payment goes to the PSP most likely to approve it, by country, currency, card brand, amount or product.
Smart payment routingMulti-gateway payment orchestration with gateway and MID cascading
Every declined card is an ad click you already paid for. Smart payment routing sends each payment to the gateway most likely to approve it and cascades soft declines to your next gateway or MID before the shopper sees an error. Renewals route too, so subscribers stay subscribed.
4,600+ brands have processed $3.8B+ on Funnelish
Transparent pricing: up to 0.3% per routed transaction, because the card is stored in a secure vault that works across gateways, and we pay for that vault on every routed payment. 0% of your revenue otherwise. On the Advanced plan, for cards on any MID. See plans
Smart routing
Set your rules once. Funnelish routes every order, upsell and renewal to the right gateway and MID, and cascades soft declines to the next one.
Each payment goes to the PSP most likely to approve it, by country, currency, card brand, amount or product.
Soft declines cascade to the next gateway or MID before the shopper sees an error. One card form, one charge.
Split volume across MIDs by %, so no single merchant account carries all your revenue.
Renewals rebill on any connected gateway. If a PSP bans or closes your account, subscribers keep their plan.
Free 14-day trial · No credit card · Any MID, any PSP
Peak days and account holds
Split peak-day volume across accounts and ramp new MIDs gradually. Your second gateway is already approved and taking traffic, so an account hold or freeze doesn't stop sales.
Black Friday orders go to two gateways, not one. Less pressure on each account.
Send it a small share of orders first. Raise it once approvals hold.
If one account pauses, orders cascade to the next gateway. Your ads keep selling. Why Stripe pauses accounts
Set up in minutes. Your checkout stays the same.
Routing rules
Pick a default gateway under Settings, then add rules for declines, volume splits, currency, customer location or region, order amount, card brand and product. Change them anytime without touching the checkout.
Raise auth rates
When the first gateway soft-declines, the payment cascades to the next gateway or MID in line.
Handle peaks
Send a fixed share of orders to a second account. Ramp a new account up gradually.
Sell abroad
Send each market to the account that acquires there. Pairs with local funnels.
Cut fees
Send Amex to the account that has it enabled, or charges least for it.
Protect margin
Send big tickets to a high-limit account. Keep small ones where approvals are highest.
Route anything
Keep subscriptions on one account and one-time orders on another.
No code. Change rules anytime.
MID health
Processors watch each MID's volume, declines and disputes. Spread the load so no single MID carries everything, and see each account's fail rate, so one weak MID never drags down your auth rates.
Gateway-agnostic rebilling
Half of subscription churn comes from failed card payments. Renewals follow your routing rules and cascade to another gateway before any dunning email goes out, so subscribers you never meant to lose keep their plan.
26.3%
What retries alone recover. Retries recover about one declined renewal in four: 26.3% of managed renewals declined on the first attempt were paid on a later retry.
Managed renewals on card gateways, last 90 days to November 6, 2026. Not a smart payment routing figure.
Cross-border payments
Cross-border cards get more soft declines. Route each market to a gateway that acquires locally, in that currency, and lift auth rates abroad.
Compare
Payment orchestration platforms route payments too, but you integrate them yourself. In Funnelish it's part of the funnel.
| Orchestration platform | Funnelish | One gateway | |
|---|---|---|---|
| Cascade soft declines to another gateway or MID | Yes: Yes | Yes: Yes, same card form | No: No |
| No single point of failure | Yes: Yes | Yes: Yes, second gateway already live | No: No |
| Route by country, card, amount, product | Yes: Yes | Yes: Yes, no code | No: No |
| Setup | No: Developer integration | Yes: A few rules in settings | Yes: Done |
| Checkout, upsells, subscriptions | No: Separate tools | Yes: Built in | No: Separate tools |
| Cost | No: Platform fee + gateway fees | Yes: Up to 0.3% per routed payment + gateway fees | Yes: Gateway fees |
Orchestration platforms vary by vendor and plan. More on what slows a paid-traffic checkout in Shopify checkout optimization.
FAQ
Smart payment routing sends each card payment to the payment processor (PSP) and merchant account (MID) most likely to approve it, using rules you set, and retries a declined payment on a backup. In Funnelish you connect two or more card MIDs, on any PSP, pick a default and add rules by declined transaction, volume split, currency, customer location or region, order amount, card brand, product type or product tag. You find payment routing under Settings.
Routing guideYes. Each charge follows your rules, so a customer's main order, one-click upsell and later renewals can run on different processors or merchant accounts. The customer only sees one checkout.
Managed subscriptions keep renewing. Move the default to another connected MID and rebills run there from the next billing date. Subscriptions held inside a gateway's own billing system can't move this way.
Managed subscriptionsPayment orchestration is the wider category: one layer that connects several gateways, fraud tools and payment methods. Smart payment routing is the part that decides where each charge goes. Funnelish builds it into the checkout, so there is no separate platform to integrate.
Cascading, also called payment failover, passes a declined payment to the next gateway or merchant account (MID) in line, so one processor's soft decline doesn't cost you the sale. In Funnelish this is the Transaction declined rule. The shopper types the card once and sees one attempt.
Card payments route on any MID, and you need at least two card MIDs connected. Checkout.com and Razorpay connections can't join a routing setup yet. If that is where your MID sits, or it is one we have not connected at all, say so on your onboarding call and we connect it, through a PSP you already run or by building it for you, fast. High-risk MIDs connect the same way, often through Authorize.net, which works with a wide range of acquirers.
Card paymentsNo. Routing covers card payments only. PayPal, Klarna, iDEAL and other methods stay on the same checkout as usual. They just aren't routed between gateways.
Add payment methodsApple Pay and Google Pay run through Stripe. If your routing setup doesn't lead with Stripe, Funnelish flags it, so you choose between routing and wallets for each funnel.
Express checkout"Do not honor" is a generic decline from the card issuer that gives no reason. It often hits genuine buyers, especially on cross-border payments. With a Transaction declined rule, the payment is retried on your backup gateway, where a different acquiring bank may approve it.
Failed and declined paymentsNo. The backup gateway only runs after the first one declines, so the shopper sees one card form and one attempt, and pays once.
Hard declines: insufficient funds, expired or invalid cards, and cards reported lost or stolen. They decline on every gateway, so the shopper needs another card or payment method.
You can, but two Stripe accounts usually decline the same cards. Put your backup MID with a different acquirer, through any PSP.
It keeps new orders coming in. Your backup is already connected and approved, so card traffic can move to it straight away. Routing doesn't release funds a processor is already holding.
It works alongside Stripe rather than replacing it. Keep Stripe as your default and add a backup MID on any PSP, so one account is never the only way your customers can pay. With routing or managed subscriptions, the card vault and your subscriptions live in Funnelish, not in Stripe, so they stay yours. Orders still sync to Shopify.
Shopify integrationYes, for managed subscriptions, which route on every rebill. Subscriptions held inside a gateway's own billing system aren't routed. You can also keep subscription products on a separate MID from one-time orders.
Managed subscriptionsEach gateway is a merchant account underwritten in your name, and Funnelish routes by clear rules: declines, volume share, country, currency, card brand, amount and product. Check each provider's terms for anything specific to your account.
No. Orders from every gateway land in the same Funnelish orders list and sync to Shopify like any other order. Analytics shows approvals and failures per gateway. Each gateway still pays out to your bank separately.
Payment analyticsSmart payment routing is available on the Advanced plan and costs up to 0.3% per routed transaction, on top of your gateway's fees. The fee exists because the card is stored in a secure vault that works across gateways, and we pay for that vault on every routed payment.
How routing fees compare with Checkout ChampConnect a second gateway, turn on cascading, and the next "do not honor" goes to another gateway or MID instead of being lost.
4,600+ brands have processed $3.8B+ on Funnelish
No credit card required · Your own gateway accounts · Free migration
Book a demo
A 30-minute walkthrough with our team, built around your offer. Tell us where to send the invite.
Sales across every channel. It tells us who on the team should run your demo.
Before the call, our team goes through your offers, pages and checkout and prepares the demo around what would move your numbers. You leave with a clear plan either way, even if Funnelish turns out not to be the fit.
We build the demo around it.
A 30-minute walkthrough with the Funnelish team ·
Calendar not loading? Open the booking page · Prefer to try it yourself? Start free
The invite is in your inbox. Before the call we go through your offers, pages and checkout, so the demo is built around your numbers.