Settlement, refunds and exceptions before the purchase order.
A successful tap or card authorization is only the beginning of a vending transaction. The operator still needs to know which machine sold the item, which provider settled the payment, whether a refund or reversal followed and which fee explains the difference between gross sales and the bank deposit.
This article turns those questions into a procurement checklist. It does not claim a specific WEIMI payment integration, bank timetable or fee schedule. Ask for the exact terminal, provider, market and reporting workflow in the quotation.
| Format | Payment context | Reconciliation question |
|---|---|---|
| AI vision fridge | Open-door packaged retail | How are basket events, authorization and final capture matched? |
| WM22 | Touchscreen selection and dispensing | How are failed delivery, refund and provider fee recorded? |
| WM22-W PPE | Staff-card issue controls | How do issue records map to payment, subsidy or internal allocation? |
This guide is for vending operators, distributors, finance teams and employers who need a repeatable settlement process across sites. It is especially useful when the machine supplier, payment provider and acquiring bank are separate parties.
Bring finance and operations into the equipment demonstration. The person who loads products may not own refunds, while the person who downloads a provider report may not see the machine’s failed-delivery event. A named handoff prevents the exception from disappearing between teams.
We evaluate traceability, not payment performance. Ask the supplier and payment provider to demonstrate a sandbox or controlled test using a unique reference. Follow it through authorization, dispense or access result, capture, refund and report export. Record time zone, currency, rounding and fee fields.
A normal sale proves little. Test a declined payment, an item that does not dispense, a customer cancellation, a duplicate tap and a delayed provider report. Use test credentials and approved environments. Do not trigger real customer refunds or share payment data during a demonstration.
Ask which identifier links the machine, transaction, terminal and provider report. If each system uses a different reference, request the crosswalk or export field that connects them.
Confirm timestamp source, time zone, daylight-saving treatment, currency, decimal precision and exchange-rate responsibility. A report that appears one day late may simply use a different reporting boundary.
Write down who approves and submits refunds, where the status appears and how the operator handles a customer who leaves before a failed dispense is confirmed.
Request the fee fields and settlement statement format. Do not infer a rate from a sample invoice or assume the machine supplier sets the acquiring fee.
Confirm which staff can view reports, export records and approve refunds, and how long the operator retains the data under its own policy.
These are fit-based supplier listings, not independently tested payment rankings. Confirm terminal model, acquiring coverage, refund flow and reporting fields for your destination market.
Listed fit: A browsable chilled assortment where shoppers may choose several items.
Payment questions: Test look-alike packages, take-and-return actions and mixed baskets. Confirm the card terminal, local settlement and network dependency.
Cost line: SKU onboarding, software, connectivity, cooling and exception support
Boundary: This cabinet sells packaged products; it does not prepare juice or heat meals.
Listed fit: A defined range of packaged refreshments with tested dispensing paths.
Payment questions: Submit real packs for slot selection, pickup tests and repeat delivery checks. Confirm which slot types are included in the quote.
Cost line: Channel configuration, payment equipment, refill labour and service access
Boundary: An adjustable slot does not establish compatibility with every shape, wrapper or weight.
Listed fit: A controlled supplies program with an approved item list and named policy owner.
Payment questions: Test allowed and denied users, issue limits, stock exceptions and the proposed interface. Confirm integration scope rather than assuming plug-and-play.
Cost line: Integration, badge management, supply replenishment and audit administration
Boundary: Controlled dispensing is not PPE certification and must not replace the employer’s safety or emergency-access arrangements.
Use the matrix to organize the payment demonstration.
| Check | AI fridge | WM22 | WM22-W |
|---|---|---|---|
| Primary trace | Basket and capture | Dispense and refund | Issue record and allocation |
| Confirm | Recognition and payment handoff | Terminal and failed-delivery handling | Badge, subsidy and report access |
Use the quote to separate hardware, terminal, payment-provider, connectivity, software, refund and support costs. Public product pages do not establish a universal fee or settlement rate.
Illustrative assumption only: a pilot processes 900 transactions monthly at an assumed $0.20 average provider cost per transaction ($180), plus a hypothetical $40 monthly reporting allowance. The planning total is $220. These figures are invented assumptions, not WEIMI or processor pricing. Replace them with written terms and actual transaction mix.
For open-door basket retail, start with the AI fridge and trace multi-item capture. For standard packaged goods, start with WM22 and test dispense failures and refunds. For controlled PPE issue, start with WM22-W and map internal allocation beside any payment or subsidy record.
A campus operator may reconcile card sales with a central finance report. An airport operator may need multiple currencies and time zones. A factory may allocate PPE issues to departments rather than treat every issue as a retail sale. A distributor may support different payment providers by country. Each application needs its own owner map and exception script.
No. Confirm terminal, provider, acquiring coverage, authentication, settlement currency and refund handling for the destination.
Authorization indicates a payment request was accepted or declined. Settlement is the later reporting and transfer process handled by the provider and bank. Confirm the exact lifecycle in the project documentation.
The contract should identify the responsible party, evidence required, approval path and customer communication. Do not infer ownership from the cabinet brand.
No. Compare identifiers, fees, refunds, reversals, taxes, currency and settlement timing before drawing a margin conclusion.
Use an approved test account or sandbox where available. Never paste full card details into an article CMS, support chat or test document.
They may need an internal allocation or subsidy record. Confirm the employer’s accounting and privacy policy rather than assuming a retail payment flow.
Make reconciliation a purchase deliverable. Require one traceable test transaction, an exception matrix, a report sample, a fee and refund map, and named owners for machine, payment provider and finance handoff. Select the cabinet that fits the physical workflow only after its cashless operating process is clear.
Planning a cashless vending rollout? Send destination markets, currencies, product workflow, terminal preference and reporting needs. Request a configuration-specific quotation with settlement and refund responsibilities in writing.
