Payment service

Owns logical operations and recorded state

Parts

1 parts on this layer, as on the map.

Confirmation handler Component. Checks event identity and compatible outcomes.

Refund the unavailable lamp

Who: Merchant support. Goal: Request one refund and explain whether its processor outcome is known. Starts when: The shop cannot supply Mira’s lamp.

First, Support checks the confirmed payment and its existing refund history. Finally, Support requests a separate refund; the service records its request and compatible processor confirmation.

Ends with: A separate authored processor record confirms refund-1001; bank posting and settlement remain outside this story. If it fails: An unanswered or rejected request is not a confirmed refund. Keep uncertainty visible and do not create another refund to conceal it.

Notes

Explore Alexandria 6 of 6

Illustrative payment system · authored sample knowledge

Can the next conversation start with the reason included?

Read the Payment service’s actual generated context. Copy it for your external agent with its source identity, connected knowledge and recorded reasons.

Give people and agents the same project knowledge.

Back

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