Routing
Get in touch
Sign in
Routing
Optimize the payment infrastructure, success rates, and risk metrics while reducing costs

Routing configurations enable the management of payment flows, ensure compliance, and optimize processing performance, all while maintaining flexibility and control over their payment infrastructure.

With a no-code, customizable platform, you can scale quickly to new geographies, improve payment conversion rates, and diversify risk.


Routing flow

Routing configuration is set up for a channel with payment method level. This allows operators to manage and optimize payment traffic across multiple payment methods, such as Cards and Digital wallets, Apple Pay and Google Pay.

Each channel corresponds to a product, website, or store. To process payments at the same time, one account can have several channels.


Routing components

Routing configurations consist of several components, each essential for directing and optimizing payment traffic.

  • Rule preset sets initial conditions, like blocking payments or enforcing Guide
    3D Secure (3DS) enhances online payment security by adding an extra authentication step for credit and debit card transactions.
    3DS.
  • Rules define how payments are routed based on parameters and logic operators.
  • Splits distribute payment traffic across connector accounts.
  • Segments configure the processing sequence for payments, including fallbacks.

Rule preset

Rule presets are evaluated before routing rules are applied, ensuring that specific criteria are met before proceeding with the transaction.

Presets are evaluated from top to bottom, with the first matching condition taking precedence over subsequent ones. Each configuration type has its own rule presets. Key condition:

  • Block payments
    Blocks certain payments.
    If triggered, the transaction is declined with the decline code 0.04 Payment processing unavailable.
  • Force 3DS
    Determines whether payment processing rules fall under force 3DS. This preset applies to all payments that antifraud system has identified as force 3DS, or provided force3ds true through the Solidgate API .
    • SCA regulation
      A European rule to reduce fraud in online and contactless payments.
    • Low-value SCA exemption
      Allows low-value transactions to skip SCA under PSD2.
    • TRA SCA exemption transaction handling
      Permits low-risk transactions to bypass SCA, reducing friction.
    • Non-3DS for MIT/MOTO
      3DS can often be bypassed or handled differently than standard online payments.
  • Other PAN only
    Specifies that only payments involving other PANs are allowed.
  • All other payments
    Applies to all payments not otherwise categorized by the specific routing presets.

For the Digital wallets payment method, Force 3DS with Other PAN only is included in the Google Pay PAN only preset. This ensures that transactions are routed and processed only for Google Pay PANs with 3DS enforcement.

Each rule preset, except Block payments, includes a Default branch that must be completed. You cannot add rules to the Default branch, as it serves as the base setting. You can configure other branches as needed.


Rules

Routing rules are the core logic that defines how payments are routed through different payment processors (PSPs). These rules consist of parameters and values that can be combined using logical operators.

Rules condition:

  • Can be as simple or complex as necessary, with condition nesting supported up to 3 levels.
  • Work top-down by priority, meaning that if a payment matches the first rule, it follows that path, and further rules are not checked.
    Similarly, conditions within a rule operate in the same way.

Splits

Splits define how payment traffic is distributed across different connector accounts.

  • Each split is assigned a percentage of traffic, and each group block of rules requires a separate split.
  • Sum of all segments in a group must equal 100%.
  • Maximum of 20 groups can be defined for a single rule.

Segments

Configuring a segment involves setting up the sequence of steps for a split group.

The list of available options depends on the connector itself, making it flexible and adaptable to the specific configuration of the connector account. Additionally, display whether the connector account supports the acceptance of External MPI Data.

  • A maximum of 5 steps can be defined in a group.
    They can be the same, but the features and descriptors must differ.
  • Fallbacks are not available on the Force 3DS branch.

For each segment, it is essential to ensure that the features/descriptors vary, even if the same connector account is used multiple times.

Steps allow fallback routing, directing traffic to MIDs when the initial route fails. Each step level is evaluated in sequence, providing up to 5 levels of fallback routing. Use steps for retry strategies after declines or failures to ensure continuous payment processing.

