What is a stablecoin checkout? Two models explained (2026)

A stablecoin checkout is a payment page where stablecoins carry the value from the shopper to the business. It comes in two models. In the wallet model the shopper pays USDC or USDT from their own wallet. In the settlement model the shopper pays with a local method like Pix or SPEI, and the business receives stablecoins after the deposit lands.

Readers mix the two up all the time, and the choice changes who your checkout can serve. This guide explains both, as of October 2026. For the full picture of the checkout stack, start with what a global payments checkout is.

Key takeaways

• There are two stablecoin checkout models: the shopper pays in stablecoins, or the shopper pays locally and the business settles in stablecoins.
• A stablecoin is a digital dollar token such as USDC or USDT. In the settlement model the shopper never touches one.
• Stripe's test of 50+ payment methods found an average 7.4% conversion lift when businesses showed at least one relevant method beyond cards, which favors local methods at checkout.
• BlindPay runs the settlement model: shoppers pay by Pix, SPEI, Transfers 3.0, PSE, ACH, wire, or RTP, and the merchant receives USD stablecoins.
• The off-ramp matters as much as the on-ramp. Check that the provider converts to local currency on named rails.

What are the two models of stablecoin checkout?

The difference is who holds the stablecoin. In model A the shopper does. In model B only the business does.

Model A: the shopper pays from a wallet. The checkout shows a wallet address or a QR code. The shopper opens their crypto wallet, sends USDC or USDT, and the merchant's wallet receives it. This works when your buyers already keep dollars on-chain, such as freelancers paid in USDC or crypto-native teams.

Model B: the shopper pays locally, the business settles in stablecoins. The checkout shows a local payment method. A Brazilian shopper copies a Pix code into their bank app. A Mexican shopper sends a SPEI transfer to a CLABE. Once the money lands, the provider converts it and delivers stablecoins to the merchant. The shopper only ever sees their own currency and their own bank.

How merchants accept stablecoin payments covers the merchant side of model A in more detail.

Why do businesses settle in stablecoins behind the checkout?

Because the business gets dollars fast without asking the shopper to change how they pay. Local rails collect the money, and stablecoins move it to the merchant.

Three reasons come up most:

• Speed. Instant rails settle fast at the source. Banco de México says a SPEI payment should take no more than 30 seconds after approval, and Pix runs 24/7. Converting to stablecoins right after the deposit keeps that speed on the merchant side.
• One dollar balance. Pesos, reais, and dollars from US bank transfers all end up as USDC or USDT in one place. That is simpler to reconcile than a bank account per country.
• Hours. A stablecoin balance can move on a weekend. A merchant does not wait for a correspondent bank to open.

The local method itself drives conversion. Stripe's test of more than 50 payment methods, published April 2025, found businesses that surfaced at least one relevant method beyond cards saw on average a 7.4% increase in conversion and a 12% increase in revenue. Results varied by method, country, and industry, and Pix was not part of that test. Do local payment methods raise checkout conversion? walks through the numbers.

What are the limits of stablecoin checkout?

Each model has a weak spot. Know it before you build.

• Off-ramp availability. A stablecoin balance only helps if you can turn it into the currency you spend. Ask which rails the provider pays out on, by country, not just which countries it lists.
• Compliance. Someone must verify the merchant (KYB), screen payments against sanctions lists, and monitor activity. In model B that sits with the provider running the local rails. In model A, a raw wallet address gives you little information about the payer.
• Finality and refunds. An on-chain transfer is final once confirmed. Refunds become a new payment in the other direction, not a reversal. Plan a refund process before launch.
• Shopper reach. Model A only reaches people who already hold stablecoins. Model B reaches anyone with a bank account in a supported country.

How does a settlement model checkout work, step by step?

The shopper pays in local currency and the merchant receives stablecoins in minutes on instant rails. Here is the flow for a Brazilian shopper paying a US merchant by Pix:

1. The merchant prices the order in USD, for example US$86.00.
2. The checkout requests a payin quote for Pix. The quote locks the rate and fees for 5 minutes and returns the BRL amount the shopper pays, fees included.
3. The shopper enters their CPF. The quote validates it against the Receita Federal check digits before any money moves.
4. The checkout creates the payin and shows the Pix code as a QR code and as copyable text.
5. The shopper pays from their bank app. Pix payins typically arrive within minutes.
6. The provider converts the reais and delivers USD stablecoins to the merchant's wallet, then sends a webhook.
7. The merchant withdraws to a bank account whenever it wants, with a payout quote.

The shopper never sees a token. The merchant never handles reais. Stablecoin settlement for merchants compares this timing with card settlement.

How do you pick a stablecoin checkout model?

Start from how your buyers pay today. Then check what you need on the way out.

• Your buyers pay by bank transfer and see prices in local currency. Use the settlement model. That covers most consumer and SMB checkouts in Brazil, Mexico, Colombia, and Argentina.
• Your buyers already hold USDC or USDT. Offer wallet payments, but keep a local method next to it, since most people still pay from a bank.
• You need to pay suppliers or sellers in local currency. Pick a provider whose payout side covers your corridors on named rails.
• You are a platform with many merchants. You need KYB per merchant and a way to earn a fee on each payment.

Some gateways accept stablecoins into the merchant's wallet without converting to local fiat on either side. Stablecoin API vs crypto payment gateway explains that split. Ask any provider whether it converts to local currency and on which rails.

How does BlindPay fit into a stablecoin checkout?

BlindPay runs the settlement model through one API. You build the checkout page and sessions, and BlindPay moves the money.

Shoppers pay with the rail they already use: Pix in Brazil, SPEI in Mexico, Transfers 3.0 in Argentina, PSE in Colombia, or ACH, wire, or RTP in the US. Each payment starts with a payin quote that locks the amount, the fees, and the destination for 5 minutes. With a receiver-denominated quote and cover_fees set to true, the merchant receives exactly the USD price and the shopper's local amount includes fees and exchange.

Once the deposit lands, BlindPay converts it and delivers USDC or USDT to the merchant's wallet, then fires payin.complete. Read the payin's status to know whether it completed. BlindPay-managed wallets are custodial. Payouts from a wallet you control are non-custodial: you authorize the exact amount and BlindPay executes that single transaction.

For the way out, merchants withdraw with a payout quote over ACH, RTP, wire, SWIFT (POBO/COBO), Pix, SPEI, SEPA, or Faster Payments. Merchant KYB, sanctions screening, and monitoring run inside the flow. Fees vary by rail and appear in the live quote before execute.

Who this is for: fintechs, platforms, and merchants selling into Latin America and the US who want dollar settlement without asking shoppers to use crypto.

Methodology and sources

External facts: Stripe's test of 50+ payment methods (April 10, 2025), Banco de México on SPEI, and Banco Central do Brasil on Pix. BlindPay facts come from the payins, payin quotes, and cut-off times docs. Rules on stablecoins vary by country, so confirm your requirements with your compliance counsel.

What to do next

Write down where your buyers are and how they pay today. If the answer is a bank app, open a BlindPay development instance and run the payin quickstart with a Pix or SPEI quote to see the settlement model end to end.