Invoice Lifetime

Overview

Invoice lifetime is the configured duration during which a newly created invoice or payment session remains valid for payment. 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.

Systems should store configured lifetime, creation and expiry timestamps, time zone or epoch format, status transition, late-payment checks, and replacement linkage.

A complete record for Invoice Lifetime should show where it depends on Payment Lifetime and how it differs from Commercial Invoice. That distinction lets teams reconcile Invoice Lifetime without treating a related interface or event as final financial evidence.

For Invoice Lifetime, the invoice and the payment used to settle it should remain separate records. When Invoice Lifetime interacts with Payment Lifetime, the invoice defines the commercial obligation, parties, amount, denomination, tax, due date, and revision history; payment records hold quotes, addresses, transaction identifiers, confirmations, fees, refunds, and settlement. In the relationship between Invoice Lifetime and Commercial Invoice, keeping these layers separate prevents a late payment, repricing event, or refund from silently changing the document originally issued to the customer.