Skip to content
Copper Lane Payments Read-only example
Processor confirmation
Entity

Processor confirmation

Owned by Payment service

AI context

Subject type: entity
Subject ID: data-confirmation
Project ID: showroom-payments
Revision: 1
Project settings version: 1
Project settings hash: sha256:11eb9324f48ccccdfbf345321fa5ffff2df6e34be7357a383b848db997e22834

# Entity: Processor confirmation (`data-confirmation`)

Owned by Payment service

## Description

Authored event evt-9001 confirms pay-1001; evt-9002 confirms refund-1001. Event identity supports deduplication, but arrival order alone never establishes truth. Sources: src-processor-confirmation and src-refund-confirmation.

- Attributes: 4
- Use cases: 2
- ID: data-confirmation

## Attributes

- event_id (string · required): A stable identifier in this authored sample, independent of network delivery attempts.
- payment_id (reference · required): An explicit relation to the original authored operation or order reference.
- refund_id (reference): An explicit relation to the original authored operation or order reference.
- outcome (string · required): The outcome reported by an authored processor record, checked against the logical operation and compatible state.

## Connections

- → Payment (many_to_one)
- → Refund (many_to_one)