US-DC · run world-payments-2026-07-05 v13.3.0
content: ai_generated 143 sources retrieved model claude-sonnet-5 ·

United States – District of Columbia

US-DC schema world-payments-v1 trajectory: not recorded

Last updated · 14 modules · 68 sourced findings · 143 sources in the cumulative register

14Modulesbaseline.modules[]
68Findingsmodules[].findings[]
61Tier-1 sourcesrun_metadata.t1_source_count
Confidence mix (sums to 14 rendered modules; click to filter)

Jurisdiction brief

Lead Signal

Washington, DC enters this baseline cycle as a jurisdiction where the most consequential payments-regulatory development is not local at all: the Federal Reserve, headquartered in the District, has proposed a new "Payment Account" access tier for nonbank and fintech firms, triggered by a 19 May 2026 Executive Order directing regulators to reduce fintech market-access barriers. The proposed Payment Account is deliberately narrower than a full Reserve Bank Master Account — it excludes FedACH access and correspondent/respondent relationships, and imposes a Closing Balance Limit set at the lesser of $500 million or 10% of the holder's total assets, with no interest paid and no discount-window access. Federal Reserve Governor Michael Barr's dissent on the proposal signals that the eventual final rule may face pressure to incorporate more robust AML/BSA requirements and oversight, leaving the settlement-access reform's ultimate shape unresolved. Because the Fed's rulemaking apparatus sits in DC, the District functions as the policy epicentre for this reform even though the substantive rule is a national one; DC-domiciled nonbank PSPs and digital-asset firms are direct stakeholders in whether a Payment Account ultimately gives them federal settlement rails without the full privileges — or costs — of a Master Account.

14 of 14 modules
Signal
Density

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

#

DC regulates payments licensing through DISB under the Money Transmitters Act of 2000 (DC Code Ch.26-10), a bank-vs-nonbank dual structure typical of the US state model, with DISB also chartering DC banks/trust companies; crypto/virtual-currency activity is explicitly captured as money transmission.

Movement — NEWestablishedFirst-time capture of DC Money Transmitters Act and DISB virtual-currency guidance.
Standing sub-brief319 words · last cycle wpm-2026-08-06

Licensing, Authorisation & Market Access

Washington, DC regulates payments licensing through a single statutory anchor: the Money Transmitters Act of 2000 (DC Code Ch. 26-10), administered by the Department of Insurance, Securities and Banking (DISB). Money transmission activity in DC requires a licence from DISB under this Act, absent an applicable exemption — the foundational dual bank/nonbank licensing structure typical of the US state-by-state model. DISB's non-depository licensing instructions impose a prudential floor on applicants: money transmitter applicants must show net worth of not less than $100,000, plus an additional $50,000 net worth per authorised delegate for multi-location licensees, a capital requirement designed to ensure a baseline of financial resilience before a nonbank is permitted to move consumer funds.

Periodic update · new data 2026-08-11 · run wpm-2026-08-06

Licensing, Authorisation & Market Access

The District of Columbia's payments-licensing baseline rests on the DC Money Transmitters Act, codified at D.C. Code Title 26, Chapter 10, which defines money transmission and requires a DISB-issued licence absent exemption. DISB's own guidance confirms this squarely: no person may engage in money transmission in the District without a DISB licence, with applications processed through the Nationwide Multistate Licensing System, the same multistate infrastructure used across most US money-transmitter regimes. This positions DC's nonbank payments licensing pathway as broadly consistent with peer state regimes in structure, even though DC is a federal district rather than a state.

A distinct and less firmly sourced feature of DC's licensing perimeter is DISB's reported position, via a secondary account rather than DISB's own primary bulletin text, that Bitcoin and virtual-currency money transmission, including kiosk-based, application-based, and custodial models, falls within the same money-transmitter licensing requirement, with the regulator citing United States v. Harmon as its legal anchor. If confirmed against DISB's own primary text, this would place crypto-adjacent nonbank operators under the identical NMLS-based licensing pathway as traditional money transmitters, with no DC-specific virtual-currency carve-out identified this cycle. This finding is carried at Assessed rather than High confidence pending that primary-source confirmation.

