MID routing that saves sales
Spread charges across the NMI merchant accounts you already hold. A soft decline retries on the next MID when the card can be re-sent — not for Collect.js, Apple Pay or Google Pay.
How ElasticFunnels picks the MID
Every rule below runs together on one charge, not a menu you pick one item from. A fraud filter runs first. Part of Checkout & Payments.
- Weighted split
- Each MID's share of traffic comes from its weight
- Card brand
- Only MIDs whose rules allow that brand are eligible
- Product
- Only MIDs whose rules allow that product are eligible
- Amount range
- Only MIDs whose min/max amount covers the charge are eligible
- Daily cap
- A MID over its daily cap drops out until it resets
- Monthly cap
- A MID over its monthly cap drops out until it resets
A second MID for a soft decline
Insufficient funds or Do Not Honor on one account is often an approval on the next. The cascade retries on another eligible MID when the card can be re-sent; it does not apply to Collect.js tokenized entry, Apple Pay, Google Pay or vault charges.
- Pick the NMI and processor decline codes that count
- Set the maximum number of retries (at most twice by default, configurable 0-5)
- Direct-encrypted/keyed card entry only — not Collect.js, wallets or vault charges
- Hard declines are never cascaded
Keep each MID inside its limits
Give every NMI MID a weight, the traffic it may take and a daily cap. Preview which MID a charge would pick before it goes live.
- Rules by card brand, product and order amount
- Upsells and rebills stay on the MID that stored the card
- Daily transaction cap per MID, monthly volume cap
- Routing preview to test a rule
- Per-MID sales, revenue and refunds in the load balancing report
Why one MID is a fragile place
ElasticFunnels does not issue merchant accounts. It decides which of yours each charge goes to.
Caps and reserves
Spread volume so no account breaches its monthly cap.
Chargeback ratio
Alerts and auto-refunds keep each MID healthy.
Phone recovery
Failed charges go to agents, with the decline code.
MID routing FAQ
What is MID routing?
MID routing decides which of your NMI merchant accounts (MIDs) each charge is sent to. ElasticFunnels splits charges by weight across the eligible MIDs, filtered by the rules you set for card brand, product, order amount and daily or monthly caps. That pick is for the first sale: upsells and rebills stay on the MID that stored the card, because the saved card only works there.
What is payment cascading?
When a charge is soft-declined, for example for insufficient funds or Do Not Honor, the cascade retries it on another eligible MID — only when the card can be re-sent, so it does not apply to Collect.js tokenized card entry, Apple Pay, Google Pay or vault charges. You choose which decline codes count and how many retries are allowed, at most twice by default (configurable 0-5).
Are hard declines retried too?
No, and they should not be. A stolen card, a closed account or an issuer block must not be retried on another MID, because it inflates your decline ratio. Cascading is for soft declines only.
Is ElasticFunnels a high-risk merchant account provider?
No. ElasticFunnels does not underwrite anyone or issue merchant accounts. You bring the MIDs you already hold, from your acquirer or ISO, and ElasticFunnels decides which one each transaction goes to.
Which gateways does MID routing work with?
The routing rules run on NMI MIDs, and the cascade retry works when the card can be re-sent, so it does not apply to Collect.js, Apple Pay, Google Pay or vault charges; you can connect as many NMI merchant accounts as you hold. Stripe, PayPal, Klarna and Authorize.net connect as separate payment methods on the checkout.
Can I keep one MID from breaching its cap?
Yes. Set a daily transaction cap per MID and a monthly volume cap, and a MID at its cap is skipped automatically so volume spreads to the ones still under it.