Quick answer: Keep a dependable coin or token setup when its operating costs and guest experience still fit your venue. Consider cashless when handling money and tickets, changing prices, issuing party packages or reconciling activity creates a measurable burden. Compare the complete operating system: readers, reload points, network, redemption, support and recovery. A newer payment method earns its place by solving your documented problems.
Start with the work your payment system creates
For two representative weeks, record every change-machine fault, coin jam, ticket reload, rejected banknote, disputed game charge and manual balance adjustment. Include a busy Saturday and a quiet weekday. Note the minutes spent, whether a guest could still buy and play, the remedy and the person involved.
Separate preventive work from failures. Emptying cash boxes is normal work; leaving a changer empty for an hour is a service problem. Counting paper tickets is different from a dispenser missing pulses. This distinction prevents a purchase decision based on one frustrating incident.
Build a one-page baseline: active games, paid plays, staffed hours, guest payment preferences, weekly handling time, consumable purchases and recurring repair spend. Identify your three largest problems. If none depends on the payment method, replacing the entire system may leave the real cause untouched.
Compare three operating models
| Model | When to examine it | What to test |
|---|---|---|
| Coins or tokens | A smaller floor, familiar guest experience, serviceable installed hardware and manageable collections. | Change availability, jam recovery, physical security, spare-part support and pricing flexibility. |
| Cashless game cards or wristbands | Frequent package sales, many games, electronic redemption or a need for transaction-level operating reports. | Game interfaces, reload queues, internet and local-network failures, permissions, exports and guest balance recovery. |
| Phased or hybrid conversion | A venue that needs to spread installation work or honor existing tokens and paper tickets. | Clear guest instructions and complete reconciliation between the remaining physical and new electronic systems. |
Cashless at the game does not necessarily mean refusing cash at the entrance. Your reload counter or kiosk may still accept banknotes, depending on the equipment ordered. Likewise, replacing tokens does not automatically require eliminating paper tickets: Embed documents support for a mixture of physical and electronic tickets. Confirm your exact configuration before planning a transition. [1]
If you keep a changer, ask what is actually redundant
Two hoppers are not proof that a machine can survive a validator failure. Ask the supplier to draw the path from each banknote validator to its controller, power supply and payout hardware. Which components are shared? What happens when either side stops responding?
Standard Change-Makers describes its MC520RL-DA dual-redundancy arrangement as allowing both validators to communicate with both hoppers, so a validator jam does not remove access to the other hopper's coins. American Changer lists dual validators, hoppers, control boards and power supplies for its AC2225. These are specific product descriptions, not guarantees that every two-hopper machine has equivalent protection. [2] [3]
Request a demonstration of approved fault isolation, low-coin behavior and restoration. Ask whether a fault is visible only on the cabinet or can generate a remote alert, whether that alert needs a subscription, and who receives it. Include a documented refill threshold, controlled access to reserve coins and a guest-facing backup at the counter. Never bypass safety devices or improvise powered electrical tests to demonstrate redundancy.
For cashless, define “offline” precisely
Intercard advertises an offline mode for internet outages on its iTeller product page. That is a useful starting point for a supplier discussion, but it does not establish how your installation handles a failed router, disconnected reader, dead local server, power failure or unavailable bank-card processor. Obtain the supported behavior for each condition in writing. [4]
- Internet unavailable: Can existing cards still play? Can cash reloads proceed? Which transactions wait for synchronization?
- Local network interrupted: Which readers remain usable, and where are transactions stored?
- Bank-card processing unavailable: What payment methods remain supported? Who accepts the risk of any approved offline bank-card transactions?
- Kiosk or counter terminal fails: Can another sales point issue and reload cards?
- Power returns: What starts automatically, what requires an operator, and how are incomplete transactions identified?
Run vendor-approved tests after hours using test media and documented starting balances. Record the expected result before each test. After reconnection, reconcile every deduction, reload and ticket award. A screenshot showing a reader online is not evidence that transactions synchronized correctly.
Calculate the full cost, including the work that remains
Ask for itemized quotes covering readers, game-specific harnesses, network installation, kiosks, card stock, software, support, training, freight, taxes and migration. Obtain renewal terms, replacement-reader costs and data-export arrangements. Separate mandatory charges from optional features.
Do the same for keeping the existing setup: changer repairs, ticket and token purchases, counting equipment, collection time, service interruptions and spare parts. Compare over the same time horizon. A low installation quote can hide recurring costs; a reliable existing system still consumes labor.
Illustrative calculation, not a vendor quote: Suppose conversion costs $18,000. You estimate six handling hours saved each week at a loaded labor cost of $22 per hour, $1,200 less annual consumable spending and $600 less legacy repair spending. You also estimate $2,400 in new annual support and supplies and $1,500 in additional annual processing costs.
| Annual item | Illustrative amount |
|---|---|
| Labor capacity freed: 6 × 52 × $22 | $6,864 |
| Consumables and legacy repairs avoided | $1,800 |
| New recurring costs and incremental processing | −$3,900 |
| Modeled net annual benefit | $4,764 |
Simple payback is $18,000 ÷ $4,764, approximately 3.8 years. That result excludes financing, tax effects and unproven revenue growth. More importantly, six hours freed are not automatically six hours removed from payroll. If staffing remains unchanged, treat that portion as capacity for service or maintenance, then rerun the cash-only calculation. Also compare incremental processing costs, not every existing card fee as though it were new.
Make reconciliation part of the installation
Define separate reports for money collected, paid credits loaded, promotional credits, paid play deductions, ticket awards, ticket redemptions, refunds and manual adjustments. These are different operational events. A bonus-credit promotion should not look like cash received, and a ticket correction should not disappear inside an unexplained daily total.
Give each device a stable ID and each employee a personal account. Restrict refunds, price changes and balance adjustments to appropriate roles; require a reason and preserve the audit history. Reconcile counter receipts and processor settlement reports separately from game activity. Ask your accountant how to handle balances, promotional value and any accounting or tax obligations.
For bank-card acceptance, small size does not remove payment-security responsibilities. The PCI Security Standards Council says PCI DSS applies to entities involved in payment processing regardless of size, while validation requirements depend on the payment brands. Confirm your reporting obligations with your merchant bank or processor, and use supported payment hardware rather than recording card details in a service log. [5]
Pilot a representative part of the floor
- Inventory compatibility. Include a redemption game, a multiplayer game, a prize game and any unusual controller or pricing arrangement. Obtain approval for each interface.
- Document starting conditions. Save pricing, ticket settings, meter readings and configuration backups before installation.
- Test guest journeys. Buy, reload, play, redeem, refund, recover a lost registered card and complete a party-package transaction where supported.
- Test exceptions. Reject an invalid payment, interrupt a permitted test transaction and verify the supplier's recovery procedure.
- Train the team. Give counter staff short instructions for the common cases and a clear escalation path for adjustments.
- Keep a rollback decision. Agree who can stop the rollout, what evidence triggers that decision and how guests retain access to their purchased value.
Measure queues and assistance requests as well as collections. A system that removes back-office work but causes a line at one reload kiosk may need a different front-of-house layout.
Choose on evidence from your venue
Keep the changer when supported repairs and a dependable backup solve the actual problem at lower cost. Choose cashless when the pilot proves useful operational improvements and the ongoing terms fit your budget. Use a hybrid period only with a clear reconciliation process and guest instructions.
Before signing off, require three things: a complete cost comparison, a successfully reconciled outage test and a shift team that can handle common guest problems. Those checks are more useful than a broad claim that either coins or cards are always better.