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

United States – District of Columbia

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

Last updated · 14 modules · 70 sourced findings · 151 sources in the cumulative register

14Modulesbaseline.modules[]
70Findingsmodules[].findings[]
119Tier-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 – District of Columbia is covered once, on the United States page. This page covers United States – District of Columbia’s own layer: its own law, regulators and enforcement.

Jurisdiction brief

Latest update · 18 October 2026

Lead Signal

Two commercial events involving the crypto-kiosk operator Coinme Inc. define this cycle's District of Columbia signal. Coinme has agreed to close down its virtual-currency kiosk operations across multiple states as part of a BSA/AML consent settlement, with the shutdown required by 1 January 2027, and DC's Department of Insurance, Securities and Banking is named as one of 34 participating state regulators in that coordinated action. Separately, and on a faster timeline, Polygon Labs completed its acquisition of Coinme on 14 October 2026, bringing Coinme's multistate money-transmitter footprint, including its District of Columbia money-transmission licence under D.C. Code § 26-1001 et seq., into Polygon's payments stack.

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.

Standing sub-brief · as of 7 July 2026319 words · last cycle 2026-09-28

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-09-28

Licensing, Authorisation & Market Access

The District of Columbia's money-transmitter licensing framework has undergone a statutory recodification this cycle. The former Title 47, Chapter 31 statute is marked repealed in the current DC Code, with money transmission now governed by DC Code Title 26, Chapter 10. DISB is confirmed as the licensing authority under this recodified statute. This is a bank-PSP versus non-bank-PI/EMI relevant finding: DC operates a single general money-transmitter licence tier for non-bank payment businesses, with no separate electronic-money-institution or payment-institution category distinct from the standard MTL.

DISB's primary notice confirms that Bitcoin ATM operators and crypto-exchange kiosk businesses fall within this same licensing perimeter, being treated as money transmitters requiring a DC MTL, with active licensing-compliance monitoring underway since 16 March 2023. This means DC draws no regulatory distinction between a conventional money-services business and a virtual-currency kiosk operator for market-access purposes: both are non-bank payment institutions subject to the same MTL requirement and the same DISB oversight.

A review of DISB's legislation-and-rulemakings status page found no rulemaking not yet final for money transmitters as of this cycle. This is a lower-confidence, dashboard-tier finding rather than a standing-brief-tier finding, but it indicates that, on current evidence, no imminent amendment to the recodified Title 26, Chapter 10 framework is in the pipeline. Taken together, DC's market-access picture for non-bank payment institutions, including virtual-currency businesses, is one of a stable, recently-recodified, single-tier MTL regime under DISB, with no near-term regulatory change signalled on the public rulemaking record.

Outlook

Absent a new rulemaking, the recodified Title 26, Chapter 10 framework is likely to remain the stable licensing basis for non-bank payment institutions in DC, including virtual-currency kiosk and exchange operators, in the near term. The principal open item is confirmation of the precise repealing instrument and date for the former Title 47, Chapter 31 statute, which would complete the statutory-history record for this licensing regime.

1 earlier distinct update(s)
Periodic update · new data 2026-08-11

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-brief · as of 7 July 2026264 words · last cycle 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 on record for 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.pdfretrieved
  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.

Standing sub-brief · as of 7 July 2026266 words · last cycle 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 on record for 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/retrieved
  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/retrieved
  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.

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 →

Standing sub-brief · as of 7 July 2026121 words · last cycle 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 on record for 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.

Standing sub-brief · as of 7 July 2026201 words · last cycle 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 on record for 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.

Standing sub-brief · as of 7 July 2026164 words · last cycle 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 on record for 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-brief · as of 7 July 2026207 words · last cycle 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 on record for 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.

Standing sub-brief · as of 7 July 2026248 words · last cycle 2026-09-21

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.

Periodic update · new data 2026-09-22

Legal & Litigation