Standard licence conditions, per a single Tier 4 licensing-intermediary summary not independently corroborated this cycle, reportedly include a surety bond ranging from 25,000 to 500,000 dollars, a minimum net worth requirement of 100,000 dollars, audited financial statements, a BSA/AML compliance program, background checks for control persons, and annual licence renewal by December 31. These terms should be treated as indicative of the general DC money-transmitter licensing burden rather than as confirmed regulatory text.

DISB's licensing perimeter extends well beyond payments specifically. The Department's own 2026 SR0 budget submission confirms that DISB's oversight spans state-chartered banks, mortgage lenders and brokers, check cashers, consumer sales finance companies, money lenders, and student loan servicers. This matters for market-access analysis because DC does not maintain a payments-only regulator; nonbank payment institutions and money transmitters sit within a single regulator's much broader nonbank-credit and banking supervisory remit.

Outlook

The single most consequential open item for this module is confirmation of the DISB virtual-currency money-transmission bulletin against DISB's own primary published text rather than a secondary account; that confirmation would materially raise confidence in DC's crypto-inclusive licensing position. Secondary items worth tracking include whether DISB publishes updated or more granular licensing-condition guidance that would allow independent corroboration of the currently single-sourced surety-bond and net-worth figures.

Sources and findings (6)
  1. T1https://code.dccouncil.gov/us/dc/council/code/sections/26-1001retrieved
  2. T1https://disb.dc.gov/sites/default/files/dc/sites/disb/publication/attachments/non_dep_initial_lic_inst_4_14_05_corrected.pdfretrieved
  3. T3https://suretygroup.com/surety-bond/district-of-columbia-money-transmitter-bond/retrieved
  4. T1https://disb.dc.gov/sites/default/files/dc/sites/disb/page_content/attachments/bulletin-disb-cryptocurrency-money-transmission-approved.pdfretrieved
  5. T3https://www.investmentmonitor.ai/sponsored/why-washington-dc-should-be-the-first-tap-for-fintech/retrieved
  6. T1https://disb.dc.gov/page/banking-licensing-requirements-fintech-companiesretrieved

#

DC's conduct/safeguarding regime rests on MTA bonding/net-worth requirements plus the general Consumer Protection Procedures Act (CPPA); DISB's Enforcement and Consumer Protection Division investigates conduct violations, and the OAG has begun actively litigating conduct failures (safeguards, fee disclosure, unlicensed activity) against digital-asset kiosk operators.

Standing sub-brief264 words · last cycle wpm-2026-07-05

Conduct, Safeguarding & Promotions

DC's approach to safeguarding customer funds diverges from the segregation-of-funds trust model used elsewhere: DC money transmitters satisfy financial-responsibility and safeguarding obligations via a surety bond, with a minimum of $50,000 scaling to a maximum of $250,000, filed through NMLS as part of DISB licensure, rather than through a trust-based segregation regime. This bond-based approach is DC's core consumer-fund-protection mechanism and contrasts with the UK/EU segregation-of-funds approach that safeguarding-focused jurisdictions increasingly favour.

No periodic updates recorded against this sub-brief.

Sources and findings (5)
  1. T3https://suretygroup.com/surety-bond/district-of-columbia-money-transmitter-bond/retrieved
  2. T1https://disb.dc.gov/sites/default/files/dc/sites/disb/publication/attachments/non_dep_initial_lic_inst_4_14_05_corrected.pdf
  3. T1https://disb.dc.gov/page/disb-divisionsretrieved
  4. T1https://oag.dc.gov/consumer-protection/other-consumer-help-agencies-and-websites/submit-consumer-complaint/district-columbia-consumer-protection-lawsretrieved
  5. T3https://www.forbes.com/sites/ajdhaliwal/2026/03/10/state-enforcement-is-defining-the-rules-for-digital-asset-companies/retrieved

#

DC has no bespoke stablecoin statute; digital-asset activity is captured under the existing Money Transmitters Act (per the 2022 DISB bulletin and the Harmon precedent), overlaid by the new federal GENIUS Act framework and pending FinCEN/OFAC AML rulemaking for stablecoin issuers.

Open gap — wpm-int-3DC has no DC-specific (sub-federal) stablecoin issuance statute; the module relies entirely on the federal GENIUS Act overlay and MTA-based crypto capture.no under-indexing note recorded
Open gap — wpm-int-5The FinCEN/OFAC GENIUS Act AML/sanctions NPRM remains in proposed status (comment period closed 9 June 2026); the final-rule publication date and resulting 12-month effective date are not yet set and could not be added to regulatory_horizon without fabricating a date.no under-indexing note recorded
Standing sub-brief266 words · last cycle wpm-2026-07-05

