Invoice Session ID

Overview

Invoice session ID is the provider- or merchant-generated identifier for a specific invoice payment session. A robust implementation treats the concept as structured payment data rather than as a label shown only on the checkout page.

It links checkout configuration, quote, address, selected asset, expiry, payment attempts, redirects, callbacks, and status history. A new session ID can be issued when instructions are refreshed or a customer retries through a new checkout. In practice, the system should preserve the original request, the observed blockchain or checkout evidence, and every status change that affects this value. This makes support investigations and financial reconciliation possible without reconstructing the payment from screenshots or mutable client data.

The identifier should be unique, opaque where exposed publicly, validated on every lookup, and kept separate from authorization credentials. Logs and callbacks should preserve it consistently for troubleshooting and reconciliation. The implementation should use exact asset precision, authenticated server-side updates, and idempotent processing wherever repeated API calls, blockchain observations, or webhook deliveries can occur.

A session ID is not the same as an order ID or customer ID. Those identify the commercial purchase or customer, while the session ID identifies one payment interaction. It should be interpreted alongside Invoice Payment Session, Invoice Order ID, Invoice Payment Attempt. These concepts belong to the same workflow, but each answers a different operational question and should not be collapsed into one ambiguous field.

Order ORD-77 can have session PS-1001, which expires, followed by PS-1002 with a new rate and address while remaining attached to the same order. The practical test is whether a merchant can explain how the value was produced, verify it independently, and apply the same rule consistently when the payment is delayed, duplicated, partially paid, refunded, or reviewed manually.