Stop error codes prevent transactions from proceeding to the next step. These errors indicate fundamental issues with the card, account, or transaction that cannot be resolved by routing to an alternative processor.

Attempting retries would result in the same failure regardless of the payment gateway used, while unnecessarily increasing processing costs and delaying the final response to the customer.

  • Guide
    The order has exceeded its validity period and can no longer be processed.
    0.02 Order expired
  • Guide
    The Card Verification Value (CVV2) provided does not match the card's security code.
    2.06 Invalid CVV2 code
  • Guide
    The card number entered is not valid or does not exist.
    2.08 Invalid card number
  • Guide
    The expiration date provided for the card is incorrect or the card has expired.
    2.09 Invalid expiration date
  • Guide
    The cardholder does not have sufficient funds available to complete the transaction.
    3.02 Insufficient funds
  • Guide
    The account associated with the card has been closed and cannot be used for transactions.
    3.12 Closed user account
  • Guide
    The payment card being used is listed on a security blocked list, often due to prior suspicious or fraudulent activities.
    4.01 Card is on black list
  • Guide
    The card in use has been reported as stolen, all transactions are restricted.
    4.02 Stolen card
  • Guide
    The card has been reported as lost and is blocked from processing any transactions.
    4.04 Lost card
  • Guide
    The transaction was blocked by a trusted antifraud system due to suspicious activity or high-risk indicators.
    4.07 Trusted antifraud system

Configure routing

Routing configurations manage payment traffic based on merchant routing rules. A version represents the state of a routing configuration, where Draft indicates it is in development or testing, and Live means it has been published and is in use.

Managing versions is crucial for ensuring smooth updates, preventing disruptions, and maintaining control over the routing setup as configurations evolve through different stages. Key routing statuses for:

  • Configuration
    • Inactive a configuration that is not currently in use.
    • Active a configuration that has been published and is active.
  • Version
    • Draft a configuration under development or testing.
    • Live a configuration that has been published and is active.

When creating routing configurations, operators can view, edit, and manage them for each channel and payment method.

Configurations are versioned, and each version can either be Draft or Live . When initially created, the configuration is set to Inactive .

Once tested and ready, the configuration status can be set to Active and published to production, changing the configuration version to Live .

To configure a route configuration

  1. Go to Orchestration > Routing configuration.
  2. Click on Create routing configuration.
  3. Select Payment method.
  4. Choose Channel from the list.
  5. Enter Title and optionally Description.
  6. Click on Create.

Rule preset

To set the rule preset

  1. Go to Orchestration > Routing configuration.
  2. Find the needed ID routing configuration and click on it.
  3. Click on Force 3DS preset and enable the needed preset conditions.
  4. Click on ×.
No configuration exists for other presets.

Rules

To set rules

  1. Go to Orchestration > Routing configuration.
  2. Find the needed ID routing configuration and click on it.
  3. Find the needed rule preset and click on +.
  4. Click on New condition and name it.
  5. Add Rule, Metadata rule or Rule group.
  6. Click on Save.
To set rule

  1. Click on Add rule and set:
    • Parameter
    • Logic operators
    • Value
  2. Click on Save.
To set metadata rule

  1. Click on Add metadata rule and set:
    • Data type
    • Parameter name
    • Logic operators
    • Value
  2. Click on Save.
To set the rule group

  1. Click on Add rule group:
    • Choose Rule or Metadata rule, or Rule group and set it.
    • Set logic operators.
  2. Click on Save.

Splits

To set splits

  1. Go to Orchestration > Routing configuration.
  2. Find the needed ID routing configuration and click on it.
  3. Find the needed rule and click on + Add splits.
  4. Set % percentage for each group.

Segments

To configure the segments

  1. Go to Orchestration > Routing configuration.
  2. Find the needed ID routing configuration and click on it.
  3. Find the needed split group and click on Configure segment.
  4. Select Connector, Account, and Descriptor.
  5. Set additional settings.
  6. Click on Save.

Looking for help? Contact us
Stay informed with Changelog