Documentation
Search…
PayKun Basic-Know-How
Webhooks
Webhooks helps you get notified about events that happen over PayKun.
For example:- when a buyer makes a payment, PayKun can send an HTTP POST request to the merchant server. This avoids keeping polling over PayKun servers for updates.
It is simply a communication channel between PayKun servers and merchant servers.
Webhooks allow you to build or set up integrations which subscribe to certain events on PayKun API.
Functional use cases of Webhook are :
- Sending customized emails to merchants at the end of every transaction.
- Registration of a new user account on server.
Webhook is an alternative way by which Paykun can inform about different events, this is server to server calling mechanism and so you have to implement logic for how you want to handle this event in your system and you have to provide a Callback URL where PayKun would send the event data.
Your Callback URL should handle POST Request and it should return HTTP 200 on successful processing of request. For any other status, PayKun will again try Calling URL for 3 times after some time intervals.
Note : In very rare cases you might receive the same event twice, in that case you need to handle the request by keeping in mind to avoid the duplicate processing.
In Callback request, you will get following data :
1
{
2
"transaction": {
3
"payment_id": "55873-83139-75447-76995",
4
"merchant_email": "[email protected]",
5
"merchant_id": "123456789012345",
6
"status": "Success",
7
"status_flag": 0,
8
"payment_mode": "WALLET",
9
"order": {
10
"order_id": "DEMO_ORD1560424646862",
11
"product_name": "Test Checkout",
12
"gross_amount": 11,
13
"gateway_fee": 0.22,
14
"tax": 0.04
15
},
16
"customer": {
17
"name": "Customer Name",
18
"email_id": "[email protected]",
19
"mobile_no": "1234567890"
20
},
21
"shipping": {
22
"address": null,
23
"city": null,
24
"state": null,
25
"country": null,
26
"pincode": null
27
},
28
"billing": {
29
"address": null,
30
"city": null,
31
"state": null,
32
"country": null,
33
"pincode": null
34
},
35
"custom_field_1": null,
36
"custom_field_2": null,
37
"custom_field_3": null,
38
"custom_field_4": null,
39
"custom_field_5": null,
40
"date": "1581769083",
41
"signature": "e08bf1fcaf01d5fa4198de47d08a0158a9526b9e341e8a53bb8d3373b9268861f0bc0c363e60371e0f723558296f23ec43de8aceafd833498d2cf94bf8032b64"
42
}
43
}
44
​
Copied!
Note: Request data will be posted as a Raw JSON body. In Core PHP you will be able to get it using [$data = json_decode(file_get_contents('php://input'), true);]
Here, the status will be Success if transaction is successful otherwise it will represent other status like Failed or Not Attempted.
status_flag will be 1 (true) for successful transactions and for all other status it will be 0 (false).
We provide the signature. You should always calculate the signature and compare it at your end before processing the request any further. If the signature is a mismatch then you should discard that request for security reasons. Signature is generated using the API Secret.
You can use below function to compare Signature in PHP :
1
function compareSignature($transactionData, $receivedSignature, $apiSecret) {
2
$dataString = '';
3
4
// Unset signature from data
5
unset($transactionData['signature']);
6
7
foreach ($transactionData as $key => $value) {
8
if (is_array($value)) {
9
foreach ($value as $_key => $_value) {
10
$dataString .= $_value;
11
$dataString .= '|';
12
}
13
} else {
14
$dataString .= $value;
15
$dataString .= '|';
16
}
17
}
18
$dataString .= '#';
19
20
// Creating signature
21
$signature = hash_hmac('sha512', $dataString, $apiSecret);
22
23
if(hash_equals($receivedSignature, $signature)) {
24
// Signature match
25
return true;
26
}
27
28
// Signature mismatch
29
return false;
30
}
31
​
Copied!
​
​
Last modified 1yr ago
Copy link