Skip to content
Copper Lane Payments Read-only example

Payment service

Owns logical operations and recorded state

Parts

6 parts on this layer, as on the map.

Merchant support Actor. Explains outcomes and requests refunds.

Checkout Process. Makes the payment outcome understandable.

Confirmation handler Component. Checks event identity and compatible outcomes.

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. Event from Fictional processor to Confirmation handler.
  2. From Merchant support to Payment service.
  3. From Checkout to Payment service.
  4. Command from Confirmation handler to Payment service: Apply a compatible outcome.
  5. Data from Payment service to Payment records: Read and record payment state.
  6. From Payment service to Fictional processor.