Cash vouchers, payment slips and convenience store payments

What a cash voucher payment actually is

The mechanics are consistent across countries even though the brands differ. At checkout the customer chooses cash. Your system asks the provider to issue a voucher, which comes back with a reference number, a barcode or a printable slip, and an expiry date. The customer takes that reference to a participating shop, bank branch, lottery outlet or ATM, or pastes the number into their banking app, and hands over cash. The provider receives confirmation from the collection network and notifies you, usually by webhook, and only then do you fulfil. Nothing about the customer's card or bank account is involved until they choose to involve it. In Mexico the best-known network is OXXO, in Brazil it is Boleto, in Japan it is konbini payment at convenience stores, and similar over-the-counter models exist in Colombia, Peru and Egypt. From the merchant's side the important thing is that a voucher is an instruction to pay, not a payment, and your order state machine needs to reflect that difference from the first day.

• Treat a voucher as a pending order with an expiry date, never as a completed sale.
• Store the voucher reference, the barcode and the expiry date against the order as soon as it is issued.
• Fulfil only on a server-to-server confirmation from the provider, never on the customer saying they paid.
• Design the order state to handle expired, cancelled and paid-late as distinct outcomes.

Why over-the-counter cash still matters

The obvious reason is that large numbers of people hold no card that works online, or hold one and prefer not to use it. The second reason is trust: paying cash in a shop you walk past every day feels safer to many first-time online buyers than typing a number into a website. The third is that cash is how a whole household shops. One person with a bank app may be paying for several people who are not online at all. For a merchant this means cash collection is not a nostalgic legacy option. In several markets it is the difference between serving the mass of consumers and serving only the banked minority. It also converts well for specific products: gaming credit, mobile top-ups, event tickets, bus tickets, utility bills and modest-sized retail orders. The flip side is that cash buyers often behave differently. They are more likely to be first-time buyers, more likely to need reassurance, and more likely to need a reminder before the voucher expires.

• Offer cash wherever a meaningful share of your target customers are unbanked or underbanked.
• Expect cash buyers to need more reassurance at checkout, including clear instructions and a visible expiry date.
• Test cash on the product categories where it already works locally, such as top-ups, tickets and small retail orders.
• Do not assume cash buyers behave like card buyers when you plan reminders and customer support.

The delayed-confirmation problem

Every voucher method shares one characteristic: the money arrives later than the order. Depending on the country and the collection network, confirmation can take hours or a couple of business days after the customer pays at the counter, and the provider's settlement to you starts from that confirmation rather than from the moment you issued the voucher. Plan three things around it. First, inventory. If you reserve stock on issue rather than on payment, you will tie up stock for orders that never get paid. Second, customer expectation. Tell people at checkout how long confirmation takes, then repeat it in the confirmation email, because an anxious customer contacts support. Third, digital fulfilment. If you sell something instant, do not release it on voucher issue. Some providers now offer faster variants that layer instant rails onto a voucher flow, which are worth asking about, but the default assumption should always be that confirmation is not immediate.

• Reserve stock on payment confirmation, not on voucher issue, or set a short reservation window that expires.
• State the expected confirmation time on the checkout page and repeat it in the confirmation message.
• Never release digital content before the provider confirms the payment server-to-server.
• Ask whether your provider offers a faster voucher variant built on an instant payment rail.

Expiry, non-payment and how to handle both

A meaningful share of vouchers are never paid. Some customers change their minds, some lose the slip, some find the shop queue too long, and some simply forget. Every provider handles expiry differently, so you need to know exactly what yours does: whether the voucher is cancelled automatically on the due date, whether you must call an API to cancel it, and whether a late payment is accepted or bounced back to the customer. The good news is that non-payment is recoverable in a way that a failed card payment often is not. Send a reminder on the day of issue with the reference and a link, another the day before expiry, and make it trivially easy to reissue. Watch your expiry window as a performance metric. If a large share of your paid orders arrive on the last day, your window may be too short, or your reminders may be too weak, and both are cheap to fix.

• Confirm whether expiry is automatic or requires you to call a cancellation endpoint.
• Send a reminder on issue and another before expiry, each with the reference and a reissue link.
• Track the share of vouchers that expire unpaid, and how late the paid ones arrive.
• Make reissuing a voucher a one-click action for both the customer and your support team.

Reconciliation: matching cash to orders

Cash collection produces reconciliation problems that card payments do not. A customer can pay the wrong amount, or pay twice, or pay a voucher that your system has already cancelled, or pay at a branch that reports late. Your reconciliation therefore has to be built on the voucher reference rather than on the amount. Store the reference as the primary key on the order, match incoming notifications against it, and treat any payment that does not match as an exception for a human rather than trying to auto-guess. Ask your provider what the settlement report contains: it should include the reference, the amount actually collected, the collection date, the confirmation date and the fee, so finance can tie a bank line back to an order without opening a support ticket. Also reconcile on a schedule that fits the method. Reconciling vouchers daily will generate noise; reconciling on confirmation plus one business day usually matches reality better.

• Key every reconciliation record on the voucher reference, not on the order amount.
• Route amount mismatches, duplicate payments and late payments to a manual exception queue.
• Check that the settlement report includes reference, amount collected, collection date and fee.
• Set the reconciliation cadence to match the confirmation lag rather than reconciling on a fixed daily cycle.

Fighting abandonment

Abandonment on voucher methods happens in a distinctive place: after the order is created but before the customer leaves the house. That is a different problem from checkout abandonment and needs a different fix. Make the voucher impossible to lose. Show it on screen, email it, send it by messaging app if you have consent, and give a printable version. Put the instructions in the customer's language, with the shop names they will recognise locally rather than a generic phrase. Show the exact amount and the expiry date prominently. Reduce the friction of the trip itself by naming the nearest outlet types rather than making the customer search. And consider a small incentive for instant methods alongside the cash option, because some customers choose cash out of habit rather than necessity and will switch if the alternative is clearly easier.

• Show the voucher on screen, email it, and offer a print version, so it cannot be lost.
• Use the local shop names customers recognise rather than generic payment instructions.
• Display the exact amount and the expiry date prominently on the voucher itself.
• Offer an instant method next to cash with a small incentive, because some cash use is habit rather than need.

When cash collection is the wrong tool

Cash is a poor fit for anything that depends on speed or on repeat behaviour. High-value orders are a bad match, because customers are reluctant to carry large amounts of cash and providers often cap the ticket. Instant digital delivery is awkward, because the confirmation lag breaks the promise. Subscriptions are the weakest fit of all: a voucher cannot auto-renew, so every period requires the customer to remember, travel and pay, which produces churn that has nothing to do with your product. Business-to-business sales almost never use it. And if your customer base is genuinely banked and mobile-first, adding cash mainly adds operational cost. Public pricing is only a first filter here too. Actual pricing changes with country, industry, volume, settlement currency, integration method and contract terms. Confirm against the provider's official pricing page or a written quote before you go live.

• Avoid cash for high-value orders, where caps apply and customers are reluctant to carry sums.
• Do not build a subscription on vouchers unless you are prepared to run a manual renewal process.
• Skip cash for business buyers, who expect bank transfer and invoicing.
• Compare the operational cost of handling vouchers against the incremental orders they actually bring.

Questions merchants ask

Public sources

• EBANX developer docs - Boleto payment method
• dLocal developer docs - Cash payments and ticket vouchers
• FEBRABAN - Brazilian banking federation portal