Skip to content
Copper Lane Payments Read-only example

Payment service

Owns logical operations and recorded state

Parts

1 parts on this layer, as on the map.

Confirmation handler Component. Checks event identity and compatible outcomes.

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.

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