Funding Records Message Push
TruBit uses webhooks to notify merchants of funding-related events in real time, such as deposits, withdrawals, crypto purchases, and refunds. When triggered, a POST request with detailed transaction data is sent to your configured webhook URL.
Endpoint Information
Request Method: POST
Request Path: (Specify the appropriate path for your webhook notifications)
Requesst Headers: Requires signature
signature(string: To verify that a webhook request is coming from trubit, you can use the signature header. The value of the header is a RSA-SHA256 signature of the request body, Use hexadecimal encoding.)
Request Body Parameters
The request body should include the following fields:
{
"webhookId": "ebab8a9663704e7cbbebe672c7c67912", // (number: ID of the webhook)
"eventType": "FUNDING_WEBHOOK", // (string: event type [FUNDING_WEBHOOK: merchant funding event])
"txId": "1123123123", // (number: ID of the fiat claim)
"merchantId": "3", // (number: ID of the merchant)
"merchantName": "Rrturo Tellez", // (string: name of the merchant)
"fiat": "ARS", // (string: name of the fiat currency)
"totalAmount": "22.00", // (decimal: total fiat amount)
"amount": "20.00", // (decimal: actual fiat amount)
"fee": "2.00", // (decimal: amount of the fee)
"userPaymentId": "91", // (number: ID of the user payment method)
"type": "DEPOSIT", // (enum: type [DEPOSIT: The add of the funding record, WITHDRAW: The claim of the funding record, BUY_CRYPTO: The buy crypto of the funding record, REFUND: The refund of the funding record])
"status": "1", // (enum: status [1: pending, 2: completed, 3: canceled])
"createTime": "1737452292000", // (string: timestamp of the create time in milliseconds)
"updateTime": "1737452344000", // (string: timestamp of the update time in milliseconds)
"payerName": "Matias Alva", // (string: name of the entity sending funds)
"payerAccount": "CH8508843132556121020" // (string: bank account of the entity sending funds)
}Response Structure
The response will include the following fields:
Example Request
Example Response
Notes
Ensure that the webhook URL is properly configured to receive and process the notification.
The
callbackStatusindicates whether the message was successfully sent to the webhook. If it showsSUCCESS, the notification was sent without issues.
Last updated