Voucher Accepted but No Time on Piso WiFi: Why a Success Message Can Still Show Zero
Up: Piso WiFi Troubleshooting | Related: Voucher Not Working | GCash Paid but No Voucher
Answer first: A success message only means the code was recognised; it does not guarantee time on your device. The voucher may give data instead of time, may belong to another device, or may have been replaced or hidden by a stale portal page. Check the timer and voucher type on the original device, and do not redeem a second code until the first one has been checked.
A voucher can be accepted by the portal and still show no usable time. That is confusing, because “accepted” sounds like success. In practice, accepted often means only that the code was recognised and recorded. It does not always mean a new session started, that the time was added to your current device, or that the voucher type matches what you expected.
This post covers only the accepted but no time case. If the code is rejected as invalid, already used, or expired, go to the Voucher Not Working guide. If you paid by GCash and no voucher arrived at all, go to the GCash Paid but No Voucher guide. If you paid by coin and got no credit, go to the Coin Slot Not Working guide.
Symptom Check: What Exactly Does Accepted Mean Here?
Before you redeem a second code, note which of these you saw. The fix depends on the answer.
| What you saw | What it may mean | First check |
|---|---|---|
| A success message, then a timer of zero or no timer at all | The code was recorded, but no session started, or the session started on a different record | Check the portal timer, device, and session list before redeeming again |
| A success message, then a very short time, far less than expected | The voucher may be a data voucher, a partial voucher, or it replaced an older session | Check the voucher terms: time, data, or a combination, and the timer shown |
| A success message on one device, but no time on the device you want to use | The voucher may be tied to the first device, or to a device limit | Check whether the time appears on the original device |
| A success message, then the portal returns to the payment page | The session may have ended at redemption, or the portal page may be a stale cached copy | Refresh in an incognito window, then check the timer, without redeeming again |
Do not redeem a second voucher until you have checked these points. A second redemption can replace the first session on some systems, which makes the first voucher harder to trace.
Likely Causes, in Order
Cause 1: The voucher gave data, not time
Some vouchers give a data allowance, not a time allowance. A data voucher may show no time countdown, or a different timer, even though it was accepted. Check the voucher terms from the seller: time, data, or both. If you expected time and bought data, that is a voucher type mismatch, not a portal fault.
Cause 2: The session started, then was replaced
On some systems, redeeming a new code replaces an active session. If you had an active session and then redeemed a second code, the portal may show only the new record, and the older time may be lost or hidden. This is why the Voucher guide warns against redeeming a second code before the first problem is checked.
Cause 3: The voucher was redeemed on a different device or network
A voucher redeemed on one device, or on a different WiFi name for the same operator, may not appear on the device you are now using. Sessions are usually tied to one device. Check the original device first, on the exact WiFi name you used at redemption.
Cause 4: Validity started at purchase or at an earlier redemption
Some vouchers start their validity clock at purchase, not at first use, and some start at redemption. If a voucher was bought days ago and has a short validity window, it may be accepted as a known code but give no remaining time. Check the purchase date, the validity period, and the redemption time together.
Cause 5: Device limit already used
If a voucher allows only one device, and it was already redeemed or tested on another device, a second device may see an accepted message but no usable session, depending on how the platform reports the limit. Check the original device and the device limit in the voucher terms.
Cause 6: A stale portal page hid the timer
A cached portal page can show an old timer, a zero timer, or no timer, even after a successful redemption. This is less common than the causes above, but it is easy to rule out with an incognito window, without redeeming again.
User Checks You Can Do Yourself
- Stay on the exact WiFi name you used at redemption, on the same device.
- Open the portal in an incognito or private window and check the timer again, without entering the code a second time.
- Note the code, the redemption time, the timer shown, and whether the voucher was sold as time, data, or both.
- Check whether you had an active session before redeeming, and whether that session is still shown.
- Check the original device, if you redeemed on a different device first.
- Do not share the code in a public group to test it. Show it only to the operator or seller, in private, with the receipt.
Operator Checks, Labelled as Operator Only
Customers should not change voucher settings, session records, or platform data themselves. For the operator, the checks are:
- Check the session list and voucher record for the code: redemption time, device, time or data granted, validity window, device limit, and whether a later redemption replaced an earlier session.
- Check whether the voucher was sold as time, data, or a combination, and whether the portal timer display matches that type.
- Check whether the code was already redeemed, tested, or partially used before the customer report, and whether the platform reports that as accepted on a second attempt.
- Check whether a platform update, a mode change between coin and voucher, or a session list clear happened between redemption and the report.
- If the record shows no grant, correct it through the platform’s own voucher or session tools, and keep a note of the correction. Do not ask the customer for banking details or social media passwords to check a voucher.
Proof to Show the Operator
Include, in one private message:
- Machine location and WiFi name.
- Voucher code, or a photo of the code and receipt, sent privately, not in a public post.
- Purchase date and time, redemption date and time, and the device used.
- Timer shown after redemption, with a screenshot if you can take one safely.
- Whether you had an active session before redeeming, and whether you redeemed on a different device first.
- Whether the voucher was sold as time, data, or both, if the seller stated it.
Prevention
For users, the prevention habit is simple: confirm the voucher type before you buy, redeem on the device you intend to use, on the exact WiFi name, and do not redeem a second code until the first one is checked. For operators, the prevention habit is equally simple: state time versus data, validity start, and device limit at the point of sale, test a sample code on the live portal before printing a full batch, and keep voucher records that show redemption time, device, and grant type.
Frequently Asked Questions About Voucher Accepted but No Time
The portal said success, so why is my timer zero?
Success can mean the code was recognised, not that a usable session started. Check whether the voucher gave data instead of time, whether it was redeemed on a different device, whether validity had already started, or whether a later redemption replaced it. Show the operator the code and redemption time before redeeming again.
Can the operator recover time from an accepted voucher with no time?
Sometimes, if the session or voucher record still exists in the platform. Recovery depends on what the record shows: grant type, validity, device, and whether a later session replaced it. If the record was cleared by a reset or expiry, recovery may not be possible, which is why proof and a quick report matter.
Should I redeem the same code again to make the time appear?
No, not until the operator checks the record. A second redemption can replace a session, use up a device limit, or lock a code on some systems, and it makes the first redemption harder to trace.
My voucher gave data, but I wanted time. Can I convert it?
That depends on the operator and the platform. Some systems do not convert a data voucher to a time voucher after redemption. Ask the operator before redeeming, and confirm the type at purchase, because conversion after the fact is not guaranteed.
The time appeared on my other phone, but not on this one. Is the voucher broken?
Not necessarily. Sessions are usually tied to one device. If the voucher was redeemed on the other phone, the time may belong to that device. Check the original device first, and ask the operator whether transfer is offered on that machine, as explained in the Transfer Time to Another Device guide.
How is this different from a voucher rejected as invalid?
A rejected code was not recognised, was already used, or had expired at the point of entry. An accepted code was recognised, but the grant, device, validity, or session handling did not produce usable time. The operator check is different, so the two cases need different reports.
What to Read Next
If the code is rejected, go to the Voucher Not Working guide. If you paid by GCash and no voucher arrived, go to the GCash Paid but No Voucher guide. If you want the full voucher rules, including WiPass types, transfer, and expiry, go to the Voucher guide. If your session disappeared after a pause, go to the Session Expired While Paused guide. If the portal itself will not load, go to the Portal Not Loading guide.