The CLARITY Act failed in the Senate — and the rules for accepting stablecoin payments didn't move an inch

What happened on September 15, 2026

The Senate took its first floor test of comprehensive crypto market structure legislation and lost it. The vote was on cloture on the motion to proceed to H.R. 3633 — whether the chamber could even begin debating the bill — and the official record shows 49 yeas to 50 nays. Sixty were needed. The bill did not clear fifty.

Every Democrat voted no, including the seven who had spent months at the negotiating table. Three Republicans joined them on the merits: Susan Collins of Maine, Josh Hawley of Missouri and Jerry Moran of Kansas. One further "no" was pure procedure — Senator Thom Tillis voted yes, then switched, so that as a member of the prevailing side he could file a motion to reconsider and keep the question alive. Senator Chris Coons did not vote.

Senator Cynthia Lummis, who led the Republican push, made the closing argument on the floor: "Let's vote yes. Let's not only join the 21st Century economy… Let's lead it." It didn't land. Republican leadership had released a revised text on the Sunday before the vote, adding ethics restrictions aimed squarely at Democratic objections, and it still wasn't enough, as CoinDesk reported from the floor.

Markets read it immediately. Bitcoin slid as the count came in, and in the following 24 hours XRP fell about 8.5%, with ether and solana down roughly 2.9% and 3.3%. Prediction markets that had priced the bill's chances in the eighties earlier in the year collapsed to single digits.

Why the CLARITY Act failed — and why it wasn't really an argument about payments

This is the part worth getting right, because "Congress rejected crypto" is the wrong summary and it will lead businesses to the wrong conclusions.

The bill did not fail on its treatment of exchanges, or its definition of a digital commodity, or the technical question of when a token stops being a security. Those were the parts that had been negotiated — reportedly through more than a hundred revisions requested by Democrats, across a text that ran past six hundred pages. It failed on the final sections: ethics provisions governing whether the president and senior officials can profit from digital asset ventures while the rules covering those ventures are being written. Democrats wanted an enforceable ban. Republicans said the latest draft had gone far enough. Neither side moved, and the calendar did the rest.

A second pressure point was closer to home for anyone holding a dollar-denominated balance: community-bank lobbying over stablecoin yield. That fight is the direct continuation of the one we covered in July, when Wall Street and the banking associations pushed to strip yield-bearing arrangements out of the text — see the CLARITY Act stablecoin yield fight. Deposits leaving banks for tokens that pay interest is an existential worry for a small bank, and it bought at least one Republican no vote.

With the November midterms close and the legislative calendar compressed, the practical consensus is that market structure is finished for 2026. The motion to reconsider keeps the question technically alive; most analysts put the earliest realistic window in mid-November, and a Congress under split control next year makes the timeline worse, not better.

What the bill would have done

Three things, broadly, and it's worth separating them because they land on different people.

• Jurisdiction. Draw the line between digital assets regulated as commodities by the CFTC and those regulated as securities by the SEC, and give the CFTC new authority over crypto spot markets. This is the headline item, and it affects exchanges, brokers and token issuers.
• Registration. Put spot trading platforms under a federal registration regime for the first time, with the usual apparatus of disclosure, custody standards and market conduct rules. This affects the venues where tokens trade — not the merchant who receives one.
• Self-custody and developers. The Senate text carried language derived from the Keep Your Coins Act protecting an individual's right to use a self-hosted wallet, plus a safe harbour saying a non-controlling blockchain developer is not a money transmitter merely for publishing software, providing tools for a customer's own custody, or maintaining infrastructure. The House-passed text, available in full at Congress.gov, carries a version of that provision with an explicit rule of construction preserving AML obligations for conduct outside it.

Note the asymmetry. Items one and two are about who supervises the venues. Item three is the one that touches how an ordinary business is allowed to hold and move its own money — and it is the one nobody was fighting about when the bill died.

Why a business accepting stablecoins is unaffected

