Copper Lane Payments
One shared picture of a fictional payment
Parts
3 parts on this layer, as on the map.
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.
How they work together
- From Checkout to Payment service.
- Data from Payment service to Payment records: Read and record payment state.
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.