Marketplace checkout: collect locally, pay sellers in their currency
How a 2026 marketplace checkout collects by Pix, SPEI, PSE, or ACH, keeps its commission, and pays each seller in their own currency on local rails.
A marketplace checkout lets the shopper pay in local currency over a rail like Pix, SPEI, PSE, or ACH, keeps the marketplace's commission as a fee on that payment, and pays each seller in their own currency. On BlindPay the payment settles as USD stablecoins, and payout quotes deliver BRL, MXN, COP, ARS, USD, EUR, or GBP to the seller's bank.
This guide covers the checkout side of a marketplace as of October 2026: who owns the balance, where the commission comes from, and which rail pays which seller. For the general payout playbook, read marketplace payouts in Latin America. For the checkout basics, start with what is a global payments checkout.
Key takeaways
- Shoppers pay on their own rail: Pix in Brazil, SPEI in Mexico, PSE in Colombia, Transfers 3.0 in Argentina, ACH, wire, or RTP in the US.
- The marketplace's commission rides on the payin as a BlindPay partner fee, collected per transaction and released on the first day of the following month.
- Sellers get paid from one USD stablecoin balance over Pix, SPEI, ACH Colombia, Transfers 3.0, ACH, RTP, wire, SEPA, Faster Payments, or SWIFT (POBO/COBO).
- Payout quotes lock the rate and fees for 5 minutes, so each seller sees the exact local amount before you send.
- Every party that owns money in the flow must be visible to BlindPay. Onboard sellers as customers, or run the marketplace as merchant of record with counsel's sign-off.
How does money move in a marketplace checkout?
Money moves in three legs: the shopper pays in, the commission comes off, and the seller is paid out.
- The shopper picks a rail. The checkout shows the rails for the shopper's country and creates a payin quote for the order.
- The shopper pays. Pix code, CLABE, PSE link, Argentine account, or US bank details with a memo code, depending on the rail.
- The payment settles. BlindPay detects the deposit, converts it, and credits USD stablecoins (USDC or USDT, digital dollar tokens) to the destination wallet. A
payin.completewebhook fires when the payin finishes; read itsstatus. - The commission comes off. The partner fee on the quote is collected during the payin.
- The seller is paid. A payout quote locks the rate for 5 minutes, then the payout executes to the seller's bank account in their currency.
Legs 1 to 3 take minutes on Pix, SPEI, Transfers 3.0, and PSE. Leg 5 runs on the seller's rail, on your schedule.
Who should own the balance: the seller or the marketplace?
Pick one model before you write code. It decides who goes through onboarding and whose wallet each payin lands in.
| Seller-owned balances | Marketplace as merchant of record | |
|---|---|---|
| Who is the BlindPay customer | Each seller, plus the marketplace instance | The marketplace |
| Onboarding | KYB or KYC for every seller | KYB for the marketplace |
| Where the payin lands | The seller's own wallet | The marketplace's wallet |
| How the marketplace earns | Partner fee on each payin quote | Its margin on the sale |
| How sellers get paid | Payout from the seller's wallet to the seller's bank account | Payout from the marketplace's wallet to the seller as a supplier |
| Best for | Platforms where sellers set prices and own revenue | Marketplaces that buy and resell |
The constraint comes from BlindPay's nested payments rule: you may not move money for a party BlindPay has not onboarded, screened, or approved. One account that collects for many underlying sellers is a sign of nesting. Seller-owned balances avoid it by making every seller a customer. The merchant of record model works only when the funds really are the marketplace's own. Confirm which model fits with your compliance counsel.
Which rail pays which seller?
Pay each seller on the local rail of their bank account. The table shows the rail and typical settlement per country.
| Seller's country | Payout rail | Currency | Typical settlement |
|---|---|---|---|
| Brazil | Pix, PIX Safe, TED | BRL | Pix and PIX Safe in minutes; TED about 1 to 2 business days |
| Mexico | SPEI | MXN | Minutes |
| Argentina | Transfers 3.0 | ARS | Minutes |
| Colombia | ACH Colombia | COP | About 1 business day |
| United States | ACH, RTP, domestic wire | USD | RTP instant; ACH and wire about 1 to 2 business days |
| SEPA zone | SEPA | EUR | About 1 to 2 business days |
| United Kingdom | Faster Payments | GBP | About 1 to 2 business days |
| Rest of world | SWIFT (POBO/COBO) | USD | Up to 5 business days, with UETR tracking and MT103 confirmations |
The local rails on the shopper side are fast by design. Banco de México says a SPEI payment should not take more than 30 seconds after approval. Argentina's central bank describes Transfers 3.0 as credited online in a maximum of 15 seconds. Pix runs 24/7. In the US, RTP settles 24/7/365 with final settlement.
For EUR destinations, which countries are in SEPA lists every country a SEPA payout can reach.
When should a marketplace pay its sellers?
Pay on a schedule your refund policy can survive. Fast rails make a slow policy a choice, not a constraint.
- Instant release suits digital goods and services delivered at checkout.
- Release on delivery suits physical goods. Hold the seller's share until the order is marked delivered, then quote and pay.
- Batched payouts suit sellers who prefer one transfer a week. Quote each payout when you send it, since a quote lasts 5 minutes.
Refunds are easier before the seller is paid. Bank transfer payments do not carry card-style chargebacks, so the refund is a payout back to the shopper, funded from the balance that still holds the money. Keep the window between sale and seller payout at least as long as your return window.
How does BlindPay fit into a marketplace checkout?
BlindPay is the money layer under the marketplace: collection on local rails, settlement in USD stablecoins, the commission, and the seller payouts.
- Collection over Pix, SPEI, PSE, Transfers 3.0, ACH, wire, and RTP, with payin quotes priced in USD through
currency_type: "receiver"so the seller's share is exact. - Commission through partner fees in basis points and cents, collected per payin and paid out monthly, net of your BlindPay invoice.
- Seller onboarding with KYB for businesses and KYC for individuals, so every owner of funds is visible.
- Seller payouts over Pix, SPEI, ACH Colombia, Transfers 3.0, ACH, RTP, wire, SEPA, Faster Payments, and SWIFT (POBO/COBO), each with a 5-minute quote.
- Webhooks for every payin and payout, so your marketplace ledger updates without polling.
You build the storefront, the cart, and the release rules. To fund many currencies from one treasury, see running multi-currency payouts from a single USDC balance.
Methodology and sources
BlindPay facts come from the payins, payment methods, partner fees, nested payments, and payouts docs, read in October 2026. External sources: Banco de México on SPEI, the BCRA on Transfers 3.0, Banco Central do Brasil on Pix, and The Clearing House on RTP. Settlement times are typical, not guaranteed, and holds for review can add time.
What to do next
Decide whether sellers own their balances or the marketplace is merchant of record, and write it down with your counsel. Then list your top five seller countries, match each to a payout rail in the table above, and run one payin and one seller payout on a development instance.
FAQ
More payments articles
See all payments articlesStablecoin payouts for NGOs and aid programs: fixed local amounts, local rails, and donor-ready records
How aid programs use stablecoin payouts: lock the local amount each household gets, pay over Pix or SPEI, screen recipients, keep donor-ready records.
How to build a global checkout like Stripe with BlindPay
Yes, you can build a Stripe-style global checkout on BlindPay: sessions, a hosted page, Pix, SPEI, PSE, Transfers 3.0, ACH, wire, and RTP, paid out in USD.
How to evaluate a global checkout provider: 12 questions
A 2026 scorecard for choosing a global checkout provider: 12 questions on rails, pricing, sandbox, webhooks, compliance, settlement, and custody.