Platform
MID rerouting and failover.
When an account gets restricted, your checkout does not have to be your only point of failure. Eligible traffic can move.
What is MID Rerouting? MID rerouting moves eligible transaction traffic between configured merchant identification accounts when routing policy calls for it.
Why use multiple MIDs?
Multiple MIDs are a standard redundancy layer, not an upsell. They give a merchant configured alternatives when an account is restricted or its operating conditions change, subject to each account’s underwriting and allowed transaction profile.
- •Backup MIDs should be provisioned before they are needed.
- •Each MID remains subject to its bank’s decisions and approved profile.
How does automatic failover work?
Health monitoring can watch configured MID signals and trigger an automatic failover threshold for eligible traffic. The policy is explicit, and a manual dashboard override lets an operator respond when business context requires a different routing decision.
- •A failover path is prepared before a restriction becomes a checkout incident.
Illustrative routing example — not measured PayFull performance.
How does this support resilient operations?
Rerouting does not override a bank’s decision or guarantee processing. It reduces dependence on one account by giving the payment stack a preconfigured alternative while the merchant and PayFull address the underlying account situation.
- •See High-risk processing for the approved no-surprise-shutdowns commitment.
Common questions
How do I discuss this with PayFull?
Start with your business model, customer journey, existing payment stack, and underwriting context. PayFull can then discuss an appropriate configuration; availability depends on review and applicable providers.
Start accepting payments the way your business actually sells.
Set up in days, not months. White-glove onboarding included on every plan.
Talk to us before you commit to anything.