Skip to main content

​
Use the payment ledger

Open Billing → Payments. The ledger is the ISP’s operational view of money received or initiated for subscriber service. It supports search, method/status/date filters, incremental loading, detail pages, manual records, import/export, receipts, and—when the Centipid wallet is enabled—collection and withdrawal tabs.

​
Payment status

The list distinguishes confirmed and pending records. A provider initiation, request ID, or customer prompt is not a confirmed payment. Treat access activation and reconciliation as complete only when the payment reaches the successful/final state expected by the current integration.

​
Find a payment

Search using a stable value such as receipt, provider reference, subscriber name/username, phone, account number, or amount/date context. Apply status, method, date-window, and wallet-view filters before exporting or taking a bulk operational decision. If two records appear similar, compare provider reference, receipt, amount, timestamp, subscriber, and gateway before deciding one is a duplicate.

​
Payment detail

The detail page can show:
  • amount, method, status, receipt/reference, and timestamps;
  • subscriber and package/network context;
  • invoice linkage;
  • payout/disbursement state where applicable;
  • related payments and activity;
  • receipt actions and safe edit/delete actions allowed by policy.
Use the detail page when a subscriber reports “paid but offline.” Confirm the record belongs to that subscriber before changing expiry or access.

​
Record a manual payment

Use manual creation only for money received outside an automatic callback and supported by the business process.
  1. Select the subscriber when available.
  2. Enter the amount and current payment method/reference fields.
  3. Use the real receipt/reference; do not invent one to satisfy a workflow.
  4. Review the resulting package/expiry/invoice effects.
  5. Save once and verify the ledger/profile.
Do not record a manual payment merely because an online payment is still pending. First check the provider and callback state to avoid double credit.

​
Receipts

A payment can expose a PDF receipt, resend action, and email-receipt dialog. The email defaults to the subscriber address when available and must be a valid address if supplied. Receipt resend/email endpoints are rate-limited; repeated clicking is not a delivery troubleshooting strategy. Verify the amount, receipt number, subscriber, the ISP’s identity, and email before sending.

​
Import and export

The import/export workspace supports controlled payment migration/reporting. Export requires a valid start/end date with end on or after start. Limit columns and date range to the business need, protect exported personal/financial data, and reconcile totals with the filtered ledger. When importing, preview a small set, preserve provider references, and identify duplicates before writing. Never upload a bank/provider export to an unrelated ISP account.

​
Editing and deletion

Editing a payment can affect subscriber, invoice, and reporting relationships. Deletion is destructive and should be limited to demonstrably incorrect records. Reconciliation adjustments should preserve an audit trail whenever possible.
  1. Confirm successful status and provider/receipt uniqueness.
  2. Verify subscriber association.
  3. Check package, expiry, account pause/block status, and device limit.
  4. Review active sessions and NAS health.
  5. Confirm invoice state if the payment was intended for an invoice.
  6. Apply one targeted correction; do not create duplicate payments.
See Invoices, Payment troubleshooting, and Subscriber profile.