Start with the payment’s timeline rather than changing the invoice status. PD Crypto Pay separates a quoted amount, an observed payment, confirmations and invoice crediting. Each state calls for a different check.

Read the affected payment

1. Open PD Modules → PD Crypto Pay → Payments.
2. Find the payment for the affected invoice and open Details & timeline.
3. Compare the selected coin, network, receiving address and quoted amount with the customer’s transaction details.
4. Read the latest state and events before issuing another payment request or recording credit manually.

Waiting for your payment means the request has not matched an incoming payment. Seen and Confirming mean detection has occurred but the confirmation requirement is not complete. Waiting for confirmations is not the same as an authentication or provider error, and no fixed confirmation time is guaranteed.

Check amount and expiry states

For Underpaid, review the shortfall and any available top-up guidance. Confirm the intended invoice and receiving address before asking the customer to send anything further. A shared address can make an unusual amount ambiguous when several requests are open.

For Paid after expiry — needs review, inspect the actual payment and invoice first. Mark as settled rechecks receipts attributed to this quote and credits the confirmed amount, subject to the module’s payment rules. An underpayment can still leave the invoice part-paid. Use it only after your team has established which invoice the payment belongs to and checked that it has not already been recorded elsewhere; it is not a diagnostic test or a way to bypass confirmations.

The payment window and Keep watching an expired quote are separate settings. A payment first seen in the window may confirm later; one first observed after expiry can require review. Read the actual timeline rather than assuming the customer’s send time establishes the detection time.

Investigate a missing receipt

Ask for the transaction reference and the network/address used. Check the relevant blockchain record and your configured provider state. A payment sent to an old address or before the current request existed may need a different reconciliation from a normal current quote.

Do not declare funds lost merely because a network check reports nothing. Establish the address, chain, request timing and provider result. Correct a provider error before treating a failed read as evidence that no payment exists.

Reconcile once

Check whether a payment or account credit has already been recorded in Blesta. Do not manually credit it and then settle the same module request again. If ownership or the outcome is uncertain, compare the original transaction, quote timeline and existing invoice payments using your own records. Hold further accounting actions while your team establishes attribution.

Use the amount and expiry settings guide to adjust your future acceptance policy after understanding the individual case.

See the PD Crypto Pay guide for Blesta for related tasks, or explore the module.