NEW 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.

For EUR, GBP, AUD, CHF, SEK, DKK, NOK and HUF (currencies, where we are directly connected to one or more clearings) payments, you can:

• Specify a list of payment rails using the serviceLevels property This means that our system will only attempt to process the payments using the rails specified, in the order of priority stated. If none of the networks in your list are available, the payment will be rejected rather than using other eligible rails.

Read more about this payment routing control option in the sections below.

Controlling the payment route

Occasionally, you may want to process payments only on specific rails, and exclude other available options. You can do that by setting the serviceLevels property, which accepts a list of payment rails 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 none of the networks in your list are available, the payment will be rejected rather than using other eligible rails.

💡

Use cases

A common use case for this feature is, if you want to ensure that a payment is executed via the instant rail, and prefer that we do not process it, if it cannot be executed via the instant rail.

Another common use case is if you need the payment to go out today, and it's past the batch clearing system's cut-off, but there is still some time before the RTGS system's cut-off time. In that case, you can ask us to try the instant rail, skip the batch, and try the RTGS system as the second option.

Feature availability

You can use the serviceLevels property to control payment routing and define the order in which rails should be attempted.

• The serviceLevels property is available via the Single payment and the Agency and Correspondent Banking endpoints.
• For bulk payments, the same values can be provided using field 29
• For payment instructions using the pain.001 and pacs.008 message types, you can use the service level (SvcLvl) tags. Note that for now, you can only provide one instance of the SvcLvl tag, meaning you can only specify one payment rail, when using one of these two endpoints.

Below you can find supported values:

• INST – Indicates instant processing (payments are routed via the instant rail)
• NURG – Indicates non-urgent processing (payments are routed via the batch clearing system)
• URGP – Indicates urgent processing (routed via RTGS system)

For example, if you instruct a EUR payment with service level as [INST] only, it will be routed via SEPA Instant. If SEPA Inst is not possible, the payment will be rejected.

The feature is available in the currencies:

📘

Note: For non-EUR currencies, we will only try the first value provided after INST. If the first value provided in the list is anything else than INST, then we will only try the first value provided.

Routing Control examples

Important note

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

Automatic Rerouting for SEPA Instant payments

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