California's Digital Financial Assets Law and Stablecoin Acceptance

California DFAL stablecoin merchants questions come up more often now that stablecoin checkout is a real option and the state has a licensing regime with a name. The Digital Financial Assets Law (DFAL) was enacted in 2023, with the licensing requirement phased in over subsequent years, and it puts the Department of Financial Protection and Innovation (DFPI) in charge of who may conduct "digital financial asset business activity" with California residents. The practical question for a business owner is simple: if I accept stablecoins for my products, am I the one who needs the license? Usually not, but the reasoning matters, and this is not legal advice.

What DFAL actually regulates

DFAL is modeled on money-transmitter licensing. It covers businesses that exchange, transfer or store digital financial assets on behalf of California residents, or that operate as an exchange. The target is custodial wallets, exchanges, and services that hold or move assets for customers. The law includes exemptions, and the DFPI has issued guidance and rulemaking to define the edges. Check the current rule text and DFPI guidance for the effective dates and thresholds, because the details have shifted since enactment.

Where a merchant sits

A retailer in Los Angeles that lets a customer pay for a $200 order in a dollar-pegged stablecoin, receives the stablecoin in its own wallet, and sells nothing but its own goods is not exchanging, transferring or custodying assets for anyone else. That is the general reasoning under which merchants accepting payment are not the licensee. The entities that facilitate the transaction (the processor, the wallet provider, anyone converting the stablecoin to dollars on the merchant's behalf) are the ones whose activities DFAL is written for. Two cautions:

• If you start doing anything beyond accepting payment (holding customer balances, converting for customers, running a loyalty token that customers can trade), you may have crossed into regulated activity. Ask counsel before you build it.
• The processor you use should be able to explain its own licensing posture. Flux does not make claims here about specific licenses; ask for the current status in writing.

How stablecoin acceptance works mechanically

With stablecoin payments the customer pays from their wallet, the transaction is confirmed on Solana or the XRP Ledger, and the funds land in the merchant wallet instantly. There is no authorization-then-capture step, no batch, and no 1-2 business day wait. Compare that to cards at 1-2 business days and ACH at 1-3. Because there is no card network in the middle, there is no chargeback mechanism: the customer cannot call an issuer and reverse the payment. That cuts both ways.

Refunds and disputes become your policy

Card chargebacks are a consumer protection tool. When you remove them, the customer relies on your refund policy, and California's consumer-protection framework still applies to the sale. Publish a refund policy that covers stablecoin payments explicitly (refund in stablecoin, in dollars, at what exchange value, within what window), and keep the customer's wallet address and transaction ID with the order so a refund can be executed. Businesses in high-dispute categories often find stablecoins attractive precisely because a dispute-prone customer cannot weaponize the chargeback process; that is a legitimate benefit, but it does not remove your obligation to make the customer whole when you are wrong.

Taxes, accounting and pricing

The CDTFA treats a sale paid in stablecoin as a sale; sales tax is due on the dollar value at the time of the transaction. For income purposes the IRS treats digital assets as property, so if you hold the stablecoin rather than converting immediately there can be a small gain or loss to track; a dollar-pegged stablecoin keeps this close to zero but not exactly zero. Push the settled transactions into QuickBooks (Flux syncs one-way into QuickBooks) with the dollar value recorded, and talk to your accountant about how to book any holding period.

Pricing: SB 478 applies to how you advertise. If you offer a discount for stablecoin payment, the advertised price must still be the price a customer paying by any accepted method can pay. A discount for stablecoin is easier to present than a surcharge on cards.

Data and privacy

A stablecoin transaction includes a public wallet address and a transaction hash. If you link those to a customer record, you are holding personal information under CCPA/CPRA and the usual access and deletion rights apply. Wallet addresses are pseudonymous, not anonymous. Treat them like any other identifier.

Who this is actually for

Stablecoin acceptance makes the most sense for businesses that (a) sell to customers who already hold stablecoins, (b) are tired of the 1-2 day card float or the chargeback exposure, or (c) sell across borders and want to avoid cross-border card fees and currency spreads. A Central Valley exporter, a software company in San Francisco selling internationally, and a high-ticket service business with a dispute problem each get something different from it. For a neighborhood restaurant it is a nice-to-have, not a strategy.

The short version: DFAL is about businesses that handle digital assets for other people, and a merchant accepting payment for its own goods generally is not that business. Confirm the position with counsel, pick a processor that can explain its own licensing, write the refund policy before the first transaction, and treat the instant settlement as the operational win it is.