Transactions and payments
Track payments, links, claims and reconciliation actions.
Sub-tabs
- Transactions: plan payments and their lifecycle.
- Payment links: links created for deferred or shareable payment.
- NotchPay claims: verification requests when a customer reports a payment that is not reflected.
Lifecycle
Common statuses include created, pending, processing, complete, failed and abandoned. A complete payment must only be treated as delivered after backend confirmation and access creation/synchronization.
To process a transaction:
- Search by reference, customer or plan.
- Open the detail and check zone, amount, currency, method, customer and timestamp.
- For a temporary status, wait for provider confirmation and refresh.
- For a failure, do not create access manually; offer a retry or a claim.
Account or guest purchase
A plan may allow guest purchase. The customer can then pay without a ReadyZone account and receive credentials according to the supplied contact. Otherwise, the customer must sign in or create an account. Smart Device plans require a ReadyZone account and must not expose guest purchase.
See plan listing, guest purchase and payment verification.
Force success
The Force success action is disabled for operators by default. An administrator can grant the company permission payments.forceComplete. The UI disables the action when permission is missing and the backend enforces it as well.
Use it only after checking external payment evidence, reference, amount and customer. Record the reason in the operational log; never use it to bypass a missing payment.
Claims and links
A claim must contain the reference and the information needed to reconcile the payment. Use preview before importing a claim file, then confirm only after checking row counts and errors. For a payment link, copy or share the URL and check its expiry.