Webhook for Tylt Prime (Pay-in)

Overview

Tylt provides a webhook mechanism for merchants to receive real-time updates on the status of their payment instance, whether for pay-ins or for pay-outs. Merchants can specify a callBackUrl in their API requests, and Tylt will send notifications to this URL whenever there is a status change in the transaction.

Setting Up the Webhook

1. Implement a Callback Endpoint: Merchants must set up an HTTP POST endpoint that can receive JSON payloads. This endpoint should be capable of processing the incoming webhook data and verifying its authenticity using HMAC-SHA256 signature validation.

2. Insert the Callback URL: While calling the Create Pay-in or Create Pay-out instance API's , insert your endpoint URL in the callBackUrl field. Tylt will send updates to this URL whenever the transaction status changes.

3. Status Updates: The life cycle of a payment instance is tracked via eventId. Below is the list of possible eventId values and their meanings:

   eventId	Description
   1	Order Created
   2	Order Processing
   3	Payment Processing
   4	Payment acknowledged and trade settled
   8	Payment Failed
   9	Trade expired as action or payment was not completed prior to the deadline or disputed payment was expired due to non payment.

4. Callback Validation: To ensure the integrity and authenticity of the callback, Tylt signs each callback payload using HMAC-SHA256 with the merchant’s API secret key. This signature is sent in the HTTP header X-TLP-SIGNATURE.

5. Acknowledge the Callback: Upon receiving the callback, merchants must respond with an HTTP 200 status code and the text "ok" in the response body. This acknowledges the successful receipt of the callback. If the acknowledgment is not received, the webhook will not be retried automatically. Merchants can manually resend webhooks from their Tylt dashboard.

Validating Callbacks

Merchants should validate the HMAC signature included in the X-TLP-SIGNATURE header to ensure the callback is from Tylt and has not been tampered with. The HMAC signature is generated using the raw POST data and the MERCHANT_API_SECRET as the shared key.

Example Web-hook Handling Code

JavaScript

const express = require('express');
const crypto = require('crypto');

const app = express();
const PORT = 3000;
const apiSecretKey = 'YOUR_TLP_API_SECRET_KEY'; // Replace with your actual API secret key

// Middleware to parse incoming JSON requests
app.use(express.json());

// Callback endpoint
app.post('/callback', (req, res) => {
    const data = req.body;

    // Calculate HMAC signature
    const tlpSignature = req.headers['x-tlp-signature'];
    const calculatedHmac = crypto
        .createHmac('sha256', apiSecretKey)
        .update(JSON.stringify(data)) // Use raw body string for HMAC calculation
        .digest('hex');

    if (calculatedHmac === tlpSignature) {
        // Signature is valid
        if (data.isBuying == 1) {
            console.log('Received pay-in callback:', data);
            // Process pay-in data here
        } 
        // Return HTTP Response 200 with content "ok"
        res.status(200).send('ok');
    } else {
        // Invalid HMAC signature
        res.status(400).send('Invalid HMAC signature');
    }
});

// Start the server
app.listen(PORT, () => {
    console.log(`Server listening on port ${PORT}`);
});

Again, please note that these code snippets serve as examples and may require modifications based on your specific implementation and framework.

Example of Web-hook Responses

eventId: 1

{
  "data": {
    "accounts": {
      "MDR": 2,
      "fees": 0.46,
      "rate": 1.3,
      "fiatAmount": 30,
      "cryptoAmount": 23.08,
      "fiatCurrency": "EUR",
      "cryptoCurrency": "USDC"
    },
    "isBuying": 1,
    "instanceId": "443bd1a8-944b-4595-8dcf-21e274e6386c",
    "callBackUrl": "",
    "eventDetails": { "eventId": 1, "description": "Order Created" },
    "merchantOrderId": "merchant-test-ANHOGoRiG3"
  }
}

eventId: 2

eventId: 3

eventId: 4

eventId: 8

eventId: 9

Important Considerations

• Security: Always verify the X-TLP-SIGNATURE header to ensure the callback originates from Tylt.

• Response: Always return an HTTP 200 response with "ok" in the body to acknowledge successful receipt of the web-hook.

• Manual Retry: In case of missed callbacks, use the tylt.money dashboard to manually resend the webhook.