Skip to content
Copper Lane Payments Read-only example
Refund
Entity

Refund

Owned by Payment service

AI context

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

# Entity: Refund (`data-refund`)

Owned by Payment service

## Description

Authored refund-1001 references pay-1001 for EUR 10000 with separate key refund-op-1001. The requested state precedes prepared confirmation evt-9002; bank posting remains unknown to this sample.

- Attributes: 6
- Use cases: 1
- ID: data-refund

## Attributes

- 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.
- amount_minor (integer · required): Integer minor units. EUR 10000 represents the fictional €100.00 purchase or full refund.
- currency (string · required): The authored example uses EUR; it is not a live exchange rate or price feed.
- operation_key (string · required): refund-op-1001 is separate from the payment key and retained when retrying the same authored refund.
- state (enum · required): Requested records intent. Confirmed requires compatible fictional processor evidence; neither state reports bank posting.

## Connections

- ← Processor confirmation (many_to_one)
- → Payment (many_to_one)