Skip to main content
Webhooks notify your application when a transaction changes status. In every transaction notification, details.description contains the payment description recorded for that transaction. It is always a string and is "" when no payment description is available. details.message reports the status change. Webhooks v3 keeps the same configuration and notification contract as v2. Get a token with POST /v3/auth/login and send Authorization: Bearer {accessToken} with configuration and log requests. The callback url must use HTTPS with a domain name; IP addresses and local domains are not accepted. If configured, apiKey is sent to your receiver in the x-api-key header. status defaults to ACTIVE. Creating or updating a webhook returns HTTP 200.

Create a Webhook

Response

List Webhooks

Response

Retrieve a Webhook

Response

Update a Webhook

Response

Virtual Account Transaction Payload

deposit_virtual_account

Collections received in virtual accounts send transaction notifications with this transactionType and status: "completed_transaction":
details.amount is a string, and details.currency contains the fiat code. This webhook type does not include transactionHash. details.description is the transfer note written by the sender when sending the transfer from their bank, as reported by the provider. It is not set by Mesa de Pagos or the partner. If the sender did not write a note, "" is sent. It always includes these fields: details.payer identifies who sent the transfer, using the data reported by the provider: details.payer is omitted if the provider does not report the sender’s name.

Deposit Express Transaction Payload

deposit_express

Payer details

details.payer is optional for deposit_express and deposit_virtual_account. It is included when a payer detail is recorded for the transaction and omitted otherwise. Other transaction types do not include this object. The ATC v2 confirmation webhook does not provide documentType, so this field may be absent even when payer is included.

Crypto Transaction Payloads

withdrawal_crypto

deposit_crypto

transactionHash is included when the blockchain provider supplies it and can be used to look up the operation in the corresponding network explorer.

Logs

Query Parameters

Response

Supported Events

Transaction subscriptions use events.transaction. Business client notifications use events.businessClient with business_client_status_updated. On update, omitted subscription categories keep their existing values; send an empty array to clear a category. Log pagination defaults to page=1 and limit=10, with a maximum limit of 100. See the Webhooks API reference for request and response schemas.