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, allowing 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 a rule preset, rules with conditions, splits, and segments, each essential for directing and optimizing payment traffic.

• 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.

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 a Payment processing unavailable message and the decline code 0.04.
• Force 3DS
  Determines whether payment processing rules fall under Force3DS. This preset applies to all payments that antifraud system has identified as Force 3DS, or provided force3ds true through the Solidgate API Reference.
  • 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 Digital wallets payment method Force 3DS with the Other PAN only are included to the Google Pay PAN only preset, ensuring that transactions are routed and processed only for Google Pay PANs with 3DS enforcement.

For every rule preset, except Block payments, there is a Default branch that must be filled out. Rules cannot be filled in the Default branch, as that is its default purpose. Everything else is at your discretion.

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’s 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.

Create routing

Routing configurations manage payment traffic based on merchant routing rules. A version refers to the state of a routing configuration, with Draft indicating it is under development or testing, while Live means it has been published and is actively 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 status for:

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

Preset

Rules

Splits

Segments

---