Explore Alexandria · Optio Alexandria

Data Command Query Event In-process Scroll or drag to pan · Ctrl + scroll or pinch to zoom

Notes

Explore Alexandria 3 of 6

Illustrative payment system · authored sample knowledge

What does the recorded payment tell us?

Inspect Payment and its confirmation records. The authored source explains when the outcome becomes known and how duplicate deliveries are recognized.

Read the data, its ownership and the evidence behind the picture.

Back Next

Explore freely Open my projects

Refund the unavailable lamp

Illustrative system · authored sample records. The lamp is unavailable after payment confirmation. Support requests refund-1001 for EUR 10000 against pay-1001.

Actor: Merchant support
Goal: Request one refund and explain whether its processor outcome is known.
Trigger: The shop cannot supply Mira’s lamp.
Outcome: A separate authored processor record confirms refund-1001; bank posting and settlement remain outside this story.

Next step 2 steps

Preconditions

The recorded payment is processor-confirmed and no full refund is already confirmed.

Steps

1 Support checks the confirmed payment and its existing refund history. · Read an order’s payment evidence
2 Support requests a separate refund; the service records its request and compatible processor confirmation. · Request refund-1001, Read and record payment state, Submit the same refund operation, Receive refund confirmation, Apply a compatible outcome

Failures and retries

An unanswered or rejected request is not a confirmed refund. Keep uncertainty visible and do not create another refund to conceal it.

Acceptance criteria

Retain refund-op-1001 for retries of the same refund. Show Requested until compatible processor confirmation is recorded.

Flows

Request and confirm the €100 refund · Step 2