Daily internet USD 1Package selected ✓
Create the purchase
Your login page saves the customer's package choice, payer number and purchase reference, then shows your payment instructions.
Explore payment intents ↗ THE DIRECT PAYMENT GATEWAY FOR ISPs
Get paid directly.
Keep customers
connected.
Turn mobile money arriving on your own number into payments your billing system understands. Match receipts, automate activation and keep every transaction in view.
✓ Funds stay with you✓ No mobile money API required
Built for internet providers, because getting a payment gateway approved is often the hardest part of starting out. There is no application to pass here: the money arrives on the number you already use.
Finding your country · sample amounts, not prices.
YOUR PAYMENT OPERATIONS
Good things are connecting.
ReceivedUSD 64Sample receipts
Matched24 / 26Ready for your billing system
Recent paymentsView all ↗
01
Customer • 018DEMO-0194 · Mobile money
USD 1Matched02
Customer • 027DEMO-0195 · Mobile money
USD 0.50Matched03
Customer • 042DEMO-0196 · Mobile money
USD 1ReviewThe right payment. The right purchase.
Match by payer number and amount.
Match by payer number and amount.
Payment matchedUSD 1 DEMO-0194
Signed webhook queued for delivery
Product illustration · your billing platform controls activation
Your receiving numberKeep the way customers already pay
Your billing platformConnect with a simple API and webhooks
A clear payment trailFrom incoming receipt to matched purchase
A SHORTER PATH TO ACCESS
Three steps.
One connected experience.
Your customer pays the number they know. We turn the confirmation into an event your billing platform can act on.
↙Payment receivedFrom your mobile money providerForwarded by your listener phone
Receive the payment
Your dedicated Android phone forwards supported payment notifications. Payments land in your wallet, with a record in the gateway.
Meet the Android listener ↗Receipt→Match→Webhook ✓
Your billing system takes it from hereMatch and activate
Matched payments trigger a signed webhook. Your billing system activates the package; uncertain matches remain available for review.
Understand webhooks ↗PAYMENTS WITH CONTEXT
Every receipt.
A clear next step.
A useful payment gateway gives your team the context to resolve a payment and keep the customer moving.
INTERACTIVE PREVIEW
Demo dataPayment inbox
SELECTED RECEIPTDEMO-0194
Payer number and amount match the waiting purchase. A payment.matched event is ready for the billing system.
Match on more than an amount
Payer number and amount must match. Ambiguous purchases stay in review rather than being assigned by timing.
Give missed payments a way forward
The claim endpoint helps your portal find a received payment by transaction ID and check it against the purchase.
Keep your team in control
Review unmatched receipts, assign a reference, rotate phone keys and see when a listener last checked in.
DESIGNED AROUND CLEAR BOUNDARIES
Your money stays yours.
Your integration stays in control.
We connect the payment message to your billing workflow. Funds move directly between the payer and your receiving account.
Explore security practices ↗Signed delivery
Verify webhook signatures and timestamps before acting on an event.
Merchant isolation
Payment records and device actions are scoped to the authenticated merchant.
Controlled retries
Transaction identities and delivery records support safe reconciliation and retry handling.
Revocable access
Phone credentials can be rotated or revoked from your integration.
START WITH THE RIGHT CONNECTION
Local payment habits.
A consistent integration.
Some countries have their networks built in. Everywhere else connects the same way: name the sender your payment messages arrive from and read amounts in your own currency. Validate receipt samples during onboarding, then connect through the same gateway API.
Bring your market to the conversation ↗Ghana GHS
MTN MoMo · Telecel Cash · AT Money
Parser support includedNigeria NGN
Name the sender your payment alerts arrive from
Custom senderSouth Africa ZAR
Name the sender your payment alerts arrive from
Custom senderNo country matches that search.
Provider names describe compatibility, not commercial partnerships or endorsement.
FOR THE PEOPLE BUILDING THE CONNECTION
A small API.
A useful set of building blocks.
Create a payment intent. Receive a signed event. Keep package activation in your existing billing system.
Read the documentation ↗create-payment.sh
curl https://ispbillingpay.com/v1/intents \
-H "Authorization: Bearer $ISP_PAY_KEY" \
-H "Content-Type: application/json" \
-d '{
"amount": 1,
"payer_phone": "CUSTOMER_PHONE",
"payer_name": "Example",
"reference": "purchase-1042"
}'201 CREATEDIntent saved. Ready for the payment.
Sample figures in USD. Use your merchant’s configured currency and real purchase details.
Do you collect or hold our customers' money?+
No. Customers pay your mobile money receiving account directly. The gateway handles receipt records, matching and notifications to your billing system.
Do I need a mobile money API contract?+
This connection uses an Android listener on your receiving phone, so it does not require a provider API integration. Your receiving account still needs to meet the provider's terms and limits. Your billing system uses a separate ISP Billing Pay merchant API key.
What happens if a payment cannot be matched?+
It remains unmatched with a reason for review. Your billing system can expose a claim flow or let an authorised operator assign the receipt to the correct purchase reference.
Will this connect a customer after their MAC changes?+
The gateway links payments to purchase references. Your billing system handles the username, remaining package, device binding and router login. The claim API can support that recovery without creating another payment.
What happens when the listener phone goes offline?+
The app queues payment messages it has received until they can be uploaded. The gateway exposes last-seen information. Keep the phone charged, connected and monitored; reconcile missed notifications against your receiving account.
MAKE THE NEXT PAYMENT COUNT