Payment Routing Controls

While our default routing logic handles most scenarios automatically, for some currencies you can specify your preferred payment rail when needed, overriding the default logic and giving you full control over how your payments are processed.

The followign controls are currently only available for EUR payments.

Scheme Selection Override

1. Preferred Clearing Network

This option allows you to specify a preferred rail, but not at the expense of processing the payment if the selected rail is not available.

We will prioritize the rail you specify, but if it is not available, we will use the default routing logic to select from other eligible rails. You can set the clearingNetwork values to the following values:

• SEPAINST: Attempts SEPA Instant Credit Transfer first
• SEPA: Attempts SEPA Credit Transfer first
• T2: Attempts T2 (Target2) first (note: specifying T2 is not available if instructing via pacs.008)

For example, if a EUR payment with a scheme selection override value set to SEPAINST and that rail is not available, the system will then prioritize SEPA (SEPA Credit Transfer), then T2 (Target2), then correspondent bank from the remaining eligible rails.

This feature is available by setting the clearingNetwork property in the single and bulk API endpoints, as well as ISO 20022 pain.001 and pacs.008 messages. See the API Reference for more details.

Possible values and their routing logic

2. Prioritized Clearing Network List

Occasionally you may want to process payments only on specific rails, and exclude other available options. You can do that by setting the PrioritizedClearingNetworks property, which accepts a list of clearing networks to try, in the order of priority.

Our system will only attempt to process the payments using the rails specified, in the order of priority stated. If all networks in your list are not available, the payment will be rejected rather than using other eligible rails.

For example, you might specify ["SEPAINST", "T2"] for a payment with a EUR amount.

This means our system will:

• Try SEPA Instant first
• If that rail is not available, try T2
• If T2 is not available, reject the payment (the system will not use SEPA Credit Transfer or correspondent bank)

This property is available in the single and bulk API endpoints, as well as ISO 20022 pain.001 and pacs.008 messages. See the API Reference for more details.

Note: The availability of override options depends on your client ID configuration, the specific payment details and your contractual agreement.

Example values and their routing logic

Note: if you set both clearingNetwork and prioritizedClearingNetworks, the first value set in prioritizedClearingNetworks must match the value set in clearingNetwork

Important note

Certain payments may continue to follow alternative routing paths based on various factors, including compliance requirements (such as payments requiring sanction screening), specific payment parameters (including FX transactions), and other operational considerations.

Retry and Rerouting for SEPA Instant payments

For SEPA Instant payments specifically, we also support Automatic Retry & Rerouting.