This allows merchants to receive real-time notifications about successful transactions and integrate this data into their own systems.
\nLynk.id webhooks use a token-based authentication method to secure webhook payloads. Here's how to verify incoming webhook requests:
\nWhen you receive a webhook from Lynk.id, it will include a X-Lynk-Signature header
Use your merchant key to validate that the request is genuinely from Lynk.id
Extract the X-Lynk-Signature from the request headers
Extract refId, amount(grandTotal), and message_id from the request body
Use your merchant key (obtained from your Lynk.id dashboard)
Process the webhook only if the signature is valid
\nNever share your merchant key with anyone
Always verify the signature before processing webhook data
\nConsider validating timestamps to prevent replay attacks
\nStore your merchant key securely in environment variables
*Note: merchant key will be available once you saved a webhook URL.
import hashlib\ndef validate_lynk_signature(ref_id, amount, message_id, received_signature, secret_key):\n signature_string = amount + ref_id + message_id + secret_key\n calculated_signature = hashlib.sha256(signature_string.encode('utf-8')).hexdigest()\n return calculated_signature == received_signature\n\nconst crypto = require('crypto');\nfunction validateLynkSignature(ref_id, amount, message_id, receivedSignature, secretKey) {\n const signatureString = amount + ref_id + message_id + secretKey;\n const calculatedSignature = crypto\n .createHash('sha256')\n .update(signatureString)\n .digest('hex');\n return calculatedSignature === receivedSignature;\n}\n\npackage main\nimport (\n \"crypto/sha256\"\n \"encoding/hex\"\n)\nfunc ValidateLynkSignature(refID, amount string, message_id string, receivedSignature, secretKey string) bool {\n signatureString := amount + refID + message_id + secretKey\n hash := sha256.New()\n hash.Write([]byte(signatureString))\n calculatedSignature := hex.EncodeToString(hash.Sum(nil))\n return calculatedSignature == receivedSignature\n}\n\nThe webhook_url is dynamically obtained from the user data. You'll need to replace this with an actual URL for testing.
\n","urlObject":{"host":["webhook_url"],"query":[],"variable":[]}},"response":[],"_postman_id":"61e14299-db58-4289-8557-da08632e2528"}],"id":"69125184-1743-463f-9b5a-2558c0b996a2","description":"Webhook provide a way for notifications to be delivered to an external web server whenever certain event occur in Lynk.
\nThe format prepared by the engine is JSON. with Method use POST and application/json for Content-type.
Message event webhooks can be triggered by several types of events:
\nEvent payment.received payload
\npayload that will be sent to the webhook server URL when there is a transaction
\n{\n \"event\": \"payment.received\",\n \"data\": {\n \"message_action\": \"SUCCESS\",\n \"message_code\": \"0\",\n \"message_data\": {\n \"createdAt\": \"2025-04-10T14:30:45\",\n \"customer\": {\n \"email\": \"user@lynk.id\",\n \"name\": \"Lynk User\",\n \"phone\": \"0812345677889\"\n },\n \"items\": [\n {\n \"addons\": [\n {\n \"id\": \"67c6b9a5593dd002a0ec4ab7-5498-4703872927-1741076901767\",\n \"name\": \"Iniprodukaddon\",\n \"price\": \"50,000\"\n }\n ],\n \"appointment_data\": {},\n \"pafId\": \"\",\n \"price\": 25000,\n \"public_affiliate_content\": {},\n \"qty\": 1,\n \"stock\": 1,\n \"title\": \"Digital Produk\",\n \"uuid\": \"63cfd869524d15196a557388-8244-36439\"\n }\n ],\n \"refId\": \"13f8d23beeb2aacbbc01c94060cc88d7\",\n \"shippingAddress\": \"\",\n \"shippingInfo\": \"\",\n \"totals\": {\n \"affiliate\": 0,\n \"convenienceFee\": -3000,\n \"discount\": 0,\n \"grandTotal\": 72000,\n \"totalAddon\": 50000,\n \"totalItem\": 1,\n \"totalPrice\": 25000,\n \"totalShipping\": 0\n }\n },\n \"message_desc\": \"\",\n \"message_id\": \"API_CALL_1744270275143115_4624014\",\n \"message_title\": \"\"\n }\n}\n\nDescription of fields:
\nRoot Level:
\nevent: (String) The name of the event that triggered the webhook. In this case, it's \"payment.received\".
data: (Object) Contains the details of the payment received event.
data Object:
message_action: (String) Indicates the status of the message. Example: \"SUCCESS\".
message_code: (String) A code representing the message status. Example: \"0\".
message_data: (Object) Contains the actual data related to the payment.
message_desc: (String) A description of the message.
message_id: (String) A unique identifier for the message. Example: \"API_CALL_1744270275143115_4624014\".
message_title: (String) A title for the message.
message_data Object:
createdAt: (String) Timestamp indicating when the payment was recorded, in ISO 8601 format. Example: \"2025-04-10T14:30:45\".
customer: (Object) Contains customer information.
items: (Array of Objects) An array of items included in the payment.
refId: (String) A reference ID for the payment. Example: \"13f8d23beeb2aacbbc01c94060cc88d7\".
shippingAddress: (String) The shipping address associated with the payment.
shippingInfo: (String) Shipping information related to the payment.
totals: (Object) Contains a breakdown of the payment totals.
customer Object:
email: (String) The customer's email address. Example: \"user@lynk.id\".
name: (String) The customer's name. Example: \"Lynk User\".
phone: (String) The customer's phone number. Example: \"0812345677889\".
items Array (each object in the array):
addons: (Array of Objects) An array of addons associated with the item.
appointment_data: (Object) Data related to appointments, if applicable.
pafId: (String) Potentially an ID related to a public affiliate.
price: (Number) The price of the item. Example: 25000.
public_affiliate_content: (Object) Content related to public affiliates.
qty: (Number) The quantity of the item. Example: 1.
stock: (Number) The stock level of the item. Example: 1.
title: (String) The title of the item. Example: \"Digital Produk\".
uuid: (String) A unique identifier for the item. Example: \"63cfd869524d15196a557388-8244-36439\".
addons Array (each object in the array):
id: (String) The ID of the addon. Example: \"67c6b9a5593dd002a0ec4ab7-5498-4703872927-1741076901767\".
name: (String) The name of the addon. Example: \"Iniprodukaddon\".
price: (String) The price of the addon. Example: \"50,000\".
totals Object:
affiliate: (Number) The affiliate commission amount. Example: 0.
convenienceFee: (Number) The convenience fee amount. Example: -3000.
discount: (Number) The discount amount. Example: 0.
grandTotal: (Number) The final net amount that the seller receives after deducting fees. . Example: 72000.
totalAddon: (Number) The total amount for addons. Example: 50000.
totalItem: (Number) The total number of items. Example: 1.
totalPrice: (Number) The total price of the items (excluding addons, shipping, etc.). Example: 25000.
totalShipping: (Number) The total shipping cost. Example: 0.
Expected Response:
\nA successful response (200 OK) would typically indicate that the webhook was received and processed correctly by the merchant's system. The exact response body will depend on the merchant's implementation.
Error Handling:
\nThe code includes basic error handling. If the response.status_code is not 200, the code logs the error message and candidate for a retry.
\n","_postman_id":"69125184-1743-463f-9b5a-2558c0b996a2"}],"event":[{"listen":"prerequest","script":{"id":"6237b658-54c1-443c-90ea-ddc1a43f302c","type":"text/javascript","exec":[""]}},{"listen":"test","script":{"id":"736e17ec-c468-4673-9e8c-1a495183757e","type":"text/javascript","exec":[""]}}],"variable":[{"key":"baseUrl","value":"https://farming-simulator.pstmn.io"}]}