QR crypto payments with no chargebacks: why a scan is final

The QR on your counter is not the payment — the rail underneath it is

Ask ten business owners what a QR payment is and you will get ten versions of the same answer: the customer points a phone at a square and the money arrives. That description is right about the gesture and wrong about everything that matters.

A QR code is a way of moving a short string of text from a screen or a sticker into a phone. What that string says decides which payment system runs, who holds the money on the way, and — the part almost nobody asks about until it bites — whether the payment can be taken back.

Three very different things routinely hide behind the same black-and-white square at a point of sale:

• A QR that opens a card payment. The code points at a hosted page or a wallet app that charges a card on file. The rail is Visa or Mastercard; the transaction lands in an acquirer's balance and pays out to your bank in one to three days. Every dispute right the card network grants the cardholder applies exactly as it would have at the terminal.
• A QR that opens a bank transfer scheme. Depending on the country this may be instant and hard to reverse, or it may sit inside a scheme with its own recall and fraud-reimbursement rules. It also usually requires a licensed bank account in that country, and stops at its border.
• A QR that carries an on-chain payment request. The code encodes a destination address, an asset, an amount and a reference. The customer's wallet builds a transfer and broadcasts it; the network confirms it; the value moves from their wallet to yours. There is no intermediary balance at any point, and therefore no intermediary with the power to reverse it.

Only the third one gives you QR crypto payments with no chargebacks. The other two give you a convenient way to start a payment on a rail that still allows reversals. If a processor tells you "QR payments have no chargebacks" without telling you which rail settles, that claim is about the packaging, not the payment.

What a card-present dispute actually costs a small business

The comfortable assumption in face-to-face retail is that disputes are an e-commerce problem. The customer was standing in front of you, they took the goods, they left happy — what is there to argue about?

Plenty, as it turns out, and the rulebook says so in writing. The Visa Core Rules and Visa Product and Service Rules set out dispute conditions and the time limit attached to each, and those limits are counted in 120 calendar days from the transaction — extending as far as 540 days in some circumstances where the customer was waiting on goods or services. A payment you counted into your till in March can be pulled back out of your account in July.

The EMV chip in the terminal does not close that door. What the liability shift settled was counterfeit card fraud: process a chip transaction properly and the cost of a cloned card generally stays with the issuer. It says nothing about the cardholder who recognises the charge perfectly well and disputes it anyway — the category the industry politely calls first-party or "friendly" fraud, which merchant surveys have reported rising year after year.

And the loss is never just the ticket. LexisNexis Risk Solutions' 2026 True Cost of Fraud study puts the all-in cost at more than $5 for every $1 of direct fraud loss in US retail and e-commerce — the first time that multiplier has crossed five. For a business taking face-to-face payments, that multiplier is made of concrete things:

• The goods are gone. A haircut, a meal, a repair, a session — you cannot restock a service.
• The dispute fee. Charged per case by most acquirers, win or lose.
• The hours. Somebody pulls the receipt, the CCTV timestamp and the signed job sheet, writes the rebuttal, and uploads it to a portal — usually the owner, usually at night.
• The ratio. Disputes accumulate against thresholds written into your merchant agreement. Cross them and you get monitoring, reserves, higher rates, or a closed account — and a business with a closed account and no alternative rail stops trading that week.

None of that is exotic. It is the ordinary tax on accepting a reversible payment for an irreversible service.

Why the card rail cannot simply switch reversibility off

It is tempting to read chargebacks as a policy choice someone could reverse with a better contract. They are not. They are structural, and understanding why is what makes the alternative make sense.

A card payment is not a transfer of money. It is a promise to settle, made by an issuer against a credit line or a deposit account, and routed through an acquirer. At no point during the sale does the customer's money reach you. What reaches you, a day or three later, is a net settlement from your acquirer for a batch of promises — minus fees, minus reserves.

