Hash Information - Sipay API Documentation

Hash Validation Example
In 3D payment, after the payment is completed, the user is redirected to the merchant's successful or unsuccessful link. The problem with these links is that they can be accessed by an anonymous person. To prevent this problem, it is recommended that some parameters such as status, invoice_id, order_id, and hash_key are added to the links when redirecting from Sipay, and the request is validated using the hash key.

Also, in recurring payments, a submission request is sent to the merchant webhook in each iteration. Usually, the webhook is an open link. Therefore, the recurring request can also be validated using the hash key. The example code for the validation process is given below.

Here,

ha s h_{k} eys h o u l d b eo b t ain e df ro m t h ere q u es t, an d

secret_key is the merchant application's secret key (app_secret) provided by Sipay.

For 3D payment, status = 0 or status = 1
However, for recurring webhooks,
status = COMPLETED or
status = FAIL

Click here to download the sample hash validation file, or review the sample code below.