A customer buys a drink and a snack from a smart cooler, opens their banking app, and sees an amount larger than the purchase. Their first thought is understandable: “This machine charged me too much.”
Your response matters. A quick explanation can restore confidence, but only if you check what actually happened. Calling every unexpected amount “just a hold” can turn a simple question into a real service problem.
A smart cooler authorization hold is a temporary reservation of available funds or credit. A completed charge is the finalized purchase. Check whether the transaction is pending or posted before deciding what needs to happen next.
This guide is for operators and workplace contacts who need a clear customer explanation and a practical support process. Exact amounts, purchase steps, receipt options, and release timing depend on the cooler, payment provider, and card issuer. Confirm those details for the equipment at your location.
1. Explain a hold and a charge in everyday language
Start with the question the customer is asking: “Did I pay this amount?” The word pending is useful, but it needs an explanation. Someone unfamiliar with payment processing may reasonably see any amount in their banking app as money already spent.
A temporary authorization checks that a payment method can support a transaction before the final purchase amount is settled. In some unattended shopping systems, that happens before the customer has finished selecting products.
Cantaloupe’s customer payment FAQs describe estimated holds used when the final sale amount is not known at authorization. That provides helpful context, but your response should still be based on the actual transaction.
A posted charge is the completed amount recorded for the purchase. A refund, when needed, is a separate correction to a charge. The release of an unused authorization does not necessarily appear as a separate refund line.
Keep those terms separate in your own records. If you tell a customer “we refunded it” when you only confirmed that an authorization is pending, you have described an action that may not have happened.
Do not say the hold has no effect. Capital One’s credit-card guidance explains that pending transactions reduce available credit before becoming part of the posted balance. Its debit-card guidance also explains the effect on available funds.
For a customer watching a tight balance, that distinction matters. “It is temporary” may be accurate, but it does not erase the inconvenience. Acknowledge the concern and give them the next useful step.
A helpful opening is: “Let’s check whether that amount is still pending or has posted. That tells us whether we are looking at an authorization or a completed purchase.”
You do not need to teach the entire payment network. You need to identify the status, compare it with the purchase record, and explain what you can verify.
Keep the explanation accessible to the location manager too. They may receive the complaint before you do. Give them a short script and a direct support contact so they are not forced to guess.
2. Connect the explanation to the cooler’s shopping process
Smart coolers are not all configured alike. Some use cameras, sensors, or a combination of technologies to identify products. Payment and receipt steps can also differ across models and providers.
For example, Cantaloupe describes smart-store systems in which customers present payment, unlock a cabinet, select products, and complete their shopping. Treat that as an example of a system, not a universal instruction for every cooler.
Walk through the actual customer journey at your location. What appears before the door unlocks? Is an authorization amount disclosed? What tells the customer their shopping session has ended? How can they obtain a receipt?
Follow the manufacturer’s instructions when explaining how to remove or return products during a shopping session. Do not invent rules about putting items back, reopening doors, or combining purchases across cabinets.
The most useful customer explanation follows what they just experienced:
- You presented a payment method to start shopping.
- The system requested an authorization according to its configuration.
- The purchase was recorded when you finished the required shopping steps.
- The final transaction and any temporary authorization must be checked separately.
Adjust that outline to match your equipment. If your system uses a different flow, use its documentation and on-screen prompts.
During onboarding, ask the provider to demonstrate a normal purchase, an abandoned shopping session, and a request for a receipt. Find out which records an operator can see and which questions need provider support.
Ask how repeated attempts are handled. A customer who is unsure whether the first tap worked may try again. Do not assume multiple pending entries prove multiple completed purchases, or assume they are harmless without checking.
Also confirm the name customers may see on their statements. A payment descriptor may differ from the workplace name or the brand on the cooler. An accurate descriptor explanation can prevent confusion, but it is not proof that an unfamiliar transaction is legitimate.
If a customer does not recognize or authorize a transaction, direct them to their card issuer promptly. Do not tell them to wait for posting when they suspect fraud.
For connection problems that interrupt the purchase experience, see our separate guide to what to do when a vending card reader is offline. Payment status and equipment connectivity are related questions, but they require their own checks.
3. Use a simple example without inventing a policy
Numbers can make the difference easier to understand. Label them clearly as an illustration, because readers may otherwise assume the example is the amount charged at your own cooler.
Suppose a fictional system requests a $10 authorization before shopping. The customer chooses products with a final purchase total of $6, including any applicable charges shown in that example. These are teaching numbers, not Big City Vending’s hold amount or a promise about any specific device.
| What the customer sees | What to check |
|---|---|
| $10 pending | Whether this is the initial authorization for the shopping session |
| $6 posted | Whether this matches the completed receipt |
| Both amounts temporarily visible | The status of each entry and the provider’s transaction record |
| $10 posted instead of the expected $6 | A possible purchase or billing discrepancy that needs investigation |
Do not add a pending authorization to a posted charge and automatically declare that the customer paid $16. At the same time, do not dismiss the customer’s concern just because one entry is pending.
Use the example to explain the questions you will ask, not to predict exactly how their banking app will display the transaction. Different issuers can present pending and completed activity differently.
The next question will often be, “When will it disappear?” Give the current guidance for the actual provider and advise the customer to check with their issuer about the specific hold. Avoid turning a typical processing range into a guaranteed deadline.
Weekends, processing differences, transaction conditions, and issuer practices can affect what the customer sees. You should not promise “by tomorrow” simply because most previous questions resolved quickly.
If the provider gives an expected window, record the source and the date you checked it. Build a follow-up point around that guidance, while leaving room for the customer to contact the issuer sooner if access to funds is a concern.
A second fictional example helps separate a hold from a genuine error. Imagine the receipt lists two drinks, but the customer says they took one. Even if the payment began with a normal authorization, the item count still deserves review.
Check the transaction detail through the provider’s approved process. Do not use the existence of a hold as an explanation for an unrelated product-recognition or pricing complaint.
Clear examples should make the support process easier to follow. They should never replace the evidence from the actual sale.
4. Give customers a short, useful explanation
Your sign does not need a lecture about card processing. It needs enough information to prevent a surprise and a clear way to get help.
Before posting a sign, confirm the actual authorization policy, the shopping instructions, the receipt method, and the support contact. Include an amount only when it is verified for that equipment and will stay accurate.
A general starting point is: “A temporary card authorization may appear before your purchase is finalized. Your final charge should match your completed purchase. If an amount looks wrong, check whether it is pending or posted and contact the support information shown here.”
Adapt that language to the provider’s required disclosures. It is not a substitute for the terms or notices your system requires.
Place the explanation where customers can read it before presenting payment. A small sticker hidden behind the door is unlikely to help someone making their first purchase.
Keep the support route visible after the sale too. A customer may notice the bank entry later, away from the cooler. A receipt or clearly identified machine number can make it easier to connect the concern to the correct location.
For a direct response, use three parts: acknowledge, check, and explain the next action.
“I understand why that amount looks concerning. Please check whether it says pending or posted. I can help review the purchase record using the location, approximate time, and receipt reference.”
Then respond to the status you actually find. If you confirm a pending authorization, explain its role and the appropriate issuer or provider follow-up. If the posted amount does not match the purchase, begin the correction process.
Avoid phrases such as “you read it wrong,” “everyone knows that,” or “the machine never makes mistakes.” They add friction and discourage customers from reporting problems you need to hear about.
Coach the workplace contact to share the support route without collecting sensitive payment information. They should not become an informal billing department simply because the cooler is in their building.
For a new placement, include this explanation in the launch conversation alongside stocking and service expectations. Our first 30 days at a new vending location guide explains why early feedback deserves its own tracking process.
5. Investigate the right problem and protect customer information
Start a support record with the location, machine identifier, approximate purchase date and time, reported amount, and whether the customer says it is pending or posted. Add the receipt or transaction reference when available through the approved support process.
Ask which products they expected to purchase. This helps separate an authorization question from an incorrect item count, an unexpected price, or a product that was not received.
Use the minimum information needed. Do not ask for a full card number, security code, banking password, or an unredacted bank statement by email or text. If the provider needs payment identifiers, direct the customer through its approved secure process.
If a screenshot is useful, ask the customer to hide unrelated transactions, balances, account details, and other personal information. A support record should solve the complaint without becoming a collection of unnecessary financial data.
Match the report to the operator dashboard or provider record you are authorized to access. Confirm the device and time rather than searching loosely and choosing a transaction that merely looks similar.
Then assign the issue to the correct path:
- Pending authorization: verify the related shopping session and explain the provider or issuer follow-up.
- Incorrect posted amount: review receipt details and request or perform an authorized correction.
- Two posted purchases reported as a duplicate: investigate both transaction references.
- Unrecognized activity: advise prompt contact with the issuer, especially if the customer suspects unauthorized use.
- Missing product or incorrect item recognition: review the shopping record through the equipment provider’s process.
Record what you actually did. “Ticket opened” is different from “refund approved,” and “refund submitted” is different from “customer confirmed receipt.” Give each action an owner and a follow-up date.
Do not promise to control the customer’s bank display. You can review your own records, contact your provider, and make authorized corrections. The issuer can explain account-specific timing and availability.
If you cannot resolve the question immediately, say what you are checking and when you will provide an update. A specific next step is more reassuring than an unsupported guarantee.
Close the support loop after the evidence is reviewed. Save the resolution in your business records and tell the customer the result through the agreed channel.
6. Prevent repeat confusion with a better operator routine
A good support process also produces useful operating information. If the same question arrives repeatedly, look for the cause instead of treating each message as an isolated interruption.
Track authorization questions separately from confirmed incorrect charges. Combining them in one “overcharge” count hides the difference between a communication problem and a transaction problem.
Review whether complaints cluster around one device, a recent configuration change, a new location launch, or a particular step in the shopping process. Share specific examples with the provider through its support process.
Check signs after equipment or payment changes. An old hold amount, outdated support number, or incorrect receipt instruction can create confusion even when the current system is working as configured.
During a routine service visit, inspect the customer-facing instructions, product prices, and available support information. Follow approved procedures for any test transaction and record it appropriately.
Choose one person to maintain the customer explanation. If the route driver, location manager, and support contact each use a different version, customers can receive conflicting answers about the same transaction. Review the wording when the provider changes its process and retire outdated copies.
Measure whether the change helps. Compare the type of questions received before and after updating instructions, while accounting for purchase volume and new users. A quieter inbox is useful only if customers still know how to report a real problem. Keep the support contact easy to find and invite specific feedback about confusing steps.
Keep a short location reference sheet containing the device identifier, provider, support route, receipt method, payment descriptor, and current explanation of authorization behavior. Store sensitive account details separately with appropriate access controls.
For organizing those records alongside route and inventory work, explore Vending 102: Staying Organized & Running Your Business Like a Pro.
Is a pending hold an extra fee? A hold is an authorization, not automatically a separate purchase fee. Verify the actual transaction and any disclosed charges.
Does every smart cooler use the same hold? No. Confirm the equipment and provider configuration rather than borrowing an amount from another machine.
Should every unexpected charge be dismissed as pending? No. Check its status and compare the completed purchase record.
Who can explain a customer’s available balance? Their card issuer can address account-specific questions. The operator and provider can help investigate the purchase and their own processing records.
The best explanation is calm, specific, and backed by a real check. Customers do not need to become payment experts. They need to understand what happened, know where to get help, and trust that a genuine error will receive attention.
