This is the decision record as it was written, grilled and shipped. It’s copied from our repository unedited, apart from customer, partner and bank names, which read [redacted]. It was written for the people and agents building the product, so expect internal shorthand, and the mistakes are left in.
ADR-843: Cards and Authorisation: the rolling reserve and the acquiring side of chargebacks
Status: Shipped — 2026-10-04
Context
The Problem
An acquirer pays a merchant for sales the cardholder can still dispute for months. When a chargeback arrives the scheme takes the money back from the acquirer at once; if the merchant has been paid and has nothing left, the acquirer carries the loss. So every acquirer holds back part of what it owes: a rolling reserve (a percentage of each day’s sales, released after a fixed period) or a fixed reserve (a sum built up to a target and held for the life of the agreement), stepped up when a merchant’s dispute ratio climbs toward the schemes’ monitoring thresholds. And every acquirer runs the other side of the dispute the issuer raised (ADR-840): the chargeback lands in the feed, the merchant is debited with a fee, the merchant’s evidence is represented, and the money comes back if the merchant wins.
ADR-842 left both open: a Chargeback line is an exception on the batch, and the agreement
has no reserve. The proposal names the mistake to avoid: a reserve held as one balance cannot
be released per day or consumed oldest-first, so the merchant’s statement stops reconciling
after the first chargeback.
What Already Exists
- Reductions on available balance (ADR-836): another feature holds money on an account by
implementing
IAvailableBalanceReductionsReaderover its own documents; Accounts sums every implementation wherever it projects available balance. Card holds are the first holder. - Claims (ADR-251): the account’s own dated holds — instructions, notices, uncleared funds, ADR-842’s T+n holds — raised and released by Accounts.
- The merchant agreement, the feed and the settlement account (ADR-842): terms dated on the agreement, the net of each sale held to T+n by a claim, payout by the step at 55.
- The issuer’s dispute (ADR-840): the scheme’s stages, the reason-code vocabulary with its category and windows, in Cards.
- The price card (ADR-841): a chargeback fee is one more price row.
Scope
This ADR covers:
- The rolling reserve and the fixed reserve as rules on the agreement’s terms, each held as reserve days on Acquiring’s own documents and reported to Accounts as a reduction on the settlement account’s available balance, the second holder of ADR-836’s mechanism.
- The acquiring chargeback: an aggregate per chargeback opened by the feed, the debit and the fee, the reserve consumed oldest-first when the free balance cannot bear it, the bank’s representment recorded, the clocks, and the reversal when the merchant wins.
- Dispute monitoring: a merchant’s monthly chargeback ratio and count, and a reserve stepped up by rule when either crosses the agreement’s threshold.
Out of scope: an on-us short cut when the issuer and the acquirer are the same tenant (the two sides stay two aggregates linked by the scheme case reference, the scheme the arbiter, as ADR-840 decided); submitting the representment through the processor’s API (the clerk submits it in the processor’s portal and records it here; the API is the adapter’s when a processor is named); retrieval requests; fraud reporting to the schemes (TC40, SAFE); stepping a reserve down by rule (a clerk amends the terms); collecting a merchant’s debt beyond its settlement account (collections, as any owing balance).
Decisions
1. The reserve joins the reductions another feature already places on available balance
ADR-836 gave the platform one mechanism for money held on an account by something outside it:
IAvailableBalanceReductionsReader. A feature implements it over its own documents; Accounts
injects every implementation, sums them, and subtracts the sum wherever it projects available
balance — a withdrawal’s guard, a payout’s guard, the account detail, the availability reader.
ADR-836’s card holds were the first holder and the reader was named for the concept so that a
second would join. The reserve is the second.
Acquiring keeps the reserve on its own documents, one MerchantReserveDay per settlement
account, business date and increment (…-{date}-{n}, n counted by the agreement, its single
writer): the amount withheld, the amount consumed and by which chargeback, the release date or
the release rule, and whether it has been released. Acquiring’s reader reports, per account,
the reserve days withheld and not yet consumed or released. Accounts learns nothing new: no
claim seam, no new claim origin, no new account event. Withholding, consuming and releasing are
Acquiring’s own facts on the agreement’s stream, replayable there, and the account’s available
balance moves because the reader’s figure moves.
Two words, kept apart everywhere: a reserve day consumed has paid a debt and its money is gone; a reserve day released has returned its money to the available balance.
2. The reserve is a rule on the terms, withheld as the day’s holds release
The agreement’s dated terms gain a reserve rule: None, Rolling (a percentage of each
settlement day’s gross sales, held for a number of calendar days counted from the day it is
withheld, a weekend release date standing) or Fixed (a percentage of each day’s gross sales
until the reserve outstanding in that settlement currency reaches the currency’s target — the
day that crosses it withholds only the remainder, and withholding resumes when a chargeback
consumes part of it — held until a number of days after the agreement terminates; a fixed rule
names a target for every settlement currency, or it is refused). The basis is gross sales — the
schemes’ and acquirers’ measure of processing volume — not the net. An agreement with a reserve
rule has a settlement delay of at least one business day; a T+0 merchant would be paid before
any reserve could be withheld. Amounts round half-up to the currency’s minor unit.
The reserve is withheld when the day’s money becomes payable. A day-end runs in this order:
the account walk releases the day’s T+n holds (30); ReleaseMerchantReserveStep (49,
PreIncrement) releases the reserve days due; ReserveMerchantSettlementStep (50, PreIncrement)
withholds; the feed’s post step posts the
day’s sales and chargebacks (54); the payout step, opening the next trading day (55,
PostIncrement), pays what is left. The reserve step finds, for each settlement account, every
business date whose T+n release date has come and whose gross is not yet fully reserved, and —
where the terms in force on that business date carry a rule, whatever the agreement’s status
since — withholds the rule’s percentage of the unreserved gross, capped at the account’s
available balance: nothing is withheld from money that is not free now, so a reserve day and a
T+n hold never hold the same money. What the cap leaves unwithheld stays unreserved and is
withheld on a later run when money is free; the agreement records the shortfall while it stands.
The payout step pays nothing from an account with a business date released and not yet
reserved, so a failed reserve step never lets a payout carry the reserve away.
A rolling day releases in the reserve step on its date. A fixed day releases on the day the given number of days after termination arrives; a fixed rule stops withholding at termination. The terms in force on the business date decide whether and how much, so a stepped-up reserve applies to sales from its date, never re-reserves the past, and a rule changed later leaves existing days on their own terms.
Ruled at the plan grill. The reserve is tracked in money per settlement account and business
date, never in gross: each date’s required reserve is the rule’s rate times its gross, rounded
half-up once, so no cent of gross is ever left over. A date is settled when its withheld amount
reaches the required amount, when a fixed rule’s target caps it, or when a fixed rule’s
agreement has terminated; the payout waits only for released dates not yet settled. Under a
fixed rule, a chargeback that consumes the reserve reopens withholding only for dates released
after it. Releasing is wind-down, so it runs in its own step at 49 with no feature key (ADR-363
D3); withholding stays behind cards.acquiring at 50. The withholding step reads each account’s
availability once and lowers a running cap with each withholding. A fixed reserve day carries
its own release period, so amending the rule later never moves it. The rule’s rate is a
fraction, and its periods name calendar days. A step-up rule is validated when the terms are
amended, exactly as the reserve rule is.
Ruled at phase B. Withholding is wind-down too. Gating it while the payout waits for it would
strand every reserve-ruled merchant the moment acquiring is switched off. It only reserves sales
already posted, under the agreement’s own terms, and the feed steps stay gated, so nothing new
arrives. Both reserve steps run ungated; only the feed steps and monitoring stay behind
cards.acquiring. Gross is the day’s sale lines in the settlement currency; a refund does not
lower it. A fixed rule’s date released after termination settles, withholding nothing. A
release date’s money is released in the day-end that closes that date. A rule mixing the two
kinds’ settings, a target of zero or less, two targets in one currency, a target in a currency
the agreement does not settle in, or a step-up threshold out of range is refused; a zero delay
is reported before an invalid rule. Adding a settlement currency is checked against every terms
row in force from its date. The reserve read shows each live shortfall, and each day’s kind and,
for a fixed day after termination, its release date.
3. A chargeback is an aggregate of its own, opened by the feed
MerchantChargeback lives in LedgerTM.Acquiring, one per scheme case, its id derived from
the connection and the case reference — a chargeback line without a case reference is an
exception on the batch, CASE_REFERENCE_MISSING: the agreement, the settlement account (the
line’s settlement currency’s), the original sale’s processor reference, the amount and
currency, the scheme reason code (the line carries the scheme’s code, resolved to ADR-840’s
CardDisputeReasonCodeId through a Contracts reader Cards implements, so the windows are one
set; an unknown code is noted REASON_CODE_UNKNOWN and runs on thirty-day windows), the stage
(Received, Represented, Reversed, PreArbitration, Closed), the outcome (Won,
Lost), the due date of the acquirer’s next move or the date the scheme’s is expected, the
evidence the bank recorded, and the money posted. ADR-842’s feed line gains the reason code,
the original sale’s processor reference and, on a final line, the outcome.
Money moves only on the scheme’s lines, and each line posts its own amount once (ADR-842’s line
id). A first Chargeback line opens the case and, in one dispatch,
ProcessMerchantChargebackCommand posts the debit (MerchantChargeback) and the price card’s
chargeback-fee, trading-dated the run date and value-dated the batch’s business date, priced
there with the bag attribute stage: first; every later Chargeback line on the case is the
issuer’s pre-arbitration, debiting again with stage: pre-arbitration (the template waives that
fee) and moving the case to PreArbitration. A ChargebackReversal line moves the case to
Reversed and posts MerchantChargebackReversed for its amount, which may be part of what was
charged back but never more (REVERSAL_EXCEEDS_CHARGEBACK); the fee stands. A
ChargebackFinal line closes the case Won or Lost and moves no money, since the money has
already moved. A reversal or final line naming no case is CASE_UNKNOWN, re-scanned until its
case arrives. The bank may accept a received, represented or pre-arbitration case for the
merchant, closing it Lost; a reversed case is the merchant’s win and cannot be accepted. A
money line on a closed case posts, reopens the case at the line’s stage and is noted
CASE_REOPENED; an agreement does not close while it has an open case. ADR-842’s
CHARGEBACK_NOT_HANDLED lines are non-terminal, so the re-scan posts them once this lands.
Ruled at the plan grill. The case id includes the scheme, since two schemes’ case numbers can
collide on one connection. A chargeback line’s transaction date is the original sale’s date,
which is what routes it to an agreement. The case’s checks run before the Accounts post, so a
refused reversal never credits the merchant. A chargeback line is the first stage when no
other chargeback line is recorded on the case, never by whether the case exists, so a retry
after a half-failed post stays the first stage and keeps its fee. The reversal cap compares
transaction-currency amounts and posts the settlement amount, because a cross-currency reversal
can settle above the original at a different rate. A chargeback routed to a closed agreement
opens its case with no money, is excepted CHARGEBACK_AGREEMENT_CLOSED, and raises a follow-up
task: recovering that money is the bank’s, outside the ledger, and the task makes it visible.
The case holds ADR-840’s typed reason-code id, and the outcome type is named for the merchant’s
view (MerchantChargebackOutcome). The chargeback fee is a taxable fee row, as every merchant
charge is under ADR-842 D4; the worked example shows it net of VAT.
Ruled at phase B. A batch posts its sales and refunds first, then its chargeback lines one at a time in file order, so the day’s sales bear its chargebacks. The scheme is lower-cased in the case id. The reversal cap is cumulative, against everything charged back on the case, pre-arbitration included. A chargeback line on a closed case reopens it at pre-arbitration, with no fee. A line with no case reference is terminal; an unknown reason code is a note on the line; a final line records posted with no money. “Received” is the business date of the line that opened the case. The case names, for each consumption, the reserve day it consumed, and keeps the scheme’s raw reason code beside the typed one.
4. The free balance bears a chargeback first, then the reserve, oldest first
After each chargeback posts — the post step takes an account’s lines in their file order, one
at a time — it measures the free balance: the available balance with the T+n holds added
back, since sales not yet payable are still the merchant’s money and bear a chargeback first. If
the free balance is below zero it consumes the account’s reserve days oldest business date first
by the shortfall until the shortfall is covered or the reserve is spent, recording each on the
chargeback and on the day. Consumption is the agreement’s own event, keyed by the chargeback’s
line and the reserve day, so a redelivered post consumes nothing twice. A shortfall the reserve
cannot cover leaves Current below zero: the merchant owes the acquirer, later sales repay it,
and the account’s balance shows the debt. Consuming a reserve day moves no money — the reserve
was always the merchant’s money in Current, held — it lifts the reduction so the balance nets,
which is why the statement still reconciles: every reserve day shows what it withheld, what a
chargeback consumed and what it released. A reversal returns its amount to Current; it never
re-creates a consumed reserve. A debt shown on Merchant payable as a debit balance is presented
as a receivable by the reporting layer, not reclassified here.
GL: MerchantChargeback Dr Merchant payable / Cr Scheme settlement receivable (the scheme
takes it back from settlement); MerchantChargebackReversed the reverse;
ChargebackFeeCharged Dr Merchant payable / Cr Acquiring fee income. The reserve itself
posts nothing: it is a hold on money already in Current.
Ruled at the plan grill. Each chargeback line is its own unit of work, posted one at a time in file order, so the second chargeback on an account reads the free balance after the first one’s consumption has committed. Consumption is keyed by the line’s transaction id and the reserve day. A refund or a fee that takes the balance below zero consumes nothing: the reserve answers chargebacks, as the schemes intend, and the debt waits for later sales, the next chargeback, or the reserve’s own release.
5. Representment is recorded, and the clocks are watched, as the issuer’s are
The bank records a representment — the merchant’s evidence (an attachment, ADR-840 D7’s
AttachmentId), a description, the date submitted in the processor’s portal, which may not be
in the future or before the case was received — moving the case to Represented. A Received
case is the acquirer’s move, due the code’s representment window in calendar days after the
line’s business date; a PreArbitration case is due the code’s pre-arbitration window after
its line’s business date; a due date on a Sunday stands, as the schemes count it. A
Represented or Reversed case is the scheme’s, expected by the code’s response window after
the representment. MerchantChargebackDeadlinesStep (56, PostIncrement, non-critical, no
feature key) raises one follow-up task per due date to the acquiring disputes group when
the acquirer’s own window is within the tenant’s warning days, and marks the case overdue the
day after that due date; a case awaiting the scheme past its expected date reads awaiting
scheme and is never overdue. The step never closes a case: as on the issuer’s side, only the
scheme’s word does, through the feed or the bank’s own acceptance.
Ruled at the plan grill. A representment may be dated on the day the case was received. Overdue clears when the case moves to its next stage. Recording a representment is not four-eyes: it records a submission already made in the processor’s portal, and a pending checker would let the case run overdue. Accepting a case for the merchant stays four-eyes, since it gives up the merchant’s money. The deadline step carries no feature key, because watching an open case is wind-down.
Ruled at phase B. The deadline step judges the trading day being opened, as the issuer’s step does. Accepting a reversed or closed case is refused when the clerk submits it, before any approval is captured. The accept’s reason is recorded on the closing event, so the auditor sees why the bank gave up the merchant’s money; the closer is the maker. A reversed case never represented awaits the scheme’s final word, expected the response window after the reversal. The acquirer’s due date clears while the case is the scheme’s move.
6. Dispute monitoring steps the reserve up by rule
MonitorMerchantDisputesStep (57, PostIncrement, non-critical, cards.acquiring) records each
completed month once, on the first run whose date falls in a later month, so a month is never
skipped whichever days day-end runs. For each agreement and each scheme it counts the month’s
sales and chargebacks by their batches’ business dates — counts, not values, as the programmes
measure — and records the ratios (MerchantDisputeRatioRecorded); a month with chargebacks and
no sales reads as over any ratio. Where the agreement’s terms carry a step-up rule (a ratio
threshold, a count threshold, a stepped reserve rule) and any one scheme meets both thresholds —
the Visa and Mastercard monitoring programmes’ shape, a ratio near 0.9% and a count near 100 —
it amends the terms from that day to the stepped rule (MerchantReserveSteppedUp, a system
amendment carrying the scheme and the counts that triggered it), unless the rule in force
already withholds at least the stepped percentage for at least the stepped period. The approved
terms carry the rule, so carrying it out needs no second approval; stepping back down is a
clerk’s dated amendment, four-eyes as every clerk’s amendment is.
Ruled at the plan grill. A month is a date on its first day. A month with chargebacks and no sales records no ratio and counts as over any ratio threshold. The agreement read carries each month’s ratios per scheme and every step-up with the counts that triggered it.
Ruled at phase B. The step judges the trading day being opened, and the stepped terms run from that day. Chargebacks count by the business date of the batch that opened the case; a month is recorded once, and a later batch for it is not re-counted, as the programmes count what was processed in the month. Ratios round half-up to six places. The stepped row keeps its step-up rule. A rule in force is as strict as the stepped one only if it is the same kind and at least as strict on every measure. Only active and suspended agreements are monitored, each in its own unit of work. The step-up is the system’s own verb on the agreement, never the clerk’s amendment, so no second approval is captured; it records the month that triggered it.
7. Permissions, four-eyes and the screens
Recording a representment and accepting a chargeback are user commands on the chargeback.
Accepting is four-eyes eligible and reviewable (MerchantChargebackApproverViewReader,
SelfHoldingAggregate); recording a representment is not (D5); amending the reserve rule is AmendMerchantAgreementTerms (ADR-842).
The postings, the steps and the step-up are system commands. The screens:
the agreement viewer gains a Reserve panel (each reserve day, withheld, consumed, released,
outstanding) and a Chargebacks panel (cases with stage, due date and money), each case has a
viewer, and the monthly ratio shows beside the terms.
Contracts
Ids — MerchantChargebackId, MerchantReserveDayId (LedgerTM.Contracts/Acquiring).
Commands — ProcessMerchantChargebackCommand, ProcessMerchantChargebackReversalCommand
(LedgerTM.Contracts/Accounts, ISystemCommand); RecordMerchantRepresentmentCommand,
AcceptMerchantChargebackCommand (LedgerTM.Acquiring, ICommand);
ReleaseMerchantReserveCommand, ReserveMerchantSettlementCommand,
PostMerchantChargebackLineCommand, WatchMerchantChargebackDeadlinesCommand,
MonitorMerchantDisputesCommand (the steps’, ISystemCommand); RequestMerchantChargebackFollowUpTaskCommand
(LedgerTM.Contracts/Tasks, ISystemCommand).
Events — on the agreement: MerchantSalesPostedForDate, MerchantReserveWithheld,
MerchantReserveDateSettled, MerchantReserveShortfallRecorded, MerchantReserveConsumed,
MerchantReserveReleased,
MerchantDisputeRatioRecorded, MerchantReserveSteppedUp; on the chargeback:
MerchantChargebackReceived, MerchantChargebackMoneyRecorded, MerchantChargebackRepresented,
MerchantChargebackReserveConsumed, MerchantChargebackOverdue, MerchantChargebackReopened,
MerchantChargebackClosed.
Queries — GetMerchantChargebackQuery, ListMerchantChargebacksQuery,
GetMerchantReserveQuery (IQuery<T>).
Consumed from LedgerTM.Contracts — IAvailableBalanceReductionsReader (ADR-836; Acquiring
implements a second one), IAccountAvailabilityReader (ADR-836, changed: gains the uncleared
funds held), PriceContext (ADR-841), ICardDisputeReasonCodeReader (new, Cards implements),
the feed and agreement contracts (ADR-842).
Changed — AcquiringFeedLine gains ReasonCode, OriginalProcessorReference and
ChargebackOutcome (a new MerchantChargebackOutcome, Won or Lost in the merchant’s view, on a
final line); AttachmentId moves to LedgerTM.Contracts (ADR-840 bite 1
does it; this ADR lands after); AccountAvailability gains UnclearedFunds;
AcquiringFeedLineKind gains ChargebackFinal;
MerchantAgreementTerms gains Reserve and StepUp; ExternalIntegrations and
TransactionSource gain MerchantChargeback and MerchantChargebackReversal.
Added beside them — ReserveKind, ReserveRule, ReserveTarget, StepUpRule (LedgerTM.Contracts/Acquiring, the terms’ reserve and step-up), MerchantChargebackStage (the case’s stage), CardDisputeReasonCodeView (what ICardDisputeReasonCodeReader answers); AcquiringFeedOutcomes gains CASE_REFERENCE_MISSING, CASE_UNKNOWN, REVERSAL_EXCEEDS_CHARGEBACK, CHARGEBACK_AGREEMENT_CLOSED and the notes CASE_REOPENED, REASON_CODE_UNKNOWN. ProcessMerchantPayoutCommand is untouched; the chargeback commands are appended after it in the same file.
Removed — none.
Prior art
| Declared | Search returned | Verdict |
|---|---|---|
MerchantReserveDay, MerchantReserveDayId, Acquiring’s IAvailableBalanceReductionsReader |
IAvailableBalanceReductionsReader and CardHold (ADR-836), Claim (ADR-251) |
reuse — the second holder of ADR-836’s reductions, as that ADR named it for; an account claim seam was drafted and dropped at phase A as a second mechanism answering the same question |
the reserve rule on MerchantAgreementTerms |
Collateral (ADR-027, ADR-423), the notice claim (ADR-251) |
genuinely new — collateral is a loan security with a one-shot release, the wrong shape; the reserve is reserve days |
MerchantChargeback, MerchantChargebackId |
CardDispute (ADR-840, the issuer’s side) |
genuinely new beside it — the acquirer’s mirror on its own aggregate, linked by the case reference as ADR-840 decided |
ICardDisputeReasonCodeReader |
CardDisputeReasonCodeSettings (ADR-840, in Cards) |
extend — one vocabulary read across features, so the windows never drift |
ProcessMerchantChargebackCommand, ProcessMerchantChargebackReversalCommand |
ProcessMerchantSaleCommand, ProcessMerchantRefundCommand (ADR-842) |
extend — the same shape |
ReleaseMerchantReserveStep, ReserveMerchantSettlementStep, MerchantChargebackDeadlinesStep, MonitorMerchantDisputesStep, their commands (ReserveMerchantSettlementCommand, ReleaseMerchantReserveCommand), PostMerchantChargebackLineCommand |
MerchantPayoutStep (ADR-842), CardDisputeDeadlinesStep (ADR-840) |
extend — steps in the same shape |
RequestMerchantChargebackFollowUpTaskCommand |
RequestCardDisputeFollowUpTaskCommand (ADR-840) |
extend — the same task shape |
RecordMerchantRepresentmentCommand, AcceptMerchantChargebackCommand |
RecordCardDisputeEvidenceCommand, ConcedeCardDisputeCommand (ADR-840) |
extend — the acquirer’s verbs |
MerchantSalesPostedForDate, MerchantReserveDateSettled, MerchantReserveShortfallRecorded … MerchantChargebackClosed, MerchantChargebackOutcome, GetMerchantChargebackQuery, ListMerchantChargebacksQuery, GetMerchantReserveQuery |
ADR-842’s agreement events and reads | genuinely new — the reserve’s and the chargeback’s own facts and reads |
MerchantChargebackReceived, MerchantChargebackMoneyRecorded, MerchantChargebackRepresented, MerchantChargebackReserveConsumed, MerchantChargebackOverdue, MerchantChargebackReopened, WatchMerchantChargebackDeadlinesCommand |
RequestMerchantChargebackFollowUpTaskCommand, MerchantChargebackStage, MerchantChargebackOutcome (this ADR’s own contracts) |
genuinely new — the chargeback’s own facts and its deadline step’s command; the names the search returns are this ADR’s siblings, not prior art |
AcquiringFeedOutcomes, ProcessMerchantPayoutCommand |
ADR-842’s feed outcomes and payout command | reuse — the outcomes gain the chargeback codes; the payout command is unchanged, named only because the chargeback commands sit after it |
chargeback-fee |
card-dispute-fee (ADR-840) |
extend — a price row |
IAccountAvailabilityReader, AccountAvailability, PriceContext, AttachmentId (moved by ADR-840), AcquiringFeedLineKind, MerchantAgreementTerms, ExternalIntegrations, TransactionSource |
the seams as they are | reuse — read or extended by a member |
Relies on
| Symbol | What it does today | What this ADR assumes |
|---|---|---|
AvailableBalance.Project |
Ledger less every Reduce claim, and with ADR-836 less the summed reductions | The reserve reduces available through the reductions (D1) |
SelfHoldingAggregate |
An aggregate holding its own change set (ADR-780) | The chargeback is one (D7) |
IDayEndStep |
A step with an order, a phase and a criticality | The three steps (D2, D5, D6) |
ADR-842’s agreement, terms, feed, post step, settlement account and payout step, ADR-840’s reason codes and ADR-841’s price card are relied on as their plans declare them.
Worked example
Fixture: ADR-842’s Boutique Bleu, its ZAR settlement account and interchange++ terms,
amended to a rolling reserve of 5% for 180 days; chargeback-fee 150.00; Visa 13.1’s
acquirer representment window 30 days.
| Date | Event | Account | Current | Available |
|---|---|---|---|---|
| Mon 2026-10-05 | a 1 000.00 sale made Sat 10-03: charges, net of VAT as in ADR-842’s example, 3.00 + 0.50 + 0.06 + 5.00 + 0.10 = 8.66 | net 991.34 held to Wed | 991.34 | 0.00 |
| Wed 10-07 | the hold releases in the walk; the reserve step withholds 5% of the day’s 1 000.00 gross | reserve day 50.00, releasing Mon 2027-04-05 | 991.34 | 941.34 |
| Thu 10-08 | the payout step instructs 941.34; it settles Fri | — | 50.00 (Fri) | 0.00 |
| Fri 12-04 | a chargeback of 30.00 (the fee shown net of VAT) on the sale, reason Visa 13.1, case VC-7731 |
MerchantChargeback 30.00; ChargebackFeeCharged 150.00; the free balance is −180.00, so the reserve day of 10-07 is consumed, all 50.00 |
−130.00 | −130.00 |
| Fri 12-11 | the clerk records the merchant’s proof of delivery; it was due Sun 2027-01-03 | the case moves to Represented, the scheme’s move expected by Sun 2027-01-10 |
−130.00 | −130.00 |
| Fri 2027-01-15 | a ChargebackReversal for VC-7731 |
MerchantChargebackReversed 30.00; the case moves to Reversed; the fee stands |
−100.00 | −100.00 |
| Mon 2027-03-01 | a ChargebackFinal for VC-7731, won |
the case closes Won; no money moves |
−100.00 | −100.00 |
The merchant owes 100.00, which the next sales repay; the reserve panel shows the 10-05 day,
withheld on 10-07, at 50.00, consumed 50.00 on 12-04, released nothing. Had the reserve been 200.00, Current
after the payout would have been 200.00; the chargeback and fee would take it to 20.00, the free
balance to −180.00, and 180.00 of the reserve would be consumed, leaving Current 20.00 with
20.00 still held.
Model
Generated from docs/model/model.json (ADR-773 D8): the shape the model knows today, <<new>> for what
## Contracts declares and the model does not know, relies-on for ## Relies on. Regenerate with
python3 scripts/model/adr_model.py ADR-NNN --write; frozen at Shipped.
classDiagram
class ChargebackFinal {
<<new>>
}
class ChargebackOutcome {
<<new>>
}
class Lost {
<<new>>
}
class MerchantChargebackReversal {
<<new>>
}
class OriginalProcessorReference {
<<new>>
}
class ReasonCode {
<<new>>
}
class Reserve {
<<new>>
}
class StepUp {
<<new>>
}
class UnclearedFunds {
<<new>>
}
class Won {
<<new>>
}
class AvailableBalance {
<<relies-on>>
}
class IDayEndStep {
<<relies-on>>
}
class SelfHoldingAggregate {
<<relies-on>>
}
Consequences
Positive
- The reserve reconciles per day, because it is reserve days: withheld, consumed oldest-first, released on its date, each a fact on the stream.
- One mechanism, a second holder: the reserve joins ADR-836’s reductions, as card holds did; Accounts changes by one figure on its availability read.
- The merchant’s side of a dispute runs in the ledger, with the issuer’s vocabulary and clocks, so “show me day one and day sixty” is a replay on either side.
- A step-up is a rule, dated and auditable, not a risk officer’s spreadsheet.
Negative / Trade-offs
- The representment is submitted outside, in the processor’s portal; the ledger records it.
- A merchant’s debt beyond its reserve is a negative balance the next sales repay; recovery beyond that is collections’.
- Withholding at release means the reserve for a day appears T+n days after the sale; the statement says so.
Neutral
- An issuer that also acquires sees the same scheme case on two aggregates, linked by the case reference, as ADR-840 decided.
Implementation Plan (Bites)
Six bites, one land; reseed: true. Every bite starts after ADR-842 lands, and after ADR-840
for the reason codes and AttachmentId.
Bites, acceptance criteria, files touched, and status live in ADR-843-plan.md.
Changed during the grill
Grilled 2026-10-02 by the author against ADR-251, ADR-840, ADR-842 and the press; the operator’s standing instruction was to take the recommendations.
- Decision 4 — the free balance ignores the T+n holds. Measuring the available balance would have consumed the reserve while sales not yet payable still covered the chargeback.
- Decision 2 — the withheld amount is capped at the free balance, a late line reserves its own gross only, the claim id carries the gross reserved so far, and a reserve needs a delay of at least one business day. The day-end order is stated: release, withhold, post, pay next day.
- Decision 3 — a reversal is
Reversed, not won; a second chargeback on the case is the issuer’s pre-arbitration;ChargebackFinalcarries the outcome and closes the case. A money line on a closed case reopens it. A chargeback without a case reference is an exception. - Decision 5 — whose move: the acquirer’s windows are watched and go overdue; the scheme’s are shown as expected and never go overdue. Calendar days, a Sunday standing.
- Decision 6 — per scheme, by count, and no step-up when the rule in force is already stricter; carrying out an approved rule needs no second approval.
- Decision 1 — consumed and released are two words for two facts.
- Decision 2 — the fixed target is per currency, capped on the crossing day, resumed after consumption, withholding stopping at termination.
- Example — the 200.00 counterfactual corrected; the reversal no longer closes the case; the due and expected dates shown.
Contradiction press: 20 pairs, resolved as above — 1, 10, 12 into Decision 2’s day-end order; 2, 3 into the example and Decision 1; 4, 5, 6 into Decision 5; 7, 8 into Decision 3; 9 into Decision 4; 11, 13, 14, 15, 16, 17 into Decision 2; 18 into Decision 4 (oldest business date first; ADR-251’s unbacked order marks the T+n holds first); 19, 20 into Decision 6. The silent inputs are answered in Decisions 1 to 6.
Press block
- The payout’s day. 2. The 200.00 counterfactual. 3. “Released” meaning two things. 4. The due date after representment. 5. Overdue while the issuer owes the move. 6. Whose windows the vocabulary holds. 7. Pre-arbitration after a won representment. 8. A line on a closed case.
- What D4’s trigger measures. 10. Free balance against tonight’s release. 11. The gross basis against the money there. 12. A zero-day delay. 13. A late line re-reserving the date.
- Redelivery against the suffix. 15. Which date’s terms gate the step. 16. One target, several accounts. 17. Fixed claims after termination. 18. Claim order. 19. Four-eyes on the step-up. 20. Per scheme or combined.
Phase A (acceptance-test author, 23 questions), 2026-10-02. The rulings that changed a decision:
- Decision 1 — the reserve joins ADR-836’s reductions; the claim seam is dropped. ADR-836 already gives another feature a hold on available balance, named so a second holder joins. The draft’s claim seam was a second mechanism answering the same question, and it opened four money holes the reductions avoid: an unkeyed reduce consuming twice, any feature reducing any claim, a raise silently overwriting, and nobody recording a rolling release.
- Decision 2 — the cap is the available balance, so a reserve day and a T+n hold never hold the same money; a shortfall stays unreserved and is withheld later; the payout pays nothing from an account with a released date not yet reserved; rolling reserves follow the business date’s terms through termination; a fixed rule names a target per currency.
- Decision 3 — later chargebacks on a case are pre-arbitration; a reversal is capped at the
charge; a reversal or final with no case waits as
CASE_UNKNOWN; a reversed case cannot be accepted; the feed line carries the reason code and the original sale. The fee is priced at the batch’s business date. - Decision 4 — the free balance is the available with the T+n holds added back, read from the availability reader’s new uncleared-funds figure; consumption is keyed by line and day.
- Decision 5 — pre-arbitration runs on its own window; one task per due date.
- Decision 6 — each month once, on the first run after it, and no sales with chargebacks reads as over.
- Filed for the coordinator, pre-existing: the account detail never applies
ClaimMarkedUnbacked, so ADR-251 D7’s unbacked state is invisible there.
Changed during the plan grill
An Opus plan grill pressed every signature on 2026-10-02 and returned 29 points; all were taken on its recommendations, the operator’s standing instruction. The ones that changed a decision:
- Decision 2 — the reserve is tracked in money per date, so rounding, a fixed target and termination can no longer block a payout for good; release is ungated and runs before withholding; a fixed day carries its own release period.
- Decision 3 — the case id names the scheme; checks run before money moves; a retry stays the first stage; the reversal cap is in the transaction currency; a chargeback on a closed agreement raises a task; the reason code is typed; the outcome is the merchant’s view; the fee carries VAT.
- Decision 4 — each chargeback line is its own unit of work, so two chargebacks in one feed never consume the same reserve twice; refunds and fees consume nothing, deliberately.
- Decision 5 — recording a representment is not four-eyes; the deadline watch is ungated.
- Decision 6 — a month with chargebacks and no sales has no ratio and counts as over; the ratios and step-ups are read on the agreement.
- Names frozen differently —
MerchantChargebackOutcome,MerchantReserveShortfallRecorded,Rate,HoldCalendarDays,ReleaseCalendarDaysAfterTermination, and the derived permission keys in place of the hand-chosen ones. - Pressed and held — reductions on a liability account, the payout’s guard, uncleared funds against unbacked claims, reserve-day ids on replay, the account detail’s freshness, the step orders, the GL legs, raw scheme codes on the feed line, and the worked example’s arithmetic.
Changed during phase B
Six acceptance-test authors wrote the cold tests on 2026-10-02 (docs/adr/ADR-843-tests/).
Their findings, folded as the “Ruled at phase B” paragraphs of Decisions 2, 3, 5 and 6:
- Decision 2 — withholding is ungated. The plan grill gated it; the bite-2 author showed that stranded every reserve-ruled payout when acquiring was switched off.
- Decision 2 — the rule’s validation is complete, and the reserve read shows shortfalls and fixed days’ release dates.
- Decision 3 — a batch’s sales post before its chargebacks; the reversal cap is cumulative; a chargeback reopening a closed case is pre-arbitration; the case names the reserve day.
- Decision 5 — the accept’s reason reaches the record; a reversed or closed case is refused before capture; the reason-code reader finds a code by its typed id.
- Decision 6 — the counting rules, the strictness test, and the month on the step-up.
- ADR-842’s tests corrected — two assertions on a field its phase B removed, and the pre-VAT nets its own VAT ruling overturned.
- Stale text struck — the reserve step’s release, the deadline step’s feature key, the representment’s four-eyes, the outcome type’s old name, and the 10-07 day.
Outcome
Landed as designed across six bites: the reserve as ADR-836’s second reductions holder, chargebacks per line with the reserve consumed oldest first, representment and the clocks, monthly monitoring, and the screens. Two calls differed from the text: the free balance is read from the availability reader’s unfloored figures because ADR-837 floors its available at zero, and the reads are gated over HTTP only by a small route guard, since no route-level feature attribute exists.
Notes
- Depends on ADR-842 (the agreement, the feed, the settlement account, the payout step),
ADR-840 (the reason codes,
AttachmentId) and ADR-841 (the price card). - Standards: the schemes’ dispute monitoring programmes (Visa’s, Mastercard’s Excessive Chargeback Programme) give the step-up’s shape; the scheme rules row ADR-840 adds names them.
- Scale, observed: a large merchant’s settlement account carries a claim per sale for T+n days (ADR-842) and a reserve day per date for the reserve period; per-day hold claims are the likely refinement once a buyer’s volumes are known.
- Spend controls and corporate cards follow in the series.