Enrutamiento de conmutación por error
El enrutamiento de conmutación por error es fundamental para mantener el tiempo de actividad del procesamiento de pagos. Cardflo detecta y responde automáticamente a las interrupciones del adquiriente o la pasarela redirigiendo las transacciones a canales alternativos y operativos.
Este enfoque proactivo minimiza el tiempo de inactividad y evita la pérdida de ventas, lo que garantiza que sus operaciones de pago sigan siendo resilientes en condiciones adversas.
- Categoría
- Enrutamiento
- Capacidades
- 10
- Disponible en
- Todos los planes
La visión general
Failover routing serves as a contingency mechanism within the payment orchestration layer to preserve authorisation continuity during technical interruptions.
When a primary acquirer, gateway, or processor experiences a service degradation or complete outage, the routing engine identifies the failure through specific response codes or timeout thresholds. The system then redirects the volume to a pre-configured secondary or tertiary endpoint.
This technical architecture addresses the inherent fragility of single-point processing models by diversifying risk across multiple Merchant Identification Numbers (MIDs) and payment service providers. By decentralising the flow of transactions, merchants can maintain operational stability even when external infrastructure components fail.
The process is typically transparent to the cardholder, as the redirection occurs within the backend authorisation flow before a final response is rendered at the checkout.
Effective failover management requires precise configuration of health checks and priority tiers to ensure that redirected traffic aligns with the merchant's commercial agreements and regional compliance mandates.
Cómo funciona
Health monitoring and detection
The system continuously monitors the responsiveness of active acquirers and gateways. It identifies anomalies such as elevated error rates, persistent timeouts, or specific HTTP status codes indicating server-side issues.
If a provider fails to meet predefined performance benchmarks, the routing engine marks that channel as temporarily unavailable to prevent further transaction failures.
Triggering the failover logic
Once a disruption is confirmed, the orchestration layer intercepts incoming authorisation requests intended for the affected provider.
The logic evaluates the transaction metadata, including the BIN, currency, and MCC, to determine which alternative processing path is best suited to handle the redirected volume while maintaining high authorisation prospects.
Dynamic path redirection
Transactions are instantly rerouted to a secondary or tertiary acquirer as defined in the merchant routing table.
This transition happens in real time, ensuring that the payment process continues without requiring the consumer to re-enter their card details or restart the checkout session, thereby protecting the conversion rate.
Automated recovery and rebalancing
The system continues to probe the primary endpoint with low-volume tests or heartbeat requests. Once the service provider demonstrates stability and returns to normal operation, the failover rule is deactivated.
Traffic is then gradually rebalanced back to the primary channel in accordance with the merchant's cost and volume preferences.
Por qué importa
Mitigating systemic downtime risks
Even Tier 1 acquirers experience scheduled maintenance or unplanned technical incidents that can halt processing for hours. Failover routing acts as a structural safeguard, ensuring that a merchant's ability to accept payments is not tethered to the uptime of a single partner.
By distributing traffic across a multi-acquirer setup, businesses can insulate their revenue from localised infrastructure failures and maintain a consistent processing profile.
Protecting the customer experience
Technical declines caused by processor instability often lead to cart abandonment, as many cardholders will not attempt a second transaction after a system error. Failover mechanisms resolve these issues in the background, allowing the transaction to clear through a healthy path.
This minimises the occurrence of soft declines related to system connectivity, preserving brand reputation and reducing the customer support burden associated with payment failures.
Casos de uso
High volume flash sales
During peak traffic events, a primary gateway may become throttled or overwhelmed. Failover routing automatically shifts excess load to a secondary provider, preventing a total collapse of the checkout process.
Cross border processing
When a regional acquirer faces connectivity issues with international schemes, failover rules can redirect the traffic to a global acquirer to ensure that foreign transactions continue to be authorised without interruption.
Scheduled provider maintenance
Merchants can pre-emptively activate failover paths during a known maintenance window of their primary PSP, ensuring that midnight batches and recurring billing cycles proceed through an alternative active channel.
SCA and 3DS outages
If an issuer or ACS provider has latency issues, the system can attempt an alternative route that may have different connectivity to the relevant authentication rails, minimising potential friction.
En cifras
Typical availability achieved by merchants using multi-acquirer redundancy to bypass individual provider outages, based on industry-standard infrastructure reliability.
The estimated volume of transactions usually lost to technical declines and service timeouts that can be recovered through automated path redirection.
The standard duration required for a modern orchestration engine to identify a gateway timeout and initiate an alternative routing path.
Términos relacionados
Talk to our team about a live rollout on your acquiring stack.
Lo que obtienes con Enrutamiento de conmutación por error
- Detección automatizada de interrupciones del adquiriente y la pasarela
- Redireccionamiento instantáneo a conexiones de conmutación por error designadas
- Prioridades y reglas de conmutación por error configurables
- Soporte para múltiples rutas de conmutación por error
- Impacto reducido de las interrupciones del servicio externo
- Resiliencia mejorada del procesamiento de pagos
- Support for multi-MID setups to diversify risk across different geographical banking entities.
- Customisable timeout thresholds to prevent excessive wait times during the authorisation attempt.
- Granular logging of failover events for post-incident analysis and service level agreement monitoring.
- Integration with smart routing logic to maintain cost-efficiency during emergency redirection periods.
A short scoping call, then a written plan for your MIDs.
Preguntas sobre Enrutamiento de conmutación por error
¿Qué activa el enrutamiento de conmutación por error de Cardflo?
El enrutamiento de conmutación por error se activa mediante la supervisión en tiempo real de las respuestas del adquiriente y la pasarela.
Cardflo identifica fallos como errores de conexión, tiempos de espera de procesamiento o códigos de denegación explícitos que indican una interrupción, iniciando una redirección inmediata a una conexión activa.
¿Se puede personalizar el enrutamiento de conmutación por error?
Sí, Cardflo permite una amplia personalización de las reglas de conmutación por error. Puede especificar qué adquirientes actúan como respaldo para otros, definir umbrales de volumen de transacciones o establecer condiciones basadas en regiones geográficas, adaptando el sistema a sus necesidades operativas.
¿Cómo afecta el enrutamiento de conmutación por error a la velocidad de las transacciones?
El enrutamiento de conmutación por error está diseñado para ser fluido. Aunque puede haber un aumento fraccional de la latencia durante el proceso de redireccionamiento, suele ser imperceptible para el usuario final, lo que garantiza una experiencia de pago continua y eficiente sin retrasos significativos.
Does failover routing require the customer to re-enter their payment details?
No, if the merchant uses a central vault or payment orchestration layer, the card data is captured once and held securely.
If the first authorisation attempt fails due to a technical error, the system use the existing token to attempt the transaction with the secondary provider.
To the cardholder, this may appear as a slightly longer processing time, but the interface remains consistent and no secondary data entry is required.
What happens to 3D Secure authentication during a failover event?
If 3DS authentication has already been successfully completed, the authentication payload must be compatible with the secondary acquirer for the failover to succeed. If the interruption occurs before 3DS is finalised, the system may need to restart the authentication flow with the new provider.
Advanced orchestration platforms manage these handovers to ensure that the SCA requirements of PSD2 are still met during the redirection.
How quickly can the system detect a failure and switch to a new acquirer?
Detection usually happens within milliseconds or after a defined number of consecutive failures. Merchants can set thresholds, such as three consecutive 5xx errors or a timeout exceeding five seconds.
Once the threshold is met, the switch is instantaneous for all subsequent transactions. This rapid response is critical for maintaining high-volume checkout flows where even a few minutes of downtime can result in significant revenue loss.
¿Listo para la velocidad?
Cuéntanos sobre tu negocio. Te pondremos en contacto con los socios adquirentes y la ruta adecuada, normalmente en una semana.