Transaction rules
Transaction rule configuration provides merchants with precise controls to accept, decline or reroute payments based on static data points. Payment operations teams use transaction attribute filtering to evaluate individual purchases against specific country, currency and card-level parameters before acquirer submission.
- Category
- Risk
- Capabilities
- 6
- Available on
- All plans
Payment routing specialists require precise control over which individual purchases reach an acquirer partner. Static payment data like country codes, currency types and card issuer details dictate whether a purchase meets a merchant's acceptance criteria. Sending ineligible payments to the wrong partner creates unnecessary processing costs and increases decline rates.
Cardflo provides the orchestration logic to evaluate each purchase against predefined transaction rules. The platform inspects static data fields to trigger automated routing decisions or immediate blocks based on exact value thresholds, currency mismatches or specific bank identification numbers, keeping ineligible volume away from the payment network.
Routing payments or triggering 3DS based on card type optimises global performance. By carefully setting risk parameters, merchants can enhance payment flow efficiency across all acquirer partners.
Transaction rules overview
Merchants configure exact parameters for incoming volume using static data evaluation rather than complex scoring algorithms or time-based limits, which are managed through dedicated risk rules and velocity rules configurations. By setting up strict BIN blocking rules and precise transaction value limits, payment operations teams stop specific types of volume at the gateway level.
The orchestration platform reads the incoming payload, identifying the card scheme, the issuer country and the requested currency. If the static attributes conflict with the merchant's accepted profile, the platform issues an immediate block before attempting authorisation.
For eligible payments, the platform applies payment routing constraints to direct the transaction to the most suitable acquirer partner for that specific country or card type. This keeps processing efficient and ensures acquirers only receive the traffic profiles they expect to approve.
How transaction rules works
Static data evaluation
The gateway reads the incoming checkout payload, identifying fixed data points such as the card number, order value and IP address. The orchestration platform compares these static attributes against the merchant's active rule set, bypassing any need for historical profiling. Payments matching a strict decline rule receive an immediate rejection code, preventing the transaction from reaching the acquirer network and incurring processing fees.
Value limit enforcement
Payment routing teams define exact transaction value limits for specific card types or payment methods. When a purchase exceeds the maximum configured threshold for a specific currency, the platform immediately intervenes. The system can either block the transaction entirely or apply payment routing constraints that direct the high-value payload to an acquirer partner equipped to handle large ticket sizes.
Card type restriction
The platform matches incoming card numbers against global identification databases to determine the issuing bank and card product. Merchants use BIN blocking rules to filter out specific card categories, such as prepaid debit cards or commercial purchasing cards, which often carry higher interchange fees or present specific scheme liabilities. The gateway halts these payments at the checkout stage.
Why transaction rules matters
Reduced gateway processing fees
Sending predictably ineligible volume to acquirer partners wastes resources and accumulates transaction fees for declined authorisations. By implementing strict transaction attribute filtering at the gateway level, merchants stop unwanted payments before submission. This drops the overall processing cost and keeps the merchant's authorisation ratios healthy across their entire acquirer partner network.
Precise geographic compliance
Regulated merchants must restrict services to approved jurisdictions to maintain their operating licences. Country-specific payment rules allow compliance teams to enforce geographic boundaries accurately. If a payment originates from an IP address or card issuer outside the approved region, the platform blocks the transaction instantly, preventing regulatory breaches and scheme penalties.
Regulatory notes for transaction rules
Card scheme geographic restrictions
Visa and Mastercard enforce strict cross-border acquiring rules that require merchants to process payments within specific regional boundaries.
Attempting to process volume outside a permitted territory without the correct entity setup leads to substantial scheme fines and risks the immediate termination of the merchant's processing facilities.
Country-specific payment rules provide a technical safeguard against these scheme violations. By configuring strict geographic blocks, merchants ensure that their acquirer partners never receive payment payloads that violate cross-border regulations, maintaining strict compliance with the local operating guidelines defined by the major card networks.
Operating licence restrictions
Digital merchants operating in regulated sectors, such as financial services or online gaming, hold specific licences that dictate exactly where they can accept customers.
Processing a payment from an unregulated jurisdiction breaches the core terms of these regulatory agreements, exposing the business to severe legal consequences.
Transaction attribute filtering enables compliance teams to map their exact regulatory footprints into the payment gateway.
The platform blocks IP addresses and card issuer codes originating from prohibited territories at the point of checkout, ensuring the merchant only accepts funds from fully verified and legally permitted jurisdictions.
Transaction rules use cases
Wholesale order value ceilings
Trade wholesalers need to prevent exceptionally large card orders from reaching a standard MID when pallet quantities push the transaction above an approved value ceiling. Cardflo applies amount-based rules that decline the payment or route eligible commercial card transactions to a suitable acquirer partner configuration.
Licensed territory payment blocks
Regulated operators must reject card payments where the billing country, issuing country or BIN country falls outside territories covered by their licence. Cardflo filters these static attributes before authorisation and sends only permitted transactions to the acquirer partner network, supporting territory-specific acceptance policies.
AOV filters for subscription boxes
Equipment hire operators may exclude prepaid cards because available balances can be insufficient when deposits and final damage charges are submitted separately. Cardflo identifies configured prepaid BIN ranges at checkout and declines those instruments while allowing eligible debit and credit cards to follow the relevant routing rule.
MID currency acceptance controls
Retailers operating separate sterling and euro MIDs need to stop unsupported currencies reaching an acquirer partner configuration intended for domestic settlement. Cardflo matches the transaction currency against permitted values, declining incompatible payloads or directing accepted GBP and EUR payments to the corresponding configured route.
Transaction rules by the numbers
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.
Methodology: these figures are illustrative ranges drawn from published industry data and observed merchant cohorts, not guarantees. Actual results depend on your risk profile, card mix, geography and acquiring setup, and are confirmed only in your own pricing and approval terms.
Related terms
Talk to our team about a live rollout across our acquirer partners' rails.
What you get with Transaction rules
- Restrict specific issuer regions using country-specific payment rules to maintain compliance with regional operating licences.
- Implement strict BIN blocking rules to stop known prepaid cards or corporate cards from completing checkout.
- Configure transaction value limits that force higher-value purchases to route through premium acquirer partners automatically.
- Apply currency-specific constraints that drop payment requests attempting to process in unsupported fiat denominations.
- Filter payments based on missing billing address information before the payload reaches the acquirer network.
- Isolate purchases originating from specific IP ranges to ensure compliance with geographic restriction policies.
A short scoping call, then a written plan for your MIDs.
Questions about Transaction rules
How does the gateway distinguish between prepaid and credit cards for block rules?
The gateway identifies the card type by referencing the Bank Identification Number during the initial routing phase. As the customer enters their payment details, the orchestration platform queries a global BIN database to verify the issuing bank, the card brand and the specific funding type.
If the merchant has configured BIN blocking rules for prepaid or virtual cards, the platform reads this static data and drops the transaction payload before attempting to contact the acquirer partner. This prevents unwanted funding sources from entering the processing flow.
Can merchants apply different transaction value limits for different currencies?
Yes, payment operations teams establish distinct transaction value limits for each supported currency. A merchant might configure a maximum threshold of five thousand euros for SEPA transactions while restricting USD card payments to one thousand dollars.
The orchestration platform evaluates the requested currency in the checkout payload and applies the exact rule associated with that denomination. If a payment breaches the currency-specific limit, the platform either triggers a decline code or applies specific payment routing constraints to divert the transaction.
Does IP geolocation blocking override the card issuer country code?
The platform evaluates both data points independently based on the merchant's specific configuration. Finance teams can create country-specific payment rules that block a transaction if either the customer IP address or the card issuer country falls outside the permitted list.
Alternatively, merchants can mandate that both data points must match the same approved jurisdiction. This dual evaluation ensures strict adherence to regional compliance requirements without requiring complex historical profiling of the customer's previous behaviour.
How do static transaction blocks impact acquirer authorisation rates?
Stopping incompatible transactions at the gateway level directly improves a merchant's overall authorisation ratio with their acquirer partners. When merchants filter out out-of-region cards, unsupported currencies or unsupported BIN ranges, the acquirer only receives highly qualified traffic that aligns with their risk appetite.
This targeted approach prevents the acquirer from processing guaranteed declines, which protects the merchant's reputation within the acquirer partner network and ensures cleaner reporting data across the entire payment operation.
Related features.
Related guides.
See how Cardflo compares.
Ready to improve your payments setup?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.