ISP operations in DR Congo
Keep subscriber records and connection evidence together. Scope a guided billing pilot around USD, CDF and the payments your team already collects.
Currency, payment, connection
Start with the operator's collection workflow
For an ISP or WISP in the Democratic Republic of the Congo, begin with the currency on the invoice and the currency actually received. A payment reference arrives at support, yet the subscriber still has no connection. Match the payer, amount and reference before deciding whether the problem is payment, access, power or backhaul. Keep the existing billing system authoritative during the pilot.
M-Pesa Vodacom, Orange Money and Airtel Money: operator collection methods, ISPAgents integrations not shipped
These public services describe payment methods an operator may already collect, not shipped ISPAgents integrations:
- M-Pesa Vodacom: live ISPAgents DRC client not shipped; custom integration required.
- Orange Money: live ISPAgents DRC client not shipped; custom integration required.
- Airtel Money: live ISPAgents DRC client not shipped; custom integration required.
In a guided pilot, use synthetic payment references to review the provider-neutral payment foundations, partial payments, duplicate confirmations and reconciliation exceptions. Name the cashier and reviewer. Do not treat a provider receipt as proof that subscriber access has returned.
USD by default, CDF in whole francs
Prepare for both USD and CDF: the public public provider tariff table and Vodacom payment guidance show the currencies alongside each other. On this page, USD is the default display currency. CDF is displayed without decimals, in whole francs. This is a display convention for the pilot discussion, not a claim about ISO minor units, accounting precision or payment API scaling.
| Display example | Amount |
|---|---|
| Default currency — USD | USD 10.00 |
| Whole-franc display — CDF | CDF 30,000 |
The amounts above are display examples using boundaries from the cited public provider tariff table. They are not ISPAgents subscription prices, a subscriber offer or a currency conversion. Record invoice currency and received currency separately. Agree any exchange-rate evidence and rounding rule with finance; this page supplies no live rate or automatic currency conversion.
Plan for weak backhaul and power cuts
When a backhaul link degrades or site power fails, separate a recorded payment from evidence of connectivity. Available TR-069 diagnostics and subscriber-to-device assignment help the operator inspect a reachable CPE; they do not guarantee fresh evidence from an unreachable device.
Within a guided pilot, rehearse a delayed confirmation, an unreachable router and an interrupted operator connection. Mark missing evidence as unknown, assign an owner and review the result before another access decision. MikroTik operations, service-policy previews and simulated access results remain guided pilot scope. Offline operation, queued work surviving power loss and automatic recovery are not claimed as shipped here. Agree those acceptance checks before extending the pilot.
Prepare the pilot with your team
Bring router models, firmware, renewal rules, invoice currencies and synthetic payment references. Agree the source of truth, roles, stop conditions and rollback requirements. Keep a disputed payment or stale connection result under operator review. Do not submit passwords, API credentials or customer exports in the form.
Use the mobile-money pilot scope, MikroTik guided pilot scope, RADIUS evaluation guide and migration review to frame the discussion.
French and English handoffs
Review cashier, finance and support wording in the language your team uses. These paired public pages do not imply that every product screen is translated. Automated WhatsApp and SMS customer workflows remain planned, not shipped. Browse country pages or read the French DRC page.
Frequently asked questions
Are M-Pesa, Orange Money and Airtel Money integrations not shipped by ISPAgents?
Not shipped. These are payment methods your operator may already collect. ISPAgents live DRC payment clients are not shipped. Payment evidence and reconciliation foundations are guided pilot scope with synthetic records; provider connections require custom integration.
Why show USD first and CDF without decimals?
This page defaults to USD and displays CDF in whole francs for the operator review. That is a page display convention, not a change to ledger precision or provider API units. The examples are not an exchange quote or ISPAgents subscription prices.
Will service return automatically after a payment or outage?
Automatic restoration remains guided pilot scope with simulated outcomes. A payment receipt does not prove a powered CPE, a healthy backhaul or restored access. Offline work and safe recovery must be qualified for the agreed pilot.
Continue the operations map.
ISP and WISP software in Algeria
Scope a guided pilot around your payment references, equipment and support procedures in Algeria.
Open pageCountriesISP and WISP software in Bénin
Start with subscriber records and TR-069 device management in Bénin. Evaluate billing and reconciliation foundations in a guided pilot using fictitious XOF records.
Open pageSolutionsAutomatic Internet Suspension Software — Guided pilot
Guided pilot: Preview, queued jobs, approvals, result recording, and a mock-safe worker can be evaluated in a guided pilot. Live router/RADIUS mutation remains gated; automated suspension and restoration are not a shipped promise.
Open pageSolutionsCustomer Self-Service Foundations — Guided pilot
Guided pilot: Field-job lifecycle, serialized stock, basic tickets and subscriber portal flows have narrow synthetic-data proof and remain guided pilots. Physical installs and invite email delivery are unproven. The technician PWA, dispatch board, dedicated stock workspace and IPAM remain roadmap.
Open page