Start with the actual access network
Algérie Télécom lists IDOOM fibre, ADSL and fixed 4G services. Use those access types to frame the inventory, then confirm the actual upstream and customer equipment with the small operator. A wireless customer link or shared-site hotspot is a pilot scenario to verify, not evidence of resale rights or a universal national network model.
For an ADSL-to-fibre customer equipment change, record the old and new CPE and the access account before testing PPPoE authentication. For a hotspot on your existing gateway, distinguish voucher validity, captive-portal login and upstream reachability; an ISPAgents captive portal is planned, not shipped. None of these checks implies a live ISPAgents provisioning adapter.
Local payments: verify the whole path
Algérie Poste documents online payments with EDAHABIA and describes BaridPay merchant QR payments from BaridiMob. Check locally for merchant enrolment, settlement evidence and current terms. A BaridiMob transfer reference must not be treated as an automatic ISP payment confirmation.
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
Show DZD explicitly with two fractional digits in the reconciliation worksheet. Keep the provider reference and the fee separate from the gross payment.
Example amount
DZD 1,234.50
Illustrative display only: not a commercial price or proof of locally compliant invoicing.
Agree French and Arabic customer wording for the pilot (an Arabic product interface is planned, not shipped), then ask whether Tamazight or another language is needed for this subscriber group. Language choice is a pilot requirement, not a shipped localization claim.
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 DZD 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.