Webhook events - Lynq developer documentation

Webhook payloads use a common event envelope. Lynq currently sends payment_intent.succeeded after successful payment completion.

Event envelope

{
  "id": "evt_...",
  "object": "event",
  "type": "payment_intent.succeeded",
  "createdAt": "2026-08-07T12:00:00.000Z",
  "environment": "live",
  "data": {
    "id": "pi_...",
    "object": "payment_intent",
    "amount": 2500000,
    "currency": "AMD",
    "status": "succeeded",
    "orderId": "order_123",
    "createdAt": "2026-08-07T11:59:00.000Z"
  }
}

Use the event ID to deduplicate delivery and data.orderId to locate your order.

Field	Type	Description
`id`	`string`	Unique event identifier. Also sent in the `Lynq-Event-Id` header.
`object`	`"event"`	Object discriminator.
`type`	`string`	Event type. Use this value to dispatch handling.
`createdAt`	`string`	ISO timestamp when Lynq created the event.
`environment`	`"test" \| "live"`	Environment that produced the event.
`data`	`object`	Resource associated with the event.

`payment_intent.succeeded`

Sent after a Payment Intent succeeds.

Data field	Type	Description
`data.id`	`string`	Payment Intent ID.
`data.object`	`"payment_intent"`	Resource discriminator.
`data.amount`	`number`	Paid amount in minor currency units.
`data.currency`	`string`	Payment currency.
`data.status`	`"succeeded"`	Final payment status for this event.
`data.orderId`	`string`	Merchant order identifier supplied at Payment Intent creation.
`data.createdAt`	`string`	Payment Intent creation timestamp.

Receiver rules

Verify Lynq-Signature before trusting any field.
Deduplicate by event ID, not only by Payment Intent ID.
Match orderId, amount, and currency to your stored order.
Treat unknown event types as non-destructive: record them and return 2xx if the envelope is valid, unless your operational policy requires review.
Keep event handling backward-compatible with additional fields.

See Verify webhooks for signature verification and retry behaviour.

Last modified on August 8, 2026