US-OR v13.3.0
content: ai_generated 143 sources retrieved model claude-sonnet-5 · 2026-07-05

United States – Oregon

US-OR schema world-payments-v1 trajectory: not yet assessed

Last updated · 14 modules · 63 sourced findings · 138 sources in the cumulative register

14Modulesbaseline.modules[]
63Findingsmodules[].findings[]
35Tier-1 sourcesrun_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 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.

14 of 14 modules
Signal
Density

Selections OR within a group, AND across groups. Press / to search.

#

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 2026132 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.

no periodic updates on record for this sub-brief

Sources and findings (7)
  1. T1https://oregon.public.law/statutes/ors_717.205retrieved
  2. T1https://dfr.oregon.gov/business/licensing/financial/pages/money-transmitters.aspxretrieved
  3. T1https://oregon.public.law/statutes/ors_717.205retrieved
  4. T1https://apps.oregon.gov/SOS/LicenseDirectory/LicenseDetail/21retrieved
  5. T1https://secure.sos.state.or.us/oard/displayDivisionRules.action?selectedDivision=2162retrieved
  6. T3https://www.bondexchange.com/oregon-money-transmitter-bond-a-comprehensive-guide/retrieved
  7. T3https://moneytransmitterlaw.com/state-laws/oregon/retrieved

#

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 2026429 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.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and findings (5)
  1. T1https://www.oregonlegislature.gov/bills_laws/ors/ors717.htmlretrieved
  2. T3https://legalclarity.org/oregon-unlawful-trade-practices-act-violations-and-remedies/retrieved
  3. T1https://secure.sos.state.or.us/oard/view.action?ruleNumber=441-745-0340
  4. T1https://www.oregonlegislature.gov/bills_laws/ors/ors717.htmlretrieved
  5. T1https://www.doj.state.or.us/consumer-protection/about-us/retrieved

#

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 2026111 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.

no periodic updates on record for this sub-brief

Sources and findings (5)
  1. T2https://stevenscenter.wharton.upenn.edu/publications-50-state-review/retrieved
  2. T2https://stevenscenter.wharton.upenn.edu/publications-50-state-review/retrieved
  3. T1https://dfr.oregon.gov/help/Documents/5342-cryptocurrency.pdfretrieved
  4. T3https://moneytransmitterlaw.com/cryptocurrency-state-laws/oregon/retrieved
  5. T1https://www.doj.state.or.us/wp-content/uploads/2025/05/Oregon-v.-Coinbase-Complaint.pdfretrieved

#

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.

Standing sub-brief · as of 5 July 2026126 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.

no periodic updates on record for this sub-brief

Sources and findings (4)
  1. T1https://www.occ.gov/news-issuances/bulletins/2021/bulletin-2021-55.htmlretrieved
  2. T1https://www.federalreserve.gov/supervisionreg/cybersecurity-and-operational-resilience.htmretrieved
  3. T1https://www.doj.state.or.us/consumer-protection/id-theft-data-breaches/data-breaches/retrieved
  4. T3https://www.recordinglaw.com/us-laws/data-privacy-laws/oregon-data-privacy-laws/data-breach-notification/retrieved

#

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 2026113 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.

no periodic updates on record for this sub-brief

Sources and findings (5)
  1. T3https://merchantcostconsulting.com/lower-credit-card-processing-fees/oregon-surcharge-laws/retrieved
  2. T1https://oregon.public.law/statutes/ors_825.502retrieved
  3. T1https://oregon.public.law/statutes/ors_802.112retrieved
  4. T3https://ebizcharge.com/blog/credit-card-surcharging-a-state-by-state-legal-analysis/retrieved
  5. T3https://pivitstrategy.com/oregon-cybersecurity-laws-you-should-know-2026/retrieved

#

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 2026110 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.

no periodic updates on record for this sub-brief

Sources and findings (3)
  1. T3https://thedialogue.org/blogs/2025/04/the-state-of-the-remittance-industry-and-an-outlook-for-2025retrieved
  2. T3https://www.bankingdive.com/news/fednow-instant-payments-real-time-banks-credit-unions-transactions/688516/retrieved
  3. T3https://www.nerdwallet.com/banking/learn/banks-that-use-fednowretrieved

#

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 2026118 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.

