iCustomer Android App

iCustomer is the subscriber app for the ISPbills customer portal. Its Android navigation surrounds the live portal, while the server remains responsible for login, tenant branding, enabled features, forms, support ownership, and payment-gateway redirects.

Install and choose the ISP portal

iCustomer requires Android 8.0 or later. Download it from Get iCustomer on the customer sign-in page; the current link is https://ispbills.com/customer.apk?v=1.1.0.

The initial portal is https://my.ispbills.com/. After signing in, open More → Portal address to use another HTTPS address supplied by the ISP. The app adds https:// when omitted, rejects a value without a host, and does not permit cleartext HTTP. Changing the portal rebuilds the web session, so sign in to the selected server again.

Use only a domain supplied by the ISP. Push registration on a custom domain also requires that server to run the current customer-mobile backend and use the matching Firebase project.

Sign in and navigate

Select the phone button on the sign-in screen to use native SMS verification. Enter the registered number in full international format (for example, +8801712345678) and the one-time code. ISPbills accepts the Firebase identity only when the verified number belongs to an existing customer account, then opens a short-lived one-time customer session. The original portal mobile-number form and Customer ID recovery remain available when required by the ISP.

The bottom bar contains Home, Bills, Usage, and Support. More includes instant recharge, packages, internet history, payment history, profile, profile editing, a new support ticket, card stores, MAC replacement, and the portal-address control. Some items can be unavailable because of tenant settings or account state.

The web session is kept in the Android WebView cookie store. Use the portal’s account menu to sign out. Logout also removes this installation’s customer push registration.

Bills and payments

Open Bills, choose an unpaid bill, and use its payment action. iCustomer shows the payment methods enabled by that ISP; it does not maintain a separate Android gateway list. Gateway pages and callbacks remain in the portal session, and third-party cookies are enabled for these flows.

Wait for the provider and ISPbills result page before retrying. Then use More → Payment history to verify the recorded status. Do not treat a wallet debit alone as proof that ISPbills completed the payment.

Authenticated invoice and attachment downloads use Android Download Manager. Support ticket attachments use Android’s file picker and give the app access only to selected files.

Support, deep links, and push

Support lists the customer’s public tickets. Customers can create a ticket, open a ticket they own, reply, and attach a selected file. Internal staff tickets and internal notes are not exposed.

Current push alerts cover:

• a new invoice;
• a public staff reply on a customer ticket; and
• a staff-driven customer-ticket status change.

Allow notifications when Android asks. The installation registers after an authenticated customer or support page loads. Notification deep links are restricted to /customers/bills and /complaints-customer-interface; arbitrary server paths cannot be injected through a push message. Verified https://my.ispbills.com links with an allowed path can open the app. If sign-in is required, complete it and reopen the alert.

Privacy and current limitations

The app stores the selected portal URL, a random installation ID, and Firebase token. The authenticated session stays in WebView cookies. Android backup and cleartext traffic are disabled.

There is no offline queue. Bills, payments, usage charts, profile changes, and support actions require the server. Treat bills, usage, tickets, identity fields, and downloaded files as private customer data.

Troubleshooting