Invoice Due Time
Pronunciation: IN-voys doo tym
Definition
Invoice due time is the time by which a merchant expects a payment to satisfy an invoice under the agreed commercial terms. It is not necessarily the same as a blockchain payment-request expiry or the moment a transaction confirms.
Overview
What it means and why it exists
Invoice due time is the time by which a merchant expects a payment to satisfy an invoice under the agreed commercial terms. It is not necessarily the same as a blockchain payment-request expiry or the moment a transaction confirms.
How it works
An invoicing system records a due timestamp with a timezone and links it to the order, amount and customer terms. Separately, a crypto checkout may set an expiration or quote-validity period for the payment session. A merchant's policy must say whether timely payment means first broadcast, first detection, sufficient confirmations or actual receipt before a cutoff.
Technical details worth understanding
These distinctions matter because a customer can submit a transaction before the due time but receive its first block inclusion afterward. The business can define a grace period or exception review without rewriting historical timestamps. Accurate audit trails preserve the original due time and the observed on-chain event times.
What can go wrong
A late payment is not automatically a lost payment, and an invoice appearing expired does not erase an incoming blockchain transfer. Automatic refunding may be unsafe until sender ownership and compliance checks have been completed. Customer-facing instructions should explain which event counts as on time.
Practical checks
When defining due time, state whether the cutoff refers to broadcast, observed arrival or completed confirmations. Save the timestamp and timezone. Do not automatically lose track of value sent after the deadline: route late arrivals to a clearly defined exception workflow while maintaining the original contractual record.
Related concepts
Crypto Invoice, Crypto Payment Status, Crypto Checkout.
Further reading
Example
A $120 consulting invoice is due Friday at 17:00 UTC. The customer broadcasts at 16:59, but the transaction confirms at 17:08. The merchant's policy accepts a timely broadcast plus later confirmations, so the order is recorded as received with a final confirmation timestamp.
Comparison
Due time is a contractual payment deadline; checkout expiration ends a particular payment session; rate-lock expiration limits a quoted conversion price. They can occur at different times.
Key Takeaway
These distinctions matter because a customer can submit a transaction before the due time but receive its first block inclusion afterward.
Sources
- The Invoice object — Stripe Documentation (2026-08-02)
- Invoices API — PayPal Developer Documentation (2026-08-02)
- Generate Invoice — OxaPay (2026-08-02)