---
title: "What is a global payments checkout? How it works in 2026"
seoTitle: "What is a global payments checkout? How it works (2026)"
description: "A global payments checkout lets shoppers in other countries pay with their local method and currency while you get paid in yours. Steps, layers, and risks."
date: "2026-10-10"
updated: "2026-10-10"
category: "payments"
author: "BlindPay Team"
faq:
  - q: "What is a global payments checkout?"
    a: "A global payments checkout is a payment page that lets a shopper in another country pay with the method and currency they already use, such as Pix in Brazil or SPEI in Mexico, while the business receives funds in its own currency. Behind the page sit payment rails, currency conversion, compliance checks, and settlement into the merchant's account."
  - q: "Is a global checkout the same as a payment gateway?"
    a: "No. A payment gateway connects a checkout to one set of methods, usually cards. A global checkout is the whole flow: the page, the local methods per country, the exchange rate, the compliance checks, and how money reaches the merchant. Many teams keep a card gateway for cards and add a second provider for local bank rails."
  - q: "What is the difference between collections and payouts?"
    a: "Collections, also called payins, are money coming in from a shopper or customer. Payouts are money going out to a seller, supplier, or employee. A checkout is mostly a collections problem, but marketplaces and platforms also pay out, so the same provider often handles both: shoppers pay by Pix or SPEI, sellers get paid in their own currency."
  - q: "Do I need a local entity to accept local payment methods?"
    a: "Not always. Some providers let a business outside the country accept local methods through their own licensed setup. With BlindPay, each merchant passes KYB as a BlindPay business customer, and payin quotes for Pix, SPEI, Transfers 3.0, PSE, ACH, wire, and RTP all go through the same API. Confirm local requirements for your products with your compliance counsel."
  - q: "How long does cross-border settlement take?"
    a: "It depends on the rail. Pix, SPEI, Transfers 3.0, and PSE payins typically arrive within minutes. US ACH and wire payins can take up to 5 business days. When the deposit lands, BlindPay converts it and delivers stablecoins to the merchant's wallet, and the merchant can withdraw to a bank account through a payout."
---

A global payments checkout is a payment page that lets shoppers in other countries pay with their own local method and currency, such as Pix in Brazil, SPEI in Mexico, or ACH in the US, while the business gets paid in the currency it keeps its books in. Underneath sit four layers: the page, the rails, settlement and FX, and compliance.

This is the hub of our 2026 global checkout series. If you already know the basics and want the routing layer, read [what payment orchestration is](/resources/more/what-is-payment-orchestration). For how merchant funds settle, see [stablecoin settlement for merchants](/resources/more/stablecoin-settlement-for-merchants).

**Key takeaways**

- A global checkout has four layers: the front-end page, payment methods and rails, settlement and FX, and compliance and risk.
- Local methods matter: in Stripe's test of 50+ payment methods, adding at least one relevant method beyond cards raised conversion by 7.4% on average.
- Bank rails differ by country: Pix in Brazil runs 24/7, SPEI in Mexico should take no more than 30 seconds after approval, Transfers 3.0 in Argentina credits in up to 15 seconds.
- Collections (payins) and payouts are separate flows, and platforms usually need both.
- BlindPay is the money layer behind the page: payin quotes over Pix, SPEI, Transfers 3.0, PSE, ACH, wire, and RTP, stablecoin settlement, and payouts out.

## What is a global payments checkout?

It is the full path a foreign shopper's money takes, from the click on "Pay" to funds the merchant can spend. The page is the visible part. Most of the work happens after the click.

A domestic checkout can get away with cards and one currency. A global one can't. A shopper in São Paulo expects Pix. A buyer in Monterrey expects to pay into a CLABE over SPEI. A US company paying a large invoice expects ACH or a wire. Each of those is a different rail, with its own data, timing, and failure modes.

Who this is for: product, engineering, and finance leads at marketplaces, SaaS platforms, and online businesses selling into Latin America and the US. Who it's not for: a store that sells only to domestic card holders.

## How does a payment move from checkout click to settled funds?

Six steps, in order. Each one can fail on its own, so each one needs its own status.

1. **Method selection.** The page shows the methods that fit the shopper's country, for example Pix for Brazil or PSE for Colombia, and hides the rest.
2. **Currency.** The page shows the price in the shopper's currency. The exchange rate gets locked in a quote, which at BlindPay lasts 5 minutes.
3. **Authentication and compliance.** The shopper's identity data gets checked where the rail requires it. Pix, for example, needs the payer's CPF or CNPJ, validated against Receita Federal check digits before the quote is issued.
4. **Routing.** The payment goes to the rail that matches the method: the Pix network, SPEI, the ACH network, and so on.
5. **Settlement.** The deposit lands, gets converted, and reaches the merchant's account or wallet.
6. **Reconciliation.** Each payment is matched to an order, using an ID, a memo code, or a webhook event, so finance can close the books.

