Webhooks typically maintain a consistent information structure across various instances, with the primary differentiating factor being the unique webhook event that prompts their activation. In essence, while the core data format remains uniform, it's the distinctive event, such as a user registration or a purchase confirmation, that gives each webhook its specific purpose and relevance within the broader application or system.
{
"payment":{
"id":"99a337b3-3a7d-4e0b-b5ea-7098b562d4dd",
"status":"pending",
"currency":"COP",
"amount":"180000",
"external_id":"814",
"phone": "+573155555555",
"title":"Renta PAZCNTPDG0 mes mayo Rondoo",
"description":"PAZCNTPDG0",
"document_link":"https://s3.us-east-2.amazonaws.com/rondoo.co/invoices/8b4995be-1c01-47f6-8ee2-d0d60022f746",
"allow_credit":true,
"allow_debit":true,
"created_at":"2023-07-13T15:42:12.000000Z",
"paid_at":null,
"deletable":false,
"amount_label":"$180.000",
"payment_link":"https://wa.me/+573126761889?text=Pagar ref: 99a337b3-3a7d-4e0b-b5ea-7098b562d4dd",
"message_status": "delivered",
"customer":{
"first_name":"Daniela",
"last_name":"Lozano",
"email": "[email protected]",
"phone":"+573155555555"
}
},
"event":{
"type":"payment.created",
"timestamp":1689262934
}
}
Events
This is the list of available events.
payment.created
payment.deleted
payment.rejected
payment.approved
Payment Statuses
pending
cancelled
approved
declined
in_progress
refunded