Transaction Routing Rules allow financial institutions to define how cross-border transactions should be processed. This functionality helps to:
Routing rules can be configured with different visibility levels:
These rules are visible to all end-users. They're ideal for sharing general knowledge that can help expedite payments.
Example: No payments to sanctioned countries (e.g., IRAN) will be processed.
Public rules improve transparency and reduce payment rejections by informing senders about restrictions in advance.
These rules are applied to requests of other financial institutions that use our system. When a bank attempts to route a transaction that violates these rules, they will receive a rejection.
Example: Preferred correspondent bank for USD payments.
These rules help financial institutions communicate specific requirements to other banks without exposing this information to end customers.
These rules are visible only to your institution. They're used internally when you route transactions.
Example: Route USD transactions to specific correspondent banks based on amount thresholds.
Private rules allow you to implement custom routing logic that remains confidential to your organization.