Webhook Events

Order events

These events are sent to both direct merchants and partners.

Event	Description	When it fires	Status
`order_payment`	Payment completed successfully	After buyer completes payment	Active
`link_paid`	A payment-link order was paid	After payment on an API-created payment link (in addition to `order_payment`)	Active
`order_created`	Order was created	After order is created via API	Upcoming
`order_confirmed`	Order confirmed by gateway	After gateway confirms payment	Upcoming
`order_cancelled`	Order was cancelled	After cancellation via API or timeout	Upcoming
`order_refunded`	Refund processed	After refund is completed	Upcoming

order_payment is the active event for payment notifications. For payment links created via the API, link_paid fires alongside it for the same order. The remaining order events are planned; their payloads are not yet finalized.

Partner events

These events are sent only to partners, on the single webhook URL configured for the partner account. See Partner Webhooks for setup, and Onboarding Merchants for the flow they belong to.

Event	Description	When it fires	Status
`store_onboarded`	A merchant onboarded through the partner’s link	When the merchant finishes onboarding, and again whenever they re-subscribe through the link	Active
`integration_uninstalled`	The partner integration was removed from a store	After the merchant or the partner deactivates the integration	Active
`integration_installed`	Integration activated on a store	—	Upcoming
`store_updated`	Store configuration changed	After a store updates its settings	Upcoming
`store_deleted`	Store was removed	After a store is deactivated	Upcoming

Payload structure

All webhook payloads are a flat JSON object — fields are at the top level, not nested under a data key. Every payload includes the event name and an ISO 8601 timestamp.

`order_payment`

{
  "event": "order_payment",
  "timestamp": "2026-06-24T02:05:12.952Z",
  "id_order": 12345,
  "id_external": "order-12345",
  "status": "confirmed",
  "total_price": 50000,
  "currency": "COP",
  "payment_method": {
    "gateway": "nequi",
    "status": "processed"
  },
  "totalItems": 1,
  "shopper": {
    "first_name": "Jane",
    "last_name": "Doe",
    "email": "jane@example.com"
  },
  "external_store_id": null
}

`link_paid`

Fires for payment-link orders created via the API, in addition to order_payment.

{
  "event": "link_paid",
  "timestamp": "2026-06-24T03:19:39.159Z",
  "id_payment_link": 17624,
  "id_order": 22316,
  "id_store": 2366,
  "wallet_id": 4712,
  "status": "confirmed",
  "amount": 12312,
  "currency": "COP",
  "source": "api",
  "id_external": null
}

The id_external field contains the order_key you provided when creating the order. Use it (or id_order) to match webhooks to your internal records and to deduplicate retries.

`wallet_id`

The Wava balance wallet this payment credits — the merchant’s account inside Wava where the funds land, not the buyer’s payment method. (Nequi and Daviplata are also called digital wallets; those appear under payment_method on order_payment, and are a different thing entirely.)

Value	Meaning
An integer	The link was created bound to that specific wallet, via the `wallet_id` field on Create payment link. The payment credited it.
`null`	The link is not bound to any particular wallet. The payment credited the merchant’s default wallet for the order’s currency.

Most merchants hold a single wallet per currency, so null is the normal value and means “the merchant’s only wallet”. wallet_id is populated only for merchants who have multiple wallets enabled on their account; if you create a link with wallet_id for a merchant who does not, the field is ignored and the webhook reports null.

A null here means “this event does not name a wallet” — it is never a stand-in for a specific one. If you need to know which wallet a merchant’s funds settled into, read the wallet bound to the link rather than inferring it from the event, since a merchant can re-bind a link after it was paid.

`store_onboarded`

Partner event. Sent when a merchant who signed up through the partner’s onboarding link finishes onboarding and the partner integration is created on their store, and again whenever that merchant re-subscribes through the link. This is the event that hands a partner a merchant it can charge for — merchant_key is the credential used for that merchant’s orders and links. Handlers must be idempotent on id_store: the same merchant can produce this event more than once.

{
  "event": "store_onboarded",
  "timestamp": "2026-08-06T14:22:31.004Z",
  "id_store": 2841,
  "external_id": "your-internal-merchant-id",
  "store_name": "Café Bogotá",
  "store_url": "https://cafebogota.co",
  "status": "active",
  "merchant_key": "mk_live_9f2c7a1e4b8d6350a1c9",
  "country": "Colombia",
  "currency": "COP",
  "referred_by": null
}

Field	Notes
`id_store`	Wava’s ID for the merchant.
`external_id`	The partner’s own identifier for the merchant, taken from the `eid` parameter on the onboarding link; `null` if none was passed.
`merchant_key`	The merchant’s API key. Store it — it is not retrievable from the Partners API.
`country`	Country name (e.g. `Colombia`), not an ISO code.
`currency`	The store’s default currency (ISO 4217).
`referred_by`	Store ID from Wava’s separate store-referral program, unrelated to the partner relationship. Normally `null`.

See Onboarding Merchants for the full flow around this event.

`integration_uninstalled`

Partner event. Sent when the partner integration is removed from a merchant’s store, by either side.

{
  "event": "integration_uninstalled",
  "timestamp": "2026-08-06T16:02:44.881Z",
  "id_store": 2841,
  "external_id": "your-internal-merchant-id",
  "store_name": "Café Bogotá"
}

Getting Started

Orders

Payment Flows

Payment Links

Partners

Webhooks

Integrations

Testing

Error Handling

Webhook Events

Webhook Events

Order events

Partner events

Payload structure

`order_payment`

`link_paid`

`wallet_id`

`store_onboarded`

`integration_uninstalled`

​Webhook Events

​Order events

​Partner events

​Payload structure

​order_payment

​link_paid

​wallet_id

​store_onboarded

​integration_uninstalled

Webhook Events

Order events

Partner events

Payload structure

`order_payment`

`link_paid`

`wallet_id`

`store_onboarded`

`integration_uninstalled`