Step 3: Refund processing
Ozow will process the refunds as soon as possible. Payment will be made into the account from which the original EFT payment was made.
Outcome
Once you receive a bank message that contains a transaction status the transaction has been concluded and the status of the payment can be determined. You can trigger the relevant actions on your system based on the payment status received.
Status types
| Status | String | Description |
|---|---|---|
| 0 | Pending | The refund request has been submitted and accepted. |
| 1 | Complete | The refund has been paid successfully. |
| 2 | Submitted | The refund has been assigned to a batch and is being processed. |
| 3 | Failed | The refund payment has failed. |
| 4 | Cancelled | The refund has been cancelled before it was submitted. |
| 5 | Returned | The refund payment has been returned because the account that was being refunded no longer exists. |
| -1 | Invalid | The refund has not been processed successfully by the provider |
Notification
Once the refund has either failed or been completed, Ozow will send a notification to the URL in the request.
| Name | Type | Description |
|---|---|---|
RefundId | Guid | The refund identifier. |
TransactionId | Guid | The transaction identifier of the transaction that is being refunded. |
CurrencyCode | String (3) | The refund currency. Will always be the same as the amount in the transaction. |
Amount | Decimal (9,2) | The refund amount. The amount is in the currency specified by the currency code. |
Status | String | The refund status. See possible values. |
BankName | String (50) | The name of the bank the refund was paid to. |
AccountNumber | String (50) | The masked account number payment was made to. |
StatusMessage | String (500) | Message regarding the status of the refund. This field will not always have a value. |
isRtc | Bool | True/False for refunds paid via RTC |
Hash | String (150) | SHA512 hash used to ensure that certain fields in the message have not been altered after the hash was generated. Check the generate hash section below for more details on how to validate the response variables using the hash. |
Notification hash check
Follow these steps to generate the hash check:
- Concatenate the notification variables (excluding the isRtc and hash fields) in the order they appear in the notification fields table above.
- Append your private key to the concatenated string. Your private key can be found in merchant details section of the merchant admin site.
- Convert the concatenated string to lowercase.
- Generate a SHA512 hash of the lowercase concatenated string.
- Compare generated hash to the hash value received.
Updated 3 months ago
What’s Next