Stablecoins & Digital Money

DC has no bespoke sub-federal stablecoin issuance statute; digital-asset activity in the District is captured entirely under the existing Money Transmitters Act, an arrangement now overlaid by two federal developments. The GENIUS Act, signed into law on 18 July 2025, creates the first federal regulatory framework for payment stablecoins, including issuer licensing and reserve-backing requirements, forming the overlay federal layer above DC's MTA-based crypto treatment. Underneath that federal layer, DC's own MTA-based capture of virtual currency rests on the July 2020 Harmon decision from the US District Court for DC, which held that the Money Transmitters Act, though it does not define "money," extends to virtual currency because Bitcoin functions as a medium of exchange and store of value — the precedent underpinning DISB's 2022 crypto bulletin.

No periodic updates recorded against this sub-brief.

Sources and findings (5)
  1. T3https://www.atlanticcouncil.org/blogs/new-atlanticist/four-questions-and-expert-answers-on-the-new-us-cryptocurrency-legislation/
  2. T1https://www.consumerfinancemonitor.com/2022/08/25/d-c-department-of-insurance-securities-and-banking-issues-bulletin-on-money-transmission/retrieved
  3. T1https://www.consumerfinancemonitor.com/2022/08/25/d-c-department-of-insurance-securities-and-banking-issues-bulletin-on-money-transmission/
  4. T1https://www.arnoldporter.com/en/perspectives/advisories/2026/04/implementing-the-genius-act-fincen-and-ofac-proposeretrieved
  5. T3https://technical.ly/civics/stablecoins-crypto-regulation-midterm-elections/retrieved

#

DC has no standalone operational-resilience statute; DC-chartered banks and DISB-licensed nonbanks fall under the federal interagency cybersecurity/operational-resilience framework (OCC/FDIC/Federal Reserve), with DISB coordinating examinations jointly with federal regulators.

Standing sub-brief121 words · last cycle wpm-2026-07-05

Operational Resilience & Critical Infra

DC has no standalone operational-resilience statute of its own. DC-chartered banks and their service providers instead fall under the federal interagency cybersecurity and operational-resilience framework, including the Computer-Security Incident Notification Final Rule and the "Sound Practices to Strengthen Operational Resilience" guidance issued by federal banking regulators. DISB examinations of DC-regulated institutions may be conducted jointly with federal regulators such as the OCC, reflecting a joint federal/DC oversight model for resilience-relevant institutions rather than a District-specific supervisory regime.

No periodic updates recorded against this sub-brief.

Sources and findings (4)
  1. T1https://www.fdic.gov/banker-resource-center/information-technology-it-and-cybersecurityretrieved
  2. T1https://www.federalreserve.gov/supervisionreg/cybersecurity-and-operational-resilience.htmretrieved
  3. T1https://disb.dc.gov/page/examination-reportsretrieved
  4. T1https://www.fdic.gov/banker-resource-center/information-technology-it-and-cybersecurityretrieved

#

DC allows card surcharging under disclosure rules enforced via the CPPA; a swipe-fee/interchange restriction bill has been introduced in the DC Council (following the Fair SWIPE coalition model) but is not yet enacted, while federal Durbin Amendment debit-interchange rules and PCI DSS apply nationally.

Open gap — wpm-int-4The pending DC Council swipe-fee/surcharge bill (Fair SWIPE Coalition model) lacks a confirmed bill number, sponsor, or current legislative status; only trade-press (T3) coverage is available. Requires DC Council legislative-record verification.no under-indexing note recorded
Standing sub-brief201 words · last cycle wpm-2026-07-05

Scheme & Network Compliance

The federal Durbin Amendment (Regulation II) requires that debit-card interchange fees be reasonable and proportional to issuer cost, applying uniformly to DC-based debit issuers and acquirers as the national interchange baseline. Layered on top of PCI DSS — the technical standard maintained by the PCI Security Standards Council (American Express, Discover, JCB, Mastercard, and Visa) and binding on all card-accepting entities in DC per OCC merchant-processing guidance — this federal and scheme-level architecture governs card-network compliance in the District today.

No periodic updates recorded against this sub-brief.

