The exposure is delayed
Merchant acquiring enables card acceptance and settlement. The OCC’s Merchant Processing handbook treats this as distinct from issuing cards and discusses credit, operational, compliance and other risks. The August 2014 handbook is historical supervisory material, checked through its current official publication page; it is not a new rule. [1, 2]
Analysis: a merchant may receive settlement before goods are delivered or disputes are resolved. If customers later obtain refunds or and the merchant cannot reimburse the acquirer, the apparent processing business can become a credit loss. Exposure follows unresolved obligations, not just yesterday’s processed sales.
Three protections that should not be conflated
A rolling reserve retains part of settlement under the contract. A fixed funded reserve is a designated pool. A guarantee or indemnity is a promise whose value depends on enforceability and the counterparty’s ability to pay. Their legal treatment and access conditions differ; a spreadsheet total should not simply add them as equally liquid protection.
The OCC’s payment-processor guidance emphasizes understanding merchants and monitoring volume and information. The practical implication is to connect the reserve calculation to the underlying business, sales pattern and delivery cycle, rather than use the same percentage for every merchant. [3]
Worked example: a reserve that looks large
Hypothetical: an advance-sale merchant has $2 million of undelivered purchases. Assume a stress produces $600,000 of net valid customer claims after recoveries. A $200,000 funded reserve plus a $500,000 unsecured merchant guarantee is not $700,000 of certain protection. If the merchant fails and the guarantee recovers nothing, the immediate gap is $400,000.
Now assume a 10% rolling holdback on $100,000 of daily sales for 30 days. It accumulates $300,000 before releases, fees and other adjustments—not 10% of all historical exposure indefinitely. Once sales stop, replenishment stops too. The release schedule and remaining claim tail determine whether protection is still adequate.
A reserve decision should explain its assumptions
Analytical control map:
Scroll horizontally to see all columns.
| Input | Question | Consequence |
|---|---|---|
| Unfulfilled sales | What remains undelivered or cancelable? | Measures exposure beyond recent processing |
| Claim timing | When can valid disputes emerge? | Determines the reserve-release tail |
| Recoveries | Which funds are actually controlled? | Separates cash from unsecured promises |
| Concentration | Do merchants share a platform or supplier? | Tests correlated failure |
| Customer friction | Will holdbacks create distress? | Reassesses risk created by the protection itself |
Reserve tightening can change merchant behavior
Analysis: larger holdbacks can protect an acquirer but also reduce the merchant’s cash to complete orders. A poorly timed reserve increase can therefore worsen the non-delivery risk it was meant to cover. Consider staged restrictions, limits on advance sales and verified delivery milestones alongside collateral.
Monitor delivery delays, refunds, dispute aging, abrupt ticket-size changes and unusual sales acceleration. None alone proves fraud. Compare with seasonality and business changes, investigate the cluster and document the decision. A favorable ratio during rapid growth can lag the exposure embedded in unfulfilled sales.
Release cash only against understood residual risk
Recommended exit review reconstructs outstanding sales, pending claims and available funds after processing ends. Do not equate termination of the commercial relationship with termination of liability. Legal rights to hold or use money must be assessed from contracts and applicable law.
A reserve strategy is credible when assumptions reconcile to transaction data, stress outcomes are explicit and releases reflect the remaining tail. The analysis weakens when guarantees are counted at full value, customer claims are excluded merely because they are inconvenient, or the bank cannot obtain merchant-level records. This article proposes no universal reserve rate or network dispute deadline.
Sources
- 1. OCC, Merchant Processing handbook publication page; August 2014Official sourceBack to text: ↑
- 2. OCC, Merchant Processing handbook, current linked PDFOfficial source · PDFBack to text: ↑
- 3. OCC Bulletin 2008-12, payment processors risk management guidanceOfficial sourceBack to text: ↑