External system
Fictional processor
An external system with an authored contract
Outside the merchant payment system. Its sample contract permits identical same-key requests for 24 hours and repeated, unordered confirmations. These assumptions are not guarantees about real providers.
- ID
part-processor
Outgoing
- Receive payment confirmation · Fictional processor → Confirmation handler · Event · Network · Processor confirmation endpoint The fictional processor sends authored event evt-9001 for pay-1001, processor reference processor-pay-7001, EUR 10000 captured. src-processor-confirmation records this prepared evidence.
- Receive refund confirmation · Fictional processor → Confirmation handler · Event · Network · Processor confirmation endpoint Authored event evt-9002 confirms refund-1001 for EUR 10000 against pay-1001. src-refund-confirmation does not establish bank posting.
Incoming
- Check the existing operation · Payment service → Fictional processor · Query · Network · Fictional processor operations A bounded, on-demand read asks the fictional processor about the existing operation. An unanswered lookup leaves the outcome unknown; it does not start another payment.
- Submit another payment after timeout · Payment service → Fictional processor · Command · Network · Fictional processor operations Unsafe proposed change: a timeout creates a new logical payment and new operation key immediately, although pay-1001 may already have succeeded. Authored scenario; not an executed test.
- Submit the same refund operation · Payment service → Fictional processor · Command · Network · Fictional processor operations The payment service submits refund-op-1001 with identical refund parameters. A retry of that logical refund retains the key inside the fictional contract window.
Use-case steps