Buy now, pay later in a physical store
Buy now, pay later splits a purchase into instalments for the customer while paying the merchant in full up front, minus a fee. At a physical counter it usually arrives as a virtual card in the customer's app, which your terminal accepts like any other card, or as a QR code tied to a specific provider.
From your side it is a sale that settles normally and costs more than a card transaction. From the customer's side it is credit. Those two facts explain most of what follows.
Why would a small store want it?
Because it raises what customers can afford in one visit. That matters where tickets are large enough for the instalment to change the decision — appliances, phones, tools, furniture, a big grocery restock.
It matters much less at a counter where the average sale is a few dollars. The fee is real and the basket effect is not, which is why this is a question for higher-ticket categories rather than for every store.
What does it cost?
More than card acceptance, typically several times more as a percentage, because the provider is taking credit risk and funding the instalments. That is the trade you are being offered: a higher cost per sale in exchange for sales that might not otherwise happen.
Evaluate it as a margin question rather than a payments question. If your gross margin cannot absorb the fee on the incremental sales, the arithmetic does not work regardless of how the offer is framed.
How do refunds and returns work?
Through the provider, and this is where stores get caught. A refund has to unwind an instalment plan rather than simply returning money, and the mechanics differ between providers. A customer who has paid two of four instalments is in a different position from one who has paid none.
Get the refund process in writing before you sign, and make sure whoever works your returns counter knows it. A confused return on a plan the cashier has never seen produces an angry customer and a slow resolution.
Who handles a dispute?
Usually the provider rather than the card networks, because the credit relationship is between them and the customer. That can be simpler than a chargeback or considerably less predictable, depending on the provider.
Ask specifically: if a customer disputes a purchase, who decides, on what timeline, and can the funds be taken back from me. The answers vary and they are the most consequential part of the agreement. The category's general shape is described in the buy now, pay later overview.
What should you tell customers?
Only what you actually know, and nothing about their eligibility or the credit terms. It is a lending product and the terms are between the customer and the provider. A cashier describing late fees or credit consequences is making statements about somebody else's loan.
"That's offered through their app, and the terms are on their side" is the accurate and sufficient answer, and it keeps your staff out of a conversation they cannot be right in.
Where does it not belong?
At a convenience counter, mostly. Instalments on a twelve-dollar basket serve nobody: the fee eats the margin, the customer gains little, and the complexity arrives anyway. The cases where it earns its place are high-ticket, considered purchases.
If you sell both — a store with a counter and a stock of higher-value goods — restrict it to the categories where it does work rather than enabling it everywhere.
Frequently asked questions
Do I get paid in full immediately?
Typically yes, minus the fee, on the provider's settlement schedule. Carrying the instalments is the provider's business, which is what you are paying for.
Is it a card transaction to me?
When it arrives as a virtual card, yes, and your terminal treats it like one. That also means your processing fee may apply on top of the provider's fee, which is worth confirming rather than assuming.
Can I offer it only above a certain amount?
Most providers support a minimum, and setting one is usually sensible. It keeps the fee off transactions where it cannot pay for itself.
Does it affect my chargeback ratio?
If the transaction runs as a card payment, disputes on it can flow through the normal channels, so it can. If it runs entirely inside the provider's system, it does not. Ask which applies to the specific integration you are offered.
What happens if the customer stops paying?
That is the provider's risk, not yours, which is the core of the arrangement. Confirm it in the agreement rather than assuming, particularly around fraud and first-payment defaults where some agreements differ.
Does accepting it require a separate account?
Usually a separate agreement with the provider, even when the transaction reaches you through your existing terminal. That means another statement, another settlement schedule and another support relationship.
Is it worth it for a grocery or convenience store?
Rarely, for ordinary baskets. The one scenario worth considering is a store doing large restock sales to other small businesses, where the ticket is big enough for instalments to matter and the margin can carry the fee.
How should I test whether it works for my store?
Run it on one category for a quarter and compare units sold and average ticket in that category against the same period last year. That is a small, reversible experiment with a readable answer, and it is more honest than a provider's estimate of incremental sales.