Top level

One shared picture of a fictional payment

Parts

3 parts on this layer, as on the map.

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.

How they work together

From Merchant support to Copper Lane Payments.
From Copper Lane Payments to Fictional processor.
Event from Fictional processor to Copper Lane Payments.

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.

Confirmation handler

Checks event identity and compatible outcomes

A component inside the payment-service process. Receives fictional processor callbacks, recognizes repeated events and applies compatible state changes. Delivery order alone never establishes truth.

Inside

Payment service

part-confirmations

Outgoing

Apply a compatible outcome · Confirmation handler → Payment service · Command · In-process · Apply confirmed outcome The confirmation component invokes payment operations in-process. Check event identity and logical operation before recording an accepted transition.

Incoming

Receive payment confirmation · Fictional processor → Confirmation handler · Event · Network · Processor confirmation endpoint The fictional processor sends authored event evt-9001 for pay-1001, processor reference processor-pay-7001, EUR 10000 captured. src-processor-confirmation records this prepared evidence.

Receive refund confirmation · Fictional processor → Confirmation handler · Event · Network · Processor confirmation endpoint Authored event evt-9002 confirms refund-1001 for EUR 10000 against pay-1001. src-refund-confirmation does not establish bank posting.

Use-case steps