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 3DS authentication decision and the reason for that decision.
  • Default strategy selected
    Shows that the default recurring strategy was used. The system applies it to a recurring payment when no routing configuration matches the payment and sends the payment to the connector account of the initial payment. The event shows this connector account and the processing methods in the cascade, in their sequence.
  • Default strategy skipped
    Shows that the default recurring strategy cannot be used because the connector account of the initial payment does not meet one or more requirements. The event shows the connector account and the skip reason.
  • Fallback step selected
    Shows that a fallback step was selected after a previous attempt. The event shows the fallback trigger type and the parent step.
Hub To view the routing event log

  1. Go to Payments > Orders.
  2. Find an order that was processed through routing configuration and select it to go to the order details.
  3. Scroll down and click on Routing log.

Tracking routing provides visibility into routing decisions and step processing, including when and why steps are skipped during payment processing.

Step skip reason

  • SKIP_FORM_SUPPORT - form support is not available
  • SKIP_CONNECTOR_ACCOUNT_DEACTIVATED - connector account has been deactivated
  • SKIP_CONNECTOR_INTEGRATION_DEACTIVATED - connector integration has been deactivated
  • SKIP_CURRENCY_SUPPORT - currency is not supported
  • SKIP_CARD_BRAND_SUPPORT - card brand is not supported
  • SKIP_AUTH0_SUPPORT - Auth0 support is not available
  • SKIP_EXTERNAL_MPI_SUPPORT - external MPI support is not available
  • SKIP_COF_DPAN_SUPPORT - CoF DPAN support is not available
  • SKIP_COF_PAN_SUPPORT - CoF PAN support is not available
  • SKIP_MOTO_SUPPORT - MOTO support is not available
  • SKIP_NONSTANDARD_CURRENCY_SUPPORT - non-standard currency is not supported
  • SKIP_3DS_DISABLED - 3DS is turned off
  • SKIP_TRA_CONDITIONS_NOT_MET - TRA conditions are not met
  • SKIP_ZIP_CODE_MISSING - zip code is missing
  • SKIP_REASON_PSP_TOKEN_SUPPORT - connector account does not support PSP tokens
  • SKIP_REASON_NETWORK_TOKEN_RECURRING_SUPPORT - connector account does not support recurring payments with network tokens
  • SKIP_REASON_EXTERNAL_DPAN_SUPPORT - connector account does not support merchant-managed network tokens with external DPAN
  • SKIP_REASON_INCREMENTAL_AUTH_SUPPORT - payment uses estimated authorization and the connector integration does not support it
  • SKIP_REASON_MOTO_DATA_ORIGIN_WITH_COF_METHOD - payment has the MOTO data origin and no scheme transaction ID, so the Card-on-File method cannot be used
  • SKIP_REASON_3DS_CASCADE_RULES_VIOLATION - the previous step and this step both require 3DS, so the system cannot use the 3DS result of the previous step for this step
  • SKIP_REASON_CONNECTOR_ACCOUNT_MISMATCH - connector account of the step differs from the connector account of the initial payment, applies to recurring payments only
  • SKIP_REASON_DUPLICATE_OF_PREVIOUS_ATTEMPT - step has the same connector account, processing method, 3DS, and descriptor as the previous attempt, so the system does not send it again