# RefundRequest

> A schema in the Payments API reference. Source: https://hub.ozow.com/api-reference/payments-api/schemas/refund-request/

## Fields

- `transactionId` (string, uuid, required) - The transaction identifier. This is the identifier for the payment that was originally processed on Ozow.
- `amount` (number, double, required) - The amount that needs to be refunded. This can be less than the original transaction amount but not more.
- `refundReason` (string, max length 500) - The reason for the refund.
- `notifyUrl` (string, uri, max length 500) - The URL Ozow will send a notification to once the refund has been finalised.
- `hashCheck` (string, required, max length 150) - SHA512 hash proving the request has not been altered after you generated it. Concatenate four fields in this order, with no separator, then append your private key: 1. `transactionId` 2. `amount`, formatted with two decimal places, so `100.00` 3. `refundReason` 4. `notifyUrl` Hash the result with SHA512 and send the digest as lowercase hexadecimal. **Unlike the payment request hash, do not convert the concatenated string to lowercase before hashing.** Refunds hash the string exactly as you built it, so the case of your reason and your notify URL matters. Only the digest is compared case insensitively.
- `isRtc` (boolean, default false) - Whether the refund should be processed as an RTC refund.