Failover & rails
Ordered backup paths when a primary rail fails - distinct from DLR status truth.
Failover ledger tags finance can reconcile
Tag which rail fulfilled each prepaid unit without exposing brands so finance can join wallet, delivery, and switch exports on one opaque identity.
Failover ops runbook when volume is already live
At live volume, name who may reorder rails, who watches prepaid burn, and who owns client-facing status during a failover switch — white-label roles before the pager.
Partial failover send without double charge
Mid-flight rail switch on one client intent must settle once and never invent Delivered on backup — white-label prepaid honesty for partial failover.
Failover gates before any Live badge
Do not flip a corridor or channel to Live until the ordered backup path is vault-green and smoke-tested — white-label prepaid honesty before production promises.
Primary rail fails: ordered backup path without double-debit
When the primary messaging rail fails, follow a documented ordered backup so one client intent settles once — white-label statuses, no upstream brands, no double prepaid debit.