What happened?
A synthetic card-not-present payment for USD 1,280.00 went through step-up authentication and was recorded as approved after a human exception.
SYNTHETIC FLAGSHIP RECONSTRUCTION
Payment Decision Reconstruction
A read-only proof workspace for retained banking and payment transaction-decision context.
- Domain
- Banking and payment decisions
- Scenario context
- Payment and fraud-risk decision proof
- RecordArc posture
- Retrospective, read-only, and off-path
PLAIN-LANGUAGE ORIENTATION
The story of this decision
What RecordArc reconstructed
The retained payment, authentication, risk, authorization, configuration, human-exception and outcome records can be inspected in chronological context.
What is missing or uncertain
The role-delegation record for the exception is unavailable. RecordArc does not rerun the decision or establish that the approved outcome was correct.
PERSISTENT RECORD SUMMARY
- Record
- RA-PAY-2026-00128
- Event
- Synthetic card-not-present payment
- Value
- USD 1,280.00
- Merchant
- Synthetic merchant MRC-204
- Recorded outcome
- Approved after step-up authentication
Review question: Can the retained authentication, authorization, risk, configuration, and exception context be reconstructed consistently?
01 / SOURCE LANDSCAPE
Owning records stay authoritative.
The proof record references retained source identities without changing source business state.
Payment event
Source factAuthentication response
Source-system outcomeAuthorization response
Source-system outcomeRisk and rule context
Source factManual exception
Human-certified interpretation02 / MAPPING AND PROVENANCE
Source meaning and RecordArc structure remain distinct.
Authorized human certification governs source meaning. RecordArc-normalized values, derived ordering, and other derived context remain explicitly labelled.
| Source field | Proof field | Class | Authority |
|---|---|---|---|
| payment.event_id | event.identity | Source fact | Payment orchestration |
| auth.response | authentication.outcome | Source-system outcome | Authentication service |
| risk.rule_version | decisionContext.ruleVersion | RecordArc normalized | Authorized mapping |
| ops.approver_role | humanAuthority.role | Human-certified interpretation | Operations owner |
03 / RECONSTRUCTED RECORD
The retained synthetic context forms an internally consistent reconstruction.
The reconstruction matches the displayed retained identities and chronology. It does not reproduce, rerun, approve, or validate the source decision.
{
"record": "RA-PAY-2026-00128",
"classification": "Synthetic illustration",
"recordedOutcome": "Approved after step-up authentication",
"sourceAuthority": "preserved",
"decisionExecution": "not performed",
"proofGaps": ["operations.delegation_record"]
}04 / ORDERED DECISION CONTEXT
Six retained nodes form an ordered reconstruction path.
The current synthetic flagship preserves node identity, source ownership, classification, provenance, and chronology. Approved typed-edge semantics are not available for this payment scenario, so RecordArc does not invent relationship labels between adjacent nodes.
- 01Payment eventPayment orchestration recordSource fact
- 02AuthenticationAuthentication service recordSource-system outcome
- 03Risk contextRisk service and configuration registrySource fact
- 04AuthorizationIssuer authorization recordSource-system outcome
- 05Human exceptionOperations review recordHuman-certified interpretation
- 06Recorded outcomeOwning source systemSource-system outcome
Typed relationship semantics are not asserted for this synthetic payment scenario because approved edge authority is not currently available.
05 / PROOF CONDITIONS
Status remains dimensional and review-question specific.
No aggregate readiness percentage or universal score is produced.
Source identity
Owning systems and record identifiers are retained.
Version linkage
Rule, threshold, and configuration versions are linked.
Decision chronology
Event, decision, capture, and later-acquired times remain distinct.
Exception authority
Approval is retained, but the role-delegation record is unavailable.
Evidence classification: Missing/unverifiable
Outcome correctness
The source-system outcome is preserved but is not rerun or validated.
06 / TEMPORAL RECORD
Event, decision, capture, and later-acquired times remain separate.
Sequence is reconstructed from retained timestamps and disclosed assumptions.
- 01Payment event captured
PAY-128 - 02Authentication challenge recorded
AUTH-44 - 03Risk response retained
RSK-771 - 04Authorization referral recorded
AUTHZ-912 - 05Operations exception approved
OPS-17 - 06Final source outcome recorded
OUT-128 - 07Later evidence capture completed
CAP-128
07 / LIMITATIONS
Proof gaps and non-goals stay visible.
The package describes what retained evidence supports and what it cannot establish.
- The scenario is synthetic and contains no customer or production data.
- RecordArc did not authenticate, authorize, score, refer, hold, release, or approve the payment.
- The underlying rule, model, and authorization logic was not re-executed.
- One delegation record is intentionally missing and remains a disclosed proof gap.
- The reconstruction does not establish legal, regulatory, audit, or operating-effectiveness sufficiency.
08 / REVIEWER PERSPECTIVES
QA and Audit are views on the same proof record.
They are not separate product modules and do not replace reviewer judgment.
QA perspective
Inspect classification completeness, chronology coverage, proof gaps, and package consistency.
Audit perspective
Inspect whether the retained identities, versions, and chronology support the displayed reconstruction.
Control-owner perspective
Review source linkage and exceptions without asserting operating effectiveness or remediation closure.
09 / STRUCTURED PROOF PACKAGE
A structured synthetic package preview.
The preview keeps sources, mappings, ordered nodes, conditions, chronology, limitations, and reviewer views inspectable together. The graph artifact is a structured node and ordering preview; it does not assert approved typed payment-edge semantics.
Review package artifact inventory
- record.json
- sources.json
- mappings.json
- proof-graph.json
- conditions.json
- timeline.json
- limitations.json