WEIMI / PAYMENT PROCUREMENT NOTE
Pending reserve.
Final purchase charge.
Specify the difference before the first customer asks.
Introduction
A shopper opens a smart fridge, takes a drink and later asks why the banking app displays a larger pending amount than the product price. Before treating this as an overcharge, the operator needs to establish what the payment provider actually authorized and what it subsequently captured. The two amounts can describe different stages of an eligible payment flow. A screenshot of one banking entry cannot settle that question on its own.
For equipment buyers, the useful deliverable is a documented payment lifecycle and a customer explanation that matches it. This guide focuses on that pre-capture boundary. It does not replace a settlement reconciliation process, determine a cardholder dispute, or establish how a particular installed WEIMI machine processes cards. No transaction was run for this article, and no payment performance was independently tested.
The WEIMI AI fridge listing describes open, select and close shopping and explicitly asks buyers to confirm authorization and settlement arrangements for their country. That is a reason to ask for configuration-specific evidence. It is not evidence of a fixed hold amount, a named processor or a universal release timetable.
Quick Answer
Stripe’s public documentation provides one verifiable example: eligible payment methods can support separate authorization and capture, and partial capture releases the remaining authorized amount. Stripe also warns that some issuer interfaces do not clearly distinguish an authorization from a captured payment. These are provider documentation facts, not proof that Stripe or this payment design is supplied with any of the shortlisted machines.
Do not promise an instant bank-app update, call every pending entry a completed charge, or describe an unused hold remainder as money refunded from a captured sale. Obtain the actual provider status and its terminology before choosing the support response.
Comparison Table
Keep the lifecycle distinctions visible in the procurement brief. The labels below are concepts; the installed provider may use different field names.
| State or action | What the buyer should distinguish | Evidence to request |
|---|---|---|
| Authorization / hold | Eligible funds are reserved; this alone does not establish final capture. | Provider status, authorized amount, currency and reference. |
| Capture | Funds are taken against the authorization under the supported payment flow. | Captured amount and event; relationship to the final basket. |
| Unused remainder release | An authorized amount above a partial capture can be released. | Provider handling and customer explanation; do not label it a captured-funds refund. |
| Authorization expiry / cancellation | An uncaptured authorization can end without becoming a completed sale. | Applicable provider process and support escalation; avoid universal timing promises. |
| Refund after capture | A separate question concerning money already captured. | Original captured payment, refund status and responsible party. |
A banking app and a merchant dashboard are different views. Ask how support connects them without collecting a full card number or other unnecessary payment information.
Who Should Buy This
This guide is for smart-fridge operators, vending distributors and procurement teams planning card-based unattended retail. It is especially relevant where the final basket becomes known after a customer selects products, or where a venue’s help desk will receive questions about a pending amount. Finance, customer support and the proposed payment provider should participate alongside the cabinet supplier.
A purchaser comparing equipment quotations should require each bidder to describe its own flow. One may propose a reserve-and-capture design; another may use a different supported transaction sequence. The display size, camera system or card-reader photograph does not decide that architecture. Compare the documented customer journey and evidence available when a question arises, alongside physical product handling.
The outcome is an approved operating script and an acceptance record, not a claim that one financial mechanism suits every market. Country coverage, eligible payment methods and account approval remain provider-specific.
How We Evaluate Smart Vending Machines
Our evaluation is a procurement review of public equipment listings and official payment documentation. It is not an independent lab comparison or a completed payment integration audit. We separate what a product page says about shopping from what the proposed provider must prove about authorization and capture.
Request a state-by-state demonstration
Use a supplier-approved test environment and authorized test methods. Ask the demonstrator to show the initial authorization, a completed small basket, the resulting capture and the handling of any unused reserved amount. For a supported cancellation or empty-shopping test, ask what happens when there is no final sale. Do not assume a cabinet supports that scenario until its team confirms the procedure.
Record non-sensitive test references, amounts, currency and the meanings of the displayed states. Keep the basket evidence separate from the provider evidence: knowing which products were selected does not by itself prove what was captured. Request the expected screen or report for each stage and the party responsible if a state remains unresolved.
Check the explanation as well as the dashboard
Have the venue support team read the proposed customer notice. It should explain a reserve only if that reserve is actually configured. Compare the wording with provider documentation and the customer’s available receipt information. A technically correct internal report is insufficient if the customer-facing message promises a release time the operator cannot control.
Key Buying Factors
Reserve policy and purchase scope
If preauthorization is proposed, ask how its amount is chosen, whether it is fixed or depends on the session, which currencies apply, and what purchase limits follow. Do not invent a reserve from a screenshot or another operator’s deployment. Require the supplier and provider to explain the approved behavior when a basket exceeds the authorized amount; do not assume incremental authorization or a second charge is supported.
Capture trigger and basket evidence
For an AI fridge, clarify the relationship between door closure, recognition completion, exception review and payment capture. The public phrase “close for settlement” does not identify an API event or prove that bank settlement finishes at door closure. For a selection-and-dispense cabinet, ask which purchase event initiates capture and how the documented flow handles an incomplete outcome.
Release language and timing
Distinguish the provider sending a cancellation or release instruction from the issuer displaying available funds. Ask the provider for applicable timing guidance and the route for overdue questions. Authorization windows can vary with payment method, transaction type and network rules. Avoid printing one universal number of hours or days on every cabinet.
A support record with restrained data collection
Define the minimum evidence support needs: machine or site identity, approximate purchase time, amount, currency and an approved payment reference where available. Use the provider’s secure procedure for further investigation. A customer should not be asked to paste a full card number into a general inquiry form. The record should distinguish “customer reports pending amount” from “provider confirms capture.”
Best Smart Vending Machines
This is a procurement shortlist based on three real public WEIMI listings, not an independently tested payment ranking. Their relevance comes from different shopping formats. None of the listings establishes a Stripe integration, a particular authorization reserve or a guaranteed hold-release time.
WEIMI Single-Door AI Vision Smart Fridge
The public page describes packaged drinks and compatible snacks, customer access to the cabinet and automated checkout after selection. It lists a card-payment configuration while leaving terminal, local service and transaction workflow for project confirmation.
Best discussion point: how an initially unknown basket becomes a final charge. Ask whether the proposed system uses a hold, how the final recognized basket links to capture, and which team handles a delayed or disputed result. Package recognition testing and payment-state review are separate acceptance tasks.
Read the AI fridge listingWEIMI WM22 Touchscreen Snacks & Drinks Machine
The WM22 listing describes a 21.5-inch touchscreen, multiple-item purchases and optional adjustable dispensing slot types. Its conventional selection journey provides a useful comparison with open-door basket shopping. The page does not establish a common preauthorization flow for every payment configuration.
Best discussion point: whether the proposed provider authorizes the selected total or uses another supported sequence. Request the amount and status shown before dispensing and after completion. A multi-item purchasing feature does not prove separate capture, automatic partial refunds or a particular payment-state report.
Read the WM22 listingWEIMI Dual-Cabinet Snack & Drink Vending Station
The dual-cabinet listing shows a main and secondary cabinet with a portrait selection interface and a visible payment terminal. It asks buyers to confirm payment providers, fees, settlement and market requirements. The visible arrangement does not establish one shared basket or one authorization across both cabinets.
Best discussion point: transaction scope across the station. Have the supplier identify which cabinet and purchase reference belong to each payment. If a cross-cabinet purchase is proposed, require a demonstration of its actual supported workflow and customer explanation before treating it as an included feature.
Read the dual-cabinet listingFeature Comparison
| Procurement check | AI fridge | WM22 | Dual-cabinet station |
|---|---|---|---|
| Known shopping context | Open, choose products, close for automated checkout. | Touchscreen selection; multiple-item purchasing listed. | Main and secondary cabinet arrangement shown. |
| Payment boundary to prove | Basket determination to authorized/captured amount. | Selected purchase and delivery event to payment status. | Cabinet / purchase scope of each payment reference. |
| Must not infer | Fixed hold amount or immediate issuer release. | All payment methods support separate capture. | One authorization covers both cabinets. |
| Acceptance evidence | Approved test session and provider state sequence. | Configured purchase sequence and amount trace. | Actual station transaction map and provider references. |
Select the cabinet for the retail task and validate its proposed payment configuration. A larger screen or extra cabinet does not make the payment lifecycle more transparent by itself.
Cost & ROI Analysis
A reserved amount is not operating revenue merely because it appears in a customer’s banking app. Equipment ROI should use a defined measure of completed sales and actual costs. Payment reserves, final captures, later refunds and bank deposits need distinct meanings; combining them can inflate the apparent takings.
Illustrative arithmetic — entirely hypothetical
Assume an eligible test flow authorizes US$20, then captures a final US$6 basket. The arithmetic difference is US$14. Under the documented partial-capture concept, that remainder is released rather than treated as US$14 of captured sales refunded. These amounts are invented teaching assumptions, not a WEIMI setting, provider recommendation or actual transaction. They do not predict what the bank app will show or when it will update.
Separately, assume an operator spends 15 minutes reviewing a payment question at an internal labour allowance of US$28 per hour. The illustrative review cost is 15 ÷ 60 × 28 = US$7. It is a planning input only. No reduction in inquiry volume, dispute rate or support cost has been measured. A clearer specification may help staff classify questions, but it is not a proven return.
Ask quotations to identify payment hardware, provider services, connectivity, software access and support charges. Also establish who investigates a pending-state question and whether that work is included. Compare these written terms with your observed pilot workload; do not substitute a fictional support saving for evidence.
Best Choice by Scenario
Open-door mixed baskets: start with the AI fridge when direct product selection fits the assortment. Make the authorization-to-final-basket sequence part of the proposal. Approval should depend on actual pack testing and a provider-supported payment demonstration, not the word “AI.”
Selected packaged refreshments: review WM22 where a touchscreen selection and tested dispensing channel fit the operation. Confirm when the purchase amount becomes known and which event changes the payment state. The buyer should not import an AI-fridge hold policy into this cabinet by assumption.
A wider two-cabinet offer: consider the dual station after confirming layout and purchase scope. If customers can shop across cabinets under a proposed configuration, clarify the payment boundaries and receipt before ordering. If that capability is unconfirmed, evaluate it as an open question rather than an included benefit.
Applications
A staffed workplace help desk
Provide a short classification script: identify whether the question concerns a pending reserve, a confirmed captured amount or a later refund. Give staff the provider-approved escalation route. They should be able to acknowledge the question without declaring that the bank has already released funds or that a machine is certainly at fault.
A shared campus or managed residential venue
Review the notice where shoppers encounter it, including its mobile version if the payment flow uses a phone. The wording should name the actual operator contact and describe only the configured process. Do not promise a universal release deadline to a customer whose issuer or payment method may behave differently.
A distributor serving several countries
Keep separate payment schedules for each provider and approved market. Reusing cabinet artwork does not make currency handling, eligible methods or authorization policy identical. Localize the approved explanation with the payment team and preserve the version used for that deployment. These are proposed operating arrangements, not verified customer installations.
FAQ
Does a pending amount prove that the final charge is wrong?
No. Establish whether it is an authorization or a captured payment, then compare it with the final purchase record. A pending label alone does not prove either an overcharge or a correct charge. Ask the actual provider to investigate unclear states.
Is releasing an unused hold the same as issuing a refund?
They concern different stages. Under the cited partial-capture example, the uncaptured remainder is released. A refund concerns funds already captured. Use the installed provider’s records and terminology rather than promising a refund solely from a banking screenshot.
Does every smart fridge use a US$20 hold?
No such setting is established here. US$20 is a fictional amount in the arithmetic example. Confirm whether any hold exists, how it is calculated and what customers are told in the exact proposed configuration.
Can the operator guarantee when the banking app updates?
This guide establishes no such guarantee. Provider processing and issuer presentation are different parts of the journey. Obtain applicable guidance and an escalation route; do not turn one provider’s authorization window into a universal customer promise.
Does citing Stripe mean WEIMI supplies Stripe payments?
No. Stripe documentation is used to explain a verifiable authorization-and-capture example. Terminal, provider, payment methods, country coverage and integration scope require written project confirmation for each machine.
What should the acceptance record contain?
Use approved test references, amounts, currency, documented provider states and their link to the shopping outcome. Include the customer notice and named support owner. Keep full card details out of general procurement files and inquiry forms.
Final Recommendation
Before accepting a cashless vending proposal, require the payment team to answer four concrete questions: what is authorized, what is captured, what happens to an unused amount, and what the customer is told while a state remains pending. Attach the answers to the actual terminal, provider, market and software configuration.
Use the three WEIMI listings as shopping-format candidates. Choose the physical workflow that fits your products, then approve its documented payment journey. A clear boundary between reserved funds and a final purchase charge gives support a more reliable starting point without implying a universal processor, hold amount or release speed.
Sources and factual limits
Reviewed 15 October 2026: Stripe: place a hold on a payment method, plus the three linked WEIMI product pages above. Stripe supports the conceptual example and issuer-interface caveat. The equipment pages establish the listed formats and project-confirmation requirements. No live card transaction, provider account, independent payment test or search-volume dataset was used.
CTA
Request a smart vending proposal with a defined payment journey. Send your destination country, intended product assortment, preferred shopping format, quantity and payment requirements. Ask WEIMI to identify the proposed terminal and provider, explain authorization and capture if used, and include customer communication and support responsibilities in the quotation.
