Manage routing in Hub to control payment paths, increase approval rates, and reduce operational risk, while ensuring auditability and the ability to rollback changes.
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
.
- 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.
To copy a route configuration
- Find the routing configuration you need and click on Copy routing configuration.
- In the duplicate configuration modal window, specify the required information:
- Select Payment method enabled and set according to the chosen configuration.
- Choose Channel from the list.
- Enter Title and optionally Description.
- Select Configuration version of the configuration to copy.
- Click on Duplicate.
Rule preset
- Go to Orchestration > Routing configuration.
- Find the routing configuration ID you need and click on it.
- Click on Force 3DS preset and enable the required preset conditions.
- Click on ×.
Rules
- Go to Orchestration > Routing configuration.
- Find the routing configuration ID you need and click on it.
- Find the rule preset you need and click on +.
- Click on New condition and name it.
- Add Rule, Metadata rule or Rule group.
- Click on Save.
- Click on Add rule and set:
- Parameter
- Logic operators
- Value
- Click on Save.
- Click on Add metadata rule and set:
- Data type
- Parameter name
- Logic operators
- Value
- Click on Save.
- Click on Add rule group:
- Choose Rule or Metadata rule, or Rule group and set it.
- Set logic operators.
- Click on Save.
Splits
- Go to Orchestration > Routing configuration.
- Find the routing configuration ID you need and click on it.
- Find the rule you need and click on + Add splits.
- Set % percentage for each group.
Segments
- Go to Orchestration > Routing configuration.
- Find the routing configuration ID you need and click on it.
- Find the split group you need and click on Configure segment.
- Select Connector, Account, and Descriptor.
- Set additional settings.
- Click on Save.
View routing
You can search, view, and edit routing configurations and related entities directly from the configuration pages. The search supports the following entity types:
- Configuration ID
Unique identifier for a routing configuration. - Configuration version ID
Identifier for a specific version of a configuration. - Route ID
Unique identifier for a route. - Step ID
Unique identifier for a routing step.
These entities can also be retrieved from the routing log.
- Go to Orchestration > Routing configuration.
- Navigate to a configuration list page.
- Use the search routing entity list to enter one of the options from the list on the right.
- Configuration - Opens the latest published version of the configuration in a new window.
- Configuration version - Opens that specific version in a new window.
- Route - Opens the version containing that route in a new window.
The route is centered and highlighted for easy identification. - Step - Opens the version containing that step in a new window.
The step is displayed in the drawer and highlighted.
- Go to Orchestration > Routing configuration.
- Find the routing configuration ID you need and click on it.
- Navigate to a specific configuration version page.
- Use the search routing entity list to enter one of the options from the list on the right.
- Configuration version - If the searched version matches the current version, it opens here and highlights.
If it is a different version, it opens in a new window and highlights. - Route - If the route is in the current version, it opens here, centers, and highlights the route.
If the route is in a different version, it opens that version in a new window, centers, and highlights the route. - Step - If the step is in the current version, it opens here, shows it in the drawer, and highlights it.
If the step is in a different version, it opens that version in a new window, shows it in the drawer, and highlights it.
Track routing
Routing event log provides detailed visibility into the sequence of actions that occurred with a specific order processed. It displays the complete routing journey, helping you understand how each transaction was processed and troubleshoot any issues. The routing event log shows the following event types:
- Step skipped
Indicates when a routing step was skipped, along with the reason for skipping. - Step selected
Shows which routing step was selected for processing. - Payment blocked
Displays when a payment was blocked, if blocking rules are configured. - 3DS decision
Shows the Guide
Boost payment security while protecting customer transactions with 3D Secure support. 3DS authentication decision and the reason for that decision.
- Go to Payments > Orders.
- Find an order that was processed through routing configuration and select it to go to the order details.
- Scroll down and click on the Routing log.
Tracking routing provides visibility into routing decisions and step processing, including when and why steps are skipped during payment processing.
