The cashless reader is only part of the purchase

Buy the complete payment workflow

A cashless reader is a piece of hardware inside a larger service. The agreement may cover processing, connectivity, reporting, subscriptions, support, refunds, and settlement. This checklist is editorial guidance for comparing proposals, not a ranking of vendors or an assertion that a reader increases revenue by a fixed amount. Ask providers to explain their terms using the same transaction assumptions and the exact equipment you intend to install.

Start with an equipment list: model, controller, firmware where relevant, and the products and prices the machine will use. Ask the provider to confirm compatibility in writing. Include installation and configuration responsibility. A reader can be connected to a network and still fail to coordinate correctly with the machine. Acceptance testing needs to cover the complete purchase and dispense sequence, using the supplier's approved commissioning process.

Understand what each transaction costs

Request a fee schedule that distinguishes percentage fees, per-transaction charges, monthly subscriptions, connectivity, hardware, installation, and termination costs. Ask whether minimums apply and how tax, refunds, and disputes affect charges. A low advertised processing percentage may be only one part of the agreement. Compare the full expected bill for a hypothetical month, then replace the assumptions with actual data after launch.

Ask for an example settlement report. Identify gross purchases, fees, refunds, adjustments, and the amount deposited. Determine the settlement schedule and any conditions that can delay funds. Establish who receives notices and who can reconcile the bank deposit. Your purchasing schedule should reflect available cash, not merely sales displayed in a dashboard. Keep equipment financing separate so it remains visible in the account cost model.

Work through the failed vend

Ask the vendor to demonstrate how its system handles a payment authorization followed by a dispensing failure. Distinguish an authorization hold, a completed payment, and a refund. Find out which information the operator sees and what a customer sees. Avoid writing service instructions that promise an immediate bank balance change if the provider cannot support that promise.

Decide how customers contact the operator and identify the machine. Ask which non-sensitive transaction references can help support locate a purchase. Do not collect full card numbers, security codes, or photographs of cards in an ordinary contact form. Assign responsibility for refunds and define escalation for repeated errors. A support workflow should protect customer information and remain usable when the operator is away from the route.

Check signal and fault recovery at the site

Discuss the actual connectivity method and the intended installation position. A phone working in the building does not necessarily establish that the reader's service will work from inside its cabinet. Ask how signal is assessed and what options exist when connectivity is unreliable. Establish the cost and maintenance responsibility for any antenna, network equipment, or alternate service.

Ask what happens during an interruption: can a purchase begin, is authorization deferred, and what does the display tell a customer? The answer depends on the actual product and configuration. Request written instructions rather than assuming all readers behave alike. Include recovery after power loss and reconnection in commissioning. Record settings and contacts so a future operator or technician can restore the installation consistently.

Ask who controls the account and the data

Confirm the legal account holder, authorized users, access roles, and process for staff changes. Ask what data can be exported and in which format. If reporting is important to your purchasing process, review a real sample export rather than a screenshot of a dashboard. Verify whether product-level sales are available for your machine and configuration; do not assume every integration supports the same detail.

Discuss closing or transferring the account before signing. Who owns the reader? Is it locked to a service? What notice is required, what costs remain, and what data can be retained? Route sales and equipment moves can expose restrictions that were invisible at installation. Keep the agreement and equipment record together so decisions about replacing hardware also account for contractual obligations.

Security is a shared responsibility

The PCI Security Standards Council provides resources for merchants protecting payment data. Use that primary guidance to discuss the responsibilities of your business, processor, equipment provider, and any other service involved. Ask which validation and assessment steps apply to the full deployment. A device description alone does not establish the security obligations of every connected system or operating procedure.

Review support access, software updates, physical inspections, and incident reporting with the provider. Know how to recognize and report suspected tampering. Keep credentials out of shared route notes and restrict access to what each person needs. Have the provider explain what its team may access remotely and how authorization is managed. Request a clear contact for suspected payment security problems rather than relying on a general sales inbox.

Use a written acceptance checklist

Before the installation enters ordinary service, confirm compatibility, purchase and dispense behavior, connectivity, refunds, reporting, and support contacts. Document the configuration and any unresolved issue. Use authorized commissioning methods; this publication's own site testing does not run live payment transactions. For a complete operating plan, read the vending launch guide.

The useful comparison is not which reader looks most advanced. It is which complete agreement and workflow your operation can understand, reconcile, support, and eventually change. Ask the difficult questions while you can still choose another option.