Unfunded Liability is the core metric that drives payment platform risk controls and automated reserve logic. It represents the "worst-case scenario" loss the platform would be forced to absorb if a merchant went out of business, filed for bankruptcy, or abandoned their account while customers were still eligible to file disputes for previously processed transactions.
It is calculated based on a combination of factors:
- Total Processed Volume within the active Settlement Tail, representing all transactions still within the dispute window.
- Historical Reversal Rate: The merchant's average Refund Rate and dispute-to-sales ratio.
- Fulfillment Status: The volume of orders that have been paid for but not yet delivered (pre-orders or long lead times).
To manage unfunded liability, platforms implement Payout Holds and Rolling Reserves to ensure there is always enough collateral to cover potential reversals. The more evidence you provide of successful delivery and customer satisfaction, the lower the platform's calculated risk becomes, leading to faster payout cycles.
Related reading:
- Problem: Negative Cash Flow Risk
- Problem: Payout on Hold
- Glossary: Risk Confidence
Why this term matters for Stripe account risk
Unfunded Liability is not only a vocabulary item. It is a live risk signal that influences how Stripe evaluates dispute exposure, payout predictability, and verification confidence for your account. When this signal appears together with abnormal refund velocity, delivery uncertainty, or weak policy disclosures, account controls can become stricter. Treat Unfunded Liability as an operational metric that should be monitored, documented, and explained with evidence.
Diagnostic signals to review weekly
- Track trend direction, not just a single snapshot. A persistent rise is more important than one isolated spike.
- Compare this signal with fulfillment timing, support response speed, and billing clarity to identify root causes.
- Document the exact trigger conditions so your team can reproduce, audit, and resolve the issue consistently.
- Escalate early when this term appears alongside dispute-heavy reason codes or repeated verification requests.
Practical actions to improve confidence
- Define an internal threshold and owner for this signal so actions are not delayed.
- Link this signal to a checklist in your operations workflow (checkout, fulfillment, support, and evidence retention).
- Update website disclosures and receipts so customer expectations match real delivery and billing behavior.
- Keep a short incident log with timeline, root cause, and remediation to support future platform reviews.
Further reading
- Problem: Marketplace Liability Risk
- Problem: Account Takeover (ATO) Risk
- Guide: How to Structure Offers to Reduce Risk
- Hub: Fraud Signals and Risk Patterns
- Glossary Index: All glossary terms
Where This Appears
Unfunded Liability commonly appears in the following Stripe risk scenarios: