ISPAgents

Congo-Brazzaville · Guided pilot

ISP and WISP software in the Republic of the Congo

Prepare a guided pilot: local payments, whole-unit XAF amounts and PPPoE, hotspot or WISP access requirements.

Prepare a guided pilot

What you can evaluate

ISPAgents supports basic subscriber records, search and device assignment.

Guided pilot: ISPAgents has payment-provider presets, webhook mapping, signature verification and settlement-import foundations.

Live local payment-provider clients and automatic payment-to-access workflows are not shipped; these integrations are planned.

Guided pilot: ISPAgents has access-policy preview, approvals and result-recording foundations; live router/RADIUS changes remain gated.

Local payments — planned integrations

This page covers the Republic of the Congo (Congo-Brazzaville), not the Democratic Republic of the Congo. For teams in Brazzaville or Pointe-Noire, confirm that the merchant contract and settlement account belong to the correct country before discussing a provider integration.

The services below are local provider offerings; their presence does not mean they are integrated with ISPAgents.

  • MTN MoMo: MTN Congo presents its MoMo service for individuals and businesses. ISPAgents integration planned.

XAF: zero-decimal amounts

The SIX ISO 4217 list assigns this country CFA franc BEAC (XAF), with zero decimal places. For a reconciliation example, use 15,000 XAF, with no invented cents.

Keep the XAF code in exports and evidence instead of just “FCFA”. XOF and XAF are distinct codes. Confirm each provider’s amount format before constructing a request; this example does not define its API contract or prove a shipped billing feature.

PPPoE, hotspot and WISP access: prepare the evidence

These scenarios help scope a pilot around your network; they are not a measurement of local market share.

ScenarioEvidence to prepare before a trial
PPPoESubscriber reference, session identifier, intended profile and approval owner.
HotspotVoucher duration, expiry, renewal rule and partial-payment handling.
WISPSite, access link, customer equipment and a procedure to distinguish radio faults from payment issues.

Keep current collection procedures during evaluation. Prepare anonymized examples of duplicate references, late settlement, deducted fees and partial payments. Define who reviews each exception and how to return to the manual procedure.

Questions before a pilot

Does a local payment already restore access automatically in the guided pilot?

No. Local payment clients and the automatic payment-to-access workflow are planned, not shipped. Begin the pilot with payment evidence and acceptance criteria, without a promise of automatic reconnection.

Must we replace our existing billing system?

Prepare a limited trial with your team first. Define the source of truth for balances and subscriptions, manual reconciliation and stop conditions before any migration.

Prepare the discussion

Public sources verified on 16 October 2026. Names and services above describe the providers; confirm fees and contractual conditions directly with them.

Prepare your guided pilot

Bring an anonymized invoice, a settlement statement and your access-network diagram. Choose a small customer group, one router and one payment workflow to evaluate.

Discuss a guided pilot