Hash Validation

This guide explains how to validate hash key.
In 3D Secure payments, after the transaction is completed, the user is redirected to the merchant’s success or failure URL. Since this URL may be publicly accessible and can be triggered by unauthorized users. including parameters such as status, invoice_id, order_id, and hash_key in the redirect URL is recommended and and incoming requests should be verified using the hash_key.

For recurring payments, a POST request is sent to the merchant webhook for each renewal transaction. Since webhook URLs are typically publicly accessible, these requests should also be verified using the hash_key to ensure request authenticity.

For 3D Secure payments, the status parameter can be set to 0 or 1.

For the Recurring Webhook, the $status parameter can be Completed or Fail.

For Refund Webhook, the status parameter can be Completed or Fail.

Python

Shell

JavaScript

Java

Swift

Ruby

Dart