DC's data-breach notification statute, D.C. Code Section 28-3852, establishes a confirmed, standing legal obligation on any person or entity conducting business in the District that owns or licenses electronic personal information: upon discovering a security breach, that entity must promptly notify affected DC residents. This is a T1-sourced, established finding, not a new development this cycle, but it is a material component of the legal-exposure picture for payment service providers operating in the District, since it creates a direct compliance obligation triggered by any breach event touching DC-resident data, independent of whichever other state or federal breach regime might also apply to the same incident.

For payment service providers, banks, and non-bank payment institutions serving DC residents, this statute is best understood as a standing incident-response requirement layered onto whatever multi-state breach-notification compliance program the entity already runs. The notification duty attaches based on the residency of affected individuals rather than the location of the breached entity's operations, meaning a PSP with no physical DC presence but with DC-resident customers or cardholders in its affected dataset is still within scope. This distinction matters across the bank-PSP and non-bank PI/EMI line: both are captured on the same terms under the statute, since the obligation is keyed to possession or licensing of electronic personal information rather than to any particular payment-institution licensing category.

Outlook

No new legislative or enforcement development on this statute was identified this cycle. The item to watch is any DC Council or Attorney General activity that would tighten notification timelines, expand the categories of covered personal information, or increase the statutory penalty structure, none of which surfaced in this cycle's research.

Sources and findings (6)
  1. T3https://www.forbes.com/sites/ajdhaliwal/2026/03/10/state-enforcement-is-defining-the-rules-for-digital-asset-companies/retrieved
  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-brief · as of 7 July 2026123 words · last cycle 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 on record for 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-brief · as of 7 July 2026187 words · last cycle 2026-09-21

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.

Periodic update · new data 2026-09-22

Product Innovation & Market Development

The GENIUS Act stablecoin framework is the defining product-innovation development of this cycle at the federal level, with direct relevance to any DC-domiciled or DC-serving payment or digital-asset business. The statute generally prohibits any person other than a permitted issuer from issuing payment stablecoins in the United States, establishing a licensing gate around what has until now been a largely unregulated product category. Implementing rulemaking has progressed on a defined schedule: the OCC issued its notice of proposed rulemaking in February 2026, the FDIC followed in April 2026, and Treasury issued its own NPRM in August 2026, with the comment period on that NPRM open through October 19, 2026. The primary federal stablecoin regulators, spanning the OCC, FDIC, Federal Reserve, and NCUA, were statutorily required to promulgate implementing regulations by July 18, 2026, giving this rulemaking track a defined statutory deadline against which its progress can be measured.

The regime's substantive effective date is targeted for January 18, 2027, or 120 days after final rules are issued, whichever is earlier, meaning the precise date at which permitted-issuer status becomes a hard legal requirement remains contingent on how quickly final rules are published following the current comment period. For product teams evaluating stablecoin issuance, custody, or distribution strategies touching DC-based customers or DC-domiciled entities, this creates a defined near-term planning horizon: any product design that would place a business outside the permitted-issuer perimeter needs to be resolved before the substantive effective date lands, whichever of the two triggering conditions occurs first.

Outlook

The Treasury NPRM comment period closing October 19, 2026 is the immediate milestone to track, followed by the publication of final rules across the OCC, FDIC, and Treasury tracks, which will fix the exact substantive effective date. Product and market-development teams should treat the window between now and that effective date as the active compliance-runway period for any stablecoin-adjacent product strategy.

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-brief · as of 7 July 2026144 words · last cycle 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 on record for 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).

Standing sub-brief · as of 7 July 2026212 words · last cycle 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 on record for this sub-brief