Sources and findings (5)
  1. T1https://uscode.house.gov/view.xhtml?req=%28title%3A15+section%3A1693o-2+edition%3Aprelim%29retrieved
  2. T3https://www.paymentsjournal.com/d-c-may-experiment-with-swipe-fee-limits/retrieved
  3. T3https://wusa9.com/article/news/investigations/initiative82-resturant-fees-credit-card-surcharges-clydes-travelers-united-resturant-association-of-metropolitan-washington-ramw/65-b72f69eb-94f8-4eb0-9f0f-7d50ca7313b0retrieved
  4. T1https://www.occ.treas.gov/publications-and-resources/publications/comptrollers-handbook/files/merchant-processing/pub-ch-merchant-processing.pdfretrieved
  5. T3https://www.getflexpoint.com/credit-card-surcharging-us-states/washington-dc-district-of-columbiaretrieved

#

DC has no independent corridor/rail regulatory authority; cross-border and remittance activity in the District is governed by federal payment-system infrastructure (Fedwire, ACH, SWIFT), with DC functioning primarily as a policy/licensing gateway (e.g., for cross-border fintechs) rather than an operator of its own corridor rails.

Open gap — wpm-int-1DC has no jurisdiction-specific corridor/rail regulatory instrument; W5 coverage rests on general federal infrastructure (Fedwire/ACH/SWIFT) and a single market-entry event (Navro).US state-level divergence in corridor/rail policy is a bias-correction priority area; DC's thin native corridor authority should be monitored for any emerging local initiatives.
Standing sub-brief164 words · last cycle wpm-2026-07-05

Payment Corridor Dynamics

DC has no independent corridor or rail regulatory authority of its own; cross-border and remittance activity in the District is governed by general federal payment-system infrastructure rather than any DC-specific corridor rule. The clearest concrete corridor-relevant signal this cycle is commercial rather than regulatory: Navro's September 2025 DC money transmitter licence acquisition functions as a US market-entry gateway for its UK-originated cross-border payments platform, reflecting DC's role as a policy and licensing gateway rather than an independent operator of corridor rails. DISB itself lists SWIFT's global messaging platform — connecting more than 11,000 institutions across over 200 countries — as a relevant financial-industry authority for DC-regulated entities' cross-border activity, an infrastructure reference point rather than a DC-specific corridor rule.

No periodic updates recorded against this sub-brief.

Sources and findings (2)
  1. T3https://www.investmentmonitor.ai/sponsored/why-washington-dc-should-be-the-first-tap-for-fintech/retrieved
  2. T1https://disb.dc.gov/page/financial-industry-regulatory-authoritiesretrieved

#

DC hosts a mid-sized but policy-dense fintech/payments cluster (214 active fintech companies, ~12% of the local startup base) alongside major national financial-infrastructure bodies headquartered in the District (ABA, FINRA, Fannie Mae), with 2025 fintech equity funding down sharply year-on-year.

Standing sub-brief207 words · last cycle wpm-2026-07-05

Industry Structure & Commercial

As of May 2026, DC hosts 214 active fintech companies, roughly 12% of the District's local startup base, with insurtech Pie Insurance the sector's highest-funded company at $625 million raised; the sector has recorded 23 acquisitions and one IPO cumulatively. This establishes DC as a mid-sized, policy-dense fintech cluster rather than a payments-volume hub. That structural baseline sits against a cooling commercial signal: in 2025 (through December), DC fintech companies raised $14.4 million in equity funding across four rounds, a 76.26% drop versus $60.8 million across six rounds in the same 2024 period — a sharp year-on-year contraction signalling cooling local venture appetite for DC-based payments and fintech despite active federal policy tailwinds. DC's commercial structure is reinforced by the presence of major industry bodies: the American Bankers Association, the trade association for US community, regional, and money-center banks, is headquartered in Washington, DC.

No periodic updates recorded against this sub-brief.

Sources and findings (5)
  1. T3https://tracxn.com/d/explore/fintech-startups-in-washington-dc-united-states/__fmqUw3UmZKUObvWxTfLWBfMREJrJ7pvugaHNaB3ZHfU#top-companiesretrieved
  2. T3https://tracxn.com/d/explore/fintech-startups-in-washington-dc-united-states/__fmqUw3UmZKUObvWxTfLWBfMREJrJ7pvugaHNaB3ZHfU#top-companiesretrieved
  3. T3https://growthlist.co/washington-dc-startups/retrieved
  4. T3https://tracxn.com/d/explore/fintech-startups-in-washington-dc-united-states/__fmqUw3UmZKUObvWxTfLWBfMREJrJ7pvugaHNaB3ZHfU#top-companiesretrieved
  5. T3https://builtin.com/companies/location/washington-dc/type/fintech-companiesretrieved

