Invoice Payment Session

Overview

What it means and why it exists

An invoice payment session is the technical state associated with a customer's attempt to pay a particular invoice, including selected asset, network, destination, quote and status.

How it works

When the customer opens checkout, the backend creates or restores a session token tied to the invoice. It may record the chosen currency, address, exchange-rate expiry and return URL. The payment monitor and browser interface should refer to the same authoritative payment state, while business records maintain the invoice's own identity.

Technical details worth understanding

One commercial invoice can be viewed or retried through several browser sessions; one session may time out even as a valid blockchain transfer is still pending. Session identifiers should not function as unrestricted authorization to edit orders. A user-interface redirect is not a reliable substitute for backend verification.

What can go wrong

If an abandoned browser session is mistakenly treated as a failed payment, a customer can be charged twice on retry. Session tokens should have appropriate lifetimes and avoid exposing sensitive order information. Repeated webhooks should not create duplicate financial entries.

Practical checks

Use server-generated session references and do not trust client-side payment status claims. Support reloads and closed browser tabs by reconnecting the session to persistent invoice and transaction records. Test an expired session with an incoming pending transfer; do not create a second charge simply because the original screen timed out.

Related concepts

Crypto Invoice, Crypto Payment Status, Crypto Checkout.

Further reading

OxaPay — Developer Documentation.