title: United States – Oregon Payments Regulation Monitor | World Payments Monitor canonical: https://payments.gi/jurisdictions/united-states-oregon/ date_modified: 2026-10-21 publisher: Asymmetric Intelligence # United States – Oregon US-OR schema world-payments-v1 trajectory: not yet assessed Last updated 2026-10-21 · 14 modules · 63 sourced findings · 138 sources in the cumulative register 14 Modules baseline.modules[] 63 Findings modules[].findings[] 35 Tier-1 sources run_metadata.t1_source_count Confidence mix (sums to 14 rendered modules; click to filter) No modules moved this cycle. ** United States federal law** that applies in United States – Oregon is covered once, on the [United States](https://payments.gi/jurisdictions/united-states/) page. This page covers United States – Oregon’s own layer: its own law, regulators and enforcement. ## Jurisdiction brief ###### Latest update · 28 September 2026 #### Lead Signal Oregon's most consequential payments-adjacent development this cycle sits not in the payments-licensing regime itself but in commercial law: Senate Bill 167, codified as ORS 80.1010 through 80.1070 and enacting UCC Article 12, creates a new "controllable electronic record" property category for digital assets and establishes control-based perfection rules for security interests in that property, effective as of May 7, 2025. The statute amends UCC definitions to exclude cryptocurrency and other digital assets from the definition of "money" while carving out a distinct "electronic money" category with its own control and security-interest rules. This is a confirmed, primary-source finding, drawn directly from the Oregon Legislature's own chapter text and corroborated by Oregon State Bar commentary. A one-year transition period, or July 1, 2025, whichever is later, governs how perfection priority is resolved between filing-based and control-based secured parties during the changeover; this transition-mechanics detail is corroborated only at a lower evidentiary tier and is held to probable confidence accordingly. #### Other Developments No other module in the fourteen-module spine produced material content this cycle. The general money-transmission regime under ORS 717, administered by the Oregon Division of Financial Regulation, remains standing and unamended: money transmission absent an ORS 717.210 exemption requires licensure, administered through the NMLS, with net-worth requirements running from $100,000 upward (plus $25,000 per additional location, capped at $500,000) and a surety bond starting at $25,000 (plus $5,000 per location, capped at $150,000), alongside a prerequisite FinCEN MSB registration. That detail was newly captured in the source register this cycle but reflects a standing, unamended regime rather than fresh regulatory movement, and is not treated here as the cycle's lead development. #### Cross-Monitor Connections The new UCC Article 12 property-and-perfection framework for controllable electronic records is directly relevant to stablecoin- and digital-asset-adjacent commercial finance, and readers tracking the crypto monitor's Oregon coverage of stablecoin and digital-money regulation should read this development alongside that thread; this brief does not itself analyse stablecoin regulatory status, which is out of scope here. #### Outlook The one-year transition period governing perfection priority under SB 167 is due to conclude around mid-2026, at which point the control-based perfection regime becomes the operative standard for digital-asset collateral in Oregon without the transitional filing-based overlay. This is the principal item to watch: its conclusion could sharpen the practical stakes for any lender or platform relying on filing-based perfection for digital-asset-backed transactions in Oregon. ###### Standing brief · as of 23 August 2026 _Written before the update above. Where they differ, the update is the more recent position._ #### Lead Signal Oregon has moved decisively this cycle to tighten consumer-finance conduct regulation, closing a long-standing rate-arbitrage loophole and simultaneously securing a landmark multistate consumer-protection settlement against a major payments app. Governor Kotek signed HB 4116 on April 7, 2026, barring lenders from exporting interest rates above Oregon's 36% consumer-finance-loan cap via the federal Depository Institutions Deregulation and Monetary Control Act's opt-out mechanism, with the law taking effect June 5, 2026. The mechanism matters as much as the headline rate: HB 4116 targets a specific structural avenue — interest-rate exportation under DIDMCA's opt-out provision — that had allowed lenders partnering with out-of-state, DIDMCA-eligible institutions to charge rates above Oregon's own consumer-finance-loan ceiling. The Division of Financial Regulation backed the legislative closure with active enforcement, securing $900,000 in restitution from a lender that had charged interest above the statutory cap prior to the new law's enactment — evidence that the loophole closure responds to a documented enforcement problem rather than a theoretical one. The Interpreter's confidence rating for both the legislation and the underlying restitution action is High, anchored in Tier-1 sourcing directly from the Oregon Division of Financial Regulation, with a HIGH impact designation attached to the legislative change. #### Other Developments **Oregon co-leads a 46-state, $45 million settlement with Block, Inc. over Cash App.** Oregon and Texas co-led a multistate investigation into Block, Inc., resulting in a $45 million settlement 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 settlement explicitly references the Consumer Financial Protection Bureau's prior, now-partly-cancelled restitution settlement with Block as context, positioning the state action as filling space left by receding federal enforcement capacity. Commercially, this signals a rising willingness among state attorneys general to backstop payments-app consumer-protection enforcement precisely as CFPB activity recedes — a dynamic with implications for any payments app operating a consumer-facing fraud-resolution process in Oregon or comparable states. This finding carries a CRITICAL impact designation, the highest impact tier used in this cycle's Oregon coverage, reflecting both the settlement's scale and its explicit federal-state enforcement-gap framing. #### Cross-Monitor Connections Both developments carry dimensions handled elsewhere in the fleet. The Block/Cash App settlement is a shared finding with the Financial Integrity Monitor, which frames the same facts through an enabler-jurisdiction lens — Oregon as a state-level backstop against reduced federal consumer-financial-protection capacity — rather than the payments-conduct and consumer-protection lens applied here. Oregon's AML/CFT posture and stablecoin developments are tracked separately by the Financial Integrity and Crypto monitors respectively as subscribed render-only slots on this surface, and are not re-analyzed in this brief. #### Outlook The near-term item to watch on the conduct side is whether HB 4116's June 5, 2026 effective date produces a measurable reduction in above-cap lending activity reaching Oregon consumers, or whether new structuring attempts emerge to route around the closed DIDMCA export mechanism; the DFR's pre-enactment $900,000 restitution action suggests the regulator is prepared to continue enforcing the underlying rate cap directly regardless of statutory posture. On the consumer-protection side, the Block/Cash App settlement's explicit framing against a partly-cancelled federal CFPB settlement is itself worth monitoring: if federal restitution commitments continue to be narrowed or reversed, Oregon's willingness to co-lead further multistate actions against payments apps is likely to persist or grow. Enforcement momentum on both fronts appears likely to continue rather than taper: the DFR's willingness to pursue restitution ahead of the legislative fix, and Oregon's co-leadership role alongside Texas in a 46-state action, both point to a sustained, active regulatory posture rather than a single-cycle event. Firms with consumer-finance-loan or payments-app operations touching Oregon consumers should treat the DIDMCA export-closure and the Cash App settlement as two data points on the same underlying trend. trust tier: ai_unverified _Standing brief, as of 23 August 2026._ #### Regulatory Status Oregon's payments-regulatory posture tightened materially this cycle across two distinct fronts. First, HB 4116, signed April 7, 2026 and effective June 5, 2026, closes a DIDMCA-based interest-rate-export loophole that had allowed lenders to exceed Oregon's 36% consumer-finance-loan cap through out-of-state bank-partnership structures, backed by a contemporaneous $900,000 DFR restitution action against a lender that had already violated the underlying cap. Second, Oregon co-led, with Texas, a 46-state, $45 million settlement with Block, Inc. over Cash App's misrepresented account-safety features and inadequate fraud-protection and resolution services, with Oregon's own share set at $3 million; the settlement explicitly frames the action as backfilling reduced federal CFPB enforcement capacity. #### Outlook Both developments point toward a sustained, active state regulatory posture rather than isolated events: the DFR's willingness to enforce ahead of legislative fixes, and Oregon's coalition-leadership role in multistate payments-app litigation, both suggest continued tightening pressure on consumer-finance-loan and payments-app conduct in Oregon through the coming cycles. 14 of 14 modules Signal Density Selections OR within a group, AND across groups. Press / to search. ### W1a Licensing, Authorisation & Market Access Confirmed confirmed 2026-07-05 Oregon regulates money transmission (incl. virtual-currency businesses, prepaid instrument sale, and check cashing) under a single non-bank licensing regime -- the Oregon Money Transmitters Act (ORS Chapter 717) -- administered by the Division of Financial Regulation (DFR) within the Department of Consumer and Business Services (DCBS), with applications processed through NMLS. There is no separate EMI/PPI tier; a single money transmitter license covers all in-scope activity statewide, subject to bond, net-worth, and background-check conditions. Standing sub-brief · as of 5 July 2026 132 words · last cycle 2026-07-05 #### Licensing, Authorisation & Market Access Oregon requires a single money transmitter license from the DFR Director under ORS 717.205 for money transmission business, including virtual-currency exchange and wallet activity, prepaid instrument sale, and check cashing; one license covers all in-state locations and there is no separate EMI/PPI tier. DFR requires MTL applicants to show net worth of at least $100,000 plus $25,000 per location or authorized delegate, an electronic surety bond starting at $25,000 (statutory maximum $150,000), a BSA/USA PATRIOT Act Section 352 AML program, and a $1,000 non-refundable NMLS application fee. #### Outlook No legislative activity toward a separate EMI/PPI or stablecoin-specific licensing tier was identified this cycle; the single-MTL model appears entrenched rather than under near-term reform pressure, though continued crypto-sector enforcement activity may generate pressure for a bespoke digital-asset carve-out. no periodic updates on record for this sub-brief ** Sources and findings (7)** 1. T1 [https://oregon.public.law/statutes/ors_717.205](https://oregon.public.law/statutes/ors_717.205) retrieved 2026-07-05 2. T1 [https://dfr.oregon.gov/business/licensing/financial/pages/money-transmitters.aspx](https://dfr.oregon.gov/business/licensing/financial/pages/money-transmitters.aspx) retrieved 2026-07-05 3. T1 [https://oregon.public.law/statutes/ors_717.205](https://oregon.public.law/statutes/ors_717.205) retrieved 2026-07-05 4. T1 [https://apps.oregon.gov/SOS/LicenseDirectory/LicenseDetail/21](https://apps.oregon.gov/SOS/LicenseDirectory/LicenseDetail/21) retrieved 2026-07-05 5. T1 [https://secure.sos.state.or.us/oard/displayDivisionRules.action?selectedDivision=2162](https://secure.sos.state.or.us/oard/displayDivisionRules.action?selectedDivision=2162) retrieved 2026-07-05 6. T3 [https://www.bondexchange.com/oregon-money-transmitter-bond-a-comprehensive-guide/](https://www.bondexchange.com/oregon-money-transmitter-bond-a-comprehensive-guide/) retrieved 2026-07-05 7. T3 [https://moneytransmitterlaw.com/state-laws/oregon/](https://moneytransmitterlaw.com/state-laws/oregon/) retrieved 2026-07-05 ### W1b Conduct, Safeguarding & Promotions limited signal Confirmed confirmed 2026-07-05 Oregon closed a state-chartered-bank interest-rate-export (DIDMCA) loophole via HB 4116 (2026), reinforcing its 36% consumer-finance interest-rate cap against internet lenders partnering with out-of-state banks; DFR separately secured a $900,000 restitution settlement against a lender that had exceeded the cap. Standing sub-brief · as of 23 August 2026 429 words · last cycle 2026-08-21 #### Conduct, Safeguarding & Financial Promotions Oregon closed a significant conduct-regulation gap this cycle when Governor Tina Kotek signed HB 4116 on April 7, 2026, a law that bars lenders from exporting interest rates above Oregon's 36% consumer-finance-loan cap through the federal Depository Institutions Deregulation and Monetary Control Act's rate-export opt-out mechanism. The law takes effect June 5, 2026. DIDMCA rate exportation has historically allowed lenders to structure consumer-finance products through out-of-state, DIDMCA-eligible partner institutions in order to charge interest rates that would otherwise exceed a borrowing state's own consumer-finance-loan ceiling; HB 4116 targets that specific structural avenue directly, rather than simply reiterating the existing 36% cap in statute. This closure falls most directly on lenders using bank-partnership structures to access out-of-state rate ceilings, since the DIDMCA opt-out mechanism is inherently a depository-institution channel. The Division of Financial Regulation paired the legislative closure with direct enforcement activity, securing $900,000 in restitution from a lender found to have charged interest above Oregon's statutory cap prior to HB 4116's enactment. That sequencing — an active restitution action alongside a targeted legislative fix — indicates the DFR was already pursuing the underlying conduct as a violation of existing law even before the loophole-closure mechanism took effect, suggesting continuity of enforcement intent across the legislative transition rather than a wait-and-see posture pending the new law's effective date. Both developments are drawn from Tier-1 sourcing directly from the Oregon Division of Financial Regulation and carry a High confidence rating, with a HIGH impact designation attached to the legislative change. Independent local-press coverage corroborates the law's effective date and legislative rationale, reducing the risk that this is an isolated or overstated finding. Read together, the two developments describe a state regulator and legislature acting in coordination — legislative action closing a specific structural gap, paired with contemporaneous supervisory enforcement addressing the same underlying conduct under existing authority. For firms operating consumer-finance-loan products that rely on out-of-state bank-partnership structures to reach Oregon borrowers, both the mechanism and the enforcement posture are now materially less permissive than before this cycle. #### Outlook The effective date of June 5, 2026 is the immediate item to watch: whether above-cap lending activity reaching Oregon consumers through bank-partnership structures declines measurably once the export mechanism is closed, or whether new structuring approaches emerge to route around it, will determine whether HB 4116 functions as a durable fix or merely shifts the point of arbitrage. The DFR's demonstrated willingness to pursue restitution ahead of the legislative fix suggests continued active supervision of consumer-finance-loan conduct regardless of the precise structural avenue lenders attempt to use. No new data since the standing brief. 1 periodic run re-emitted it unchanged. **Sources and findings (5)** 1. T1 [https://www.oregonlegislature.gov/bills_laws/ors/ors717.html](https://www.oregonlegislature.gov/bills_laws/ors/ors717.html) retrieved 2026-07-05 2. T3 [https://legalclarity.org/oregon-unlawful-trade-practices-act-violations-and-remedies/](https://legalclarity.org/oregon-unlawful-trade-practices-act-violations-and-remedies/) retrieved 2026-07-05 3. T1 [https://secure.sos.state.or.us/oard/view.action?ruleNumber=441-745-0340](https://secure.sos.state.or.us/oard/view.action?ruleNumber=441-745-0340) 4. T1 [https://www.oregonlegislature.gov/bills_laws/ors/ors717.html](https://www.oregonlegislature.gov/bills_laws/ors/ors717.html) retrieved 2026-07-05 5. T1 [https://www.doj.state.or.us/consumer-protection/about-us/](https://www.doj.state.or.us/consumer-protection/about-us/) retrieved 2026-07-05 ### W2 Stablecoins & Digital Money Probable confirmed 2026-07-05 Oregon has no dedicated stablecoin or digital-asset issuer licensing statute; virtual currency is instead swept into the general Money Transmitters Act definition of 'money.' A narrow 2019 statute (HB 2488) restricts the state government's own acceptance of cryptocurrency and bars crypto political contributions. DFR issues consumer-protection guidance on crypto volatility and lack of FDIC insurance rather than prudential stablecoin rules. Standing sub-brief · as of 5 July 2026 111 words · last cycle 2026-07-05 #### Stablecoins & Digital Money Oregon has no dedicated stablecoin or digital-asset issuer licensing statute; the MTL Act's broad definition of money under ORS 717.200 is interpreted to include virtual currency, pulling crypto exchanges and wallets under the standard ORS 717.205 license requirement, illustrated historically by Coinbase's 2015 Oregon MTL. Oregon's HB 2488 (2019) bars state government from accepting cryptocurrency payments unless authorized by the State Treasurer, and separately bars using cryptocurrency for political campaign contributions. #### Outlook Absent a dedicated stablecoin statute, digital-asset firms operating in Oregon should expect continued treatment under the general MTL framework, with the state's regulatory posture toward crypto increasingly expressed through enforcement rather than through prudential rulemaking. no periodic updates on record for this sub-brief ** Sources and findings (5)** 1. T2 [https://stevenscenter.wharton.upenn.edu/publications-50-state-review/](https://stevenscenter.wharton.upenn.edu/publications-50-state-review/) retrieved 2026-07-05 2. T2 [https://stevenscenter.wharton.upenn.edu/publications-50-state-review/](https://stevenscenter.wharton.upenn.edu/publications-50-state-review/) retrieved 2026-07-05 3. T1 [https://dfr.oregon.gov/help/Documents/5342-cryptocurrency.pdf](https://dfr.oregon.gov/help/Documents/5342-cryptocurrency.pdf) retrieved 2026-07-05 4. T3 [https://moneytransmitterlaw.com/cryptocurrency-state-laws/oregon/](https://moneytransmitterlaw.com/cryptocurrency-state-laws/oregon/) retrieved 2026-07-05 5. T1 [https://www.doj.state.or.us/wp-content/uploads/2025/05/Oregon-v.-Coinbase-Complaint.pdf](https://www.doj.state.or.us/wp-content/uploads/2025/05/Oregon-v.-Coinbase-Complaint.pdf) retrieved 2026-07-05 ### W3 Operational Resilience & Critical Infrastructure Confirmed confirmed 2026-07-05 Operational-resilience obligations touching Oregon-chartered and nationally chartered banks operating in the state derive almost entirely from the federal layer: the OCC/Fed/FDIC computer-security incident notification rule (12 CFR 53) and FFIEC/NIST examination expectations. State-level resilience obligations for non-bank payments firms run through the Oregon Consumer Information Protection Act's (OCIPA) breach-notification and reasonable-safeguards duties, enforced by DOJ/DFR as an unlawful trade practice. Kept on Dataprotection.gi, not restated here: data and cloud switching obligations on service providers, including notice periods and charges. [Open its jurisdiction pages on Dataprotection.gi →](https://dataprotection.gi/jurisdictions/) Standing sub-brief · as of 5 July 2026 126 words · last cycle 2026-07-05 #### Operational Resilience & Critical Infrastructure Banks operating in Oregon, including OR-chartered and national banks, must notify their primary federal regulator no later than 36 hours after determining a notification incident has occurred, under 12 CFR Part 53. Non-bank payments and data-handling entities must notify affected Oregon consumers within 45 days of discovering a breach under the Oregon Consumer Information Protection Act, and notify the Oregon DOJ within 45 days if more than 250 Oregon consumers are affected, with violations treated as unlawful trade practices carrying penalties up to $500,000 for continuing violations. #### Outlook No Oregon-specific overlay on the federal bank incident-notification rule was identified, and the OCIPA breach-notification backstop for non-bank payments firms appears stable; this bifurcated framework is likely to persist absent new state legislation. no periodic updates on record for this sub-brief ** Sources and findings (4)** 1. T1 [https://www.occ.gov/news-issuances/bulletins/2021/bulletin-2021-55.html](https://www.occ.gov/news-issuances/bulletins/2021/bulletin-2021-55.html) retrieved 2026-07-05 2. T1 [https://www.federalreserve.gov/supervisionreg/cybersecurity-and-operational-resilience.htm](https://www.federalreserve.gov/supervisionreg/cybersecurity-and-operational-resilience.htm) retrieved 2026-07-05 3. T1 [https://www.doj.state.or.us/consumer-protection/id-theft-data-breaches/data-breaches/](https://www.doj.state.or.us/consumer-protection/id-theft-data-breaches/data-breaches/) retrieved 2026-07-05 4. T3 [https://www.recordinglaw.com/us-laws/data-privacy-laws/oregon-data-privacy-laws/data-breach-notification/](https://www.recordinglaw.com/us-laws/data-privacy-laws/oregon-data-privacy-laws/data-breach-notification/) retrieved 2026-07-05 ### W4 Scheme & Network Compliance Probable confirmed 2026-07-05 Oregon has no state-specific interchange-fee statute or credit-card surcharge ban; merchants may surcharge credit-card transactions subject only to federal limits (4% cap, cost-recovery-only) and card-network rules, while debit surcharging remains barred nationwide by the Durbin Amendment. Government agencies have explicit statutory authority to surcharge card payments; PCI DSS applies to any Oregon merchant handling card data as a network/contractual requirement rather than a state law. Standing sub-brief · as of 5 July 2026 113 words · last cycle 2026-07-05 #### Scheme & Network Compliance Oregon has no state-specific interchange-fee statute or surcharge ban; merchants may surcharge credit-card transactions subject to a federal 4% cap and cost-recovery-only limitation, while debit-card surcharging remains barred nationwide under the Durbin Amendment. ORS 825.502 and ORS 802.112 authorize Oregon state agencies, such as the Department of Transportation, to add a surcharge to card-based tax and fee payments to offset acceptance costs, and to surcharge where a customer selects a more expensive payment channel. #### Outlook With no Oregon-specific merchant surcharge legislation identified, private-sector card-acceptance economics will continue to be set by federal limits and card-scheme rules rather than state law, while the government-agency carve-out remains a narrow, stable exception. no periodic updates on record for this sub-brief ** Sources and findings (5)** 1. T3 [https://merchantcostconsulting.com/lower-credit-card-processing-fees/oregon-surcharge-laws/](https://merchantcostconsulting.com/lower-credit-card-processing-fees/oregon-surcharge-laws/) retrieved 2026-07-05 2. T1 [https://oregon.public.law/statutes/ors_825.502](https://oregon.public.law/statutes/ors_825.502) retrieved 2026-07-05 3. T1 [https://oregon.public.law/statutes/ors_802.112](https://oregon.public.law/statutes/ors_802.112) retrieved 2026-07-05 4. T3 [https://ebizcharge.com/blog/credit-card-surcharging-a-state-by-state-legal-analysis/](https://ebizcharge.com/blog/credit-card-surcharging-a-state-by-state-legal-analysis/) retrieved 2026-07-05 5. T3 [https://pivitstrategy.com/oregon-cybersecurity-laws-you-should-know-2026/](https://pivitstrategy.com/oregon-cybersecurity-laws-you-should-know-2026/) retrieved 2026-07-05 ### W5 Payment Corridor Dynamics Probable confirmed 2026-07-05 Oregon sits within the broader US-Latin America remittance corridor (dominated nationally by Western Union, MoneyGram, Remitly, and Intermex under the state's MTL framework) and is an early-adopter market for the Federal Reserve's FedNow instant-payments rail, with Oregon-headquartered digital-banking vendor Tyfone supporting credit-union FedNow rollouts and at least two Oregon-chartered institutions live on the network. Standing sub-brief · as of 5 July 2026 110 words · last cycle 2026-07-05 #### Payment Corridor Dynamics Approximately 80% of US-to-Latin-America/Caribbean remittance flows are managed by about ten firms, including Western Union, PayPal/Xoom, Viamericas, Remitly, MoneyGram, Ria, and Intermex, the channel through which Oregon-originated remittances predominantly flow under state MTL licensing. Portland-based digital banking vendor Tyfone helped a FedNow early-adopter credit union enable instant send and receive capability, and First Community Credit Union in Coquille and People's Bank in Medford are among the FedNow-participating institutions in Oregon. #### Outlook Corridor concentration among a small set of MTL-licensed remittance majors will likely continue to shape competitive dynamics and pricing for Oregon-originated outbound remittance flows, while FedNow adoption via the community-FI channel remains on an escalating trajectory. no periodic updates on record for this sub-brief ** Sources and findings (3)** 1. T3 [https://thedialogue.org/blogs/2025/04/the-state-of-the-remittance-industry-and-an-outlook-for-2025](https://thedialogue.org/blogs/2025/04/the-state-of-the-remittance-industry-and-an-outlook-for-2025) retrieved 2026-07-05 2. T3 [https://www.bankingdive.com/news/fednow-instant-payments-real-time-banks-credit-unions-transactions/688516/](https://www.bankingdive.com/news/fednow-instant-payments-real-time-banks-credit-unions-transactions/688516/) retrieved 2026-07-05 3. T3 [https://www.nerdwallet.com/banking/learn/banks-that-use-fednow](https://www.nerdwallet.com/banking/learn/banks-that-use-fednow) retrieved 2026-07-05 ### W6 Industry Structure & Commercial Probable confirmed 2026-07-05 Oregon's payments-adjacent banking sector is consolidating around Lake Oswego-headquartered Umpqua Bank (a subsidiary of Columbia Banking System), which is absorbing Pacific Premier Bank in a ~$70 billion-asset combination and rebranding as Columbia Bank; a fintech/vendor layer (Tyfone digital banking, Nvoicepay B2B payments, Sila banking-as-a-service) supplements a modest but growing venture-backed fintech ecosystem. Standing sub-brief · as of 5 July 2026 118 words · last cycle 2026-07-05 #### Industry Structure & Commercial Dynamics Columbia Banking System, Inc., parent of Lake Oswego, Oregon-based Umpqua Bank, completed its acquisition of Pacific Premier Bancorp, Inc. on 2025-08-31, creating a combined bank with approximately $70 billion in assets, and Umpqua Bank completed its rebrand to Columbia Bank on 2025-09-01 across more than 350 locations in eight Western states. Oregon-based fintech startups raised an aggregate $528M across 123 deals in the most recently reported annual period, a reported 39% year-over-year increase, supported by 13 active VC funds and five accelerator programs. #### Outlook The completed Columbia/Pacific Premier combination reshapes Oregon's bank-PSP landscape around a single dominant regional platform, a structural shift worth monitoring for downstream effects on correspondent access and community-banking competition. no periodic updates on record for this sub-brief ** Sources and findings (4)** 1. T1 [https://www.sec.gov/Archives/edgar/data/0001028918/000110465925038087/tm2512834d3_ex99-1.htm](https://www.sec.gov/Archives/edgar/data/0001028918/000110465925038087/tm2512834d3_ex99-1.htm) retrieved 2026-07-05 2. T1 [https://www.sec.gov/Archives/edgar/data/0001028918/000110465925040437/tm2512834d10_425.htm](https://www.sec.gov/Archives/edgar/data/0001028918/000110465925040437/tm2512834d10_425.htm) retrieved 2026-07-05 3. T1 [https://www.sec.gov/Archives/edgar/data/0001028918/000110465925038168/tm2512834d4_425.htm](https://www.sec.gov/Archives/edgar/data/0001028918/000110465925038168/tm2512834d4_425.htm) retrieved 2026-07-05 4. T4 [https://freestartupfunding.com/who-funds/fintech/in/oregon](https://freestartupfunding.com/who-funds/fintech/in/oregon) retrieved 2026-07-05 ### W7 Legal & Litigation Confirmed confirmed 2026-07-05 The dominant live payments/digital-asset litigation in Oregon is Attorney General Dan Rayfield's April 2025 securities-law enforcement action against Coinbase, filed after the SEC dropped its parallel federal case, alleging Coinbase facilitated sale of unregistered crypto securities to Oregonians; Coinbase has counter-sued the Governor over public-records access and sought federal removal, and the matter remains contested. Historically, FinCEN has also pursued Oregon-based unlicensed money-transmission enforcement under the BSA. Standing sub-brief · as of 5 July 2026 136 words · last cycle 2026-07-05 #### Legal & Litigation Oregon Attorney General Dan Rayfield filed a securities-law enforcement action against Coinbase in April 2025 in Multnomah County Circuit Court, alleging Coinbase facilitated sale of unregistered crypto securities to Oregonians and citing the ICP token's roughly 99% price collapse as investor-harm evidence, with Coinbase separately suing Governor Kotek over public-records access to the case. FinCEN assessed a $25,000 civil money penalty against a Tigard, Oregon-based unregistered money transmitter for BSA registration, AML-program, and SAR violations, following more than 4,200 funds transfers totaling over $172 million between 2002 and 2009, via coordinated FinCEN, DOJ, FBI, and USPIS action. #### Outlook The Coinbase litigation is on an escalating trajectory and remains the single most consequential legal-risk item for crypto platforms operating under Oregon MTLs; its jurisdictional resolution will be a key indicator to track next cycle. no periodic updates on record for this sub-brief ** Sources and findings (5)** 1. T1 [https://www.doj.state.or.us/media-home/news-media-releases/oregon-attorney-general-rayfield-sues-coinbase-for-promoting-and-selling-high-risk-investments/](https://www.doj.state.or.us/media-home/news-media-releases/oregon-attorney-general-rayfield-sues-coinbase-for-promoting-and-selling-high-risk-investments/) retrieved 2026-07-05 2. T3 [https://www.coindesk.com/policy/2025/06/03/coinbase-moves-to-bring-oregon-securities-suit-to-federal-jurisdiction](https://www.coindesk.com/policy/2025/06/03/coinbase-moves-to-bring-oregon-securities-suit-to-federal-jurisdiction) retrieved 2026-07-05 3. T3 [https://oregoncapitalchronicle.com/2025/07/15/ag-rayfield-let-campaign-donors-lead-oregons-crypto-case-the-company-hes-suing-wants-answers/](https://oregoncapitalchronicle.com/2025/07/15/ag-rayfield-let-campaign-donors-lead-oregons-crypto-case-the-company-hes-suing-wants-answers/) retrieved 2026-07-05 4. T1 [https://www.fincen.gov/news/news-releases/fincen-assesses-civil-money-penalty-against-oregon-based-unregistered-money](https://www.fincen.gov/news/news-releases/fincen-assesses-civil-money-penalty-against-oregon-based-unregistered-money) retrieved 2026-07-05 5. T3 [https://www.cohenmilstein.com/case-study/coinbase-securities-litigation/](https://www.cohenmilstein.com/case-study/coinbase-securities-litigation/) retrieved 2026-07-05 ### W8 Merchant Acquiring & Risk Probable confirmed 2026-07-05 Oregon merchant acquiring follows the general federal/card-network framework (no state-specific acquiring statute), but the state's legal cannabis retail sector is treated as a high-risk merchant category nationally: major card networks bar cannabis transactions outright, forcing Oregon dispensaries toward cash-only operation or specialized high-risk ISO/processor and cashless-ATM workarounds, with attendant chargeback, rolling-reserve, and account-freeze exposure. Standing sub-brief · as of 5 July 2026 71 words · last cycle 2026-07-05 #### Merchant Acquiring & Risk Visa, Mastercard, and American Express explicitly prohibit cannabis-related transactions network-wide, forcing Oregon dispensaries toward cash-only operation or specialized high-risk ISO and cashless-ATM workarounds, with high-risk processing rates running 5-6% versus near-zero-fee cashless alternatives. #### Outlook Without a change in federal cannabis status or card-network policy, Oregon's cannabis retail sector will likely remain locked out of mainstream card acceptance, sustaining elevated processing costs and cash-handling risk for the sector. no periodic updates on record for this sub-brief ** Sources and findings (3)** 1. T4 [https://paybotic.com/markets/oregon/](https://paybotic.com/markets/oregon/) retrieved 2026-07-05 2. T4 [https://bankcardinternationalgroup.com/the-truth-about-cannabis-payment-processing-what-dispensary-owners-need-to-know/](https://bankcardinternationalgroup.com/the-truth-about-cannabis-payment-processing-what-dispensary-owners-need-to-know/) retrieved 2026-07-05 3. T4 [https://www.thetransactiongroup.net/portland-or-marijuana-dispensary-credit-card-processing/](https://www.thetransactiongroup.net/portland-or-marijuana-dispensary-credit-card-processing/) retrieved 2026-07-05 ### W9 Product Innovation & Market Development 1 gap Probable confirmed 2026-07-05 Product innovation touching Oregon centers on FedNow instant-payments adoption by Oregon-headquartered digital-banking vendor Tyfone and early-adopting Oregon credit unions/community banks, alongside a modest B2B/embedded-finance vendor cluster (Nvoicepay accounts-payable automation, Sila banking-as-a-service) and a growing but still-nascent VC-backed fintech pipeline. Open gap — wpm-int-3 No Oregon-specific CBDC pilot or open-banking/PSD3-equivalent initiative was identified._no under-indexing note recorded_ Standing sub-brief · as of 5 July 2026 102 words · last cycle 2026-09-28 #### Product Innovation & Market Development The Federal Reserve's FedNow Service enables banks and credit unions of all sizes, including Oregon institutions, to send and receive payments within seconds with immediate funds availability via the FedLine network, with roughly 470 institutions having joined as of early 2024. Sila, a money-API/BaaS platform, and Portland-based Nvoicepay, a B2B accounts-payable automation provider, form part of Oregon's embedded-finance and B2B product-vendor layer. #### Outlook FedNow adoption remains on an escalating trajectory and is the clearest product-innovation signal touching Oregon this cycle, with continued uptake among community financial institutions likely to be the leading indicator to track next cycle. Periodic update · new data 2026-09-28 #### Product Innovation & Market Development Oregon enacted Senate Bill 167 in 2025, codified at ORS 80.1010 through 80.1070, adopting UCC Article 12 and creating a new commercial-law property category, the "controllable electronic record," for digital assets. This is a confirmed, primary-tier finding sourced directly from the Oregon Legislature's chapter text. The statute establishes control-based perfection rules for security interests in this new asset class, meaning that a secured party who obtains "control" over a controllable electronic record can perfect its interest through that control rather than solely through a UCC filing, and that control-based perfection prevails over filing-based perfection in a priority dispute. The statute took effect May 7, 2025. Alongside the new property category, SB 167 amends existing UCC definitions to exclude cryptocurrency and other digital assets from the statutory definition of "money," while simultaneously creating a distinct "electronic money" category carrying its own control and security-interest rules. This is a confirmed finding, corroborated by Oregon State Bar Technology Law Section commentary, and it matters for payments-adjacent commercial finance because it draws a clear legal line between a digital asset used as a payment instrument or store of value and a digital asset treated as a controllable electronic record for collateral purposes. A one-year transition period, running to May 2026 or July 1, 2025, whichever is later, governs how the law resolves conflicts between secured parties who perfected under the old filing-based regime and secured parties perfecting under the new control-based regime for the same collateral. This transition-mechanics detail comes from a lower-tier commercial-law commentary source and is held at probable rather than confirmed confidence, since it has not been independently corroborated against the primary statutory text or a second corroborating source. Oregon's adoption places it among a smaller group of US states that have moved to codify a specific commercial-law framework for digital-asset collateral ahead of broader multistate uniformity on this question, a distinction with practical significance for lenders, custodians, and platforms structuring digital-asset-backed financing that touches Oregon-domiciled counterparties or collateral. #### Outlook The one-year transition period is due to conclude around mid-2026. Its conclusion will settle, on a going-forward basis, how competing claims to digital-asset collateral are prioritized between filing-based and control-based secured creditors, removing the transitional ambiguity that currently exists. This is the principal item to watch for any counterparty relying on Oregon law to structure digital-asset-backed security arrangements. **Sources and findings (4)** 1. T1 [https://www.federalreserve.gov/paymentsystems/fednow_faq.htm](https://www.federalreserve.gov/paymentsystems/fednow_faq.htm) retrieved 2026-07-05 2. T3 [https://www.nerdwallet.com/banking/learn/banks-that-use-fednow](https://www.nerdwallet.com/banking/learn/banks-that-use-fednow) retrieved 2026-07-05 3. T4 [https://www.failory.com/startups/oregon](https://www.failory.com/startups/oregon) retrieved 2026-07-05 4. T4 [https://builtin.com/companies/location/na/usa/or/type/fintech-startups](https://builtin.com/companies/location/na/usa/or/type/fintech-startups) retrieved 2026-07-05 ### W10 Consumer Protection & APP Fraud limited signal Confirmed confirmed 2026-07-05 Oregon led a 46-state, $45M multistate settlement with Block, Inc. (Cash App) over misrepresented account safety and inadequate fraud-protection/resolution processes; Oregon will receive $3M and continues to monitor Block's compliance with its separate CFPB restitution obligations. Standing sub-brief · as of 23 August 2026 401 words · last cycle 2026-08-21 #### Consumer Protection & APP Fraud Oregon, alongside Texas, co-led a 46-state, $45 million settlement with Block, Inc. resolving allegations that its Cash App product misrepresented account-safety features and failed to deliver the fraud-protection and dispute-resolution services it had represented to users. Oregon's own share of the settlement proceeds is $3 million. The settlement documentation explicitly situates the state action against the backdrop of the federal Consumer Financial Protection Bureau's own prior restitution settlement with Block, which has since been partly cancelled — a direct acknowledgment by the states involved that their action is filling space opened by a receding federal enforcement commitment rather than duplicating an intact one. This finding carries a High confidence rating, anchored in Tier-1 sourcing from the Oregon Department of Justice, and a CRITICAL impact designation — the highest impact tier used in this cycle's Oregon coverage — reflecting both the settlement's scale and its explicit framing as a federal-enforcement-gap backstop. The commercial-relevance note attached to this finding is direct: it signals a rising willingness among state attorneys general to take on payments-app consumer-protection enforcement precisely as CFPB capacity contracts, a dynamic with implications well beyond Block itself for any payments provider whose consumer-facing safety and fraud-resolution representations have not been independently verified against actual performance. For payments apps generally, the substantive allegations — misrepresented account-safety features, and failure to deliver promised fraud-protection and resolution services — describe a gap between marketing representations and operational reality in exactly the area that is often central to a consumer payments product's value proposition. A 46-state coalition reaching a common settlement figure indicates a degree of coordinated state-level agreement on the underlying facts, which itself raises the evidentiary bar any comparable payments provider would face if a similar gap were identified in its own fraud-resolution practices. #### Outlook The explicit reference to the CFPB's partly-cancelled prior settlement is the most consequential framing device in this cycle's finding, and the item most worth tracking forward: if federal restitution commitments in payments-app enforcement continue to be narrowed, reversed, or left unenforced, the multistate coalition model demonstrated by Oregon and Texas here is likely to be replicated for other payments providers whose safety and fraud-resolution representations come under similar scrutiny. Firms operating consumer-facing payments apps in Oregon or comparable jurisdictions should treat this settlement as a template for the kind of gap-between-representation-and-performance finding that state coalitions are now positioned and willing to pursue directly. No new data since the standing brief. 1 periodic run re-emitted it unchanged. **Sources and findings (5)** 1. T3 [https://legalclarity.org/oregon-unlawful-trade-practices-act-violations-and-remedies/](https://legalclarity.org/oregon-unlawful-trade-practices-act-violations-and-remedies/) retrieved 2026-07-05 2. T3 [https://legalclarity.org/oregon-unlawful-trade-practices-act-violations-and-remedies/](https://legalclarity.org/oregon-unlawful-trade-practices-act-violations-and-remedies/) retrieved 2026-07-05 3. T1 [https://justice.oregon.gov/consumer/databreach/](https://justice.oregon.gov/consumer/databreach/) retrieved 2026-07-05 4. T1 [https://dfr.oregon.gov/financial/protect/pages/index.aspx](https://dfr.oregon.gov/financial/protect/pages/index.aspx) retrieved 2026-07-05 5. T1 [https://dfr.oregon.gov/help/Documents/5342-cryptocurrency.pdf](https://dfr.oregon.gov/help/Documents/5342-cryptocurrency.pdf) retrieved 2026-07-05 ### W11 AML/CFT & Financial Crime [Sourced from Sentinel.gi ↗](https://sentinel.gi/jurisdictions/united-states-oregon/#sec-dom-D7) Confirmed confirmed 2026-07-05 [Sentinel.gi-fed] Oregon's AML/CFT posture for payments is federally anchored: all Oregon-licensed money transmitters must maintain a BSA/USA PATRIOT Act Section 352 AML compliance program as a condition of DFR licensing, and FinCEN retains direct federal enforcement jurisdiction over unregistered/non-compliant money-transmission activity touching Oregon, illustrated by a historical Oregon-based civil-penalty case. No state-level AML statute duplicates the federal BSA framework. Standing sub-brief · as of 5 July 2026 129 words · last cycle 2026-07-05 #### AML/CFT & Financial Crime All Oregon money transmitters must develop and implement a documented AML compliance program under USA PATRIOT Act Section 352, with policies, procedures, and controls approved and reviewed by the licensee's board or senior management, as a condition of DFR licensure. FinCEN retains direct federal enforcement jurisdiction over unregistered or non-compliant Oregon money-transmission activity, illustrated by coordinated FinCEN, DOJ, FBI, and USPIS action against a Tigard, Oregon-based unregistered transmitter, and DCBS may rely on FinCEN examination reports in lieu of its own examination under ORS 706.515. #### Outlook This module is sourced from the Sentinel.gi feed; for deeper analysis of the illicit-finance dimension of unlicensed Oregon money transmission, see the Financial Intelligence Monitor. This module carries only the licensing and supervisory-architecture fact pattern feeding from that source. no periodic updates on record for this sub-brief ** Sources and findings (8)** 1. T3 [https://www.finscan.com/post/regulatory-roundup-january-2026-debanking-enforcement-and-the-expanding-compliance-perimeter](https://www.finscan.com/post/regulatory-roundup-january-2026-debanking-enforcement-and-the-expanding-compliance-perimeter) retrieved 2026-07-05 2. T? FIM (sentinel.gi) per-JID baseline profile — United States — Oregon — Oregon operates entirely within the federal BSA/CTA/FinCEN AML/CFT framework; it has no independent national AML statute. The Oregon Division of Financial Regulation (DFR) licenses money transmitters and virtual-currency businesses under ORS Chapter 717, supplementing federal supervision. Since March 2025, FinCEN's CTA rollback exempts Oregon-formed domestic entities from beneficial ownership reporting, and Oregon has no state-level BO registry to backstop this gap. 3. T? FIM (sentinel.gi) gaps_register_cumulative (issue FIM-BASE-GAP-001) — Gap: sourcing-thinness 4. T? FIM (sentinel.gi) gaps_register_cumulative (issue FIM-BASE-GAP-004) — Gap: legal-gap 5. T2 FIM (sentinel.gi) sanctions_change_register (issue FIM-BASE-SANC-001) — Sanctions: OFAC listing 6. T2 FIM (sentinel.gi) enforcement_action_register (issue FIM-BASE-ENF-002) — Enforcement: OFAC — Sinaloa Cartel Los Chapitos faction money-laundering network (Ojeda Aviles, Aispuro Felix, and associates) 7. T? FIM (sentinel.gi) gaps_register_cumulative (issue FIM-BASE-GAP-003) — Gap: enforcement-absence 8. T? FIM (sentinel.gi) gaps_register_cumulative (issue FIM-BASE-GAP-002) — Gap: regulatory-failure ### W12 Correspondent Banking, Settlement & Access Probable confirmed 2026-07-05 Oregon community banks and credit unions access instant and correspondent settlement primarily through Federal Reserve infrastructure (FedLine, FedNow) rather than through any Oregon-specific settlement scheme; smaller Oregon institutions often reach FedNow via correspondent/settlement-agent intermediaries (e.g., Vizo Financial-type providers) rather than connecting directly, and DFR's cooperative-agreement authority with FinCEN and other bank supervisors underpins cross-agency settlement/AML oversight coordination. Standing sub-brief · as of 5 July 2026 103 words · last cycle 2026-07-05 #### Correspondent Banking, Settlement & Access Smaller Oregon credit unions typically reach FedNow settlement via correspondent or settlement-agent intermediaries, such as Vizo Financial-type corporate credit union providers, rather than through direct Federal Reserve membership. ORS 706.515 and 706.520 authorize DCBS to enter cooperative, coordinating, and information-sharing agreements with FinCEN and other bank supervisory agencies, and to accept FinCEN examination reports in lieu of its own examination. #### Outlook Correspondent/settlement-agent access is likely to remain the operative model for smaller Oregon institutions' instant-settlement access given the cost of direct Federal Reserve connection, worth monitoring alongside the Columbia/Pacific Premier consolidation for any shift in the correspondent-provider landscape. no periodic updates on record for this sub-brief ** Sources and findings (3)** 1. T1 [https://www.frbservices.org/financial-services/fednow/organizations](https://www.frbservices.org/financial-services/fednow/organizations) retrieved 2026-07-05 2. T3 [https://vfccu.org/solutions_mobile/instant-payments.html](https://vfccu.org/solutions_mobile/instant-payments.html) retrieved 2026-07-05 3. T1 [https://www.oregonlegislature.gov/bills_laws/ors/ors706.html](https://www.oregonlegislature.gov/bills_laws/ors/ors706.html) retrieved 2026-07-05 ### W13 Commercial Intelligence (M&A, Investment & Product) 1 gap Probable confirmed 2026-07-05 The standout Oregon-linked commercial event of the trailing period is the Columbia Banking System / Pacific Premier Bancorp all-stock merger (announced April 2025, ~$70bn combined assets, Umpqua-to-Columbia Bank rebrand), while venture funding into Oregon's broader fintech ecosystem is reported to have grown sharply in the most recent reporting period. Open gap — wpm-int-4 Deal-level amount disclosure for individual Oregon fintech venture-funding rounds is not available; only an aggregate annual figure was located._no under-indexing note recorded_ Standing sub-brief · as of 5 July 2026 132 words · last cycle 2026-07-05 #### Commercial Intelligence (M&A, Investment & Product) Columbia Banking System's all-stock acquisition of Pacific Premier Bancorp, announced 2025-04-23, closed on 2025-08-31, with the combined Umpqua Bank entity rebranded to Columbia Bank effective 2025-09-01, combined assets approximately $70 billion across more than 350 locations in eight Western states, deal value not publicly disclosed. Aggregate reported venture funding into Oregon-based fintech startups reached $528 million across 123 deals in the most recent annual reporting period, a 39% year-over-year increase, though deal-level amounts are largely not publicly disclosed. #### Outlook The completed Columbia/Pacific Premier transaction is the standout Oregon-linked commercial event of the trailing period and its integration will be worth tracking for downstream correspondent-banking and market-structure effects; continued growth in Oregon fintech venture funding, if sustained, would point to further product and funding-round activity next cycle. no periodic updates on record for this sub-brief ** Sources and findings (2)** 1. T1 [https://www.sec.gov/Archives/edgar/data/0001028918/000110465925038087/tm2512834d3_ex99-1.htm](https://www.sec.gov/Archives/edgar/data/0001028918/000110465925038087/tm2512834d3_ex99-1.htm) retrieved 2026-07-05 2. T4 [https://freestartupfunding.com/who-funds/fintech/in/oregon](https://freestartupfunding.com/who-funds/fintech/in/oregon) retrieved 2026-07-05 ** No modules match.** Filters combine as OR inside a group and AND across groups. ## Editorial metadata Provenance only. Nothing below gates publication or affects the render. Editorial metadata for United States – Oregon| Field | Value | |---|---| | `trust.lawyer_review.status` | never_reviewed | | `trust.lawyer_review.reviewer` | no reviewer on record | | ` trust.content_source` | ai_generated | ## Provenance and declared absence **Disclosure model:** module cards load OPEN; standing positions render in full; sub-briefs and jurisdiction briefs load as a clamped teaser with an explicit “read full” control carrying the true word count; earlier updates stay collapsed behind a counted summary. No text is hidden without disclosing how much of it there is. **Sentinel-fed modules** receive no special rendering treatment. `sentinel_feed` is an attribution chip only: it does not suppress content, does not generate an absence reason code, and does not exclude the module from any count, filter, search index or export on this page. **Family taxonomy** is renderer-level presentation config, not a JID field. Colour is always duplicated in text and is never the sole carrier of meaning. **Suppressed by doctrine:** derived risk score; per-module RAG traffic light; `derived_scores` = `{"legal_accessibility": {"per_product": {"account_to_account": "regulated", "cards": "regulated"}}}`. **Band honesty:** uncertainty bands are computed against a frozen build clock of 2026-10-21. A year-precision row is never promoted into a tighter band. **Orphan deltas:** 1 cycle_delta row(s) target non-module objects and are listed in the rail rather than attached to a card. **Envelope:** baseline resolved at `jurisdiction_json.baseline`; 14 module(s), 63 finding(s), 138 source(s) in the cumulative register. **Audit trail** Machine check Challenged on 27 Sep 2026: nothing tested (no claim on this page was eligible for an automated test). An automated, adversarial test run by a second model; no person has assessed the result. Think something on this page is wrong? [Report an error](https://payments.gi/legal/#contact).