Skip to main content

​
Webhook Events

​
Order events

These events are sent to both direct merchants and partners.
EventDescriptionWhen it firesStatus
order_paymentPayment completed successfullyAfter buyer completes paymentActive
order_createdOrder was createdAfter order is created via APIUpcoming
order_confirmedOrder confirmed by gatewayAfter gateway confirms paymentUpcoming
order_cancelledOrder was cancelledAfter cancellation via API or timeoutUpcoming
order_refundedRefund processedAfter refund is completedUpcoming
Currently, order_payment is the active event for payment notifications. The remaining order events are planned and will be available in a future release.

​
Partner events

These events are sent only to partners. See Partners — Webhooks for setup details.
EventDescriptionWhen it firesStatus
store_onboardedA new store completed onboardingAfter a store activates on the partner’s platformActive
store_updatedStore configuration changedAfter a store updates its settingsUpcoming
store_deletedStore was removedAfter a store is deactivatedUpcoming

​
Payload structure

All webhook payloads follow the same structure: 
{
  "event": "order_payment",
  "data": {
    "id_order": 12345,
    "id_external": "order-12345",
    "status": "confirmed",
    "amount": 50000,
    "currency": "COP",
    "payment_gateway": "nequi",
    "created_at": "2025-01-18T10:30:00.000Z",
    "confirmed_at": "2025-01-18T10:31:15.000Z"
  }
}
The id_external field contains the order_key you provided when creating the order. Use it to match webhooks to your internal records.