Invoice Requested Amount

Overview

Invoice Requested Amount is the amount the merchant asks the payer to satisfy under the invoice before considering received payments. For reliable reconciliation, the value should remain traceable from invoice creation through payment monitoring and final reporting.

It originates from the order or billing system and may be expressed in fiat, a stablecoin, or another crypto asset. A conversion process can derive a separate payment amount for the selected asset. 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.

The value should be immutable after invoice issuance unless a controlled revision is created, use documented precision, and remain traceable to line items, tax, shipping, discounts, and credits. 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.

It differs from conversion amount, which is translated into another currency, and from received amount, which reports what the payer actually transferred. It should be interpreted alongside Invoice Requested Amount, Invoice Received Amount, Invoice Settlement Amount. These concepts belong to the same workflow, but each answers a different operational question and should not be collapsed into one ambiguous field.

An invoice can request 250 EUR while the checkout calculates the amount of USDC required during the current payment window. 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.