1. Detection comes first
The transaction can appear within seconds while still being replaceable, reversible by chain rules or absent from a finalized block.
2. Confirmations add confidence
Each new accepted block increases finality. The order page shows current and required confirmations reported by the payment provider.
3. Delays vary
Network congestion, low sender fee, exchange batching, maintenance or provider polling can slow detection and confirmation without meaning the funds are lost.
4. Paid then manual processing
Only verified confirmation changes the order to paid. It then enters manual fulfillment, and delivery status updates separately.
5. Read explorer evidence in context
A transaction ID can show whether a transfer was broadcast, its network, destination, amount and confirmation progress. It cannot by itself prove that the transfer matched the correct live invoice, arrived before expiry, included a required memo or received the provider’s final verified status. Compare the explorer record with the invoice and order page. Congestion, wallet batching, provider monitoring and risk review can create different delays, so avoid promising a universal confirmation time.
6. Reconcile before taking another action
If status appears inconsistent, do not send a second payment or switch networks. Preserve the live invoice, USV reference, transaction ID, network, sent amount, timestamp and block-explorer link, then use order tracking. Support can compare these facts with the signed provider event and expected invoice. A wallet screenshot alone is not final proof, and no one needs a seed phrase or private key to investigate.
Frequently asked questions
Why does it say detected but not paid?
The transfer has been seen, but the required confirmation count is not complete.
Can support speed up confirmations?
Usually no; block production and transaction inclusion are controlled by the network and sender fee policy.
What if the session expires after I sent?
Do not pay again. Keep the transaction ID and check the order page; contact support if it is not matched after network confirmation.
Is there one fixed number of confirmations for every payment?
No universal number should be assumed. The live payment session and provider status reflect the selected asset, network and current processing requirements. Wait for the verified order state.
Sources
- OxaPay Webhook Documentation ↗
Official webhook documentation distinguishing intermediate paying from final paid and describing HMAC signature verification.
Last reviewed: 2026-08-28 - OxaPay API Reference ↗
Official overview of OxaPay payment APIs and the payment-integration context used for live invoices.
Last reviewed: 2026-08-28