Keep the payment moving.
Get the connection right.

First, confirm that the payment went to the receiving number shown by your internet provider. Keep the original receipt reference and use Claim payment on the provider’s portal, if offered.

For the ISP: find the receipt, check whether it matched the correct purchase, then check webhook delivery and package activation in your billing system. A matched receipt does not by itself confirm a successful router login.

Check the purchase’s payer number, exact amount, currency and receiving account. Review the reason recorded against the receipt. More than one eligible purchase, missing payer details or an expired intent can require attention.

Use the claim flow or authorised payment assignment after checking the purchase. Matching by amount alone can give a genuine payment to the wrong customer.

Check power, internet access, SMS reception and the app’s receiving permission. Open the listener to review its connection and follow the phone manufacturer’s settings for background operation.

Messages already received by the listener wait in its local queue until upload succeeds. The app does not scan the SMS inbox for older messages. Compare missing receipts with the receiving account and investigate gaps before assuming they were never paid.

The payment stays linked to its purchase reference; it is not identified by the MAC address. Your portal can use the claim endpoint to locate the received payment.

Your billing platform then needs to verify the claim, retrieve the paid account, check live usage and apply its device-recovery rules. It should preserve the remaining package and avoid granting a second package for the same payment.

No. Receipt identity determines duplication, not equal amounts or nearby timestamps. Two genuine provider transaction references remain separate payments. Another delivery of the same receipt must not create another payment credit.

Your billing system must also handle repeated webhook delivery safely so that an activation retry does not add a second package.

The custom network option lets your integration configure the actual sender names used by your receiving account. Add the same names to the phone’s allowed-sender list. Countries without a built-in list can use this setup where deployment restrictions permit; Kenya is excluded by default.

Adding a sender is only the first step. The current parser handles supported English receipt patterns, so test actual transaction IDs, payer numbers, amounts, currencies and reversals before enabling automatic activation. Ask support about unsupported formats; no payment-provider API key is required.

Review the original receipt with the ISP. The gateway does not move money or issue a refund. The receiving-account owner and mobile money provider handle money corrections according to the provider’s process.

Do not create a matching purchase simply to hide an amount mismatch. Resolve what was paid and what access the customer should receive first.

Inspect webhook delivery and the billing platform’s event logs. Confirm that the endpoint is reachable, accepts the signed event and records processing before acknowledging success.

If delivery succeeded, investigate package assignment and router access in the billing system. Before retrying activation, check whether the package was already applied.