Piso WiFi Coin Counted Twice
Answer first: One coin counted twice means one physical coin produced two credits, or two timer increments, instead of one. Stop inserting coins, note the denomination, the time, and the timer before and after, and report it to the operator in private. Do not use the extra time, and do not try to trigger it again.
Related: Piso WiFi Troubleshooting · Coin Slot Not Working · Voucher Not Working
A coin counted twice means one physical coin produced two credits, or two timer increments, instead of one. It can look like good luck, but it is a fault, and it should be reported, not used as a trick. On some systems a double count is a pulse fault. On others it is a session record fault, where one payment is recorded twice. Either way, the operator needs to know, because the same fault can later count a coin zero times, or credit the wrong amount.
This post covers only the double count case. If a coin gives no credit, go to the Coin Slot Not Working guide. If a coin credits the wrong amount, that guide also covers calibration, but the proof and operator check here are specific to a double credit.
Symptom Check: Was It Really Counted Twice?
Before you report a double count, check these points, because a timer can look doubled for other reasons.
| What you saw | What it may mean | First check |
|---|---|---|
| One coin, timer jumped by two steps | A double pulse, a double session record, or a delayed update from an earlier coin | Note the coin, the time, and the timer before and after, if you saw both |
| One coin, timer jumped by a larger amount than the rate sign says | A calibration or rate mapping fault, not necessarily a double count | Compare the credited amount with the rate sign for that denomination |
| Two coins, timer jumped correctly for two coins | Normal behaviour, not a double count | Count the coins you actually inserted, including any coin you inserted earlier and forgot |
| Timer jumped after a delay, and you had inserted a coin earlier | A delayed portal update from the earlier coin, not a second credit for the latest coin | Check whether the earlier coin had already been credited, and note both times |
Do not insert more coins to test a double count. Extra coins make the record harder to read, and a second coin can hide whether the first coin was the fault.
Likely Causes, in Order
Cause 1: Double pulse from the coin acceptor
A coin acceptor sends a pulse, or signal, for each coin it accepts. If the acceptor, wiring, or controller sends that pulse twice for one coin, the platform credits twice. This is an operator and builder check, not a customer fix. It can be intermittent, which is why proof with times matters more than a single report.
Cause 2: Session record duplicated after a portal refresh or reconnect
If the portal page is refreshed, reconnected, or reopened during a payment, some systems can record the same payment twice, or show the same credit twice. This is a platform record issue, and only the operator can check the session list to see whether there are two records for one payment.
Cause 3: Rate mapping or calibration fault
If the coin slot is calibrated so that one denomination is read as two smaller credits, or the rate table maps one coin to two steps, the timer can jump by more than the sign says. This is related to calibration, but the symptom is a double step, not a wrong denomination. The operator check is calibration with clean coins of each denomination, as described in the Coin Slot Not Working guide.
Cause 4: Ghost credit from a wiring fault on some DIY builds
Operator troubleshooting notes mention a common ground issue on some DIY builds that can cause ghost credits or missed credits. A ghost credit is a credit with no coin, or an extra credit alongside a real coin. This is an owner and builder check only, from the supplier diagram. Customers should not open a machine to test wiring.
Cause 5: An earlier coin credited late
A coin inserted earlier may not have updated the portal timer at once, especially if the portal page was stale. When the page updates, the timer can jump by the earlier coin plus the latest coin, which looks like a double count for the latest coin. Note both insertion times if you can, because the operator session list will show the timing.
User Checks You Can Do Yourself
- Stop inserting coins at once.
- Note the denomination, the number of coins actually inserted, the time of each insertion, and the timer before and after, with screenshots if you can take them safely.
- Check the rate sign for that denomination, so you know what one coin should credit.
- Check whether you had inserted a coin earlier that had not yet updated the timer.
- Do not use a double credit to claim extra time from a second device, and do not try to trigger it again. Report it to the operator, in private, with the proof below.
Operator Checks, Labelled as Operator Only
Customers should not open a machine, clean inside it, adjust wiring, or change calibration themselves. For the operator, the checks are:
- Check the session list for the device and time window: one record or two records, coin count, credited amount, and timing.
- Check the coin acceptor pulse count for that denomination, using clean coins, and compare it with the rate table. A pulse count that is consistently double for one denomination points to acceptor or wiring, not to the customer.
- Check the common ground and wiring against the supplier diagram, on DIY or repaired machines, because a loose ground can cause ghost or double credits.
- Check whether a portal refresh, reconnect, or session replacement happened at the same time as the report.
- If a double credit is confirmed, correct the session record through the platform’s own tools, note the correction, and retest with a small coin as a test customer before opening to customers again. Do not ask the customer for banking details or passwords to check a coin record.
Proof to Show the Operator
Include, in one private message:
- Machine location and WiFi name.
- Denomination, number of coins actually inserted, and time of each insertion.
- Timer before and after, with screenshots if you have them.
- Rate sign amount for that denomination, if you saw it.
- Whether you had inserted an earlier coin that had not updated yet.
- Device used, and whether other customers reported the same fault at the same time.
Prevention
For users, prevention is simple: insert one coin at a time, wait for the timer to update, and report a double credit at once instead of using it as free time. For operators, prevention is calibration with clean coins of each denomination, a wiring check against the supplier diagram after any repair or move, a session list check after a reported double count, and a test payment as a customer after any acceptor or wiring work. A fault that counts twice today can count zero times tomorrow, so a quick report protects both sides.
Frequently Asked Questions About a Coin Counted Twice
Should I keep the extra time if a coin counted twice?
No. Report it to the operator. A double credit is a fault, and the operator may correct the session record. Using it deliberately, or trying to trigger it again, can be treated as misuse, and it hides a fault that may later take coins without credit.
Will the operator believe me without proof?
Proof helps, but a session list check can also confirm a double record. Note the denomination, time, and timer, and take screenshots if you can. Even without a screenshot, a report with an exact time lets the operator check the record for that window.
Is a double count the same as a ghost credit?
Not exactly. A double count is one real coin credited twice. A ghost credit is a credit with no coin, or an extra credit that appears without a matching insertion. Both can come from wiring or pulse faults on some builds, and both are operator checks, but the proof is different: a ghost credit has no coin to match, while a double count has one coin and two credits.
Can I fix a double count by inserting another coin?
No. Another coin adds a third record and makes the fault harder to read. Stop, note the times, and report it.
My coin counted twice once, then worked normally. Should I still report it?
Yes, especially if it happened at a specific time or with a specific denomination. Intermittent pulse faults are the hardest to catch, and a single report with an exact time can help the operator test that denomination.
Could a double count be caused by my phone?
A phone cannot make a coin acceptor send two pulses. A phone refresh can affect how the portal displays a credit, which is why the operator session list check matters. If the session list shows one record, the double jump was likely a display delay. If it shows two records, the fault is on the machine side.
What to Read Next
If a coin gives no credit, go to the Coin Slot Not Working guide.
If a coin credits the wrong amount, that guide also covers calibration.
If you paid by voucher and got no time, go to the Voucher Accepted but No Time guide.
If the portal itself will not load, go to the Portal Not Loading guide.
If you want the full machine parts and setup checks, go to the Vendo pillar.