Turning Stablecoins into the Default Checkout Button Across LATAM.

Stroll by any city where in-real-life crypto payments are being attempted right now. You’ll spot three or four QR stickers competing for attention: a local bank app, a regional fintech, and—if the owner has a crypto-savvy nephew—a laminated “Pay with USDC” sign no one quite understands yet.

Cards still skim 1.5 – 3.5 % and pay two days late. Stablecoins clear in seconds for pennies—so why is the Verifone still king?

Because wallets and POS terminals speak different dialects and shoppers show up empty-handed.

Merchants care about two numbers:

1. Fee percentage – Card processing still averages 1.5 – 3.5 % per swipe in most markets

2. Settlement delay – T + 2 days (or longer) for pesos to hit the bank.

A USDC transfer on an L2 clears in seconds for a fraction of a cent. It’s no wonder 71 % of Latin-American firms already use stablecoins for cross-border payments.

So why isn’t every coffee shop ditching cards tomorrow? Two words: cold start.

To pay in USDC/USDT, customers first need:

1. A wallet they actually understand.

2. Liquidity—stablecoins loaded and ready to spend.

No wallet is yet built for the checkout line. Consumers that have installed crypto wallet have either:

• A General-Purpose wallet (CB Wallet, Phantom, Metamask). These are multi-chain, asset-rich, great for Defi, but utterly confusing for the general public.

• A Payments-first wallet (Decaf, Sling, ugly cash,…). Great exposure to stablecoins, and maybe a debit card, but still no way to interact with a POS.

We need to build more than “just a better wallet”. We need a tightly integrated, opinionated (but based on open standards) whole stack so that the payments process is delightful instead of clunky.

On/Off-Ramp Rails. Users need options to move money inside and outside of the wallet without feeling trapped or going through 20 screens for KYC. ZAR is a great example of solving this problem.

Wallet UX. Account-Abstracted, Face ID, onchain-FX to switch between dollars and pesos.

Payment-Request Standard. Wallet <> POS handshake. Either QR or NFC-based spec to transmit amount, asset, network. x402 and eip-7856 come to mind as possible building blocks.

Auto-bridging. Regardless of what assets the wallet or the POS expects, bridging digital dollars should be configurable, effortless, and instant. Daimo Pay has done a great job at simplifying this for online commerce.

Settlement Signaling. QRs are not enough. We need instant notifications between both the paying wallet and the POS to let the participants know that the transaction settled successfully.

Merchant Tools. SMBs might be ok with a simpler POS, but larger retailers need better tooling: offramping workflows, tax reporting, POS management for stores with multiple cash registers, refund flows, treasury management, etc.

1. Complete your order at the register.

2. The cashier inputs the amount to charge, similar to a verifon/ingenico device.

3. The POS shows a QR or NFC signal

4. The buyer taps or scans the QR

5. The wallets shows:

   1. The amount in USDC or Pesos

   2. An option to leave a tip

   3. A confirm button

At this point there's no notion of networks or assets, just digital dollars.

1. Depending on the expected currency on the POS the wallet performs a just-in-time, fx-enabled, intent bridge, or a simple onchain transfer.

2. Both participants receive confirmation as soon as the transaction settles on the blockchain:

   1. Merchant’s POS shows “$22.50 settled”

   2. The Buyer's wallet shows a receipt of the amount paid, and the name of the merchant. Similar to ETH Receipts

3. The customer walks out with their order

Crypto payments won’t win because they’re futuristic; they’ll win because they’re cheaper, faster, and invisible. Solve the cold-start problem, and the word “crypto” quietly drops out of the conversation.

We're building this for LATAM. If you're looking for an early engineering team to join, drop us a line amhed[at]paymentstack[dot]io

Turning Stablecoins into the Default Checkout Button Across LATAM.

Stroll by any city where in-real-life crypto payments are being attempted right now. You’ll spot three or four QR stickers competing for attention: a local bank app, a regional fintech, and—if the owner has a crypto-savvy nephew—a laminated “Pay with USDC” sign no one quite understands yet.

Cards still skim 1.5 – 3.5 % and pay two days late. Stablecoins clear in seconds for pennies—so why is the Verifone still king?

Because wallets and POS terminals speak different dialects and shoppers show up empty-handed.

Merchants care about two numbers:

1. Fee percentage – Card processing still averages 1.5 – 3.5 % per swipe in most markets

2. Settlement delay – T + 2 days (or longer) for pesos to hit the bank.

A USDC transfer on an L2 clears in seconds for a fraction of a cent. It’s no wonder 71 % of Latin-American firms already use stablecoins for cross-border payments.

So why isn’t every coffee shop ditching cards tomorrow? Two words: cold start.

To pay in USDC/USDT, customers first need:

1. A wallet they actually understand.

2. Liquidity—stablecoins loaded and ready to spend.

No wallet is yet built for the checkout line. Consumers that have installed crypto wallet have either:

• A General-Purpose wallet (CB Wallet, Phantom, Metamask). These are multi-chain, asset-rich, great for Defi, but utterly confusing for the general public.

• A Payments-first wallet (Decaf, Sling, ugly cash,…). Great exposure to stablecoins, and maybe a debit card, but still no way to interact with a POS.

We need to build more than “just a better wallet”. We need a tightly integrated, opinionated (but based on open standards) whole stack so that the payments process is delightful instead of clunky.

On/Off-Ramp Rails. Users need options to move money inside and outside of the wallet without feeling trapped or going through 20 screens for KYC. ZAR is a great example of solving this problem.

Wallet UX. Account-Abstracted, Face ID, onchain-FX to switch between dollars and pesos.

Payment-Request Standard. Wallet <> POS handshake. Either QR or NFC-based spec to transmit amount, asset, network. x402 and eip-7856 come to mind as possible building blocks.

Auto-bridging. Regardless of what assets the wallet or the POS expects, bridging digital dollars should be configurable, effortless, and instant. Daimo Pay has done a great job at simplifying this for online commerce.

Settlement Signaling. QRs are not enough. We need instant notifications between both the paying wallet and the POS to let the participants know that the transaction settled successfully.

Merchant Tools. SMBs might be ok with a simpler POS, but larger retailers need better tooling: offramping workflows, tax reporting, POS management for stores with multiple cash registers, refund flows, treasury management, etc.

1. Complete your order at the register.

2. The cashier inputs the amount to charge, similar to a verifon/ingenico device.

3. The POS shows a QR or NFC signal

4. The buyer taps or scans the QR

5. The wallets shows:

   1. The amount in USDC or Pesos

   2. An option to leave a tip

   3. A confirm button

At this point there's no notion of networks or assets, just digital dollars.

1. Depending on the expected currency on the POS the wallet performs a just-in-time, fx-enabled, intent bridge, or a simple onchain transfer.

2. Both participants receive confirmation as soon as the transaction settles on the blockchain:

   1. Merchant’s POS shows “$22.50 settled”

   2. The Buyer's wallet shows a receipt of the amount paid, and the name of the merchant. Similar to ETH Receipts

3. The customer walks out with their order

Crypto payments won’t win because they’re futuristic; they’ll win because they’re cheaper, faster, and invisible. Solve the cold-start problem, and the word “crypto” quietly drops out of the conversation.

We're building this for LATAM. If you're looking for an early engineering team to join, drop us a line amhed[at]paymentstack[dot]io