Skip to content
Governed run replay
Live - no signup

Resolve disputes under your controls.
Watch a human approve the refund.

A governed transaction-dispute run, replayed end to end: source-grounded evidence from the ledger, deterministic checks, then a human approval gate where a reviewer approves a partial refund - the customer action stays in preview until approved.

Read-only replay of an illustrative run - no inputs, no production credentials.

  • Ledger-grounded evidence with citations
  • A human approval gate that owns the refund
  • A tamper-evident proof packet
  • Self-hosted, EU-hosted - under your controls

A real governed run, replayed in full below - ending in a human refund approval and an auditable proof packet.

Transaction dispute
run_d4a91ctxn-dispute/v200:00.0 elapsed
Governed runIllustrative sample - EU region
Ready to run - press play
Run received
Ledger intake & evidence extraction
Deterministic chargeback checks
Policy-trigger checks
Dispute scoring
Human approval gate
Proof packet recorded
Review complete
Watch a governed run, end to end

Eight events, exactly as the platform recorded them - from intake to a human approval gate that owns the refund. Nothing is simulated past what you see here.

status - seq 1
Run received
running

A cardholder dispute was submitted for governed review. The run is registered against flow txn-dispute/v2 and begins under the workspace's controls - every step from here is recorded.

SubjectCardholder dispute - EUR 248.00
Flowtxn-dispute/v2
Run idrun_d4a91c
RegionEU
node - seq 2
Ledger intake & evidence extraction
passed

The transaction and its history were parsed and ledger-grounded evidence was extracted - each finding carries a citation back to the record it came from.

Original authorization and capture - EUR 248.00Evidence: 3 items txn-ledger Q2
Merchant descriptor and prior partial credit EUR 100.00Evidence: 2 items merchant-feed 2026-06
Cardholder statement and dispute reason code 13.1Evidence: 4 items dispute-intake 14
node - seq 3
Deterministic chargeback checks
info

Rule-based checks ran against the network chargeback rules. Most passed - one finding caps the refundable amount the gate later approves.

Dispute filed within the network time limit
Reason code 13.1 evidence requirements met
Prior partial credit reduces refundable balanceEUR 100.00 already credited to the cardholder
node - seq 4
Policy-trigger checks
info

Workspace policies were evaluated against the extracted evidence. One policy trigger fired on cross-border settlement.

Refund amount within the auto-clear ceiling
Cross-border settlement requires reviewer sign-offPolicy: cross-border / refund-signoff
node - seq 5
Dispute scoring
passed

The findings were combined into a composite dispute score. The score lands in the partial-refund band, so the run is routed to a human reviewer rather than auto-cleared.

41/ 100Partial
0 - deny40 - partial band100 - full refund

In the partial-refund band -> routed to a human approval gate. No refund is issued automatically.

approval - seq 6
Human approval gate
approved
Refund authorization
gate: refund-authorization
Approved

A reviewer examined the run and approved a partial refund at the gate. The customer-facing refund action stays in preview - a dry-run - until this approval, and only the approved amount is released.

Valid dispute under reason code 13.1
Refund capped to EUR 148.00 after the prior EUR 100.00 credit
Reviewer Disputes reviewer Decision recorded at the gate
output - seq 7
Proof packet recorded
completed
txn-dispute_run_d4a91c.packetsha256:4d2e...a91c
Decision
APPROVED
Partial refund of EUR 148.00 released after approval. No further credit issued.
Reasons
Valid dispute under reason code 13.1
Refund capped to EUR 148.00 after the prior EUR 100.00 credit
Evidence (source-grounded citations)
Transaction authorization and capture txn-ledger Q2
Prior partial credit record merchant-feed 2026-06
Cardholder dispute statement dispute-intake 14
Written once to a tamper-evident, append-only audit ledger - decision, reviewer, reasons, and evidence.
done - seq 8
Review complete
completed
Finished with a recorded, auditable human decision

The run ended exactly where governance required: a person decided, the decision is logged, and there is a proof packet anyone can audit later. The refund stayed in preview until a human approved it.

OutcomePartial refund approved at human gate
Decided byDisputes reviewer
Proof packetrun_d4a91c
Events recorded8 of 8
What just happened

Three governance moments, in one run.

The replay is not a chatbot demo. It is the control plane doing its job: grounding, gating, and proof - the parts a regulator asks about.

Seq 2

Evidence from the ledger

Every finding is grounded in a transaction record and dispute filing. Reviewers and auditors can trace any claim back to where it came from - not to a model's recollection.

Seq 6

A human gate that owns the refund

A partial-band score routes to a person, not an auto-refund. Here the reviewer approved EUR 148.00 - and the customer-facing action stayed in preview until that approval. Nothing is released without it.

Seq 7

A tamper-evident proof packet

The decision, the reviewer, the reasons, and the cited evidence are written once to an append-only audit trail. Months later, you can prove exactly why this refund amount was approved.

Built for regulated teams - designed to run under your controls
Self-hosted
EU AI Act controls
GDPR controls
Audit trail
Data sovereignty

PrivateFlow is not certified under any compliance framework. Controls are designed to support compliance preparation. This run is an illustrative, synthetic example.

See it on your own data

Run this on your own disputes.

We'll stand up a governed pilot on your own data - sandbox first, no production credentials required. You decide what the gates do.