SMS Forwarder Android App

iPay is the dedicated ISPbills payment-message forwarder for a merchant-SIM Android phone. It receives SMS, reads supported wallet-app notifications, extracts payment fields, and sends them to the registered ISPbills Payment Forwarder device. It is separate from iAdmin and iCustomer.

Use the Payment Forwarder guide for Admin-side registration, event review, and manual approval.

Register and install

1. As a Group Admin, open the direct sidebar item SMS Forwarder.
2. Enter a device name and the exact merchant number, then select Register Device. ISPbills creates or reuses the corresponding iPay gateway.
3. Download the Android app from Download Android App on that page. The link serves /sms.apk.
4. Install it on the phone that receives the merchant messages. iPay requires Android 8.0 or later.
5. Open Settings, enter the same merchant number, and select Verify Phone & Save. Enter the number with its country code in the verification screen and complete the SMS code. ISPbills then issues the app a random revocable device token. The current app’s server URL is fixed and displayed read-only as https://app.ispbills.com.
6. Select Start Service. Keep the ongoing Payment forwarder running notification present.

The registered number, merchant SIM and verified Firebase number must match. Phone-number digits are not a password. The issued device token is stored privately by iPay and can be replaced by verifying again; do not copy or publish it.

Required Android access

Open Settings → Notification Access and enable iPay, then use Battery Optimization and choose Unrestricted, No restrictions, or the vendor equivalent. If a normal permission prompt no longer appears, use App Settings. Enable vendor auto-start when the phone offers it.

What is forwarded

An SMS is considered only when its body contains a supported currency marker next to a parseable amount. Wallet-app notification capture is limited to the supported package names above. The parser can label bKash, Nagad, Rocket/DBBL, Upay, mCash, or CellFin when those names occur in a message.

The forwarded event includes the merchant and payer numbers, amount, transaction reference when found, current device timestamp, SMS/notification source, detected provider, transaction direction, a random event UUID, and the raw message body. Refund, reversal, failed, debit, cash-out, withdrawal, outgoing transfer, and similar text is marked non_credit; it is stored for review but not auto-credited.

Because iPay can read full SMS bodies and selected wallet notifications, install it only on a dedicated, locked merchant phone. Raw messages can contain balances, phone numbers, and references and are sent to ISPbills for reconciliation. Restrict Admin access, screenshots, notification previews, device backups, and physical access accordingly.

Matching and use

The service sends a heartbeat at start and about every 15 minutes. The Dashboard reports connection state, device diagnostics, recent totals, and update availability. The drawer also provides Matched Payments, Customers, Online Customers, Monthly Report, Customer Payments, and Ledger. Customer call, SMS, and copy actions are local to the phone; opening an Admin customer profile still requires a normal web login.

ISPbills compares merchant gateway, amount, payer, and reference with pending payments. It auto-approves only a unique safe match or a supported unique customer/reference case. Partial or multiple matches remain for Admin review. A repeated event UUID or matching transaction is marked duplicate rather than credited twice.

When the phone is offline, network-failed payloads are kept in an app-private file and retried when connectivity returns or a heartbeat runs. HTTP/validation failures are not queued indefinitely. A successful forward clears the last error.

Troubleshooting