DC's OAG has become an active payments/fintech litigator, pursuing both digital-asset kiosk operators (Athena Bitcoin) and earned-wage-access providers (EarnIn) under the CPPA and MTA, building on the foundational Harmon crypto-money-transmission precedent, while the OAG's Office of Consumer Protection has recovered over $125M since 2015.

Open gap — wpm-int-6Prior-draft research summary mischaracterised the DC OAG's Athena Bitcoin complaint as alleging unlicensed money-transmission operation; corrected in this cycle's claims/patches per baseline challenge finding f-001. Downstream composer outputs referencing this case should use the corrected framing.no under-indexing note recorded
Standing sub-brief248 words · last cycle wpm-2026-07-05

Legal & Litigation

DC's Office of the Attorney General is an active payments and fintech litigator. On 8 September 2025, the OAG sued Athena Bitcoin, alleging Consumer Protection Procedures Act and Financial Exploitation of Vulnerable Adults Act violations — undisclosed kiosk fees, inadequate anti-fraud safeguards, and refusal of scam-victim refunds; the complaint does not plead unlicensed money-transmission operation as a cause of action. Separately, in DC OAG v. EarnIn, the DC Attorney General sued in 2024 alleging deceptive marketing of illegal high-interest earned-wage-access loans carrying a 24%-per-year cap; the DC Superior Court dismissed a portion of the case in May 2025, leaving the question of EWA's credit classification to lawmakers and regulators rather than enforcement, and the DC Court of Appeals declined to hear an interlocutory appeal in February 2026, while other claims — including false advertising — remain ongoing. Both cases build on the Harmon precedent's foundational holding that DC's MTA reaches virtual-currency activity. Underpinning this litigation record, OAG's Office of Consumer Protection has secured more than $125 million in penalties and restitution for DC consumers since 2015 across more than 13,000 complaints.

No periodic updates recorded against this sub-brief.

Sources and findings (6)
  1. T3https://www.forbes.com/sites/ajdhaliwal/2026/03/10/state-enforcement-is-defining-the-rules-for-digital-asset-companies/
  2. T2https://www.americanbanker.com/payments/news/why-earnins-d-c-court-win-is-a-victory-for-all-ewa-fintechsretrieved
  3. T2https://www.americanbanker.com/payments/news/why-earnins-d-c-court-win-is-a-victory-for-all-ewa-fintechsretrieved
  4. T1https://www.consumerfinancemonitor.com/2022/08/25/d-c-department-of-insurance-securities-and-banking-issues-bulletin-on-money-transmission/retrieved
  5. T1https://oag.dc.gov/release/office-attorney-generals-consumer-protectionretrieved
  6. T3https://www.washingtoninformer.com/dc-oag-legal-defense-savings/retrieved

#

DC merchant acquiring operates under the national OCC/FDIC merchant-processing risk-management framework (card-network MATCH/high-risk-merchant monitoring, chargeback liability rules) with DC's own contribution being CPPA-based surcharge-disclosure enforcement and an active DC Council debate over interchange/surcharge structuring.

Standing sub-brief123 words · last cycle wpm-2026-07-05

Merchant Acquiring & Risk

The OCC's Comptroller's Handbook on Merchant Processing frames acquirer and third-party risk decisions — chargeback liability, merchant-relationship loss, and fines — as the governing federal risk framework applicable to DC-chartered and national acquiring institutions. Layered above this federal baseline, Visa's Global Acquirer Risk Standards, Mastercard's High-Risk Merchant Monitoring program, and American Express's Merchant Risk Management framework apply nationally, including to DC-domiciled acquirers and merchants, forming a scheme-level high-risk-merchant monitoring layer on top of the OCC framework.

No periodic updates recorded against this sub-brief.

