RefundRequest

The transaction identifier. This is the identifier for the payment that was originally processed on Ozow.

The amount that needs to be refunded. This can be less than the original transaction amount but not more.

The reason for the refund.

The URL Ozow will send a notification to once the refund has been finalised.

SHA512SHA-512 A hashing algorithm. Ozow uses it to sign the values in a request or a notification so you can tell that they arrived unaltered and came from us. Hashing is one-way: the hash cannot be turned back into what produced it.Wikipedia 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.

Whether the refund should be processed as an RTCReal-Time Clearing Payments that clear immediately rather than waiting for a batch. A batch run settles at set times through the day; a Real-Time Clearing payment moves the funds between the two bank accounts as it is made, so the recipient can rely on them straight away.PayInc refund.