Because the money passes through parties who hold it, those parties can be instructed to reverse it. The dispute process is the mechanism by which the issuer, who is the customer's bank and answers to the customer, unwinds the promise and takes back the settlement. That is not a bug in the design; it is the consumer protection the card networks exist to sell. The merchant carries the risk because the merchant is the one who wanted the sale.

This structure creates three costs that no QR presentation layer can remove:

• A settlement delay, because the promise has to clear before it becomes money.
• A custodian, because someone must hold the funds while that happens — and whoever holds them can also freeze them.
• A reversal window, because the whole product is built on the ability to take a payment back.

Put a QR in front of that and you have changed how the payment is initiated. You have not changed what it is.

How Payzum makes a QR payment final instead of merely fast

Payzum is a non-custodial, crypto-only payment processor. The distinction matters here more than anywhere else in the product, because finality is a direct consequence of non-custody.

When a customer scans a Payzum POS QR, their wallet reads a payment request: the asset, the amount, the chain and a reference tying the transfer to that sale. They approve it, and their wallet broadcasts a transfer from their address to an address you control. Payzum never appears in the flow of funds. There is no Payzum balance where your takings rest overnight, no payout schedule, and no risk desk deciding whether today is a good day to release your money.

That is why there is nothing to reverse. A chargeback needs a custodian to instruct. In an on-chain payment there is no custodian — the settlement is the payment. Once the network has confirmed the transfer, the value is in your wallet and the transaction is part of a public ledger that nobody rewrites because a customer changed their mind.

Fast, and fast in the way that matters

Confirmation is roughly 0.4 seconds on Solana and around two seconds on Base and Polygon — quick enough that the cashier watches the status flip to paid before the customer has put their phone away. Compare that with a card authorisation, which is also quick, but which only authorises; the money still arrives days later. Here the two events are the same event.

Dollars, not a price chart

"I price in dollars, I can't hold something that moves" is the right instinct, and the answer is a setting. Turn on auto-convert and whatever the customer pays with arrives in your wallet as USDC or USDT, so the figure that lands matches the figure on the ticket. The chain is the transport; the stablecoin is the unit of account. If you are deciding between the two, we compared them in USDT vs USDC for payments.

A new QR per sale, not a sticker on the till

Static QR codes — one printed code taped to the counter, reused all day — are where QR payments go wrong. The customer types the amount themselves, so they type it wrong; nothing ties a transfer to a sale, so you reconcile by eye; and anyone can photograph the code.

Payzum's POS issues a dynamic QR for each sale, with the amount and the reference already inside it. The customer cannot underpay by accident, the transfer arrives labelled, and the code is spent once. Cashiers get their own PIN login, so the takings break down by cashier and by terminal at the end of the shift — the mechanics of that are in crypto POS with PIN cashiers.

How to take a QR crypto payment, step by step

From the counter's point of view this is a shorter sequence than the card flow it replaces. There is no terminal to pair, no acquirer to underwrite you, and no bank account to attach.

1. Create the account and point it at your own wallet. Sign up, switch on 2FA, and set the wallet address that receives your takings — one you already control, on Solana, Base, Polygon or any other supported chain. Turn on auto-convert to USDC or USDT if you price in local currency or dollars. Nothing is ever held by Payzum, so there is no balance to configure and no payout schedule to wait for.
2. Open the POS on any phone or tablet. No hardware purchase, no rental, no SIM. A staff phone or the tablet already by the till becomes a terminal — the full walkthrough is in turn your phone into a crypto POS. If you run a busier counter and prefer a dedicated device, physical terminals are available too.
3. Add your cashiers with PIN logins. Each person who takes money gets their own PIN. They can raise a sale and see it settle; they cannot change the destination wallet or export your keys. Every payment carries the cashier and the terminal it came from.
4. Charge: type the amount, show the QR. The cashier enters the total, the app generates a QR for that exact sale, and the customer scans it with their own wallet and approves. The screen shows pending, then paid. Total elapsed time is usually under five seconds.
5. Watch it land — and stop worrying about it. The stablecoins are in your wallet at the moment the status flips. No batch, no settlement file, no next-business-day. If you also sell online, the same account covers hosted checkout, payment links and invoices from the same dashboard and the same wallet.
6. Publish the refund policy that replaces the dispute process. This is the step people skip, and it is the most important one. Payments on this rail are final, which means your written refund, exchange and cancellation terms are now the entire agreement between you and the customer. Put them on the receipt and on the wall, and honour them quickly — a fast voluntary refund is cheaper and better for your reputation than a dispute you were going to lose anyway.

