Partially Paid Crypto Payment

Overview

How it works and why it matters

A partially paid obligation has received qualifying value that remains below its agreed threshold. The system must distinguish amount transmitted, amount detected and amount accepted under confirmation and network rules. Conversion-rate timing and transaction fees can make the shortfall less obvious than a simple token balance.

Important technical and operational details

Related operational concepts include Overpaid Crypto Payment , Payment Attempt , and Crypto Payment Exception .

Specific scope: a crypto payment in which the verified amount received is satisfy the payment obligation.

Partially Paid Crypto Payment is closely related to Overpaid Crypto Payment , Payment Attempt , and Crypto Payment Exception .

Practical decision points

The application should record the original obligation and each qualifying credit separately. For example, an invoice may be 100.00 USDC, receive 60.00, and later receive 39.99; a remaining cent can be commercially material depending on the published policy. Token precision and exchange-rate timestamps matter when the payer sends a different asset. Define if top-ups use the original address, whether expiration stops acceptance, and whether refunds net against outstanding credits. Distinguish an underpaid order with valid partial receipts from a failed transaction. Support should see the accepted portions and the exact residual amount without needing to recalculate from a screenshot.

Related concepts

Overpaid Crypto Payment; Payment Attempt; Crypto Payment Exception

Further reading

• docs.oxapay.com documentation
• docs.oxapay.com documentation