Sources and findings (5)
  1. T1https://www.occ.treas.gov/publications-and-resources/publications/comptrollers-handbook/files/merchant-processing/pub-ch-merchant-processing.pdfretrieved
  2. T1https://www.fdic.gov/news/financial-institution-letters/2012/fil12003.pdfretrieved
  3. T3https://blog.basistheory.com/high-risk-merchantretrieved
  4. T3https://wusa9.com/article/news/investigations/initiative82-resturant-fees-credit-card-surcharges-clydes-travelers-united-resturant-association-of-metropolitan-washington-ramw/65-b72f69eb-94f8-4eb0-9f0f-7d50ca7313b0retrieved
  5. T3https://www.paymentsjournal.com/d-c-may-experiment-with-swipe-fee-limits/retrieved

#

DISB's Office of Innovation and the DC BizCAP program actively position DC as a regulated fintech/regtech hub, hosting the annual DC Fintech Summit; the pending federal Reserve 'Payment Account' initiative (triggered by a May 2026 Executive Order) is a major forthcoming access-innovation development directly relevant to DC-based/DC-regulated payments firms.

Standing sub-brief187 words · last cycle wpm-2026-07-05

Product Innovation & Market Development

DISB's Office of Innovation and the DC BizCAP Innovation Finance Program, which has allocated $13.2 million, actively support DC's positioning as a regulated fintech and regtech hub, alongside the annual DC Fintech Summit; DISB's Office of Innovation co-hosted the second annual DC Fintech Summit on 14 October 2025 with the DC Tech and Venture community, featuring discussion of the GENIUS Act's stablecoin framework and the stalled CLARITY Act. The more consequential development this cycle, however, is federal: triggered by a 19 May 2026 Executive Order directing regulators to reduce fintech market-access barriers, the Federal Reserve has proposed a "Payment Account" — narrower than a full Master Account, excluding ACH access and a correspondent/respondent role, with capped end-of-day balances — for nonbank and fintech settlement access, a major forthcoming access-innovation development for DC-based and DC-regulated payments firms.

No periodic updates recorded against this sub-brief.

Sources and findings (5)
  1. T1https://disb.dc.gov/innovationretrieved
  2. T1https://disb.dc.gov/page/dc-bizcap-innovation-finance-program-0retrieved
  3. T3https://www.dctav.co/blog-posts/2nd-annual-dc-fintech-summit-2025retrieved
  4. T1https://www.mayerbrown.com/en/insights/publications/2026/05/federal-reserve-access-for-fintechs-executive-order-and-federal-reserve-payment-account-proposal-signal-potential-new-era-for-fintech-payment-accessretrieved
  5. T3https://www.investmentmonitor.ai/sponsored/why-washington-dc-should-be-the-first-tap-for-fintech/retrieved

#

DC consumer protection rests on the CPPA (private right of action, treble damages) and the Security Breach Protection Amendment Act (AG notification, 18-month ID-theft-protection mandate); DISB's Consumer Services Division and OAG's Office of Consumer Protection provide complaint/mediation channels, with the EarnIn and Athena Bitcoin cases illustrating live APP-fraud/predatory-product enforcement.

Standing sub-brief144 words · last cycle wpm-2026-07-05

Consumer Protection & APP Fraud

DC's Consumer Protection Procedures Act provides a private right of action: harmed consumers may sue for treble damages (or $1,500 per violation if greater), punitive damages, attorney's fees, and injunctive relief, with enforcement available through the OAG in DC Superior Court — the core consumer-protection statute underpinning DC's APP-fraud and predatory-product enforcement, including the Athena Bitcoin and EarnIn matters. Separately, DC's Security Breach Protection Amendment Act requires Attorney General notification for breaches affecting 50 or more DC residents and mandates 18 months of identity-theft-protection coverage for affected residents, forming DC's consumer-remedy breach-notification baseline.

No periodic updates recorded against this sub-brief.

Sources and findings (5)
  1. T1https://oag.dc.gov/consumer-protection/other-consumer-help-agencies-and-websites/submit-consumer-complaint/district-columbia-consumer-protection-lawsretrieved
  2. T1https://www.dwt.com/blogs/privacy--security-law-blog/2020/05/washington-dc-new-data-breach-notification-lawretrieved
  3. T1https://disb.dc.gov/page/consumer-services-divisionretrieved
  4. T1https://oag.dc.gov/release/office-attorney-generals-consumer-protectionretrieved
  5. T2https://www.americanbanker.com/payments/news/why-earnins-d-c-court-win-is-a-victory-for-all-ewa-fintechsretrieved

