1. What the service does
ISP Billing Pay receives supported mobile money confirmations from an authorised listener, records payment information, matches receipts to purchase intents and notifies the merchant’s billing system. Money is sent directly to the merchant’s receiving account. The gateway does not hold customer funds, provide a wallet balance, issue loans, perform foreign-exchange conversion or settle money to merchants. Provider API channels are future functionality and cannot currently be selected for live processing.
2. Account access and authority
Provide accurate business and contact information and use only systems and receiving accounts you are authorised to operate. Protect your password, API keys, signing secret and listener credentials. Access through a credential may affect the associated account’s records. Inform the operator promptly if access is lost or compromised. An email address entered at signup is not proof of a verified business identity, regulatory authorisation or completion of a provider’s onboarding process.
3. Payments, refunds and customer service
The merchant is responsible for the products or services purchased, customer activation, receipts, applicable taxes, complaints and refunds. A gateway match is a reconciliation result based on received information; it is not an independent provider settlement guarantee. Compare records with your receiving account, investigate reversals and resolve disputed transactions. The gateway cannot refund funds it did not receive. Mandatory customer rights and applicable provider rules continue to apply. See the refunds and disputes policy for the practical process.
4. Integration and operational responsibilities
Validate receipt formats before enabling live activation. Maintain the receiving phone, connectivity, webhook endpoint and billing integration. Verify webhook signatures, deduplicate event processing and preserve purchase references. Router activation and device ownership remain your billing system’s responsibility. An unmatched receipt or inactive session is not permission to assign another customer’s payment. Monitor failures and maintain a reconciliation process. Sandbox results are simulations and do not certify a production integration.
5. Data, confidentiality and security
Use payment-related personal information only for a lawful and necessary purpose. Provide appropriate notices to customers and limit the information sent to the gateway. Never submit wallet PINs, passwords, card security codes or unrelated personal messages. Agree data-processing roles, retention, hosting locations and access responsibilities for the deployment. Keep secrets out of public code and support tickets. See the privacy, data-processing and retention pages for current behaviour and matters to establish in writing.
6. Fees, availability and allocation of responsibility
Gateway fees, invoicing, taxes, renewal, termination charges and support commitments are governed by the applicable written order. Provider charges are separate. No universal service fee, production SLA, uptime guarantee, compensation formula or liability cap is created by this website. Any warranties, liability allocation and dispute forum must be established by the contracting parties consistently with mandatory law. Do not treat a roadmap item or a product illustration as a contractual commitment.
7. Misuse, restriction and closure
Do not forge receipts, compromise another account, conceal fraudulent activity or exceed your authorisation. Restrictions may be necessary to investigate misuse or protect the service under the applicable agreement. Account recovery and closure require verification of authority. Stopping an integration does not automatically erase payment evidence or cancel obligations to customers. Coordinate exports, retained records, revoked credentials and outstanding disputes with the operator.
8. Changes, intellectual property and contact
These pages document the current product and may be revised as capabilities change. Material contractual changes need the notice and acceptance process defined in your agreement. Using the service does not transfer ownership of its software, trademarks or another provider’s intellectual property. Provider references identify compatibility and do not imply endorsement. Questions, service enquiries and requests can be sent to contact@ispbillingpay.com. Do not include confidential credentials in correspondence.