B2B stablecoin payments go mainstream — Ramp puts a "pay in USDC/USDT" button in every back office

What Ramp launched — and why it's a milestone for B2B stablecoin payments

On July 21, 2026, Ramp — the corporate card and spend-management platform used by tens of thousands of businesses — announced general availability of stablecoin accounts and payments for every customer. Not a pilot, not a crypto-companies-only beta: any business on Ramp can now hold USDC and USDT balances, pay vendors and employees in stablecoins, pay its Ramp card directly from a stablecoin balance, and have every transaction reconciled automatically in its existing accounting system.

The details matter. Payments can be initiated from a stablecoin account, a Ramp checking account, or a linked external bank account — with no pre-funding required. The infrastructure is built with Stripe's Bridge and Privy handling issuance, orchestration and wallets, and checking deposits sit with an FDIC-member bank. During the public beta, over 150 companies adopted the accounts — and notably, they weren't all crypto firms: Ramp cites customers in farming and nonprofits alongside crypto-adjacent businesses.

Ramp's stablecoin product manager, Andrew Chapello, put the thesis in one line: "Businesses shouldn't need a second financial system just because a payment settles on different rails." Paying a vendor in dollars, USDT or USDC now runs through the same approvals, the same controls and the same books. That's the moment a rail stops being exotic: when it disappears into the software a finance team already uses.

The same week: a $180M clearing bank and a missed regulatory deadline

Ramp's launch didn't happen in a vacuum. On the same day, CoinDesk reported that Augustus — a startup building a federally chartered, AI-native clearing bank for stablecoin-era payments — raised $180 million at a $1 billion valuation, led by Tiger Global with participation from founders of Nubank, Circle, Deel and Ramp itself. Augustus received conditional OCC approval for a U.S. national bank charter in May, already clears billions of euros a year through a regulated Finnish entity, counts Kraken among its customers, and plans to expand across Latin America, Southeast Asia, the Middle East and Africa. Its CEO's argument: legacy clearing "is slow, unavailable, takes two days to settle" — and programmable money is what AI agents will need to interact with banking at all.

Zoom out and the pattern is unmistakable. In the last three weeks alone, Visa launched a stablecoin platform for banks, America's biggest banks confirmed a tokenized-deposit consortium to answer the stablecoin boom, and now the spend-management layer and the clearing layer are going stablecoin-native. Meanwhile the U.S. GENIUS Act's July 18 deadline for final stablecoin rules came and went with rulemaking still in progress — yet the industry isn't waiting: PYMNTS notes that 23% of CFOs already expect stablecoins to matter to their operations within three years, and 45% of finance leaders say integration with their existing banking stack is the single biggest unlock. Ramp just shipped exactly that integration.

The gap this creates: payers are ready, receivers aren't

Here is the part of the story most coverage skips. Every layer that went mainstream this month is on the paying side: spend platforms, clearing banks, card networks. When a Ramp customer decides to pay your invoice in USDC next month, the entire experience on their side is polished — approval workflow, controls, automatic bookkeeping.

Now look at your side. If you invoice businesses today, what happens when a customer asks to pay in stablecoins? For most companies the honest answer is: someone pastes a wallet address into an email. No invoice tied to the payment, no expiration, no underpayment or overpayment handling, no webhook into your books, and a real risk of a typo sending five figures into the void. The payer has enterprise software; the receiver has a text field.

That asymmetry is a commercial opening. B2B payments are two-sided: every "pay vendors in stablecoins" button needs vendors who can be paid that way. Agencies, exporters, SaaS companies, contractors and suppliers who can present a proper stablecoin invoice — one that reconciles itself — become the easiest vendors to pay on the new rail. The ones who can't will quietly push their customers back to wires and 2–3 day settlement, or worse, accept crypto informally with none of the controls their customer's CFO takes for granted.

How to receive B2B stablecoin payments properly — non-custodial

This is exactly the receiving-side problem Payzum is built for, with one structural difference from holding balances inside a fintech platform: Payzum is non-custodial. Funds never sit in a Payzum balance — every payment settles directly to a wallet your business controls. There is no platform account to freeze, no counterparty holding your revenue, and settlement is the payment: on Base or Polygon a USDC transfer confirms in seconds, not in a two-day clearing cycle.

For B2B flows specifically, that maps to features you'd actually use with a corporate payer on the other side:

• Invoices with expiration and overpayment detection — send a customer a stablecoin invoice, not a bare address. It has an amount, a deadline, and it detects under- and overpayment, so what lands on-chain matches what your books expect.
• Payment links and hosted checkout — for one-off B2B charges or deposits, a no-code link their finance team can pay from any wallet, including a Ramp-style stablecoin account.
• Auto-convert to USDC/USDT — accept whatever the payer sends and settle in stablecoins, so volatility never touches your receivables.
• Signed webhooks and a REST API — payment events flow into your ERP or accounting system automatically, mirroring the reconciliation the payer already has on their side.
• Mass payouts for your own pay-out side — when you're the one paying contractors or affiliates, CSV batch payouts in stablecoins across Polygon, Arbitrum, Optimism, Base, BNB Chain and Avalanche cover the other direction of the same flow.

Set it up, step by step

1. Create your merchant account and connect your wallet. You bring the wallet — Payzum never holds keys or funds. Choose the chains you want to settle on (Base and Polygon confirm in ~2 seconds).
2. Turn on auto-convert if you want dollar-stable receivables. Any accepted crypto settles as USDC or USDT in your wallet, so your invoices are effectively dollar-denominated end to end.
3. Issue your first stablecoin invoice or payment link. Set the amount and expiration and send it like any other invoice. Your customer pays from whatever wallet or stablecoin account they use.
4. Wire the webhooks into your books. Signed webhook events on each payment let your accounting stack reconcile automatically — the receiving-side mirror of what Ramp just gave payers.

Who feels this first: three B2B scenarios

The businesses that will meet a stablecoin-paying customer soonest look like this:

• A digital agency with venture-backed clients. Its clients run modern finance stacks; one switches vendor payments to USDC for speed. The agency sends a Payzum invoice and gets settled in seconds instead of waiting on a 3-day ACH batch — funds in its own wallet, auto-converted to USDC. (We covered the agency angle in depth here.)
• An exporter invoicing foreign buyers. Cross-border wires cost $30–50 and take days; a stablecoin invoice settles the same afternoon with cents in network fees, and no correspondent banking chain in the middle.
• A SaaS company with B2B customers. Alongside card billing, it adds a USDC payment option for annual invoices — no chargebacks, no card fees on five-figure contracts, and finance teams paying from stablecoin accounts can use their normal approval flow.

Receiving stablecoins: raw wallet transfer vs Payzum

Common objections

"My customers haven't asked to pay in stablecoins yet."

The point of the July 21 news is that the asking is about to get much cheaper. When paying in USDC is a dropdown in the same software a finance team already uses — same approvals, same books — the friction that kept this theoretical is gone. Being able to say "yes, here's the invoice" costs you a setup afternoon; saying "no" costs the payment terms conversation. And 23% of CFOs saying stablecoins will matter within three years is before this GA moment, not after.

"Why not just hold a balance in a platform like the payers do?"

For spend management, a platform balance makes sense — it's the payer's own workflow tool. For revenue, custody is risk: a balance inside someone else's platform is an account that can be frozen, gated or delayed, which is precisely the failure mode that pushes businesses to crypto rails in the first place. Non-custodial settlement means your receivables land in a wallet only you control, with the tooling layered on top rather than a balance in between. That's the difference we've written about since our non-custodial processor pillar.