Start with the actual access network
Moov Mauritel describes fixed, mobile 4G and fibre services. For a small ISP or WISP, map the available upstream, any radio distribution and the customer CPE at each site. Do not infer fibre coverage at an address or assume a cellular backup has a reachable public address.
Separate a radio or power outage from PPPoE authentication failure. In a shared hotspot, retain the voucher reference and expiry alongside a manually checked payment receipt. Reconcile manually after an upstream interruption; automatic restoration is guided pilot scope, and no offline product workflow is assumed.
Local payments: verify the whole path
Bankily describes merchant payments and bill payment in its application. Check locally whether the operator can enrol and which billers are currently supported; this does not establish an ISPAgents connection or support for every ISP invoice.
For cash or bank transfers your team already accepts, retain the receipt, reference, gross amount, fee and reviewer. A customer screenshot, an initiated transfer and confirmed settlement are different evidence. ISPAgents adapters for these local services are planned, with no live integration claimed.
Amounts and languages
Label amounts MRU explicitly, with two fractional digits in this display example. If an old ledger uses a different ouguiya unit, identify it before import; do not silently relabel or convert it.
Example amount
MRU 1,234.50
Illustrative display only: not a commercial price or proof of locally compliant invoicing.
Review Arabic and French customer messages for the pilot (an Arabic product interface is planned, not shipped), and ask the operator which other languages its subscribers use. Validate names and references on a small phone screen; multilingual billing templates remain a pilot requirement.
Guided pilot scope
Basic subscriber management and TR-069/CWMP CPE management are available. CRM, subscriber billing, payment reconciliation and MikroTik operations remain a Guided pilot, with scope qualification. Local payment API clients and automatic payment-to-access workflows are planned, not shipped. RouterOS local PPP/PPPoE management remains planned. Complete WhatsApp/SMS customer workflows are not shipped.
- Choose a small anonymized sample and one scenario: payment received, subscriber still offline.
- Record the MRU amount, transaction reference, subscriber account, CPE and PPPoE username or hotspot voucher. Do not send secrets or customer data in the first enquiry.
- In the guided pilot, manually compare receipt, invoice and access status with demonstration data. Keep the current system as the source of truth.
- Record discrepancies, acceptance criteria and rollback steps. Router/RADIUS writes and automatic restoration stay outside this demonstration.
Prepare the discussion
Review the existing scope pages for payments, RADIUS, MikroTik and migration.
Public sources
These sources describe provider services, not an ISPAgents integration. Check locally for current terms, eligibility and availability at pilot time. Sources reviewed on 16 October 2026.
Frequently asked questions
Are local payment services integrated?
No. Local payment adapters are planned. The guided pilot evaluates mapping and reconciliation foundations with examples; automatic restoration after payment is not promised.
Must we replace the existing RADIUS?
No. Keep the current system. The existing FreeRADIUS guided pilot is limited to a Status-Server probe; SQL/API sync, accounting import, policy write-back and CoA are not implemented.