Skip to content
Copper Lane Payments Read-only example

As Mira · customer, I want Pay once and understand whether the shop can fulfil the order., so that Processor-confirmed payment lets the shop fulfil the order. Unknown and confirmed-decline outcomes remain visibly different..

Actor

Mira · customer

Goal

Pay once and understand whether the shop can fulfil the order.

Trigger

Mira chooses Pay for the €100 lamp.

Preconditions

  • The fictional order ord-1042 requests EUR 10000. No real account, card, payment or provider credentials exist.

Outcome

Processor-confirmed payment lets the shop fulfil the order. Unknown and confirmed-decline outcomes remain visibly different.

Acceptance

  • Fulfil only after processor-confirmed payment; preserve the same logical operation when its outcome is unanswered.
  • Repeated delivery of evt-9001 leaves one recorded EUR 10000 payment; ordering and exactly-once delivery are not assumed.

Failures

  • 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.

Open questions

  • Who owns a payment that remains unresolved? See dec-unresolved-payment-escalation.

Steps

  1. 1Mira chooses Pay for the €100 lamp. Mira · customer Checkout No flow yet
  2. 2The service records, submits and resolves one logical payment. Checkout Payment service Payment records Fictional processor Confirmation handler Processor confirmationOrderLogical paymentRefundOpen flow
  3. 3Checkout reads what is known; a missing answer remains visibly unknown. Checkout Payment service Fictional processor Payment records Processor confirmationOrderLogical paymentRefundNo flow yet