D1 Sanctions
Sanctions is not yet covered for this jurisdiction in this report.
Oregon operates entirely within the federal BSA/CTA/FinCEN AML/CFT framework; it has no independent national AML statute.
Sanctions is not yet covered for this jurisdiction in this report.
Beneficial Ownership is not yet covered for this jurisdiction in this report.
Oregon's Department of Justice led a 46-state, $45 million settlement with Block, Inc. resolving allegations that Cash App misrepresented account-safety features and failed to deliver required fraud-protection and resolution services to users; Oregon's own share of the settlement is $3 million. The state explicitly framed the action as compensating for reduced enforcement capacity at the federal Consumer Financial Protection Bureau, a framing this brief treats as an assessed, high-confidence institutional signal rather than an isolated incident. Read through the enabler-jurisdiction lens, Oregon is not functioning as a facilitator of gaps in the financial system here — it is the enforcer stepping into a gap left by a receding federal counterpart, an important distinction for how this finding should inform any jurisdiction-risk assessment of Oregon itself.
This cycle's signal on Oregon's enabler-jurisdiction posture is otherwise limited to one structural indicator alongside the settlement itself: the 2025 creation of an Economic Justice Section within Oregon DOJ, explicitly positioned to bring further payments- or crypto-adjacent enforcement matters. No independent sweep of Oregon's broader enabler-jurisdiction exposure — beyond this settlement — was conducted this cycle, and that gap is carried forward rather than papered over. The overall signal is assessed as a genuine, if narrow, structural development rather than a one-off incident, consistent with a "watch" trajectory for this domain.
The Economic Justice Section's future case selection is the structural item to watch: whether it produces a sustained pattern of state-level backstop enforcement against payments and crypto firms, consistent with the Block settlement, or proves to be a one-off intervention, will determine whether Oregon's enabler-jurisdiction profile continues on its current watch trajectory or stabilizes. A broader independent enabler-jurisdiction sweep for Oregon, beyond the Block/Cash App settlement, remains an explicitly flagged gap for a future cycle.
Conflict Finance is not yet covered for this jurisdiction in this report.
Oregon's stayed enforcement action against Coinbase continues to anchor this cycle's crypto posture. The state's original complaint alleges the unregistered offer and sale of 31 tokens, including XRP, in violation of Oregon securities law. Removed to federal court, the case is presently stayed until March 16, 2026, with a joint status report due from the parties at that point. This assessed-confidence finding — corroborated by an Oregon Department of Justice press release at Tier 1, with the procedural docket detail sourced at Tier 2 — represents a genuine architecture-level divergence rather than an isolated incident: Oregon's securities-enforcement theory against a major digital-asset exchange runs directly counter to the federal Securities and Exchange Commission's current de-regulatory posture toward digital-asset platforms nationally. For any digital-asset firm serving Oregon residents, that divergence translates into continued state-specific compliance uncertainty until the stay resolves one way or the other.
Running alongside, rather than resolving, that enforcement tension is Oregon's 2025 enactment of UCC Article 12 via SB 167, which establishes legal recognition of digital assets as commercial-law collateral. This is a Tier-3-sourced finding this cycle, and it should be read as a distinct, enabling commercial-law instrument rather than as an indication of the state's substantive posture on token classification. Oregon has, in effect, built infrastructure making digital assets usable as collateral in commercial transactions at the same time state prosecutors pursue an unresolved securities theory against a major exchange operating in the state. These two postures illustrate a state financial-integrity posture that is simultaneously enabling of digital-asset commercial use and unresolved on digital-asset securities classification — a duality, rather than either fact read in isolation, that is analytically significant this cycle.
The single most consequential near-term development for Oregon's crypto posture is the outcome of the March 16, 2026 joint status report in State of Oregon v. Coinbase. A lifted stay moving the securities theory toward substantive resolution, a further extension preserving the present uncertainty, or a narrowing or dismissal of the underlying claims would each carry materially different implications for digital-asset platforms serving Oregon residents. A related, separately flagged item is Coinbase's own public-records suit against Governor Kotek, which could surface documents materially affecting the narrative around Oregon's broader crypto-policy posture; neither outcome is yet available, and both are carried forward as explicit gaps rather than resolved this cycle.
Compliance Technology & Active Defence is not yet covered for this jurisdiction in this report.
AML/CTF Regime is not yet covered for this jurisdiction in this report.
The Block/Cash App settlement centers on fraud-protection and resolution failures rather than a formal AML finding, but MLROs at payment platforms should note that state attorneys general are actively scrutinizing the adequacy of consumer-facing fraud controls, a category that often overlaps with suspicious-activity detection infrastructure.
Compliance functions serving Oregon residents face two live, distinct regulatory-change vectors this cycle: heightened multistate consumer-protection enforcement risk for payments apps, and continued classification uncertainty for platforms listing tokens named in the stayed Coinbase action.
Legal counsel should track the March 16, 2026 joint status report as the key event that will determine whether Oregon's securities theory against a broad token basket proceeds toward substantive ruling; the Block settlement itself is now resolved liability, but its explicit gap-filling framing may inform future state-AG litigation strategy.
The board should be aware that Oregon's overall risk direction this cycle is assessed as increasing, driven by active enforcement rather than passive enablement, with reputational and financial exposure concentrated in payments-app conduct and digital-asset securities classification.
CTOs at digital-asset firms should treat Oregon's commercial-law recognition of digital assets as collateral (SB 167) as a distinct, enabling infrastructure layer separate from the unresolved question of whether specific tokens, including XRP, are securities under the state's stayed Coinbase theory.
Risk functions should treat the newly established Economic Justice Section as a forward-looking exposure-concentration signal for payments and crypto firms operating in Oregon, alongside the unresolved Coinbase litigation as a live classification-risk driver.
Operations teams at consumer payment platforms should note that the settlement centered on a gap between marketed account-safety representations and actual fraud-resolution performance, a control area subject to heightened state-level scrutiny.
Internal audit should note that the settlement's findings on fraud-protection control gaps, combined with a newly resourced state enforcement section, suggest documented control-testing scope for consumer-payment platforms operating in Oregon should be revisited.
Oregon-led multistate settlement over payments-app fraud-protection failures carries AML-adjacent control implications for consumer-facing payment platforms.
Oregon is simultaneously tightening payments-consumer-protection enforcement and maintaining an unresolved state-level securities theory against a major crypto exchange.
Oregon's stayed Coinbase securities action and the Block/Cash App settlement both carry active liability-trajectory implications pending a March 2026 status report.
Oregon's dual enforcement posture — consumer-payments backstop and unresolved crypto-securities theory — represents rising, not stable, state-level financial-crime-adjacent exposure.
Oregon's UCC Article 12 collateral framework and its unresolved token-classification litigation create a bifurcated technical-architecture posture for digital-asset platforms.
Oregon's risk profile this cycle is assessed as increasing, with a mixed structural-episodic character spanning payments enforcement and crypto-securities litigation.
Fraud-resolution and account-safety control adequacy is the operational focal point arising from the Block/Cash App settlement.
The Block/Cash App settlement and the new Economic Justice Section both point to an evolving state-level control-testing and evidence-documentation expectation.
As the AMLA Regulation (Reg (EU) 2024/1620) transitions cross-border obliged entities from purely national AML supervision toward direct or indirect EU-level supervision, alongside the directly-applicable AMLR (Reg (EU) 2024/1624) and per-state transposition of the sixth AML Directive, illustrative orientation suggests evasion strategies could shift toward jurisdictions and entity structures that fall outside AMLA's initial direct-supervision perimeter, potentially increasing reliance on non-EEA correspondent and payment relationships of the kind that structurally resemble this cycle's Oregon findings, where state-level enforcement has substituted for contracting federal oversight. This is an illustrative structural sketch orienting analysis toward the EU supervisory transition; it does not draw on any Oregon claim as evidence of EU AML Package interaction and is not an assessment of Oregon-specific risk.
Illustrative scenario for analytical orientation only. Not compliance advice, not a prediction, and not a statement of observed fact.
| Tracker | Status | Note |
|---|---|---|
| T1 · Russian Sanctions-Evasion Architecture | stable | No material change found with an Oregon nexus this cycle. |
| T2 · EU AML Package / AMLA | no_change | Not applicable at the US-OR subnational level. |
| T3 · FATF Grey List | no_change | No US-OR-specific mutual-evaluation or grey-list movement; FATF status is set at the US federal level. |
| T4 · Beneficial-Ownership Register Status | no_change | BO registry policy is federally administered; no Oregon-specific variance identified. |
| T5 · Crypto & Digital-Asset Integrity | watch | Oregon's stayed Coinbase enforcement action and UCC Article 12 (SB 167) continue to shape a distinct state-level crypto posture. |
| T6 · Sanctions Regime Divergence | no_change | No Oregon-specific sanctions-divergence signal this cycle. |