The register says no, but the customer sees money set aside in their banking app. A calm response can prevent a second charge and give both sides a clear record while the issuer sorts out the hold.

The card reader gives a decline. The customer checks their phone and sees the purchase amount sitting under pending activity. Now both of you are staring at screens that seem to disagree, and the line is getting longer.

Start by slowing the moment down. A pending entry is not always the same thing as a completed charge, and the register's response is not a reason to guess. The shop's job is to check what its payment system recorded, explain what it can see, and avoid turning one confusing attempt into two purchases.

What the customer may be seeing

When a card is presented, the merchant may ask the card issuer to approve an amount. That authorization checks whether the card can cover the purchase. It can affect the customer's available balance or credit even when the sale does not finish as expected. The customer's bank or card app may show that authorization as pending while it waits for more information.

Visa explains that an authorization reversal tells the issuer that all or part of a sale was canceled, so the hold can be released. The issuer needs information that matches the original authorization. If important details are missing or do not match, the funds can remain outstanding for a period of time. Visa's merchant guidance says that can range from one to eight days, depending on the card and transaction type. That is a range, not a promise about what any one customer's bank will do.

This distinction matters at the counter. A pending line in a banking app does not, by itself, tell you whether the sale completed in your POS. Likewise, a decline message alone does not explain exactly what the issuer will display or when it will update. Avoid telling a customer that the money is definitely gone, definitely charged, or guaranteed to return by a particular day unless their issuer has confirmed that.

Check the sale before trying again

First, look up the attempt in the payment or POS records. Check the time, amount, tender type, and status. If your setup provides a transaction reference or response detail, keep it with the incident record. Follow the processor's instructions for interpreting that status. Do not rely only on a printed slip, a customer's screenshot, or a memory of what flashed on the reader.

If the system clearly shows that the attempt was declined and no sale was completed, explain that plainly. Before asking the customer to tap again or use another card, make sure the first attempt did not land as an approved or completed payment. When the result is unclear, pause and contact your payment provider through its normal support channel. A minute spent checking is usually less awkward than discovering later that the customer paid twice.

For a busy counter, give staff a short phrase to use: "I can see the register did not complete the sale. Your bank may show the authorization while it updates. Let me confirm the payment status before we try another payment." It acknowledges the customer's concern without making a promise the shop cannot control.

Keep a small incident record

When a customer reports a pending amount after a failed attempt, note the details while they are available. Use the recordkeeping rules your business already follows, and never write down a full card number or security code.

• Record the date and approximate time, amount, register, and the status shown in the POS.
• Keep any transaction reference your processor says is safe and useful to retain.
• Note whether the sale was completed, canceled, or left uncertain, and what you told the customer.
• If you contacted support, record the case reference and the next step they gave you.

This record helps the next person answer a follow-up without making the customer start from the beginning. It also gives your team something concrete to compare against the processor's transaction history. Keep access limited to staff who need it, and follow your payment provider's guidance for handling payment data.

If the sale was canceled after approval

Sometimes an authorization is approved, then the customer changes their mind, the item is unavailable, or the payment attempt is abandoned before a sale is settled. In that case, ask your processor how its system handles the cancellation or reversal. Do not assume that voiding a sale on the register automatically sends every message the card issuer needs. The payment provider can tell you whether a reversal was sent and whether anything remains for the shop to do.

Visa's authorization reversal guidance notes that matching details help an issuer connect a reversal to its original authorization. That is one reason to use the processor's normal void or reversal workflow rather than trying to fix a confusing transaction by entering an improvised adjustment. If you are unsure which action fits, check with the processor first.

For the customer, be clear about what the shop has done and what sits with their card issuer. If the pending entry stays after the processor confirms the transaction was canceled, the customer may need to ask their bank about its release timing. Avoid giving a fixed deadline unless the issuer does.

Make the next shift easier

A little preparation keeps this from becoming a new mystery every time. Show staff where to find transaction status and who can contact the processor. Decide who handles a disputed or uncertain attempt during a rush. Put the steps somewhere the team can reach, but do not tape sensitive transaction details beside the register.

It also helps to review confusing attempts periodically. Look for repeated reader errors, staff unsure of the status screen, or gaps in the handoff between shifts. The goal is not to blame the cashier for a message the system produced. It is to make sure the next person knows how to check the record and what to say while doing it.

If you use a POS to track the sale and keep the shift organized, you can download M&M POS and see whether it fits your shop's workflow.

A pending amount can make a customer worry, especially when the register appears to say something different. Check the actual transaction, explain the limits of what you know, and confirm the first attempt before taking another payment. That small pause protects the customer and gives your staff a steady way through an uncomfortable moment.

Direct URL: https://mmpos.app/download