Coming soon: Enhanced Routing with SEPA Instant Priority
We are pleased to announce significant enhancements to our EUR payment processing that will deliver faster settlement, greater routing control for your business, and improved end-consumer experience.
This is the first in a series of planned improvements where we will be extending these enhancements to other instant payment schemes in the future, further broadening your access to fast and efficient payment rails.
What's Changing
EUR payments to be routed first via SEPA Instant, with seamless automatic rerouting
From October 1st, our Intelligent Routing engine will automatically prioritize SEPA Instant as the first choice for EUR payments, providing instant settlement (≤10 seconds) with 24/7 availability. It will also automatically reroute payments from SEPA Instant to alternative schemes when it receives a reroutable rejection, such as scheme-specific restrictions or limitations.
By default, our system will prioritize network selection in the following order:
- SEPA Instant
- SEPA Credit Transfer
- T2
- Crossborder
This represents a change from our current default routing behavior, where SEPA Credit Transfer is prioritized due to broader network coverage and lower rejection risk. Currently, payments routed via SEPA Instant that result in rejection are not automatically rerouted when possible.
These changes, combined with wider adoption of SEPA Instant in the SEPA zone, mean you can benefit from using instant rails by default for most payments without significantly increasing rejection risk or manual handling, and without changing your existing setup.
New Advanced Routing Controls
In some cases, you may want to control exactly how a payment is routed. For example, routing via SEPA Instant first with T2 as fallback would offer a later cut-off time compared to SEPA Instant with SEPA Credit Transfer as fallback.
To give you this flexibility, we are enhancing our routing controls to allow you to override the default routing logic:
• Preferred Network: Setting the clearingNetwork field allows you to specify the first network that should be used. If the payment cannot be processed on this network, our system will automatically revert to the default logic. This allows you to specify a preferred network without risking payment failure.
• Prioritized Network List: Setting the new prioritizedClearingNetworks allows you to specify exactly which payment rails to use, in your preferred order. This option completely overrides our default logic, with no automatic fallback to other networks beyond what you specify, giving you full control over routing.
Important Notes
• No Action Required: This change is automatic and requires no configuration on your side. If you have previously chosen to opt out of some networks, these will remain disabled and skipped entirely.
Example Implementations
Use Case | Instruction | Routing Logic Applied | Notes |
|---|---|---|---|
I want to rely on Intelligent Routing and not have to think about routing logic | clearingNetwork: null prioritizedClearingNetworks: null | SEPA Inst → SEPA CT → T2 → Crossborder | Logic applied by default. Current logic prioritizes SEPA CT over SEPA Instant (unless you previously requested a configuration change) |
I prefer routing via SEPA Credit Transfer first | clearingNetwork: "SEPA" prioritizedClearingNetworks: null | SEPA CT → SEPA Inst → T2 → Crossborder | Default logic, but with SEPA CT moved to the top of the list. The current logic only attempts SEPA CT with no fallback. |
I prefer routing via T2 first | clearingNetwork: "T2" prioritizedClearingNetworks: null | T2 → SEPA Instant → SEPA CT → Crossborder | Default logic, but with T2 moved to the top of the list. The current logic only attempts T2 with no fallback. |
I want to route via SEPA Instant first, and then T2, to benefit from a later cut-off time compared to using SEPA Instant then SEPA CT | clearingNetwork: null prioritizedClearingNetworks: [“SEPAINST”, "T2"] | SEPA Inst → T2 | Overrides the default logic, and only attempts SEPA Inst first, then T2 |
I want to route via SEPA Instant only, and handle rejections myself | clearingNetwork: null prioritizedClearingNetworks: [“SEPAINST”] | SEPA Inst | Overrides the default logic, and only attempts SEPA Inst. Any rejection (inc. reroutable rejections) will fail the payment |