# RefundCompleteFullData

> A schema in the One API reference. Source: https://hub.ozow.com/api-reference/one-api/schemas/refund-complete-full-data/

The `data` of a `refund.complete` delivery whose subscription asked for `full`. Every value is a string. `Status` here is not the `thin` payload's `status`: the `full` payload carries the refund's own status unmapped, so it has two values the `thin` one folds away.

## Fields

- `RefundId` (string, uuid, required) - The refund identifier.
- `TransactionId` (string, uuid, required) - The transaction the refund was raised against.
- `CurrencyCode` (string, required) - The ISO 4217 currency code.
- `Amount` (string, required) - The amount, to two decimal places, with a full stop as the separator.
- `Status` (string, required, one of "Pending", "Complete", "Submitted", "Failed", "Cancelled", "Returned", "Invalid", "PendingInvestigation", "Error") - The refund's own status, unmapped. `PendingInvestigation` and `Error` reach a `full` subscriber as themselves, where a `thin` subscriber sees `Pending` and `Failed` in their place.
- `BankName` (string, required) - The bank the refund was paid to.
- `AccountNumber` (string, required) - The account the refund was paid to.
- `StatusMessage` (string, required) - The status detail, empty when there is none.
- `Hash` (string, required) - The check hash over the field set. Verify the Svix signature rather than this: the signature covers the whole delivery.