Generate a CSV export of routing decisions for orders in a selected date range
The report lists routing decisions for orders in a selected period. Each row covers selected and skipped steps, 3DS decisions, and the connector account used.
Use it to investigate performance, debug processing, and confirm that configurations behave as expected. Unlike track routing configuration, this export does not return the route tree.
Use the
routing events
API v1 report for order-level routing data: configuration and version, route and step details, 3DS decisions, and the selected connector account.
Routing events data is unloaded using the created_at parameter by default, reflecting the most recent updates to the records.
Receive the report URL report_url in the response.
Download the report in CSV format using the report_id from the URL and authorization credentials.
Use the same
Guide
Get API credentials and open the API reference for authentication, signing, and endpoint details.
authorization credentials
with
publicKey
and
secretKey
to download the report.
Since the report is prepared asynchronously, it may take some time to become ready for download.
If the report is not ready, the API reference returns the corresponding status code:
200
- authentication failure. Double-check your access to the Solidgate API.
204
- report is not yet ready. Wait a little longer for it to be generated.
302
- redirect to a one-time S3 download report link.
404
- report was not found.
410
- report is unavailable, expired.
Please note that the report is only available for 30 days
from its generation date. After that period, it is no longer accessible.
To create a routing events report
Go to Reports and exports.
In the top-right corner, click on +Create report.
In the pop-up window, fill in the required details:
Select the Routing events report type
Select one or multiple channels
Define a date range of up to 36 days
Optionally, modify the auto-generated file name
Click on Create. Once confirmed, reports are generated for each selected channel.
Click on Download to save and access the report.
Routing events report properties
Expand all
Description
Order identifier defined by the merchant.
Example
923bb4e6-4a5f-41ec-81fb-28eb8a152e55
Description
Order identifier generated by Solidgate.
Example
psp_order_1samrzwv8my
Description
Payment identifier returned by the external provider.
Empty when connector_id is solidgate_acquiring.
Example
charge_64789DFS3827563HGF56
Description
Transaction identifier returned by the external provider.
Empty when connector_id is solidgate_acquiring.
Example
5019d00bb70f82cd42f6bc654cbdfcbd63a9b5b1dbd6a
Description
Transaction status reported by the provider for the routing step.
created – the transaction has been created
processing – the transaction is being processed
verify – the transaction is awaiting verification, such as 3DS
Identifier of the routing configuration applied to the order.
Example
cfg_01HV9Z2K3M4N5P6Q7R8S9T0U1V
Description
Identifier of the specific configuration version that processed the order.
Example
cfgv_01HV9Z2K3M4N5P6Q7R8S9T0U1V
Description
Human-readable name of the routing configuration.
Example
EU cards routing
Description
Sequence number of the configuration version applied to the order.
Example
5
Description
Payment method group the routing configuration applies to.
card
digital_wallet
merchant_managed_network_token
solidgate_token
Example
card
Description
Identifier of the route within the configuration version.
Example
rt_01HV9Z2K3M4N5P6Q7R8S9T0U1V
Description
Human-readable name of the route.
Example
Visa EU
Description
Stable analytical route ID.
Persists across versions until the route changes, then regenerates. For merchant analytics over time.
Example
art_01HV9Z2K3M4N5P6Q7R8S9T0U1V
Description
Indicates whether the order matched the Default branch of the rule preset.
Example
false
Description
Indicates whether the recurring payment was processed using the default recurring routing strategy.
Routing sets this flag when it applies the Default Recurring Strategy configured on the Connector Account instead of a matched token configuration route.
block_payments – the route blocks matching payments
force_3ds – the route forces 3DS authentication
google_pay_pan_only – the route applies to Google Pay PAN payments only
reroute_force_3ds – the route reroutes to another connector account with 3DS forced
reroute_any – the route reroutes to another connector account without forcing 3DS
any – the route applies to payments not covered by other presets
Example
force_3ds
Description
Sequence number of the step within the route, starting with 1 for the primary step.
Example
1
Description
Identifier of the routing step.
Example
stp_01HV9Z2K3M4N5P6Q7R8S9T0U1V
Description
Stable analytical step ID.
Persists across versions until the step changes, then regenerates. For merchant analytics over time.
Example
ars_01HV9Z2K3M4N5P6Q7R8S9T0U1V
Description
Stable analytical ID for a split group.
Persists across versions until the cascade changes, then regenerates. For merchant analytics over time.
Example
arc_01HV9Z2K3M4N5P6Q7R8S9T0U1V
Description
Indicates whether the route splits segment traffic automatically. Smart routes redistribute traffic across segments instead of using fixed percentages.
Example
true
Description
Reason a routing step was skipped. For the full list of values, see the step skip reason reference above.
Empty when the step was selected for processing.
Example
SKIP_CONNECTOR_ACCOUNT_DEACTIVATED
Description
Indicates whether 3DS authentication was forced for the step.
Example
true
Description
Reason 3DS was forced. Values follow the Force 3DS preset branches:
antifraud
sca
client
external_mpi
maestro_card_brand
custom_rule
Empty when is_force_3ds is false.
Example
sca-regulation
Description
Exemption applied to 3DS authentication, such as a low-value or TRA SCA exemption.
Empty when no exemption was applied.
Example
low-value
Description
Processing method applied at the step.
card – card payment
network_token – network token payment
psp_token – PSP token payment
cof – card-on-file payment
moto – mail order or telephone order (MOTO) payment