Top level

One shared picture of a fictional payment

Parts

3 parts on this layer, as on the map.

Mira · customer Actor. Buys one €100 lamp.

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

Command from Mira · customer to Copper Lane Payments: Buy the €100 lamp.
From Copper Lane Payments to Fictional processor.
Event from Fictional processor to Copper Lane Payments.

Pay for the €100 lamp

Who: Mira · customer. Goal: Pay once and understand whether the shop can fulfil the order. Starts when: Mira chooses Pay for the €100 lamp.

First, Mira chooses Pay for the €100 lamp. Then, the service records, submits and resolves one logical payment. Finally, Checkout reads what is known; a missing answer remains visibly unknown.

Ends with: Processor-confirmed payment lets the shop fulfil the order. Unknown and confirmed-decline outcomes remain visibly different. If it fails: No checkout response within 10 seconds: keep pay-1001 confirming and seek the existing operation’s outcome.; A confirmed decline is an explicit failure; a separate new attempt can then be requested.

Checkout

Makes the payment outcome understandable

Owns the fictional checkout interface. Its 10-second wait may end before the payment outcome is known. A timeout shows Confirming payment rather than inventing failure.

Inside

Copper Lane Payments

part-checkout

Outgoing

Read the recorded answer · Checkout → Payment service · Query · Network · Payment service API Checkout reads the current logical payment. Confirming payment means its processor outcome is still unknown; it is not a failed charge.

Request one logical payment · Checkout → Payment service · Command · Network · Payment service API Checkout supplies ord-1042 and EUR 10000. The payment service retains logical payment pay-1001 and operation key pay-op-1001.

Incoming

Buy the €100 lamp · Mira · customer → Checkout · Command · Network · Checkout interface Mira submits order ord-1042 through the fictional checkout. src-purchase-requirement records the desired business outcome.

Use-case steps