Skip to content
Copper Lane Payments Read-only example
How it works Copper Lane Payments

Copper Lane Payments

One shared picture of a fictional payment

Parts

6 parts on this layer, as on the map.

Mira · customer Actor. Buys one €100 lamp.

Merchant support Actor. Explains outcomes and requests refunds.

Checkout Process. Makes the payment outcome understandable.

Payment records Data store. Keeps requests, outcomes and evidence identities.

Payment service Process. Owns logical operations and recorded state.

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

How they work together

  1. Command from Mira · customer to Checkout: Buy the €100 lamp.
  2. From Merchant support to Payment service.
  3. Event from Fictional processor to Payment service.
  4. From Checkout to Payment service.
  5. Data from Payment service to Payment records: Read and record payment state.
  6. From Payment service to Fictional processor.
Map ViewDocument ViewMira · customer ActorMerchant support ActorCheckout ProcessConfirmation handler ComponentPayment records Data storePayment service ProcessFictional processor External systemCopper Lane Payments BoundaryPay for the €100 lamp use caseRefund the unavailable lamp use caseProcessor confirmation EntityOrder reference EntityPayment EntityRefund EntityPayment state · illustrative PostgreSQL design Database designOpen my projects Page