Underpayment Tolerance
Pronunciation: UN-dur-pay-ment TAH-lur-uns
Definition
Underpayment tolerance is the maximum verified shortfall a merchant will automatically accept when a payment is below the required amount. It may be expressed as an absolute value, percentage, asset units, or a combined cap and must specify valuation time, precision, fees, and whether multiple transfers are aggregated. Tolerance is not the complete underpayment policy; it is a narrowly defined threshold used to avoid disproportionate recovery work for immaterial differences.
Overview
How it works
Underpayment tolerance is a quantitative boundary for accepting a payment whose verified receipt is slightly below the obligation. The rule reduces customer friction and manual work when network fees, rounding, or minor price movement create an economically immaterial difference. It should be deterministic enough that the same evidence produces the same result.
A tolerance can be denominated in invoice currency, received asset units, a fixed amount, a percentage, or a combination such as the lower of two caps. The rule must identify the valuation source and timestamp, decimal precision, rounding direction, treatment of sender and recipient fees, quote expiration, and whether several transactions can be aggregated.
For example, a merchant could accept a shortfall up to 0.5% but no more than five dollars. A 50-cent difference on a small order may pass, while the same percentage on a large invoice exceeds the absolute cap. The original invoice amount remains unchanged; the system records the accepted shortfall as a discount, write-off, or other defined accounting effect.
Tolerance should be narrower for high-value, irreversible, regulated, or fraud-sensitive goods. It may be disabled for unsupported assets, expired quotes, wrong-network transfers, or payments whose attribution is uncertain. Attackers should not be able to split transactions or manipulate rounding repeatedly to obtain systematic discounts.
The threshold is part of the broader underpayment policy. It does not determine how customers top up, how refunds work, who approves an exception above the limit, or when fulfillment is canceled. Those actions belong to recovery and policy workflows.
Teams should monitor accepted shortfall value, frequency, asset and network concentration, and changes after checkout releases. This shows whether the tolerance is reducing trivial work or masking a pricing, fee, or integration defect.
What matters in practice
Tolerance is an explicit rule allowing a shortfall up to a defined absolute amount or percentage without requesting a top-up. The unit matters: a 1% allowance on a $10 purchase and a $10,000 purchase produces very different losses. Price rounding, chain fees, token decimals and expired quotes can create small mismatches, but should be evaluated against the asset-network pair and rate version. Tolerance must be applied consistently and recorded for audit. A tolerance is not permission to accept arbitrary unsupported tokens or wrong-network deposits.
Related glossary concepts
Example
A 50 USDC invoice receives 49.98 USDC. If policy allows shortfalls up to 0.05 USDC, the merchant may accept it and record the 0.02 adjustment. If the shortfall is 2 USDC, the payment remains partial.
Comparison
Underpayment tolerance concerns acceptance rules; an underpayment rate measures frequency, and underpayment coverage can describe who bears the financial shortfall.
Key Takeaway
Underpayment tolerance is a precise automatic-acceptance threshold, not a substitute for the broader policy, recovery process, or accounting record.
Sources
- OxaPay API Reference: Generate Invoice — OxaPay (2026-08-01)
- OxaPay API Reference: Payment Status Table — OxaPay (2026-08-01)