Invoice Lifetime
Pronunciation: IN-voys LYFE-time
Definition
Invoice lifetime is the configured duration during which a newly created invoice or payment session remains valid for payment.
Overview
Context and purpose
It is commonly measured from the server-side creation time and can control quote validity, hosted-page availability, address use, and status transition to expired. Lifetime should not be confused with a commercial due date, retention period, subscription term, or the continuing existence of the underlying debt. A short lifetime is common for fiat-priced crypto invoices because the payable asset amount depends on a market rate. The commercial invoice can remain due for days while each generated crypto payment session lasts only minutes. The customer interface can display a countdown, but server time must determine validity. A slow or manipulated client clock should never extend the accepted payment window. The policy should define payments first detected before the deadline but confirmed afterward, as well as transactions sent to copied instructions after expiry. Risks include inconsistent lifetimes across frontend and backend, late-payment loss, duplicate replacement sessions, stale quotes, and addresses displayed beyond their supported period.
How it works
Lifetime is the period during which an invoice’s quoted terms remain available or valid according to the provider’s rules. Expiry is a business policy event, not a command that cancels a previously broadcast blockchain transfer.
Practical checks and failure points
Record created time, expiry time, timezone, detected time and confirmation status separately; do not silently reassign a late payment to a different order.
Related concepts
Example
A buyer broadcasts payment one minute before the invoice expires, but the transfer confirms afterward. The merchant needs a documented late-confirmation policy.
Comparison
Lifetime is the configured duration; invoice status describes what has actually happened.
Key Takeaway
Record created time, expiry time, timezone, detected time and confirmation status separately; do not silently reassign a late payment to a different order.
Sources
- OxaPay API Reference: Generate Invoice — OxaPay (2026-08-01)
- OxaPay API Reference: Generate White Label — OxaPay (2026-08-01)