The mobile money provider
Moves the money and manages the receiving account, transaction confirmation, account limits, reversals and its own service conditions.
HOW THE SERVICE FITS TOGETHER
Clear roles.
Service boundaries.
Understand what the gateway does, where your billing platform takes over and who handles the money.
This operational overview explains the product’s responsibilities. It does not set commercial pricing, contractual service levels or country-specific legal terms.
FOUR PARTS OF THE FLOW
A connected service.
Distinct responsibilities.
A customer’s payment, the receipt match and their internet connection are related events. Each has an owner and a separate result to check.
ISP Billing Pay
Receives supported forwarded messages, records and matches receipts, supports payment claims and sends payment events to the configured billing platform.
Your billing platform
Creates purchase references, applies package rules and manages usernames, activation, device association, remaining access and router login.
The internet provider
Operates the receiving account and phone, maintains the integration, reconciles payments and supports its customers when a payment or connection needs attention.
DIRECT TO YOUR ACCOUNT
Funds stay in
the receiving account.
Customers send money directly to the receiving account shown by the ISP. The gateway handles information about that payment; it does not hold the funds, settle balances or execute refunds.
A missing gateway receipt is not proof that no payment occurred. Likewise, a matched receipt does not confirm that a package was activated or that a customer connected successfully.
Money corrections, reversals and refunds need to be resolved by the receiving-account owner and mobile money provider through their applicable process.
RUNNING THE CONNECTION
Prepare the system.
Keep it supervised.
Before making the service available
Validate the receiving account and supported receipt format, secure your merchant and device credentials, verify webhook delivery, and test package activation and payment recovery in your billing platform.
During daily operation
Keep the listener phone powered and connected, monitor missing messages and failed deliveries, and reconcile gateway records against the receiving account. Protect customer information and give authorised staff a clear exception-handling process.
When recovering access
Confirm the payment and the correct purchase before reconnecting a device. The billing system needs to check account usage and remaining entitlement, and handle retries without issuing the same paid package twice.
When conditions change
Provider message formats, phone settings and network availability can affect receipt delivery. Validate changes and investigate interrupted flows. Availability and delivery time depend on the phone, provider, gateway and billing integration.
Compatibility is specific to the setup.
Named providers describe receipt-format compatibility. They are not a statement of endorsement, a commercial partnership or a financial-services licence. A country or provider should be validated for the intended receiving account before use.
PLAN YOUR DEPLOYMENT
Agree the details
before going live.
Contact us about your setup, commercial arrangements and the support your rollout needs.