Use cases: where "no chargebacks" stops being abstract

The value of finality is not evenly distributed. It is largest wherever what you sold cannot be taken back, and wherever the ticket is big enough that a single reversal hurts.

• The barbershop or beauty salon. A colour treatment takes three hours of a stylist's day and cannot be returned to stock. When a card charge is disputed weeks later, the salon has paid for the product, the chair and the labour, and is now also paying the dispute fee. A QR paid in USDC at the end of the appointment closes the transaction the moment the client stands up. We wrote the full version for barbershops and for hair salons.
• The restaurant, food truck or market stall. High volume, low margin, and a card processor taking a slice of every ticket plus a monthly terminal rental. A phone showing a QR per table or per order costs nothing to add, works at a festival with no power socket for a terminal, and the takings are in the owner's wallet before the service ends — the food truck walkthrough covers the mobile case in detail.
• The workshop with a four-figure invoice. A mechanic replacing a gearbox, a builder finishing a bathroom, a dentist fitting an implant. These are the tickets where a card limit is awkward, a bank transfer is slow, and a dispute at 120 days is a month of profit. The customer scans once, the payment is final, and the job sheet is the record.
• The tourist-facing business. Dive centres, tour operators, hotels, car hire — customers arriving from a dozen countries whose cards decline abroad, or whose banks treat a foreign merchant as high risk. A QR paid in stablecoins does not care about the issuing country, the currency or the border. See dive centres and tour operators.
• The pop-up, the market day, the event stand. No fixed premises, no acquirer relationship worth opening for six trading days a year, and often no reliable card signal. One phone, one QR per sale, money in your own wallet — the general case is in accepting crypto payments in person.

Card QR vs on-chain QR — the same gesture, two different rails

Common objections, answered

"If there are no chargebacks, what protects my customer?"

Your policy — and that is a more honest arrangement than it sounds. On a card rail the customer's protection is outsourced to their issuer, which is why you find out about a problem six weeks later through a portal instead of at your counter. With a final payment, a customer who is unhappy comes back to you, and you make it right under the terms they accepted at the point of sale. Businesses that already run a clear, quick, visible refund policy lose nothing by moving to this rail. Businesses that were quietly relying on disputes to filter their customer service will feel the difference, and should write the policy before switching the method on.

"Can a customer scan the QR and not actually pay?"

They can walk away mid-flow, exactly as they can with a declined card, and the sale simply does not complete — the POS shows it as unpaid and the cashier can raise it again. What cannot happen is the reverse case: a payment that shows as confirmed and then disappears. Confirmation means the network has settled the transfer into your wallet. Because each QR is generated for one sale with the amount inside it, you also avoid the classic static-QR failure where somebody pays $4 for a $40 item and nobody notices until closing.

"My customers don't have crypto wallets."

Some do not, and this is an additional payment method rather than a replacement for whatever you take today. But the population that does is larger and more ordinary than it was two years ago, and it is concentrated exactly where card rails serve you worst: tourists, customers from countries whose cards decline abroad, people who hold dollars in stablecoins because their local currency does not hold value, and high-ticket customers who would rather not put a €3,000 repair on a card. You do not need every customer to use it. You need the ones your current rail handles badly.

"What about volatility — and what if the customer pays in something else?"

Let them. The customer can pay from the coin they hold on the chain they use, and with auto-convert switched on it arrives in your wallet as USDC or USDT at the amount you charged. You never quote a price in anything but your own unit of account, and you never hold an asset that moves unless you choose to.