Invoice Expired Time

Overview

Invoice expired time is the timestamp at which an invoice or its payment session stopped accepting payments under the original instructions. In an operational payment system, this field or policy should have one authoritative meaning across the API, checkout, webhook, ledger, and support tools.

The value may be calculated from created time plus a payment window or set directly by the payment provider. After expiry, a checkout may reject new payments, require a refreshed quote, or create a replacement invoice. 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.

Systems should record expiry as a state transition, distinguish provider time from client time, and continue monitoring for late transfers so they can be placed into an exception workflow rather than silently ignored. 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.

Expired time differs from due time, which represents the commercial deadline, and from paid time, which records successful satisfaction. Expiry does not erase an on-chain transfer sent just before or after the cutoff. It should be interpreted alongside Invoice Due Time, Invoice Paid Time, Late Crypto Payment. These concepts belong to the same workflow, but each answers a different operational question and should not be collapsed into one ambiguous field.

If an invoice expires at 14:30 UTC and a transaction is first observed at 14:32, the system can classify it as a late crypto payment and apply the merchant’s documented policy. 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.