Ripple has just nine days to file a completed application under California's Digital Financial Assets Law (DFAL) before the July 1, 2026 deadline, yet as of the most recent public records through March 2026, no Ripple entity appears on the DFPI's list of applicants. The company formally engaged the regulator earlier this year, citing the deadline by name in written comments, but a completed filing has not been publicly confirmed. Without a license or pending application, Ripple's RLUSD stablecoin cannot legally be issued, redeemed, or custodied for California residents after that date — a market representing the world's fifth-largest economy.
The DFAL Framework and July 1 Deadline
California's Digital Financial Assets Law, originally enacted under AB 39 and later amended by AB 1934, pushed the operative licensing date from July 1, 2025 to July 1, 2026. Governor Gavin Newsom signed the delay in September 2024, giving regulators and firms additional runway to build compliance infrastructure. That runway closes next week.
The DFPI began accepting DFAL applications via the Nationwide Multistate Licensing System on March 9, 2026. The law prohibits any entity from engaging in — or even holding itself out as able to engage in — digital financial asset business with California residents unless it is licensed, has a completed application on file, or qualifies for an exemption. The broad "holding out" language means marketing materials, app availability, and website offerings directed at Californians can trigger obligations before any transaction occurs.
Compliance costs are significant. The application fee runs $7,500 plus the DFPI's reasonable review costs, and a completed filing must include corporate structure documentation, financials, AML/CTF programs, governance frameworks, information security policies, and consumer protection disclosures. Firms that miss the deadline and continue serving California residents face cease-and-desist orders, civil penalties, and potential criminal exposure under the California Financial Code.
Ripple's Engagement vs. Public Record
Ripple submitted formal written comments to the DFPI earlier in 2026, addressed to Regulations Coordinator Diana Pha. In that letter, the company confirmed it understood the July 1 deadline, expressed support for the DFAL framework, and requested an amendment to Section 80.3002(a)(5) — asking that entities holding a DFAL license be explicitly covered under that section, eliminating the need for a separate Money Transmitter License.
That argument is grounded in Ripple's existing regulatory footprint. The company holds more than 40 money transmitter licenses across the U.S. and is chartered as a limited purpose trust company by the New York Department of Financial Services, which directly regulates RLUSD. Ripple's position — that DFAL's background check and oversight standards are often more rigorous than a standard MTL, making dual licensing redundant — reflects a firm that understands the regulatory landscape.
However, engagement in rulemaking and submission of a completed license application are two different acts. XRP analyst WrathofKahneman flagged this discrepancy on June 19, noting that public DFPI documentation through March 2026 does not list any Ripple entity among DFAL applicants. His post drew over 13,000 views. The analyst was careful to note that non-appearance in public records does not confirm Ripple has not filed — filings may not yet be reflected — and assessed an application as likely given Ripple's direct DFPI engagement. Still, the public record shows awareness and participation, but not a completed application.
What's at Stake for RLUSD
For RLUSD specifically, the covered activities — issuance, redemption, and custody — are the core of Ripple's stablecoin business. There is no partial compliance path. If Ripple fails to have a completed application on file by July 1, it cannot legally serve California residents with RLUSD. Given California's economic weight, this is not a peripheral market. The federal-level crypto regulatory calendar is adding further pressure on firms already managing multiple jurisdictional deadlines simultaneously.