#

DC-licensed money transmitters/MSBs sit under the federal BSA/FinCEN AML/CFT regime (registration, SAR filing, recordkeeping); the Sentinel payments-context posture for this baseline reflects the current federal enforcement stance — a DOJ shift away from crypto 'regulation by prosecution' alongside FinCEN's active MSB-focused BSA enforcement and pending AML/CFT program reform (including GENIUS Act stablecoin issuer rules).

Open gap — wpm-int-2No direct Sentinel.gi platform feed record was available for W11 this baseline; the module was substituted with federal FinCEN/BSA/DOJ payments-context AML posture applicable to DC-registered MSBs.no under-indexing note recorded
Standing sub-brief212 words · last cycle wpm-2026-07-05

AML/CFT & Financial Crime (Sentinel.gi-fed)

This module's intelligence is sourced from the Sentinel.gi feed; WPM does not conduct original illicit-finance analysis here and instead attributes and links out to Sentinel's findings. FinCEN's multi-tiered border operation targeted more than 100 US money services businesses, producing six notices of investigation, dozens of IRS examination referrals, and more than 50 compliance outreach letters, forming part of the BSA-enforcement posture applicable to DC-registered MSBs. FinCEN has also proposed a rule that would fundamentally reform financial institutions' BSA/AML-CFT programs as part of Treasury's broader modernisation effort. Set against this enforcement and reform activity, the Department of Justice's April 2025 memorandum from Deputy Attorney General Blanche instructed federal prosecutors to cease pursuing actions that effectively superimpose regulatory frameworks onto digital assets — a "regulation by prosecution" policy shift. The GENIUS Act's stablecoin AML proposal itself largely mirrors proposed BSA/AML revisions for banks and broker-dealers, formalising risk-assessment and customer-due-diligence requirements into a unified AML/CFT program for permitted payment stablecoin issuers.

No periodic updates recorded against this sub-brief.

Sources and findings (5)
  1. T1sentinel.fincen-msb-border-operation-2025retrieved
  2. T1sentinel.fincen-amlcft-reform-2026retrieved
  3. T1sentinel.doj-regulation-by-prosecution-2025retrieved
  4. T1sentinel.genius-act-amlcft-2026retrieved
  5. T3sentinel.dc-msb-fincen-registrationretrieved

#

The Federal Reserve Board — headquartered in DC — is actively re-architecting nonbank/fintech access to central-bank settlement rails via a proposed 'Payment Account' (narrower than a full Master Account, no ACH, no correspondent/respondent role, capped balances), triggered by a May 2026 Executive Order, with unresolved AML/BSA concerns raised in Governor Barr's dissent.

Standing sub-brief201 words · last cycle wpm-2026-07-05

Correspondent Banking, Settlement & Access

The Federal Reserve Board — headquartered in DC — has proposed a "Payment Account," triggered by the 19 May 2026 Executive Order directing a comprehensive evaluation of Reserve Bank payment-account and service access for uninsured depository institutions and nonbank financial companies, including digital-asset firms. The proposal excludes FedACH access and correspondent/respondent relationships, and imposes a Closing Balance Limit at the lesser of $500 million or 10% of the holder's total assets, with no interest paid and no discount-window access — constraints that shape which business models a Payment Account, as distinct from a full Master Account, can support. Federal Reserve Governor Michael Barr's dissent signals the final rule may face pressure to incorporate more robust AML/BSA requirements and oversight, an unresolved tension in this correspondent and settlement-access reform.

No periodic updates recorded against this sub-brief.

Sources and findings (5)
  1. T1https://www.federalreserve.gov/paymentsystems/master-account-and-services-database-existing-access.htmretrieved
  2. T1https://www.mayerbrown.com/en/insights/publications/2026/05/federal-reserve-access-for-fintechs-executive-order-and-federal-reserve-payment-account-proposal-signal-potential-new-era-for-fintech-payment-accessretrieved
  3. T1https://www.dwt.com/blogs/financial-services-law-advisor/2026/01/federal-reserve-proposes-skinny-master-accountsretrieved
  4. T1https://www.mayerbrown.com/en/insights/publications/2026/05/federal-reserve-access-for-fintechs-executive-order-and-federal-reserve-payment-account-proposal-signal-potential-new-era-for-fintech-payment-accessretrieved
  5. T1https://www.mayerbrown.com/en/insights/publications/2026/05/federal-reserve-access-for-fintechs-executive-order-and-federal-reserve-payment-account-proposal-signal-potential-new-era-for-fintech-payment-accessretrieved

