Top level

One shared picture of a fictional payment

Parts

4 parts on this layer, as on the map.

Mira · customer Actor. Buys one €100 lamp.

Merchant support Actor. Explains outcomes and requests refunds.

Fictional processor External system. An external system with an authored contract.

Copper Lane Payments Boundary. One shared picture of a fictional payment.

Explore Alexandria 1 of 6

Illustrative payment system · authored sample knowledge

Follow the payment use case through the real project views. Select a step, a part or its supporting context.

Connect a business outcome to the parts responsible for it.

Explains outcomes and requests refunds

Support reads the recorded evidence for an order and requests a refund when the lamp is unavailable. A request and a confirmed result are distinct.

Request refund-1001 · Merchant support → Payment service · Command · Network · Payment service API Support requests EUR 10000 against pay-1001. refund-1001 uses its own operation key refund-op-1001 and initially remains requested.
Read an order’s payment evidence · Merchant support → Payment service · Query · Network · Payment service API Support reads pay-1001 and its recorded source before deciding whether to request the refund. No bank balance or settlement observation is shown.