EU CASP Sanctions and Coinbase Prime Transfer Restriction Map

Decision Matrix

Source Map

• Coinbase Help: EU Sanctions — Russian and Belarusian Crypto-Asset Service Providers (coinbase-eu-sanctions)
• Council of the European Union: 21st package of sanctions (eu-council-21st-sanctions)
• EUR-Lex: Council Regulation (EU) 2026/506 (eu-reg-2026-506)
• Coinbase Help: Your Coinbase MiCA Migration (coinbase-mica-migration)

Control Notes

1. Applicable account

Applicable account is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means Prime client Vault wallet held with CBLU. The useful action is to verify the Coinbase entity and wallet type. The unresolved edge is retail account treatment, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, applicable account should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material. The record can stay simple: the official source URL, the date checked, the product or network under review, and a non-secret note describing why the next step is acceptable. Screenshots should avoid balances, identity documents, API keys, recovery phrases, private keys, passphrases, verification codes and support-ticket private data.

2. Counterparty CASP

Counterparty CASP is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means Russian or Belarusian crypto-asset service provider. The useful action is to check destination before transfer. The unresolved edge is classification evidence, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, counterparty casp should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

3. Inbound deposit

Inbound deposit is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means asset arriving from a restricted CASP. The useful action is to expect block or holding-account treatment if flagged. The unresolved edge is case-specific handling, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, inbound deposit should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

4. Outbound withdrawal

Outbound withdrawal is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means asset sent toward a restricted CASP. The useful action is to read the notification before retrying. The unresolved edge is restriction subtype, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, outbound withdrawal should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

5. Holding account

Holding account is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means Coinbase-controlled account used for blocked funds. The useful action is to preserve email and case references. The unresolved edge is release condition, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, holding account should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

6. Rejected transfer

Rejected transfer is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means withdrawal does not proceed and funds remain accessible. The useful action is to choose a compliant destination. The unresolved edge is destination screening source, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, rejected transfer should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

7. EU instrument

EU instrument is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means Regulation 833/2014 and later amendments. The useful action is to cite legal basis separately from venue policy. The unresolved edge is future amendments, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, eu instrument should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

8. Third-country ban

Third-country ban is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means EU tool for crypto providers used by Russia. The useful action is to monitor named providers and jurisdictions. The unresolved edge is implementation scope, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, third-country ban should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

9. User communication

User communication is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means email or account-manager route. The useful action is to keep official notices. The unresolved edge is support timing, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

For an operator, user communication should be recorded before funds, account access, wallet recovery, API order flow, whitelist changes, cross-chain transfers or tokenized-asset decisions become material.

10. Stop rule

Stop rule is the part of the decision where the reader must turn a public source into an operating rule. In this package, it means when not to retry blindly. The useful action is to stop if sanction status or entity is unknown. The unresolved edge is private compliance facts, so this article does not convert that uncertainty into a promise, ranking, reward, approval, safety claim or future-availability claim.

Known Unknowns

• retail account treatment
• classification evidence
• case-specific handling
• restriction subtype
• release condition
• destination screening source
• future amendments
• implementation scope
• support timing
• private compliance facts

Practical Takeaway

The safest version of this article is the one that stays boring and exact. EU CASP sanctions now matter to exchange users as a transfer-control and custody-status question, not only as a policy headline. Coinbase says that, effective May 24, 2026, Coinbase Luxembourg S.A. must comply with EU restrictive measures prohibiting transactions involving Russian and Belarusian crypto-asset service providers for Coinbase Prime clients with Vault wallets held by CBLU. The help page says inbound deposits from those CASPs will be blocked and moved to a Coinbase-controlled holding account, while outbound withdrawals may be placed on hold or rejected depending on the restriction. EU Council material separately says the EU has expanded crypto-related transaction bans and introduced a possible full third-country ban for crypto-asset services used by Russia. The user decision is to verify destination status, entity, wallet custody and notification route before assuming a blocked or held transfer is a technical failure. The user outcome is a clearer next inspection step, not a promise that a platform, API, transfer route or tokenized asset will work under every future condition.