The single most useful fact about this vote, for a merchant, is that payment stablecoins were never in this bill. Congress split the work deliberately: stablecoins went into the GENIUS Act, enacted in July 2025, and market structure went into CLARITY. The first passed. The second just died. The first is the one that governs the dollar you receive.

Under GENIUS, a permitted payment stablecoin is not a security, not a commodity and not a deposit — it sits in its own regime, administered principally by the OCC alongside the Federal Reserve, the FDIC, Treasury and state banking regulators. The implementing rulemaking is live and public: the OCC has issued a notice of proposed rulemaking covering permitted issuers, foreign issuers and certain custody activities, summarised in OCC Bulletin 2026-3. None of that was on the Senate floor on September 15.

There's a structural point underneath it, and it's the one businesses most often get wrong. In every major market, the regulated party is the issuer or the intermediary — not the merchant. Accepting a token as payment for goods or services doesn't make a bakery a financial institution, in the same way that accepting a foreign banknote doesn't. What varies by jurisdiction is which stablecoins your counterparties can legally handle, which providers are licensed to serve you, and what happens to the money while someone else is holding it. We mapped the US version of that question in which stablecoins US merchants can accept, and the framework itself in what the GENIUS Act means for merchants.

So: your checkout works tomorrow exactly as it worked last week. USDC is still USDC. Base still confirms in about two seconds. The failed vote changed no rule that applies to you.

What didn't get written — and why that's the line to watch

Here's the part the market coverage skipped. The provisions in CLARITY that most directly protected ordinary users and builders were the self-custody right and the non-custodial developer safe harbour. They were not controversial in the endgame. They died anyway, because they were passengers on a bill that failed for unrelated reasons.

The consequence is specific: the right to hold your own keys, and the legal status of software that helps you do it, remain matters of agency posture rather than statute. Agency posture is real — it is the basis on which most of this industry currently operates — but it is revisable by the next administration, the next enforcement theory, or the next court. A statutory safe harbour would not have been.

SEC Chairman Paul Atkins put the problem plainly after the vote: rules written by regulators aren't durable without Congress behind them. The SEC is proceeding anyway, with a proposed exemptive framework for token fundraising, and the CFTC continues its own work. That's the 2027 shape of things — regulation by rulemaking, contested case by case, with no floor under it.

We'd rather name the tension than pretend it resolves cleanly in our favour. You could read the missing safe harbour as an argument for using a big regulated custodian, on the theory that they'll absorb the ambiguity for you. Our read is the opposite, and it's based on where the ambiguity actually bites: unresolved rules reach you through the intermediaries who hold your money, because they're the ones who have to make a judgement call about your account when the rules move. A wallet you control is not a party to that judgement call. This is the same logic we walked through in counterparty risk in stablecoin payments, and it didn't change on Monday — it just lost a chance to be written into law.

The second-order effects worth watching

Nothing changed in the rules. Some things did change in the environment, and three of them are worth a merchant's attention.

• Your providers stay in limbo. Exchanges, custodians, brokers and off-ramps were the constituency waiting for statutory clarity. They now face another year of state-by-state licensing and federal rulemaking that can shift. Provider risk — pricing changes, geographic pullbacks, abrupt account reviews, outright exits — stays elevated. We wrote the playbook for that in what to do when your crypto payment provider shuts down.
• Volatility got a reminder. A legislative vote knocked several percent off major tokens inside a day. If you price in a volatile asset and hold it, your revenue inherits the news cycle. If you auto-convert at acceptance, it doesn't. That's not a prediction about prices — it's the difference between a dollar-denominated balance and a bet.
• The agentic and API side is unaffected but unfinished. Machine payments run on stablecoins — TRM Labs found 99.6% of settled x402 value was USDC — and none of that was in CLARITY either. The standards fight there is happening in foundations and consortia, not the Senate. Our comparison of MPP and x402 for API sellers covers where that actually stands.

What a business can do this week, step by step

None of this requires a legislative outcome. Every item below is available today.

