Underpaid Crypto Payment

Overview

An Underpaid Crypto Payment exists when the valid value received and attributed to an obligation is below the amount due. The comparison must use the invoice’s denomination, quote time, accepted asset and network, amount precision, and fee policy. A transaction can be technically successful while leaving the order commercially unpaid.

Common causes include deducting a network or withdrawal fee from the amount, exchange-rate movement after quote expiry, token transfer taxes, decimal conversion errors, a partial first payment, or use of the wrong asset. Multiple transfers may be aggregated only when policy permits and every transfer is tied confidently to the same payer and invoice.

The system should preserve issued amount, required crypto amount, quote source and expiration, received transactions, actual recipient balance changes, confirmations, fees, and calculated shortfall. Customer interfaces need to show the remaining amount and whether a top-up is still possible without changing the original invoice.

An Underpaid Crypto Payment policy determines whether the merchant accepts the shortfall, requests an additional payment, credits an account, cancels fulfillment, or refunds the received amount. The numeric Underpaid Crypto Payment tolerance is only one input to that broader decision.

For example, an invoice requiring 100 units might receive 99.8 after a sender-side fee. A merchant may accept that difference below a defined threshold, but a high-value or regulated transaction can require the exact amount. The accepted exception should be recorded as a merchant decision, not disguised as full receipt.

Reporting should separate occurrence count, shortfall value, cause, recovery method, customer impact, processing time, and merchant loss. This reveals whether Underpaid Crypto Payment comes from user behavior, pricing design, unsupported token mechanics, or a provider configuration problem.