Finance → Payments is the transaction ledger: every payment the platform requested or received, whether it came from a customer's phone or was recorded by staff. It is the place to answer "did this customer actually pay?".
What a payment row shows
- Transaction ID - the reference for the attempt.
- Transaction Type - what kind of collection it was.
- Payment Method - the gateway used.
- Status - where the attempt ended up.
- Amount - the plan price the customer was paying for.
- Access Code and Customer Phone - who was paying.
- Invoice No - the invoice it settles, where one applies.
- Router - the router the payment was taken on.
- Device details - the MAC, vendor, device class, and OS family of the device that started the payment, which is useful when a customer disputes which device paid.
- Created At - when the attempt was made.
Filter by status, payment method, or router to narrow the list to what you are chasing. Search Transaction ID, Access / Account, or Reference / Phone to find a specific attempt.
Working a payment
- View details - the full record of the attempt and its history.
- Recheck - ask the gateway for the current state of a pending transaction. Providers that support a status query are rechecked directly; for callback-only providers the platform waits for the provider's callback. Recheck is available only while the row is Pending.
- Record manual transaction - log a payment that happened outside the platform, for example cash handed to a technician. This global action records the payment method, reference, amount, status, and notes; use Record Payment on the customer's record when the payment must be attributed to that customer and extend their service.
Recording an offline payment
Payments taken at the counter or in the field are recorded from the customer's own record: open the customer, choose Record Payment, and enter the package, the payment method, and a note. The payment is attributed to that customer and settles their billing.
Recharge analytics
Finance → Recharge Analytics reports on recharge behaviour across the base - the volume and value of recharges, and the channels customers use to pay.