#

The trailing-12-month DC commercial picture is dominated by one notable market-entry licensing event (Navro), a sharp YoY decline in local fintech equity funding, and continued OAG enforcement activity against payments/digital-asset firms — offset by DISB's ongoing innovation-hub programming (DC Fintech Summit).

Movement — NEWestablishedFirst-time capture of the B26-0656 payments-adjacent stored-value/token implication.
Standing sub-brief157 words · last cycle wpm-2026-08-06

Commercial Intelligence (M&A, Investment & Product)

UK fintech Navro's September 2025 DC money transmitter licence acquisition is the standout DC commercial and market-entry event of the trailing 12 months, illustrating the DC MTL as a credible US-market entry vehicle for European cross-border payments platforms; this event does not cleanly map to the m_and_a, investment, product_release, or partnership_restructuring categories and is rendered here as a market-entry/licensing event rather than a discrete commercial_events[] record. The dominant trailing-12-month commercial-intelligence signal for the jurisdiction, however, is aggregate rather than a single deal: DC fintech equity funding fell 76% year-on-year in 2025 ($14.4 million versus $60.8 million in 2024), a sharp contraction that offsets DC's innovation-hub positioning.

Periodic update · new data 2026-08-11 · run wpm-2026-08-06

Commercial Intelligence & Fintech

The only commercial-intelligence-relevant development identified for the District of Columbia this cycle is not, strictly speaking, a payments-sector commercial event: it is a pending piece of gambling legislation, DC Council Bill 26-0656, that carries a payments-adjacent product-structure implication. The bill would ban dual-currency sweepstakes and token-redemption stored-value platform models outright, with civil fines of up to 100,000 dollars per violation. No DC-specific payments-sector mergers and acquisitions, investment or funding rounds, or product launches were identified this cycle; the coverage gap here reflects thin dedicated payments trade-press attention to this jurisdiction relative to federal or state-level peers, a structural under-indexing rather than confirmed absence of commercial activity.

Bill 26-0656's relevance to this module is narrow but specific: sweepstakes-style platforms commonly rely on dual-currency, token-redemption stored-value structures to operate in jurisdictions where traditional real-money gambling is not authorized, and a jurisdiction-level ban on that specific product structure is a signal worth tracking for any commercial entity operating, or considering operating, such a stored-value model in or toward the District. The bill's civil-fine mechanism, at up to 100,000 dollars per violation, indicates the District intends this as an enforceable prohibition rather than a purely declaratory policy statement, should the bill pass.

Outlook

This module's coverage for DC will remain thin until either a genuine payments-sector commercial event is identified, or Bill 26-0656's product-structure-relevant provisions move from proposed to enacted status. Given the structural under-indexing of DC-specific payments trade press noted in this cycle's research, absence of a finding in a future cycle should not be read as confirmed no-activity without independent verification.

Sources and findings (5)
  1. T3https://www.investmentmonitor.ai/sponsored/why-washington-dc-should-be-the-first-tap-for-fintech/retrieved
  2. T3https://tracxn.com/d/explore/fintech-startups-in-washington-dc-united-states/__fmqUw3UmZKUObvWxTfLWBfMREJrJ7pvugaHNaB3ZHfU#top-companiesretrieved
  3. T3https://www.forbes.com/sites/ajdhaliwal/2026/03/10/state-enforcement-is-defining-the-rules-for-digital-asset-companies/retrieved
  4. T3https://www.hudsoncook.com/article/cfpb-files-action-against-fintech-bank-partner-for-alleged-unfair-practices-related-to-record-keeping-of-consumer-funds/retrieved
  5. T3https://www.youtube.com/watch?v=TvRHbB3KCAsretrieved
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 – District of Columbia
FieldValue
trust.lawyer_review.statusnever_reviewed
trust.lawyer_review.reviewernot recorded
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": {"cards": "regulated", "stablecoin": "emerging-regime"}}}.

Band honesty: uncertainty bands are computed against a frozen build clock of 2026-08-11. 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), 68 finding(s), 161 source(s) in the cumulative register.