If you have swapped tokens or sent USDC to a friend on Base, you already understand the basics of a self custody transaction. Paying a merchant is a different shape of problem. A store needs to know the payment actually arrived before it ships a product, and it sometimes needs to issue a partial refund later, or cancel a charge that never got collected. A plain transfer does not handle any of that well on its own. This is what Base Pay and the Commerce Payments Protocol are built to solve, and it is worth understanding how they work if you plan to use a self custody wallet to pay for things rather than just swap and hold.
Two separate pieces, often confused
"Base Pay" and the "Commerce Payments Protocol" get mentioned together often enough that it is easy to assume they are the same thing. They are not, and Coinbase's own engineering posts describe them separately.
The Commerce Payments Protocol is the underlying smart contract layer. Coinbase and Shopify published it as an open, permissionless escrow system that any developer can build against, not something exclusive to one wallet or one storefront.
Base Pay is the checkout experience built on top, designed to get a payment done in a single step instead of the usual connect wallet, switch network, confirm sequence. It is a product and a set of wallet standards, not a token. A tradable "Base Pay" token would be an unrelated claim, worth the same scrutiny you would give any unfamiliar token before you research it.
How the escrow contract actually works
A normal transfer is one step: funds leave your wallet and land in the recipient's. Commerce needs more steps than that, so the protocol breaks a payment into distinct operations handled by an escrow smart contract sitting between you and the merchant:
- Authorize. Your funds move out of your wallet and into escrow, not directly to the merchant. This is closer to how a card payment puts a hold on your account than to a direct transfer.
- Capture. The merchant pulls some or all of the authorized amount out of escrow and into their own funds. A capture can happen in multiple partial increments, for example if an order ships in separate packages, but the total captured can never exceed what you authorized.
- Charge. A shortcut that authorizes and captures in the same transaction, for a simple purchase that does not need a holding period.
- Void. The merchant releases uncaptured funds back to you, similar to a store cancelling a pending charge.
- Reclaim. You can pull back your own uncaptured funds yourself, but only after the authorization's expiry has passed, so a merchant cannot be cut off mid process.
- Refund. Funds the merchant already captured get returned to you.
Every one of these is a visible operation against the escrow contract. You can look it up on a block explorer, which is a meaningful difference from a card payment, where the hold, capture, and refund happen inside a bank's private ledger you cannot independently inspect.
Why you are not always the one paying gas
A payment that needs an authorize step and a separate capture step is naturally two onchain actions, and in the past that would have meant two gas payments from you. The protocol avoids this with a role called an operator, a party that submits the actual blockchain transactions on the merchant's behalf.
You still sign a message approving exactly what you agreed to: who gets paid, which token, the maximum amount, and when the authorization expires. The operator cannot change any of those terms, redirect the funds elsewhere, or lock your money in escrow beyond what you agreed to. It can only handle the gas costing parts of sending the authorize and capture calls, so you are not stuck managing ETH for gas just to buy something with USDC. Coinbase runs one such operator service, and because the protocol is open, other developers can run their own.
The reason this works without a standard token approval is a signing method called ERC-3009, which lets USDC move based on a signed authorization rather than the older approve-then-transfer pattern most swaps use. If you have read our piece on permit signatures, this will feel familiar: you are authorizing a specific transfer with a signature instead of granting a standing allowance.
What Base Pay changes about the checkout flow itself
The escrow protocol handles what happens to the money. Base Pay is mostly about trimming the steps it takes to get there. A typical crypto checkout has historically meant connecting your wallet, switching to the right network, and then confirming a transaction, three separate interruptions before you have actually paid for anything.
Base Pay compresses that into fewer prompts using newer wallet standards: a compact way to encode a wallet request as a short link or QR code, plus a signing method that lets you authorize a payment without a full wallet connection handshake first. The practical result, when a merchant has it set up correctly, is closer to tapping a card than to the multi step flow crypto checkout used to require.
What this means for your own wallet
A few practical points if you find yourself paying a merchant this way rather than just swapping tokens:
- You are still signing something specific, so read it. The same habits from our wallet signature requests article apply. A payment authorization names a receiver, a token, and a maximum amount, and those are worth glancing at before you approve.
- A refund is an onchain capture reversal, not a bank chargeback. The merchant has to actually execute a refund operation against the escrow contract. There is no card network you can separately dispute the charge through.
- You generally do not need ETH sitting around just to check out. Because an operator is handling the transaction submission, the friction of "I have USDC but no gas" mostly disappears for this specific flow, unlike a typical swap where you still need ETH for the transaction itself.
- USDC is the currency Coinbase's own materials describe here. If a checkout asks you to pay in something else entirely, that is outside what this protocol was built for, and worth more scrutiny.
The bigger picture
None of this changes what self custody means. You are still the one holding the keys, still the one reviewing what you sign, and still responsible for checking that a merchant or app integrating this protocol is legitimate before you authorize a payment to it. What changes is that paying for a physical good or service with a stablecoin on Base finally has a purpose built structure behind it, authorization, partial capture, refunds, instead of everyone improvising with plain transfers and hoping it works out.
If you hold USDC on Base and want a straightforward non-custodial wallet for everyday use, Simple Base Swap is built for exactly one network. Start at app.simplebaseswap.com, or grab the iOS or Android app.