Settlement Buffer · 120h default

120 hours.
On purpose.

Instant rails move money before anyone can ask a question. That is useful for trusted counter-parties. It is catastrophic for autonomous agents. The settlement buffer is the window where the wrong decision becomes a reversal instead of a recovery operation.

The timeline

What happens in the window.

  1. T+0

    Agent authorizes · VFP issued

    Funds are held in the FBO buffer. Counter-party sees a verified receipt. Capture latency is milliseconds.

  2. T+0 – T+24h

    Reasoning clears policy checks

    Automated checks validate the policy and counter-party. Low-confidence authorizations flag for operator review.

  3. T+24h – T+96h

    Receipts and events arrive

    Invoices, shipment confirmations, and dispute signals are reconciled against the hold. Release is scheduled or cancelled.

  4. Anytime

    Reversal is one call

    Operators — or the SafetySwitch itself — can pull any held escrow back. No vendor involvement needed. No dispute form.

  5. T+120h

    Release fires

    If no reversal or block has landed, the protocol releases funds to the counter-party and terminalizes the entry.

The buffer economics

Instant is expensive. Reversible is cheap.

Card rails charge for the ability to dispute. RTP charges for the speed. Paystack charges for the window — and the window is where fraud, errors, and bad policies get corrected before they become accounting problems.

RailSettleCost/txnReversal windowWho reverses
Card (CNP)T+12.9% + $0.30≤ 120d (chargeback)Cardholder only
RTP / FedNowT+0 · seconds~$0.045None — irrevocableNobody
ACHT+1–3~$0.0860d (unauthorized)Receiver’s bank
Paystack escrowT+120h (configurable)0.6% + $0.10The whole window · 100%Operator · SafetySwitch
Why this isn’t slow

The buffer runs while the business keeps moving.

Capture is T+0

The moment an agent authorizes a payment, the counter-party sees a Verified Future Payment. Vendors plan on it. They just can’t spend it yet.

Work continues in parallel

Receipts, shipment events, and dispute signals flow into the ledger during the window. Release fires automatically when conditions clear.

Known-good accelerates

Counter-parties with a verified history can be whitelisted to a shorter window or instant rail — without giving up reversibility for the rest.

Configurability

Tune the window per policy.

120 hours is the default. Set per-agent, per-counter-party, or per-category windows. High-risk policies get a longer buffer. Recurring trusted vendors can run at T+0. The ledger records the policy that chose the window, so audit can see why.

See the policy API →