Reglas de transacción
Las reglas de transacción de Cardflo proporcionan un control granular sobre cómo se procesan los pagos individuales. Los comerciantes pueden definir parámetros específicos que dictan si una transacción es aceptada, rechazada, enrutada a un adquirente particular o sometida a verificación adicional.
Este nivel de control optimiza los flujos de pago, gestiona el riesgo y mejora las tasas de conversión aplicando la lógica precisamente donde se necesita.
- Categoría
- Riesgo
- Capacidades
- 10
- Disponible en
- Todos los planes
La visión general
Transaction rules represent the logic layer within a payment gateway or orchestration platform that governs the lifecycle of an individual payment request. By applying conditional statements to inbound data, these rules determine the path of a transaction before it reaches the acquirer.
Logic is typically structured using attributes such as the Bank Identification Number (BIN), Merchant Category Code (MCC), or geographical metadata. This mechanism allows a merchant to manage risk profiles and cost structures in real time.
Rather than treating all traffic as uniform, rules enable the segmentation of payments by risk level, value, or origin. This ensures that high-value transactions may require more stringent verification like SCA, while low-friction paths are maintained for low-risk scenarios.
This granularity is essential for businesses operating across multiple jurisdictions where local regulations and scheme rules vary. Effective rule implementation focuses on balancing fraud prevention with the preservation of authorisation rates.
Cómo funciona
Attribute extraction and identification
When a customer initiates a payment at the checkout, the system identifies specific metadata associated with the request. This includes the card issuer country, the specific BIN, the currency, and the Merchant Identification Number.
These variables serve as the foundational data points upon which subsequent logic is applied.
Application of conditional logic
The transaction passes through a sequence of pre-defined 'if-then' statements. For example, a rule might specify that if a transaction exceeds a certain value and originates from a high-risk region, it must be diverted.
This stage determines the immediate fate of the payment before any network calls occur.
Fraud and authentication filtering
Based on the internal logic, the system decides whether to trigger Strong Customer Authentication via 3DS.
Rules can be configured to request 3DS only when risk thresholds are met, thereby reducing friction for low-value or trusted payments while maintaining compliance with relevant PSD2 or regional regulations.
Direction to optimal gateway
Once the transaction is validated, the rules engine chooses the most appropriate acquirer. This decision may be based on the lowest interchange-plus costs, the highest historical authorisation rates for the specific card type, or the need to meet volume commitments stipulated in merchant service agreements.
Authorisation and response handling
The request is transmitted to the selected acquirer. Upon receiving a response, the rules engine can interpret decline codes.
If a soft decline occurs, the system may initiate an automated retry through a different route, provided the merchant's ruleset permits subsequent attempts for that specific failure reason.
Por qué importa
Authorisation rate optimisation
Static routing often results in unnecessary declines due to regional card preferences or issuer-specific inconsistencies. By using rules to match transactions with the acquirer most likely to approve them, a merchant can increase successful captures.
This involves categorising transactions into groups that align with the strengths of different processing partners, ensuring that technical or risk-based refusals are minimised across the entire portfolio.
Mitigation of processing costs
Payment costs are rarely uniform across different card schemes or regions. Transaction rules allow for the prioritisation of routes with lower scheme fees or interchange costs.
By identifying local cards and routing them through domestic acquirers, businesses avoid the higher costs associated with cross-border processing. This systematic approach ensures that the most cost-effective path is chosen for every individual line item processed by the gateway.
Compliance and risk management
Regulatory environments like PSD2 require specific authentication behaviours. Transaction rules provide the mechanism to enforce these requirements without applying them universally.
Merchants can automate the exclusion of specific high-risk jurisdictions or restrict certain MCCs if they fall outside of risk appetite. This reduces the burden on manual review teams and protects the merchant from excessive chargeback rates or potential penalties from card schemes.
Casos de uso
Cross-border retail
A merchant selling globally can use rules to route payments through local acquirers in the European Union to capitalise on lower interchange rates, while using a different partner for North American traffic to optimise authorisation.
SCA exemptions
A subscription service can apply rules that automatically request exemptions for low-value recurring transactions, ensuring that customers are not interrupted by unnecessary 3-D Secure challenges that could lead to churn.
High-risk mitigation
An electronics retailer can implement rules that trigger 3DS for all first-time buyers whose shipping and billing addresses do not match, while allowing returning customers to proceed through a faster checkout.
Cost-based routing
A high-volume airline can direct all premium card transactions to a specific provider with a better blended-pricing structure for corporate cards, reducing the total fee burden on high-interchange payments.
En cifras
Typical uplift observed in the industry when transitioning from static routing to a multi-acquirer setup using smart transaction rules.
Standard range of savings reported by merchants who implement cost-based routing for cross-border and regional domestic transactions.
The expected performance threshold for modern payment orchestration engines when executing complex conditional logic at the gateway level.
Términos relacionados
Talk to our team about a live rollout on your acquiring stack.
Lo que obtienes con Reglas de transacción
- Define reglas basadas en el tipo de tarjeta, moneda o importe de la transacción.
- Dirige las transacciones a adquirentes específicos según el rendimiento o el costo.
- Implementa la autenticación 3DS selectivamente según el riesgo de la transacción.
- Rechaza automáticamente transacciones de países o IPs específicos.
- Establece lógica condicional para aprobación o rechazo basada en múltiples criterios.
- Prioriza el procesamiento de transacciones basado en el ID de comerciante o la línea de producto.
- Implement automated retries for soft declines by switching to secondary processing partners.
- Assign specific Merchant Identification Numbers for different product lines or business units dynamically.
- Filter transactions based on historical fraud data and internal blacklists at the gateway level.
- Apply specific currency conversion rules based on the cardholder's native currency and FX rates.
A short scoping call, then a written plan for your MIDs.
Preguntas sobre Reglas de transacción
¿Qué son las reglas de transacción en el procesamiento de pagos?
Las reglas de transacción son condiciones predefinidas que dictan cómo se manejan los intentos de pago individuales. Permiten a los comerciantes automatizar decisiones como aceptar, rechazar o enrutar transacciones basándose en varios atributos, optimizando el flujo de pago y gestionando el riesgo de manera efectiva.
¿Cómo mejoran las reglas de transacción las tasas de conversión?
Al aplicar reglas de transacción inteligentes, los comerciantes pueden optimizar el enrutamiento de pagos a adquirentes con mejores tasas de éxito para tipos de transacción o geografías específicas.
También pueden aplicar 3DS de forma selectiva, reduciendo la fricción para transacciones de bajo riesgo y mejorando la conversión global.
¿Se pueden combinar las reglas de transacción con otras herramientas de riesgo?
Sí, las reglas de transacción de Cardflo están diseñadas para integrarse perfectamente con otras herramientas de riesgo como las reglas de velocidad y la puntuación de riesgo.
Esta combinación permite una estrategia de prevención de fraude multicapa, donde las decisiones se toman basándose en una evaluación exhaustiva de todos los factores relevantes.
Is it possible to route transactions based on the cost of processing?
Merchants can use rules to direct transactions to whichever acquirer offers the best pricing for that specific card type.
For example, if one acquirer has a better rate for commercial cards, the rules engine can identify the card type via the BIN and route the transaction accordingly. This ensures that the merchant is not overpaying for interchange-plus or scheme fees on high-cost transactions.
Can I set different rules for recurring payments versus one-off transactions?
Payment systems distinguish between Merchant Initiated Transactions and Customer Initiated Transactions. Rules can be configured to apply different risk filters to these categories.
Typically, a CIT might require 3DS for the initial setup, while subsequent MITs are permitted through the ruleset without further customer intervention, provided the appropriate tokens and indicators are present in the request.
How does BIN-based routing work in a transaction ruleset?
BIN routing uses the first six to eight digits of a card number to identify the issuer and card product type. Rules are set to recognise these digits and apply specific logic.
For instance, a merchant might route all 'Gold' or 'Platinum' cards to an acquirer with higher approval thresholds for premium cards, or route all domestic debit cards to a local provider.
Características relacionadas.
¿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.