WEIMI INSIGHTS / CASH PAYMENT REQUIREMENTS
Accepting two currencies is a complete transaction design question, not just a validator setting.
ACCEPT
Confirm supported currencies and denominations.
PRICE
Define how the charged amount is presented.
RETURN
Specify change and cancellation handling.
A cash validator’s recognition capability does not by itself establish a complete multi-currency vending transaction. Pricing, change and accounting must also be supported and clearly defined.
01 / BUYER NOTES
A buyer may want a machine configured for one local currency or may want customers to use more than one currency at the same installation. Those are different requirements. State which is intended and which exact denominations are proposed.
Confirm capability with the payment component and machine-controller providers for the actual configuration. Do not infer multi-currency sales from a validator catalogue that lists several possible currency datasets. The installed combination and software must support the intended customer journey.
02 / BUYER NOTES
If more than one currency is accepted, decide how the product price is shown and how the payable amount is determined. The rule must be clear to the customer and appropriate for the market. Obtain the relevant commercial and compliance review rather than inventing an exchange-rate policy in the equipment brief.
Ask where the rule is configured and who may update it. A currency symbol on the screen is not evidence that conversion is implemented. The proposed system should demonstrate the exact price information and transaction result for each supported case.
03 / BUYER NOTES
A customer needs to know what change, if any, is available for the chosen payment. Identify the supported payout arrangement and the machine’s behaviour when it cannot provide the required change. This is separate from accepting the banknote successfully.
Avoid assuming that a device can return change in both currencies or return the same physical note after acceptance. Those behaviours depend on the hardware and transaction stage. Use the documented payment process and test the relevant cancellation and insufficient-change cases.
04 / BUYER NOTES
A person may insert one currency and then another, change the selected product or cancel before completing the transaction. Define whether such actions are supported and what the interface communicates. Unsupported combinations should not leave the customer guessing about their balance.
Include these cases in a supervised acceptance exercise using the provider’s approved method. Do not promise that every mix of notes can be converted or refunded automatically. The agreed scope should identify supported actions and clear recovery routes for exceptions.
05 / BUYER NOTES
Cash collection needs to distinguish the physical currencies and denominations received. The machine’s sales value, calculated conversion and counted cash may be different record types. Define how the operator reconciles them under the organisation’s accounting process.
Ask which reports the system actually provides and avoid filling gaps with invented precision. If manual records are required, include that work in the operating plan. A multi-currency offer can create additional reconciliation tasks even when the customer interface appears simple.
06 / BUYER NOTES
Establish why more than one currency is needed at the site and what proportion of customers is expected to use it, using evidence where available. Compare supported alternatives with the operator’s service resources and payment-provider advice. Do not assume that more accepted currencies always produce more sales.
The final configuration should use clear pricing and a predictable transaction process. If the proposed system cannot support the complete journey, revise the requirement rather than advertising a capability based only on note recognition. A narrower, accurately described offer is better than an ambiguous payment promise.
Question: Which exact notes can the installed validator accept?
Does not establish: Conversion or change behaviour.
Question: How is the payable amount calculated and shown?
Does not establish: Physical payout capability.
Question: How are currencies and sales matched?
Does not establish: That every report is automatic.
PRACTICAL ANSWERS
Not necessarily. Confirm the installed dataset, controller and complete transaction configuration.
Only the supported hardware and documented process establish that behaviour.
No. The actual calculation and payment journey must be demonstrated.
YOUR NEXT STEP
Tell WEIMI the intended currencies, pricing display and change requirements so the relevant payment configuration can be reviewed.
Explore equipment →Discuss your requirements →