The countries we can't touch — and why?
| swype |
|
COMPLIANCE • PARTNERS & MERCHANTS
Restricted & sanctioned countries policySwype maintains a list of restricted jurisdictions in line with international sanctions regimes. This article explains the scope, the rationale, and what it means for your integration. |
|
|
AUDIENCE Partners & Merchants |
SCOPE Sanctions & trade controls |
LAST REVIEWED June 2026 |
Summary: Swype cannot onboard, process transactions for, or settle funds involving entities, cardholders, or end users located in or ordinarily resident in the jurisdictions listed below. This applies regardless of where your platform itself is incorporated.
| ① |
Why this policy exists |
As a card issuing and payments platform, Swype operates under international sanctions frameworks, including those administered by OFAC (U.S. Treasury), the EU, and the UK. Onboarding or processing transactions connected to a restricted jurisdiction can expose Swype, our issuing partners, and your business to regulatory penalties — independent of intent. This list reflects our current risk posture and is reviewed on an ongoing basis as sanctions regimes evolve.
| ② |
Fully restricted jurisdictions |
Swype does not onboard merchants, partners, or cardholders connected to the following countries or territories under any circumstance:
| ● | Cuba |
| ● | Iran |
| ● | North Korea |
| ● | Ukraine — Crimea, Donetsk, and Luhansk regions specifically |
| ③ |
Comprehensive sectoral restrictions |
The following jurisdiction is subject to expansive sectoral and trade restrictions across multiple regulatory regimes. Onboarding requires heightened due diligence and is evaluated case-by-case where permitted at all:
| ● | Russia |
| ④ |
Elevated-risk jurisdictions |
These jurisdictions carry elevated sanctions, AML, or geopolitical risk. Onboarding partners, merchants, or end users connected to these regions is restricted by default and subject to enhanced compliance review:
|
|
| ⑤ |
What this means for your integration |
As a Swype partner or merchant, you're responsible for screening end users against this list during onboarding and on an ongoing basis. Specifically:
| ● | Do not onboard cardholders with a registered address, IP geolocation, or stated residency in a fully restricted jurisdiction |
| ● | Flag any onboarding application connected to an elevated-risk jurisdiction for manual compliance review before activation |
| ● | Report any existing cardholder who relocates to a restricted jurisdiction |
| ● | Do not attempt to circumvent geofencing or KYC checks on behalf of an end user located in a restricted jurisdiction |
|
Important This list is reviewed regularly and may change without prior notice as sanctions regimes are updated by OFAC, the EU, the UK, and other relevant bodies. Partners are responsible for checking this article periodically rather than relying on a cached copy. |
Need a compliance review for a specific case?
Our compliance team can review borderline onboarding cases involving elevated-risk jurisdictions.
Contact Compliance →