For operators: Digital-payment support is platform/integration specific. Verify the vending platform’s supported provider or API/QR workflow and test settlement before advertising GCash/Maya acceptance.
Start with the correct platform and role
Piso WiFi is a category of prepaid/captive-portal deployments, not one standardized router firmware. A vending/controller platform, the upstream ISP router, and separate Wi-Fi access points can all have different addresses and credentials. The customer portal and the operator admin page are also different security roles. Do not infer a specific GCash/Maya integration from a generic Piso WiFi installation; check the current vending software/payment add-on.
Step-by-step checklist
- Verify supported payment integration in official platform documentation.
- Use a business account/integration appropriate to your transaction model.
- Test ₱-value mapping, success/failure callbacks and duplicate-payment handling.
- Verify the session is credited only after confirmed payment.
- Reconcile platform logs with payment-provider records.
What not to assume
Never collect a customer’s GCash/Maya PIN, OTP or account password in your captive portal. Legitimate integrations should not require the operator to see those secrets. Likewise, 10.0.0.1 is only a private IPv4 address. Its presence does not identify the software by itself, and changing the address does not change how the vending/session system works.
Customer-side checks
- Stay connected to the Piso WiFi SSID and turn off a VPN temporarily if the portal will not open.
- Do not type operator credentials into a public search result.
- If a portal fails only on one phone, test browser captive-portal state, Private DNS, MAC randomization and date/time before blaming the machine.
- Keep payment/voucher proof until the session is confirmed.
- For pause/resume or voucher issues, use the same device when the platform ties sessions to a device identity.
Operator-side checks
Troubleshoot in layers. Confirm stable power, then WAN internet, controller WAN/LAN interfaces, DHCP/DNS, access-point reachability, captive-portal service, payment input, and finally the user/session database. If every client fails, focus on shared infrastructure. If one client fails, compare that client with a working one before rebooting or resetting the system.
Security and reliability
- Change initial/factory administrator credentials after setup.
- Keep customer traffic separated from the management LAN where the platform supports it.
- Use official software updates and make backups before upgrading.
- Protect the controller, coin acceptor and power hardware from moisture, heat and unstable power.
- Use a proper access point for coverage and capacity rather than assuming the controller board’s radio can serve a busy area.
- Never expose the admin dashboard directly to the public internet through an unrestricted port forward.
Network architecture matters more than the portal IP
A healthy installation normally has a clear upstream/downstream design: ISP modem or ONT, then the device responsible for routing/session control, then switches/access points serving customers. Avoid accidental double DHCP, overlapping subnets and a consumer Wi-Fi router running NAT behind the vending controller unless the design intentionally calls for another routed boundary. Label WAN and LAN cables so a maintenance visit does not silently reverse them.
Payment and session integrity
When money or vouchers are involved, troubleshoot payment confirmation separately from internet access. Keep transaction/session logs long enough for legitimate support and reconciliation, but do not collect secrets that the payment provider does not require. For digital wallets, the operator should never request a customer PIN or one-time password. Test duplicate payments, failed callbacks, controller restarts and recovery after power loss before advertising a new payment option.
Maintenance checklist
- Keep the controller/router and access-point software on supported releases from the official vendor.
- Back up configuration before updates and store a copy away from the machine.
- Check power supply, ventilation, storage health and cable condition.
- Review peak-hour WAN utilization, loaded latency and access-point client counts.
- Audit admin accounts after staff/vendor changes and remove access that is no longer needed.
- Test the customer journey—from joining Wi-Fi through payment, portal access, session expiry and reconnect—after every major change.
Check the exact platform before using credentials or reset steps
Piso WiFi systems are not one standardized firmware. Match the machine name, installed version, controller type and local network before applying a login, password-recovery or reset instruction. If the device label or installed platform shows a different address or workflow, use the information for that exact machine rather than forcing a value from another platform.
Treat the wallet and hotspot as separate systems
A digital-wallet payment has at least two states: the wallet/provider decides whether money moved, and the Piso platform decides whether a session or wallet balance was credited. A “paid” screenshot does not by itself prove that the controller received and matched the transaction. Operators need a supported integration or reconciliation process that can connect payment status with the correct customer/session.
Never collect a customer PIN or OTP
Wallet PINs, passwords, and one-time codes authenticate the customer to the payment provider. They should not be entered into a Piso WiFi admin page or sent to the operator. If an integration asks the operator to store customer secrets, do not deploy it until the workflow is verified with the platform/payment provider.
Test failure and duplicate-payment cases
Simulate delayed confirmation, lost internet after payment, controller restart, duplicate callback, and a customer refreshing the portal. Decide how to reconcile an amount that succeeded at the wallet but did not create time. Keep only the transaction information needed for support/accounting, and document a clear refund/credit policy before enabling digital payment publicly.
Map the payment transaction to a session deliberately
A wallet payment has at least two sides: the payment provider records money movement, while the Piso platform must receive/confirm that result and create or credit the correct customer session/account. Record a transaction reference, amount, timestamp, and the platform-side order/session identifier needed to reconcile the two. A successful wallet transfer with no session credit is an integration/reconciliation failure, not proof that Wi-Fi or DNS is broken.
Security and refund handling
The operator should never request a customer wallet PIN, password, or OTP. Use the supported payment-provider/platform confirmation method and limit access to API keys, merchant secrets, callback settings, and transaction logs. Define how duplicate, delayed, cancelled, or miscredited payments are handled before launch. Test a low-value payment end to end, including controller restart and temporary WAN loss, and make sure the customer sees the price and service terms before authorizing payment.
Frequently asked questions
Does a successful GCash or Maya transfer prove Piso WiFi time was credited?
No. Money movement and hotspot session credit are separate systems. Reconcile the payment transaction with the platform-side order/session or credit event.
Should an operator ever ask for a customer OTP or wallet PIN?
No. Those secrets authenticate the customer to the payment provider. Use transaction/reference details and the supported merchant/platform confirmation process instead.
What should be tested before enabling digital payments publicly?
Test price display, successful payment, delayed callback/confirmation, duplicate attempt, cancelled/failed payment, controller restart, temporary WAN loss, correct session credit, transaction logging, and the refund/support process.
How should payment API or merchant secrets be stored?
Restrict them to the supported platform/server configuration, limit staff access, rotate them if exposed, and never place them in public screenshots, client-side notes, or shared customer instructions.
Use the smallest change that solves the problem
A reliable network is easier to maintain when every exception has a reason. With GCash and Maya Payments for Piso WiFi: Integration Checklist, avoid enabling extra services, widening firewall rules, changing multiple radio parameters, or replacing automatic configuration with static values unless the problem actually requires it.
Re-check after firmware or ISP changes
Router updates and provider migrations can rename controls, alter defaults, or move a feature into an app. Re-verify device-specific instructions after a major firmware, gateway, or service change.