Insights

Is the Customer's Receipt Enough? What a Counter Team Should Trust Before Releasing Goods

A customer holds up a phone and says the crypto payment went through. Here is what a cashier should rely on instead, and how to train for it.

Is the Customer's Receipt Enough? What a Counter Team Should Trust Before Releasing Goods

Picture a busy counter. The customer scans your QR code, holds up their phone and says, "It's sent." Your terminal still shows a pending state. Should the cashier hand over the goods? No. The merchant's confirmation state is the signal staff should work from, not the customer's screen.

Why the customer's phone is not proof

MiraclePay describes the in-person flow simply: the merchant creates a payment request, the customer scans it with their own wallet and sends the exact amount on the network shown. A wallet that shows a submitted transfer tells you the customer acted. It does not tell you the merchant side has confirmed the sale.

Other providers say the same thing. Coinbase's checkout documentation notes that payment confirmation is asynchronous and warns against fulfilling from a success redirect or from a status that still reads active. Its guidance is to fulfill only when the status is completed. The principle carries over to the counter: act on the confirmed state.

What the cashier does

Keep the routine short enough to repeat under pressure. Create the order for the exact sale, display the QR, and tell the customer to pay the amount and network shown. Then watch the payment screen. MiraclePay's QR page says staff get a visible confirmation state to work from, and that is the only trigger for handover.

If the customer insists they have paid, the cashier stays friendly and does not argue. A line such as "Thanks, I'm just waiting for our screen to confirm" keeps the goods at the counter without blaming anyone. If the screen does not confirm, the cashier follows your escalation rule and calls a supervisor instead of improvising.

What the customer should know

Customers move faster when expectations are set before they scan. A small sign can say that the wallet must support the exact asset and network shown, and that staff will release the order once the payment is confirmed. MiraclePay advises confirming wallet compatibility with the wallet provider before a live payment, so the sign should say so too.

Make it a habit

Run a few practice sales with new staff and include one awkward case where the customer says they have paid but the screen disagrees. Reconciliation is easier when each sale uses its own order reference, which MiraclePay says follows the transaction into reporting. Before going live, confirm your account's eligibility and approved market with MiraclePay.

Before enabling live payments, confirm merchant transaction fees for your account configuration.

Sources & context

This article is published by MiraclePay. Product availability, supported assets, networks and settlement terms should be confirmed for the relevant merchant account before launch.

Related merchant paths: Explore crypto QR code payments · Explore the crypto POS system · Explore the U.S. merchant payment gateway · See crypto-to-USD settlement.

Build your launch path

See if MiraclePay
fits your market.

Become a Merchant