## What are the four layers of a global checkout?

Each layer does one job, and different companies usually provide each one.

| Layer | What it does | Who typically provides it |
| --- | --- | --- |
| Front-end checkout | The page: order summary, method picker, payer fields, instructions, status | You, a hosted checkout vendor, or a coding agent building from a prompt |
| Payment methods and rails | Moves money over Pix, SPEI, PSE, Transfers 3.0, ACH, RTP, wire, cards | A payments API for bank rails, a card gateway for cards |
| Settlement and FX | Converts the shopper's currency and delivers funds to the merchant | The payments API, a bank, or an FX desk |
| Compliance and risk | KYB for merchants, payer data checks, sanctions screening, holds | The provider, with your own policies on top |

Read the table by row. The front end is where you have the most freedom. The rail and settlement layers are where most cross-border cost and delay hide.

## What is the difference between collecting and paying out?

Collecting is money in. Paying out is money out. A checkout is mainly a collection flow, but the two meet as soon as you run a marketplace or a platform.

- **Collections (payins).** A shopper pays you. At BlindPay, you create a payin quote for the amount and method, then a payin, then show the shopper the Pix code, CLABE, CBU, PSE link, or US bank details with a memo code.
- **Payouts.** You pay someone else: a seller, a supplier, a contractor. A payout quote locks the rate and fees for 5 minutes, then the payout goes out over Pix, SPEI, ACH, SEPA, or SWIFT (POBO/COBO).

A marketplace does both on every order: collect from the buyer, keep a fee, pay the seller. [Partner fees on live quotes](/resources/more/partner-fees-markup-on-live-quotes) shows how a platform adds its own margin.

## Where do global checkouts fail?

Most failures happen between the click and the settled funds, not on the page itself. The common ones:

- **The wrong methods.** Baymard reports that 9% of US shoppers abandoned a checkout because there weren't enough payment methods, and 10% because their card was declined.
- **Hidden costs.** Extra costs that are too high are the top reason for abandonment in Baymard's research, at 40%. FX surprises are part of that.
- **Expired quotes.** A rate locked for 5 minutes runs out while the shopper is in their bank app. The page has to quote again without throwing an error.
- **Bad payer data.** An invalid CPF or a wrong CUIT gets rejected. Good checkouts validate it before the shopper hits "Pay".
- **Missing memo codes.** A US bank transfer sent without the memo code can't be matched to the order.
- **Silent status.** The shopper paid, but nobody told the page. Webhooks fix this. [Stablecoin API webhooks](/resources/more/stablecoin-api-webhooks-reconciliation) covers signature checks and duplicates.

## How does BlindPay fit into a global checkout?

BlindPay is the money layer behind the page. You build the checkout, or have a coding agent build it, and BlindPay moves the money.

Each merchant becomes a BlindPay business customer: it accepts terms of service and passes KYB. When a shopper picks a method, your backend creates a payin quote. With `currency_type: "receiver"` and `cover_fees: true`, the merchant receives exactly the USD price, and the shopper sees the exact local amount with fees included. Then you create the payin and show the instructions BlindPay returns: a Pix code, a CLABE for SPEI, a CBU or CVU for Transfers 3.0, a PSE payment link, or US bank details with a memo code for ACH, wire, or RTP.

When the deposit lands, BlindPay converts it and delivers stablecoins (digital dollar tokens such as USDC or USDT) to the merchant's wallet, and `payin.complete` fires. Read the payin's `status` to know the outcome. The merchant withdraws to a bank account with a payout. Platforms add their own fee with `partner_fee_id`.

Keep your card gateway for cards. BlindPay handles the local bank rails and settlement next to it.

## Methodology and sources

External figures come from [Stripe's test of 50+ global payment methods](https://stripe.com/blog/testing-the-conversion-impact-of-50-plus-global-payment-methods) (April 2025), [Baymard Institute's cart abandonment research](https://baymard.com/lists/cart-abandonment-rate) (updated September 2025), [Banco Central do Brasil on Pix](https://www.bcb.gov.br/en/financialstability/pix_en), [Banco de México on SPEI](https://www.banxico.org.mx/services/interbanking-electronic-payme.html), and [BCRA on Transfers 3.0](https://www.bcra.gob.ar/en/transfers-3-0/). BlindPay facts come from the [payins](/docs/payins), [payin quotes](/docs/payin-quotes), and [cut-off times](/docs/kb/cut-off-times) docs, as of October 2026.

## What to do next

List the three countries where most of your foreign shoppers live and the method each one uses. Then open a BlindPay development instance and run the [payin quickstart](/docs/quickstart-payin) for the first one. That single flow, quote to settled funds, is the core of every global checkout.