How Alchemy powers stablecoin payments

A payment is either there or it isn't.

Someone getting paid in stablecoins wants two things: the money to arrive, and to be able to see that it did. Everything underneath that, which chain it crossed, how many confirmations it took, whose infrastructure carried it, is yours to get right.

Payroll, supplier invoices, remittances, and merchant settlement all run on stablecoins now. The people on both ends expect to send, receive, and check a balance the way they would in any other payments app.

Cash App, Slash, AllScale, Pana, and Usual run the onchain half of that work on us. What we provide is the connection between a payments product and the chain: low-latency reads, real-time event delivery, historical data for reconciliation, transaction submission, and gasless infrastructure so a customer never has to hold a native token to move their own money. We run more than $1 trillion in transactions annually across the platform, at 99.99% uptime for payments.

What payment products are teams building onchain?

Checkout, payroll, business banking, remittances, and consumer money movement. All live, all moving real money.

How do you know the balance you show a customer is right?

You check it against the chain constantly, and you keep the record so you can prove it later. Cash App does this more than 3.5 million times a day.

Reconciliation is the bookkeeping question underneath all of this: does what your ledger says match what the chain says? Think of it as a bank proving your statement against its own records, except here the records are public and anyone can check them.

Two things have to be fast for that to work. A webhook has to tell you the moment a transfer lands, and a read has to confirm the balance that resulted. Cash App runs both on us, across EVM networks and Solana: roughly 360,000 real-time webhook events a day through Webhooks, and the verification reads through Node RPC.

It serves 59 million monthly transacting actives in the United States, and every balance and transfer it shows a customer is checked against public chain state as that state changes: more than 3.5 million balance reconciliation checks a day, plus thousands of onchain transaction verifications. Read speed decides whether that check finishes before a customer refreshes the screen, which is why we publish a live latency benchmark of our endpoints with the methodology and raw data open.

"Our goal is to make stablecoins feel as simple and dependable as cash," said Aaron Owusu, Product Lead for Stablecoins at Cash App. Cash feels dependable because the checking underneath it never stops.

Do you need a separate setup for every payment product?

You don't, and AllScale is the proof. Checkout, invoicing, payroll, and payouts all run for its customers through one account and one API, on a single Node RPC layer.

Underneath, that means balance reads, transaction validation, submission, gas estimation, and confirmation tracking all coming from one place. The difference shows up when something breaks. A payout that fails and an invoice that settles late are the same class of problem, and chasing them across four providers is four investigations.

AllScale runs 2.6 million wallets and more than 150 customer integrations on one confirmation path. Its CTO put the standard plainly: "Payments only feel simple when the infrastructure behind them is fast and dependable."

How do you give customers the upside of blockchain without the complexity?

Two things. You pay the gas for them, and you give them an account instead of a wallet to manage.

Gas is the one that stops people cold. A customer holding only USDC can't send it otherwise, because sending requires a different token they don't have and have never heard of. That's where first transfers stall.

Slash hit exactly that wall. The team watched potential customers "get stuck sending their first transaction."

Today Slash runs stablecoin banking for more than 3,000 businesses globally, moving more than $10 billion in annual payments. Each Global USD account is a non-custodial wallet built on account abstraction, and we sponsor the gas underneath it. What the business sees is a USD account. What it never has to see is a wallet, a seed phrase, or a gas balance.

Pana solved the same problem for consumers. It moves remittances across Latin America on Base and Ethereum, reached more than 200,000 users in under six months, and processes tens of thousands of stablecoin transactions a day, none of which require the sender or the recipient to hold ETH.

Settlement still happens onchain, and it stays verifiable. A customer doesn't need to know how it works. They need to know it worked, and to be able to check.

What are the layers of a stablecoin payment stack?

Issuance, settlement, monitoring, conversion, payout, custody, compliance. We run the onchain middle.

The layers we run have to be correct before any of the rest can. A payout partner can't wire against a deposit your system hasn't confirmed, and a close can't happen against a ledger that doesn't match the chain. For how to choose the APIs behind those three layers, our guide to stablecoin payments and monitoring walks through the options. If you're earlier than that and still designing the token itself, start with how to build a stablecoin.

Our coverage spans 100+ chains, including Ethereum, Base, Arbitrum, OP Mainnet, Polygon, BNB Smart Chain, Solana, and Tron, plus payments chains like Plasma, Stable, Arc, and Tempo.

Build for the future of money movement and settlement

The teams above aren't running pilots. They're in production, at consumer scale, for people who would never describe themselves as crypto users and who notice immediately when something is late or wrong.

That's the standard the infrastructure has to meet, and it's the only one that matters. Start on our payments stack, or talk to our team about what you're building.

Frequently asked questions

Which payment companies are building on Alchemy?

Cash App, Slash, AllScale, and Pana. Between them they cover consumer money movement, business banking for more than 3,000 businesses, checkout and payroll, and cross-border remittances.

Does Alchemy convert stablecoins to fiat or send bank payouts?

No. We run the onchain layer: Node RPC, webhooks, historical data, transaction submission, and gasless infrastructure. Fiat conversion, bank payouts, issuance, redemption, and custody sit with your processor, issuer, offramp, and banking partners.

Can customers send stablecoins without holding ETH or SOL?

Yes. Our gasless infrastructure lets your app pay the network fee on the customer's behalf, so someone holding only USDC can send it. Slash and Pana both work this way.

Which chains can you run stablecoin payments on?

More than 100, including Ethereum, Base, Arbitrum, OP Mainnet, Polygon, BNB Smart Chain, Avalanche, Unichain, and Linea, plus Solana and Tron, and stablecoin and payments chains including Plasma, Stable, Arc, and Tempo.

Who pays the gas fee in a stablecoin payment?

Whoever you decide. By default the sender pays, in the chain's native token, which is why a customer holding only USDC can get stuck. With gasless infrastructure your app pays the fee instead and gets billed in dollars, so the customer only ever handles the stablecoin.

What happens when a stablecoin payment fails?

The stablecoin doesn't move. A transfer either lands onchain or it doesn't, but a failed one produces no transfer event, so the event stream that reports successes stays silent. Track each payment by its transaction hash and check its receipt with eth_getTransactionReceipt: a status of 0 means the transfer reverted. If no receipt arrives within your timeout, the transaction hasn't been mined yet, so check whether it's still pending before you resubmit it.

Which stablecoins can you build with on Alchemy?

Any token on a supported chain, which in practice means USDC, USDT, and the regional and bank-issued stablecoins launching alongside them. We run the chain access underneath, so the choice of stablecoin is yours and your issuer's.

How do you check that a stablecoin payment actually landed?

With real-time event delivery as the transfer lands, plus historical reads to confirm it later. Cash App runs more than 3.5 million balance reconciliation checks a day this way, and AllScale tracks confirmations for checkout, invoicing, payroll and payouts on the same Node RPC layer.