1. Own the destination. Decide which wallet revenue arrives in, and treat that address as the account. With Payzum there is no Payzum balance and no payout schedule — the customer's transaction to your address is the settlement. Payzum never holds, pools or controls the funds. Turn on 2FA and keep keys where your treasury policy says keys go.
2. Switch on acceptance where you actually sell. Online: hosted checkout (redirect, modal or inline), no-code payment links and buttons, invoices with expiry and overpayment detection, donations and tip jars, and recurring subscriptions — drop-in compatible with existing e-commerce plugins, snippets and webhooks. In person: POS with a fresh QR per sale, physical terminals, PIN-protected cashiers and per-cashier analytics, with no acquirer, no card-network fees and no chargebacks.
3. Remove price risk from the equation. Accept whatever the customer holds and use optional auto-conversion to USDC or USDT, so what you keep is dollar-denominated regardless of what the Senate does next. See the case for a self-custodial stablecoin wallet for the holding side.
4. Pay out on the same rails. Mass payouts by CSV in BTC, LTC and DOGE, plus EVM stablecoin payouts on Polygon, Arbitrum, Optimism, Base, BNB Chain and Avalanche. Every dollar that goes out on-chain is a dollar that never queues behind an intermediary's compliance review.
5. Wire it into your systems. REST API with API keys, signed webhooks, a full audit log, an integration playground, and x402 so AI agents can pay USDC on Base per API call, straight to your wallet.
6. Keep a second route for fiat. Payzum is crypto-only — we accept crypto and settle in crypto, and we are not an off-ramp. For the fiat you genuinely need, use a licensed provider, test it small, and keep a backup configured before you need it.

Networks supported: Bitcoin, Ethereum, Solana, Polygon, Base, Arbitrum, Optimism, BNB Chain and Avalanche. Typical confirmations run about 0.4 seconds on Solana and around 2 seconds on Base and Polygon.

Who this changes something for

• US businesses that were waiting for "clarity" before starting. The wait just got a year longer, and it was aimed at the wrong bill. Accepting payment stablecoins has had a federal framework since 2025; the thing that died governs trading venues.
• Companies whose payment provider is a US exchange or custodian. Your provider's regulatory path is less certain today than it looked a week ago. That's an argument for knowing exactly how much of your money sits with them at any moment.
• Cross-border sellers and exporters. Unchanged operationally — you invoice abroad, you get paid in stablecoins in seconds. See getting paid from abroad without a traditional bank account.
• API providers and agent-facing services. Machine payments settle in USDC on public rails, outside the market structure debate entirely. Nothing about September 15 slows that down.
• Anyone holding volatile assets as working capital. Monday was a demonstration. Auto-conversion at acceptance turns a policy headline into someone else's problem.

What changed and what didn't — the comparison

The honest counter-arguments

"No market structure law means more risk, so I should wait."

Waiting is a position, and it has a cost. The framework covering the thing you'd actually be doing — receiving a regulated dollar token as payment — was settled in 2025 and is being implemented in public. Waiting for CLARITY to accept stablecoins is like refusing to take euros until the exchange listing rules are rewritten. If your concern is provider risk rather than payment legality, the answer isn't delay; it's fewer intermediaries between the customer and your wallet.

"Without a self-custody statute, isn't a regulated custodian the safer choice?"

It's a real argument and we won't dismiss it. A custodian absorbs key management, and a business that can't run key management responsibly is genuinely better off with one. The trade is a known risk you control — multisig, hardware signers, role separation, a documented recovery procedure — against an unknown risk you don't: a platform's own judgement about your account, made without you in the room. The missing statute doesn't change who makes that call. It just means nobody has written down that you're allowed to avoid it.

"Doesn't regulatory uncertainty mean crypto payments could be banned?"

What failed was a bill that would have expanded federal structure, not one that permitted the activity in the first place. Payment stablecoins have an affirmative federal framework, seven major jurisdictions have converged on licensed issuers with full reserves and redemption rights, and merchant acceptance sits outside the licensing perimeter in all of them. This is general information, not legal advice — confirm your own position with counsel — but the direction of the last two years is more structure, not less.