Sources and findings (7)
  1. T3sentinel.dc-msb-fincen-registration
  2. T?FIM (sentinel.gi) per-JID baseline profile — United States — District of Columbia — Federal BSA/USA PATRIOT Act/AML Act 2020 framework administered by FinCEN and OFAC, both headquartered in DC; DC's own DISB supervises DC-licensed MSBs and non-bank financial institutions. DC-formed LLCs (DCRA registry) carry no independent beneficial-ownership disclosure requirement, inheriting the national CTA framework, which since March 2025 exempts domestic reporting companies from BOI reporting. DC was named directly in FinCEN's residential real estate GTOs; the successor nationwide rule was judicially vacated in March 2026.
  3. T?FIM (sentinel.gi) gaps_register_cumulative (issue FIM-BASE-GAP-004) — Gap: absent-field-provenance
  4. T?FIM (sentinel.gi) gaps_register_cumulative (issue FIM-BASE-GAP-003) — Gap: legal-gap
  5. T3FIM (sentinel.gi) sanctions_change_register (issue FIM-BASE-SANC-002) — Sanctions: OFAC listing
  6. T3FIM (sentinel.gi) enforcement_action_register (issue FIM-BASE-ENF-001) — Enforcement: OFAC — Two digital-currency wallets attributed to the Central Bank of Iran, linked to IRGC-Qods Force and Hizballah
  7. T?FIM (sentinel.gi) gaps_register_cumulative (issue FIM-BASE-GAP-001) — Gap: regulatory-failure

#

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-brief · as of 7 July 2026201 words · last cycle 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 on record for 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).

Standing sub-brief · as of 7 July 2026157 words · last cycle 2026-10-18

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-10-18

Commercial Intelligence & Fintech

Two commercial events touching the District of Columbia converge on the same entity, Coinme Inc., this cycle. The first is a multistate BSA/AML consent settlement under which Coinme has agreed to close its virtual-currency kiosk operations, with DC's Department of Insurance, Securities and Banking named as one of 34 participating state regulators; the settlement requires kiosk shutdown by 1 January 2027. The second, closing on a faster timeline, is Polygon Labs's completed acquisition of Coinme on 14 October 2026, which the available reporting frames as following Polygon's January announcement of plans to acquire both Coinme and wallet-infrastructure provider Sequence. The acquisition's financial terms were not publicly disclosed in sources reviewed this cycle.

The commercial significance for the District lies in licence continuity. Coinme held a District money-transmission licence under D.C. Code § 26-1001 et seq., the general money-transmission code DISB administers, and that licence, along with Coinme's broader 37-state money-transmitter footprint as referenced in the settlement context, now transfers in substance to Polygon's ownership structure following the acquisition close. No source reviewed this cycle independently confirms whether Coinme's District licence has been reissued, assigned, or otherwise formally addressed in connection with the change of control, which leaves the regulatory-continuity question open on the commercial record even as the settlement's operational requirement, kiosk closure, proceeds on its own separate track.

The acquisition itself fits a pattern of wallet- and payments-infrastructure consolidation: pairing a cash-to-crypto kiosk network with wallet infrastructure (Sequence) suggests Polygon is assembling a more vertically integrated consumer on-ramp and custody stack rather than acquiring Coinme purely for its existing kiosk business, a business that is simultaneously being wound down under the settlement. This juxtaposition, an acquirer integrating a business whose flagship product line the seller has just agreed to shut down, is the commercially distinctive feature of this cycle's District-relevant event, though its interpretation depends on confirmation this cycle does not provide: whether Polygon intends to retain non-kiosk elements of the acquired business (wallet, licensing infrastructure, compliance program) while discontinuing kiosk operations specifically.

Outlook

The near-term marker is the 1 January 2027 kiosk-shutdown deadline, which now falls to Polygon as Coinme's new owner to execute. Beyond that date, the open commercial question is what becomes of the District money-transmission licence itself: whether it is retained for non-kiosk payments activity under Polygon's ownership, surrendered, or reassigned, none of which is resolved in sources available this cycle.

1 earlier distinct update(s)
Periodic update · new data 2026-08-11

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.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": {"cards": "regulated", "stablecoin": "emerging-regime"}}}.

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: 2 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), 70 finding(s), 151 source(s) in the cumulative register.

Think something on this page is wrong? Report an error.