no periodic updates on record for this sub-brief

Sources and findings (4)
  1. T1https://www.sec.gov/Archives/edgar/data/0001028918/000110465925038087/tm2512834d3_ex99-1.htmretrieved
  2. T1https://www.sec.gov/Archives/edgar/data/0001028918/000110465925040437/tm2512834d10_425.htmretrieved
  3. T1https://www.sec.gov/Archives/edgar/data/0001028918/000110465925038168/tm2512834d4_425.htmretrieved
  4. T4https://freestartupfunding.com/who-funds/fintech/in/oregonretrieved

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 2026136 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.

no periodic updates on record for this sub-brief

Sources and findings (5)
  1. T1https://www.doj.state.or.us/media-home/news-media-releases/oregon-attorney-general-rayfield-sues-coinbase-for-promoting-and-selling-high-risk-investments/retrieved
  2. T3https://www.coindesk.com/policy/2025/06/03/coinbase-moves-to-bring-oregon-securities-suit-to-federal-jurisdictionretrieved
  3. T3https://oregoncapitalchronicle.com/2025/07/15/ag-rayfield-let-campaign-donors-lead-oregons-crypto-case-the-company-hes-suing-wants-answers/retrieved
  4. T1https://www.fincen.gov/news/news-releases/fincen-assesses-civil-money-penalty-against-oregon-based-unregistered-moneyretrieved
  5. T3https://www.cohenmilstein.com/case-study/coinbase-securities-litigation/retrieved

#

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 202671 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. T4https://paybotic.com/markets/oregon/retrieved
  2. T4https://bankcardinternationalgroup.com/the-truth-about-cannabis-payment-processing-what-dispensary-owners-need-to-know/retrieved
  3. T4https://www.thetransactiongroup.net/portland-or-marijuana-dispensary-credit-card-processing/retrieved

#

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-3No Oregon-specific CBDC pilot or open-banking/PSD3-equivalent initiative was identified.no under-indexing note recorded
Standing sub-brief · as of 5 July 2026102 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.

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. T1https://www.federalreserve.gov/paymentsystems/fednow_faq.htmretrieved
  2. T3https://www.nerdwallet.com/banking/learn/banks-that-use-fednowretrieved
  3. T4https://www.failory.com/startups/oregonretrieved
  4. T4https://builtin.com/companies/location/na/usa/or/type/fintech-startupsretrieved

#

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 2026401 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.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and findings (5)
  1. T3https://legalclarity.org/oregon-unlawful-trade-practices-act-violations-and-remedies/retrieved
  2. T3https://legalclarity.org/oregon-unlawful-trade-practices-act-violations-and-remedies/retrieved
  3. T1https://justice.oregon.gov/consumer/databreach/retrieved
  4. T1https://dfr.oregon.gov/financial/protect/pages/index.aspxretrieved
  5. T1https://dfr.oregon.gov/help/Documents/5342-cryptocurrency.pdfretrieved

#

[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 2026129 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.

no periodic updates on record for this sub-brief

Sources and findings (8)
  1. T3https://www.finscan.com/post/regulatory-roundup-january-2026-debanking-enforcement-and-the-expanding-compliance-perimeterretrieved
  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. T2FIM (sentinel.gi) sanctions_change_register (issue FIM-BASE-SANC-001) — Sanctions: OFAC listing
  6. T2FIM (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

#

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 2026103 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.

no periodic updates on record for this sub-brief

Sources and findings (3)
  1. T1https://www.frbservices.org/financial-services/fednow/organizationsretrieved
  2. T3https://vfccu.org/solutions_mobile/instant-payments.htmlretrieved
  3. T1https://www.oregonlegislature.gov/bills_laws/ors/ors706.htmlretrieved

#

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-4Deal-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 2026132 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.

no periodic updates on record for this sub-brief

Sources and findings (2)
  1. T1https://www.sec.gov/Archives/edgar/data/0001028918/000110465925038087/tm2512834d3_ex99-1.htmretrieved
  2. T4https://freestartupfunding.com/who-funds/fintech/in/oregonretrieved
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
FieldValue
trust.lawyer_review.statusnever_reviewed
trust.lawyer_review.reviewerno reviewer on record
trust.content_sourceai_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 checkChallenged 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.