Account & card restrictions.
Supported jurisdictions, spend limits, and restricted merchant categories on Vcc.io.
Last updated · 15 Nov 2026
Access is prohibited from OFAC/UN/EU comprehensively sanctioned jurisdictions: North Korea (DPRK), Iran, Syria, Cuba, Myanmar, and the Crimea, Donetsk, and Luhansk regions, as well as any sanctioned individual or entity.
Standard privacy VPNs are permitted for everyday account security, provided all transactions comply with our AML Policy, Terms of Service, and merchant rules.
This Restrictions document explains geographic, merchant-category, and usage limits that apply when you use Vcc.io wallets and virtual cards. It forms part of our Terms and Conditions and should be read with the Prohibitions, AML Policy, Privacy Policy, and Risk Disclosure.
1. Purpose and scope
1.1. These Restrictions describe (a) where card spend to merchants is generally supported, (b) jurisdictions and persons that may not onboard, (c) restricted merchant categories, and (d) other transactional limits.
1.2. Lists and parameters may change when required by law, card-network rules, or funding / card partners. The version published on this page applies at the time of use.
1.3. Three ideas should not be confused:
- Supported merchant jurisdictions — places where merchants may accept a Vcc.io card. This does not mean residents of that place can always open an account.
- Restricted onboarding jurisdictions — places whose residents or entities may be refused registration or continued service.
- Limited-service corridors — places where some funding rails (especially certain digital-asset rails) may be unavailable.
2. Supported merchant jurisdictions
2.1. Virtual cards issued through partner programs are intended for online spend where major networks are accepted. Merchant acceptance is never guaranteed (including ad platforms and SaaS vendors).
2.2. Partner BINs, acquirers, and networks may block individual merchants, countries, or MCC ranges without notice. Declines for geographic or category reasons are not a platform fee event and do not guarantee a refund from the merchant.
3. Restricted onboarding
3.1. We may refuse, suspend, or close accounts connected (by residence, incorporation, control, or beneficial ownership) to high-risk or sanctioned jurisdictions, or where partners prohibit service.
3.2. Sanctions, PEP, and partner screening can block onboarding or ongoing use even when a country is not listed here.
3.3. You must not use VPNs, proxies, or false identity data to evade geographic or eligibility controls.
4. Restricted merchant categories (MCCs)
4.1. Card spend is generally not permitted for categories that partners or networks treat as prohibited or high-risk. Typical blocked or tightly controlled categories include (non-exhaustive):
- Illegal goods or services, and anything that violates local law where you or the merchant operate
- Certain adult, gambling, or wagering merchants where partners disallow them
- Weapons, munitions, and related controlled goods
- Cryptocurrency ATMs / unlicensed money services where prohibited by the card program
- Cash-like or quasi-cash MCC patterns used to circumvent funding rules
- Card testing, enumeration, or synthetic authorization abuse
4.2. Exact MCC allow/deny lists are set by issuing partners and can change. A successful authorization in the past does not guarantee future acceptance.
5. Usage restrictions
5.1. Cards are for lawful online spend tied to funded balances. They are not revolving credit lines.
5.2. You may not use the service for money laundering, sanctions evasion, fraud, unauthorized account access, or resale that conceals the true end user when prohibited.
5.3. Velocity, amount, and corridor limits may apply per wallet, card, BIN, or funding rail.
6. Consequences of breach
We may freeze cards or wallets, reverse or hold settlements where partners require it, request information, share data with processors or authorities when legally required, and suspend or terminate accounts. See the Terms and Risk Disclosure.
7. Updates and contact
Material updates are posted on this page with a revised “Last update” date. Questions: contact form on Vcc.io or authenticated support. reference “Restrictions”.
Effective: 15 November 2026 · Vcc.io