What does Acquirer Risk Steps and Reserve Survival conclude, in numbers, about “Reserves: Rolling Holdbacks, Settlement Freezes and the Minimum Buffer That Keeps Cash Flowing”?
Answer: Chapter 6 finds that a ten per cent reserve held ninety days needs a buffer of only 2,900, whereas a thirty-day freeze needs 93,000, and that even a buffer of 50,000 is used up in a share of 0.0175 of years.
Scope of the numbers: Parameters are illustrative; all calculations come from the book's programs. This is general risk analysis, not legal, financing or investment advice, and promises no income.
Data table
The numbers below are printed verbatim by the chapter's Python program and can be reproduced by running it. standard-library Python onlyprinted values that match the answer: 2900, 93000
| scenario | buffer | worst day | held peak |
|---|---|---|---|
| no measure | 0 | - | 0 |
| reserve 10% x 90d from day 1 | 2,900 | 32 | 28,500 |
| reserve 10% x 180d from day 1 | 2,900 | 32 | 42,000 |
| reserve 25% x 180d from day 1 | 13,500 | 90 | 105,000 |
| reserve 10% x 90d from day 45 | 0 | - | 25,500 |
| reserve 25% x 180d from day 45 | 4,600 | 90 | 97,500 |
| freeze 14d from day 45 | 43,400 | 58 | 0 |
| freeze 30d from day 45 | 93,000 | 74 | 0 |
| freeze 30d, spend cut day 47 | 59,400 | 74 | 0 |
Key formula
Show the full program
# Chapter 6. p61: the cash a shop must hold before a surge, by scenario.
# Daily takings: 1,000 on days 1-30, 4,000 on days 31-90 (a campaign),
# 1,500 on days 91-365. Settlement two days after the sale. Costs paid
# the same day: variable 0.65 of takings during the campaign (paid
# advertising, delivery) and 0.35 otherwise, plus a fixed 500 a day.
# Scenarios (the acquirer's measures are imposed, not chosen):
# rolling reserve r of each settlement, released T days later,
# either from day 1 or imposed on day 45; a payout freeze of 14 or 30
# days from day 45 (held payouts paid at the end of the freeze),
# with the campaign spend kept, or cut to the base share on day 47.
# Buffer = the largest fall of cash below its level on the eve of the
# measure (day 0 when there is no measure): the cash that must already
# sit aside, whatever profit came before, so that no bill goes unpaid.
# All amounts are illustrative units without currency.
import math
DAYS, LAG, FIXED = 365, 2, 500.0
def takings(t):
if t <= 30:
return 1000.0
if t <= 90:
return 4000.0
return 1500.0
def var_share(t, cut_day=None):
if 31 <= t <= 90 and (cut_day is None or t < cut_day):
return 0.65
return 0.35
def path(r=0.0, hold=0, r_from=1, frz_from=None, frz_len=0, cut=None):
cash, low, low_day = 0.0, 0.0, 0
event = frz_from or (r_from if r > 0 else 1)
eve = 0.0
release = {}
frozen = 0.0
held_peak, held = 0.0, 0.0
for t in range(1, DAYS + 1):
flows = [-FIXED, -var_share(t, cut) * takings(t)]
gross = takings(t - LAG) # days before 1 sold 1,000 a day
keep = r * gross if t >= r_from else 0.0
if keep:
release[t + hold] = release.get(t + hold, 0.0) + keep
held = held + keep
pay = gross - keep
if frz_from and frz_from <= t < frz_from + frz_len:
frozen = frozen + pay
else:
flows.append(pay)
if frz_from and t == frz_from + frz_len:
flows.append(frozen)
frozen = 0.0
if t in release:
flows.append(release[t])
held = held - release[t]
held_peak = max(held_peak, held)
if t == event:
eve = cash
cash = cash + math.fsum(flows)
if t >= event and cash - eve < low:
low, low_day = cash - eve, t
return 0.0 - low, low_day, held_peak
def main():
rows = [("no measure", {}),
("reserve 10% x 90d from day 1", dict(r=0.10, hold=90)),
("reserve 10% x 180d from day 1", dict(r=0.10, hold=180)),
("reserve 25% x 180d from day 1", dict(r=0.25, hold=180)),
("reserve 10% x 90d from day 45",
dict(r=0.10, hold=90, r_from=45)),
("reserve 25% x 180d from day 45",
dict(r=0.25, hold=180, r_from=45)),
("freeze 14d from day 45", dict(frz_from=45, frz_len=14)),
("freeze 30d from day 45", dict(frz_from=45, frz_len=30)),
("freeze 30d, spend cut day 47",
dict(frz_from=45, frz_len=30, cut=47))]
print("scenario buffer worst day held peak")
for name, kw in rows:
need, day, peak = path(**kw)
print("{:<32} {:>8,.0f} {:>5} {:>9,.0f}".format(
name, need, day if day else "-", peak))
if __name__ == "__main__":
main()Single source and citation
Fan, Y. (2026). Payment-Acquirer Risk Step-Functions, Multi-Gateway Hot Failover and Rolling-Reserve Survival for Digital Fleets (Version 1.0.0), Chapter 6: Reserves: Rolling Holdbacks, Settlement Freezes and the Minimum Buffer That Keeps Cash Flowing. 5D Library. DOI pending
DOI pending · monograph page goes live after publication · 5DL-B-397 · v1.0.0 · CC-BY-NC-ND-4.0
BibTeX
@book{fan2026397,
author = {Fan, Yafu},
title = {Payment-Acquirer Risk Step-Functions, Multi-Gateway Hot Failover and Rolling-Reserve Survival for Digital Fleets},
year = {2026},
publisher = {5D Library},
edition = {1.0.0},
note = {DOI pending}
}Other chapter answers in this book
- Chapter 1 · Steps: Noise in the Chargeback Ratio, the Beta Posterior and Card-Network Definitions
- Chapter 2 · Lag: Cohort Measures, Arrival-Date Measures and Underestimation During Surges
- Chapter 3 · Jumps: Cumulative Sums, Exponentially Weighted Averages and Bayesian Online Change Points
- Chapter 4 · Refunds: The Optimal Interception Threshold Before a Dispute
- Chapter 5 · Hot Failover: Common-Cause Failure, Timeout Budgets and Idempotency
- Chapter 7 · Reading the Classics: Peace and Peril in the Zuo Zhuan, Forethought in the Doctrine of the Mean, Joseph's Granaries and Bagehot's Reserve
- Chapter 8 · The Empirical Loop: the Acquirer-Risk Ledger, Field Tools and Checker Specifications