Receive-only SMS access
The app requests permission to receive incoming SMS. It does not request inbox-reading access, so it does not import old messages from your inbox.
THE ANDROID LISTENER
Your receiving phone.
Connected to your workflow.
Forward supported mobile money confirmations from a dedicated Android phone to ISP Billing Pay. Customers keep paying your own receiving account.
Direct APK download for your dedicated receiving phone.
A SMALL APP WITH A CLEAR JOB
From a payment message
to a useful event.
The listener receives new SMS messages, filters configured mobile money senders and sends eligible messages to your gateway. The gateway parses the receipt and matches it to a purchase.
Your money remains in your receiving account. Your billing platform uses the matched payment to manage the package and connection.
Delivery that can wait
Eligible messages are queued on the phone while delivery is unavailable. The local queued copy is removed after the gateway confirms delivery.
A dedicated connection
Pair the phone with a device credential for your merchant account. Use the gateway’s device controls to rotate or revoke access when needed.
GET YOUR PHONE READY
Set up once.
Check it every day.
- Prepare the receiving phone. Use the Android phone that receives your mobile money confirmations. Keep the receiving SIM active and provide reliable power and internet access.
- Install the listener. Download the APK from this site and follow Android’s installation prompts. Keep the phone under your team’s control.
- Register and pair the device. Create the listener device through your merchant integration, then enter the gateway address and device credential in the app. Follow the device guide for the exact settings.
- Enable incoming-message delivery. Grant the receive-SMS permission and follow the phone’s settings for reliable background operation. Use the configured provider sender list.
- Run a real receipt check. Confirm that a supported payment notification reaches the gateway and that a test purchase matches correctly before making the flow available to customers.
YOUR LOCAL NETWORK
Set the sender.
Validate the receipt.
Built-in sender lists cover Uganda and Ghana. For another network, your integration can choose the custom network option and configure the sender name shown on genuine payment messages. Country restrictions still apply; Kenya is excluded by default.
Add that sender to the phone’s allowed-sender list as well as the gateway device. These settings do not automatically synchronize. No payment-provider API key is needed.
The current receipt parser expects supported English message patterns. A new sender does not automatically add support for every language, currency layout or transaction format. Validate actual payment details and a complete test activation before enabling the customer flow.
Configure a custom network ↗KEEP THE CONNECTION HEALTHY
A few habits
make a big difference.
- Check the device’s last-seen information and investigate unexpected gaps.
- Keep the phone charged, connected and able to receive provider messages.
- Review permissions and background settings after app or Android updates.
- Reconcile received payment records with the mobile money account.
- Revoke the device credential before replacing, selling or retiring the phone.
The listener cannot recover every missed SMS from the inbox. A powered-off phone, disabled permission or changed notification format can require an operator to investigate a missing receipt.
Know where the message goes.
Payment messages can include names, phone numbers, transaction references and balances. A queued copy is temporary on the phone; the gateway can retain the original message with its payment record for review and reconciliation.
Read the data-handling overview ↗READY TO CONNECT?
Give your receiving number
a place in your billing flow.
Start with one phone, one provider and a verified end-to-end payment.