§ 1
In brief
01 · Order
from the order system
02 · Screening
rule, version 3 · a score with reasons
03 · Route
strategy: on-us first
04 · Authorisation
the bank’s answer
05 · Capture
after picking · on the order system’s request
Payer
The tracking page
Operator
The cabinet
Auditor
An export with its sources
never rewrittenThree readers, one trail.
- A cause on every step
- A rule names its version, a bank’s answer names its request, a person’s decision names the role.
- Never rewritten
- A correction is a new entry. Nothing that decided a payment is changed afterwards.
- Replay
- Every view can be rebuilt from the record at any time and must come out the same.
- Three readers
- The payer sees the tracking page, the operator the cabinet, the auditor an export with its sources.
§ 2
In detail
2.1
One payment, every step
The trail of a payment is drawn from its record as it was written: every step is a fact, numbered in the order it was appended and marked by its source — a person or a client system, the platform, or a bank — with the views it formed. Nothing in it is drawn by hand.
Demo scene 1
One payment, every step
Each step as it was recorded, in order, with its source and the views it changed.
Session ps_K2DFJX27E
2.2
What each step records
- A fact from outside names the action and the payment it belongs to.
- A decision of a rule names the facts it was based on and the version of the rule.
- A bank’s answer names the request it belongs to.
- A person’s decision — a review cleared, a refund approved, a difference accepted — is a fact with the role, never a flag changed in a table.
- A fact passed to another record, such as an export to an auditor, names its source.
Demo scene 2
Who wrote the facts of the retail stand
Facts from people and client systems, from the platform’s own rules, and from banks and the clock.
People and systems
18,131
The platform
17,081
Banks and the clock
23,168
2.3
Rebuilt by replay
Because the decisions follow from the record, an attempt can be run again from its facts and must give the same result. That makes an audit cheap — no second system to reconcile, no screenshots — and a change safe: a new variant is replayed over the old history before it is used.
2.4
Three readers, one trail
The payer opens the tracking page from the pay link and sees the events of their payment in plain words: what was held, captured and released, and where the money went. The operator opens the attempt in the cabinet and sees the same steps with the routing decision and the fee. The auditor opens every cabinet, changes nothing, and reads the audit trail beside the record. Three readings of one record cannot disagree.
§ 3