Guided pilot · BIF

ISP software in Burundi: scope a guided pilot

Prepare a guided pilot for your ISP or WISP in Burundi. Review BIF amounts, payment evidence and your access setup before agreeing on an integration.

BIF: make the amount units explicit

The SIX ISO 4217 currency list records BIF with zero decimal places.

Use whole-franc BIF display amounts, without a decimal suffix. In pilot data mapping, establish whether an external export uses major units or another encoding; never silently divide a BIF amount by 100. The example below is illustrative, not an ISP tariff.

Example amount

BIF 1,234

Local payment services: adapters planned

The Banque de la République du Burundi list dated 9 February 2026 includes Lumicash and SASAI Fintech Burundi (EcoCash) as electronic-money issuers. EcoCash Burundi describes transfers and bill payments. These are local services to discuss during discovery; ISPAgents adapters for both are planned, not shipped.

Keep the Burundi provider identity attached to every sample export. The shared EcoCash name alone is not enough to identify the country or the payment contract.

Access: establish the configuration before connecting it

For a PPPoE service, record the subscriber login, NAS, session and access profile. For a hotspot, record the login method, session expiry and how a customer is identified. For fixed wireless, also record the site, CPE and backhaul path. These are pilot discovery checks, not claims about national deployment or coverage. Check locally which access methods your network actually uses.

What the guided pilot can assess

ISPAgents has subscriber records and TR-069/CWMP device-management capabilities. CRM and accounting-grade customer billing remain guided-pilot foundations. Local wallet adapters are planned; automatic payment-to-access workflows are not shipped.

MikroTik RouterOS operations remain guided pilot. The existing FreeRADIUS guided-pilot foundation includes a signed Status-Server probe and an opt-in SQL accounting import. CoA/Disconnect drivers exist but are not qualified against a real NAS; SQL/API sync and policy write-back are not a complete integration. Treat a payment receipt and a working subscriber session as separate evidence. Live access changes need a separately validated adapter, authorization and rollback plan.

Start with one access method and a small sample of redacted records. Review amount units, payment references, duplicate evidence and partial payments before considering any live workflow. Keep the current billing and access systems in charge during discovery.

For more context, read the TR-069 ACS overview and the guided-pilot payment collection overview.

Sources and local validation

The linked currency-maintenance, central-bank and provider publications were reviewed on 16 October 2026. They establish the limited facts cited above, not ISPAgents integration availability. Check locally for current provider terms, service coverage and your own access configuration; no market-share, price or coverage estimates are assumed.

Frequently asked questions

Are local wallet integrations available?

Local wallet adapters are planned, not shipped. A guided pilot can assess sample records and provider requirements; it is not a promise of live payment collection.

How should BIF amounts appear?

BIF uses zero decimal places in ISO 4217 display formatting. Confirm the units in source records before importing them.

Scope a guided pilot

Describe the country, access type, currency and payment path to evaluate. Send only general context, without customer data or secret credentials.

Email about a guided pilot

Opens your email app to sales@ispagents.com.