[
{
"title":"Testing",
"link":"https://docs.solidgate.com/payments/testing/",
"text":"Simulate payments to test your integration before launching in production.",
"imgSrc":"https://solidgate.com/wp-content/uploads/2022/06/icon-customizable.svg"
}
,
{
"title":"Create your payment form",
"link":"https://docs.solidgate.com/payments/integrate/payment-form/create-your-payment-form/",
"text":"Understand how to integrate the payment form into your product.",
"imgSrc":"https://solidgate.com/wp-content/uploads/2022/06/icon-payments.svg"
}
,
{
"title":"Billing",
"link":"https://docs.solidgate.com/billing/",
"text":"Smart billing solutions designed for diverse business models.",
"imgSrc":"https://solidgate.com/wp-content/uploads/2022/06/icon-global.svg"
}
]
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.
Expand all
Amount USD - represents the total amount of the order.
Bank - refers to the name of the bank associated with the transaction.
BIN - defines a list of BINs used for routing based on specific patterns.
BIN country - defines the country associated with the BIN.
Card brand - used for the transaction, such as Visa, Mastercard, or other supported brands.
Card type - specifies the type of card being used.
Country - specifies the country associated with the customer or transaction for geographic routing.
Currency - specifies the
Guide
Understand which currencies you can use for making payments.
currency
of the order.
Customer account ID - specifies a unique identifier assigned to the customer's account for tracking.
Customer email - specifies the email address associated with the customer for communication and transaction purposes.
Data origin - specifies the origin of the data used in the transaction.
External MPI - allows for the configuration of conditions based on the presence of external
Guide
Strengthen payment safety with 3D Secure support for transactions.
MPI
data.
Force 3DS - specifies whether 3D Secure authentication is forced during the transaction.
Fraud risk detected - specifies whether a fraud risk has been detected in the transaction.
Initiator origin - specifies the origin of the transaction initiator.
IP address - specifies the IP address of the device used to initiate the transaction.
Order amount - represents the total amount of the transaction in the original currency.
Payment method type - defines the type of payment method being used.
Traffic source - helps identify where the traffic is coming from.
Website - specifies the website where the transaction is originating from.
For the metadata rule, you can enter any metadata parameter that corresponds to its respective data type and value.
Equal - must exactly match the specified value.
Card brand = Visa
Greater than - must be greater than the specified value.
Amount > 100
Greater than or equal - must be greater than or equal to the specified value.
Amount ≥ 100
Less than - must be less than the specified value.
Amount < 100
Less than or equal - must be less than or equal to the specified value.
Amount ≤ 100
Not equal - must not match the specified value.
BIN country ≠ US
Not one of - must not match any value from a provided list.
Card type not in [Credit, Debit]
One of - must match any value from a provided list.
Website = one of [site1.com, site2.com]
Depending on the type of parameter, the available logic operators may vary.
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 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
Go to Orchestration > Routing configuration.
Click on Create routing configuration.
Select Payment method.
Choose Channel from the list.
Enter Title and optionally Description.
Click on Create.
Rule preset
To set the rule preset
Go to Orchestration > Routing configuration.
Find the needed ID routing configuration and click on it.
Click on Force 3DS preset and enable the needed preset conditions.
Click on ×.
No configuration exists for other presets.
Rules
To set rules
Go to Orchestration > Routing configuration.
Find the needed ID routing configuration and click on it.
Find the needed rule preset and click on +.
Click on New condition and name it.
Add Rule, Metadata rule or Rule group.
Click on Save.
To set rule
Click on Add rule and set:
Parameter
Logic operators
Value
Click on Save.
To set metadata rule
Click on Add metadata rule and set:
Data type
Parameter name
Logic operators
Value
Click on Save.
To set the rule group
Click on Add rule group:
Choose Rule or Metadata rule, or Rule group and set it.
Set logic operators.
Click on Save.
Splits
To set splits
Go to Orchestration > Routing configuration.
Find the needed ID routing configuration and click on it.
Find the needed rule and click on + Add splits.
Set % percentage for each group.
Segments
To configure the segments
Go to Orchestration > Routing configuration.
Find the needed ID routing configuration and click on it.
Find the needed split group and click on Configure segment.