Cross-border payments can open the door to financial crime. Country Limits help banks control where money goes — no detours, no grey zones.
Authorised fraud often ends with a payment sent abroad. A fraudster calls, poses as the bank or police, and urges the customer to move their money to a “secure account” — usually in another country. It sounds urgent. It feels legitimate. And once the payment’s gone, it’s difficult to recover.
Why it matters
Cross-border payments carry more risk — for fraud, AML, and reputational exposure. Reversals are harder. Monitoring is more complex. And compliance obligations are stricter.
Country Limits let you proactively block outbound payments to specific destinations — based on internal policy, risk appetite, or regulatory requirements. Customers can also manage their own destination list, adding an extra layer of control. It’s a clear, defensible way to reduce risk without disrupting everyday payments.
Why It Works
Country Limits apply a hard stop based on destination. You define the rules — by country, region, or corridor. Customers can also set their own preferences, choosing where they allow (or don’t allow) funds to be sent.
When a restricted destination is selected, you decide what happens next: block it, escalate it, or step it up. There’s no friction unless it’s needed — and a clear signal when it is.
Country Limits give you fine-grained control over where money can be sent — and where it can’t.
Block payments to specific countries or corridors
Enforce internal blacklists or regulatory watchlists
Apply rules across SEPA, SWIFT, and FX rails
Flag attempts as risk signals for fraud or compliance teams
Explore developer docs, API reference, and the demo bank.