New in Chargebee: Explore Reveal and understand your payment performance end-to-end.Try Now
Docschargebee docs
HomeBillingPaymentsRevRecGrowthReveal
Support

Product Updates

  • Release Notes

Payment Methods

  • Payment Methods Overview
  • Cards
  • Direct Debit
  • Bank Based Payments
  • Wallets
  • Vouchers
  • Articles and FAQ

Payment Gateways and Configuration

  • Payment Gateways Overview
  • Chargebee Test Gateway
  • Stripe
  • PayPal Payment Services
  • Chargebee Pay
  • Adyen
  • Authorize.net
  • Bambora (formerly Beanstream)
  • Bank of America
  • BluePay
  • BlueSnap
  • Braintree
  • Checkout.com
  • CyberSource
  • dLocal
  • EBANX
  • Ecentric
  • Elavon
  • E-xact Direct Integration
  • eWay Rapid
  • Global Payments
  • GoCardless
  • J.P. Morgan Mobility Payment Solutions
  • Metrics Global
  • Mollie
  • Moneris
  • Network Merchants Incorporated (NMI)
  • Nuvei
  • Orbital (Chase Paymentech)
  • Pay.com
  • Paymill
  • Paystack
  • Pin Payments
  • QuickBooks Payments
  • Razorpay
  • Sage Pay
  • Solidgate
  • Tempus
  • Twikey
  • Windcave
  • Worldline Online Payments(formerly Ingenico)
  • Worldpay
  • Articles and FAQ

Level 2/3 Data Support

  • Level 2/3 Data Support

Payment Optimization Engine

  • Overview
  • Defaults
  • Advanced Setup
  • Payment Method Display Rules
  • Verification Rules
  • Routing Rules

Dunning

  • Dunning
  • Articles and FAQ

Offline Checkout

  • Offline Checkout
  • Articles and FAQ

Transaction Sync & Invoice Mapping

  • Transaction Sync and Invoice Mapping

Fraud Management

  • Fraud Management

Error Handling

  • Errors with Root Cause and Troubleshooting

Payment Lifecycle Logs

  • Payment Intents
  • Transactions
  • Gateway Activity Logs
  • Gateway Webhook Logs
  • Articles and FAQ

Others

  • Reach (Merchant of Record)
  • Bulk Deletion of Payment Methods
  • Custom Payment Methods
  • Payment Initiator Parameter
  • PSD2 and Strong Customer Authentication
  • RBI e-Mandate
  • RBI Tokenization Regulations
  • Chargeback Management
  • Transaction Descriptors
  • Payment Preferences
  • Visa Trial Rules
  • Mastercard Trial Rules
  • Co-badged Card Compliance
  • Articles and FAQ
  1. Payments
  3. Payment Optimization Engine
  4. Routing Rules
  1. Payments
  3. Payment Optimization Engine
  4. Routing Rules

Advanced Routing Rules

This feature is currently a Private Beta release. Contact Chargebee Support to enable Advanced Routing Rules for your live and test sites.

Routing Rules, part of Advanced Setup in the Payment Optimization Engine, conditionally route transactions to specific gateways to optimize approval rates, cost efficiency, and acquiring strategy.

Benefits of Advanced Routing for your business:

  • Geography-Based Optimization Route transactions to regionally aligned gateways based on billing or shipping country to improve authorization rates without restructuring pricing or plans.

  • Customer Segment-Based Optimization Direct different customer segments (e.g., freemium vs. enterprise) to specific gateways to tailor processing strategy and service levels.

  • Payment Method-Based Optimization Route specific payment methods or APMs to specialized gateways to improve performance and operational efficiency.

  • Cost-Aware Routing Distribute traffic to manage cross-border fees, interchange exposure, or gateway pricing models more effectively.

These are just a few examples of how Advanced Routing can benefit your business. The engine is flexible and can be customized to meet your unique payment routing needs, ensuring optimal results.

Supported variables to set routing strategy:

  • Payment method
  • Customer location (Billing / Shipping address)
  • Checkout amount and currency
  • Product catalog / Plan in PC 1.0 and Item price in PC 2.0

Note

If you need more variables, submit a request for them here. We will consider them for our next iteration.

Configuring Routing Rules

Follow these steps to create a new verification rule:

  1. Go to the Routing Rules section.

  2. Click Create Rule.

    image

  3. Configure the rule on the Create Rule page:

    • Add the required conditions such as Payment method, Plan, Billing Country, Shipping Country, Invoice Amount, and Currency.
    • Select the Payment Gateway to be routed when these conditions match.
    • Enter a Rule Name.
    image

  4. Verify the rule settings and click Publish to activate the rule.

    image

  5. The Routing Rules home page will reflect the published rules.

image

Note

While evaluating rules, if none of the rules match, then the payment gateway configured at the Default Payment Method & Routing step will be used for routing.

Testing Routing Rules

Before deploying a rule, it's essential to test it to ensure it meets your requirements and behaves as expected.

Follow these steps to run a test:

  1. Navigate to the Routing page and click Run Test.
  2. Enter values that match the specific rule you want to test.
  3. Click Run Test to see the results.

If the expected rule appears on the Result page, congratulations! Your rule is correctly configured.

Example

Let's walk through an example:

Suppose you've created a rule with the ID rule_161t4tUbLxeqJ2E0, which states:

"If the invoice amount exceeds 100 euros, the Payment Method is iDEAL, and the currency is EUR, then use the Mollie payment gateway."

To test this rule:

  • Enter values matching these conditions.
  • Click Run Test.

If the correct routing rule appears in the results, great! Your rule is working as expected. If not, close the Test Routing Rule pop-up, review the rule configuration, and test again.

Routing Rules conditionally route transactions to specific gateways to optimize approval rates, cost efficiency, and acquiring strategy.

Multi-business entity sites

If your site uses multiple business entities, payment optimization settings can be managed at the site level or customized for a specific entity. In general:

  • Site-level changes apply to entities that inherit those settings.
  • Entity-level customization lets you define routing, defaults, and related rules for a single entity without affecting other entities.
  • You can revert an entity to follow the current site-level payment optimization settings when needed.

Note

Overriding inherited payment optimization rules for a business entity gives you a clear slate for that entity: site-level rules no longer apply for that entity until you define new ones. That change can affect how new and in-progress payments are routed and processed for that entity. Review open checkouts, scheduled charges, and recurring behavior before you override, and adjust rules promptly so you do not leave the entity without the routing or defaults you need.

Information

Exact screens and actions can vary slightly by Chargebee version and the features enabled for your account. If you do not see Payment optimization, Default Payment Methods & Routing, or entity controls, contact Chargebee Support.

Was this article helpful?