Cascade routing explained for supplement merchants

What is cascade routing?

Cascade routing (sometimes called failover or retry routing) means: when a card payment attempt fails on PSP A, the orchestration layer automatically retries on PSP B (and optionally C) before showing the customer a decline — subject to rules you define.

It is not magic. Hard declines (stolen card, insufficient funds, issuer hard block) usually fail everywhere. But soft declines — issuer unavailable, acquirer policy friction, descriptor mismatch, geographic BIN quirks — are often recoverable on a different rail.

Why supplement merchants need it more than generic e-commerce

• Category risk scoring — adaptogens, weight-loss adjacency, peptide stacks, and international BINs trigger more false positives.
• Subscription economics — a 3% auth lift on rebills compounds to six figures annually at scale.
• Processor policy whiplash — the PSP that loved you in Q1 can throttle MCC risk in Q2 without a personalized warning.
• Global buyers — US-issued cards on UK acquirers (and vice versa) fail more often without intelligent routing.

Single-gateway WooCommerce plugins give you one dice roll per checkout. Orchestration gives you a loaded die — weighted by data.

How a cascade actually works (step by step)

1. Customer submits card at checkout.
2. Router scores the attempt — BIN country, cart category, amount, historical auth rate per PSP, time of day.
3. Primary PSP attempts authorization.
4. On soft decline codes (e.g. do-not-honor, processing error, generic decline where retry is allowed), secondary PSP attempts with same token or PAN (per PCI scope).
5. Success → customer sees one clean approval. Failure after all routes → decline UX with wallet alternates if configured.
6. Ledger logs every hop — which PSP cleared, latency, decline code — so finance and ops stop flying blind.

Cascade vs smart routing vs load balancing

Best orchestration stacks combine smart initial route + cascade on soft decline. Supplement merchants at $100k+/mo should ask vendors for both, plus transparent decline-code reporting.

Rules that matter for herbs, peptides, and OTC-adjacent SKUs

• Descriptor consistency — statement text that matches landing page and receipt reduces issuer fraud triggers.
• Velocity limits per PSP — avoid slamming a new MID with 100% of Black Friday on day one.
• Subscription token portability — know whether rebills can cascade or must stick to the capturing PSP.
• Chargeback routing — separate high-dispute SKUs if needed; do not poison the whole MID.

iKash implements routing + cascade as first-class orchestration — not a checkbox on a single-gateway plugin. See also our herbs & botanicals and WooCommerce high-risk pages.

Metrics to track after you enable cascade

• Auth rate by PSP — who is actually performing this week?
• Cascade recovery rate — % of soft declines saved on PSP #2+.
• Latency p95 — retries must stay sub-second feel at checkout.
• Net revenue after fees & reserves — auth rate vanity means nothing if settlement eats the margin.