Dynamic Invoice

Overview

A dynamic invoice is an invoice whose amount, currency, payment instructions, status, or other fields are generated or updated from current order, rate, usage, tax, or customer data. It is useful for variable charges and crypto conversion, but changes must be versioned. Once a payment is authorized, the system should not silently alter the obligation associated with that payment attempt.

A dynamic invoice can calculate metered usage, current inventory, late fees, taxes, discounts, or a fiat-to-crypto amount at creation time. Some systems allow controlled repricing before payment begins.

The invoice should have a stable identity even when revisions are issued. Each version should show what changed, when it changed, and whether the previous payment instructions remain valid.

For crypto, a new quote or pay currency can require a new address or payment session. Reusing an old transaction reference after repricing creates matching and refund errors.

Risks include unauthorized changes, stale customer views, duplicate versions, inconsistent accounting, late payments to superseded instructions, and dispute over the accepted price.

Systems should preserve invoice version, source data, calculation, rate, approval, effective time, superseded status, payment attempts, and final settled version. Customers should receive clear revision notices.

For Dynamic Invoice, the operational boundary with Dynamic Checkout and Dynamic Payment Address should be explicit. Identifiers for Dynamic Invoice should connect those records without allowing either linked status to overwrite its own state.

For Dynamic Invoice, the invoice and the payment used to settle it should remain separate records. When Dynamic Invoice interacts with Dynamic Checkout, 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 Dynamic Invoice and Dynamic Payment Address, keeping these layers separate prevents a late payment, repricing event, or refund from silently changing the document originally issued to the customer.