Webhooks
Lina Pay fires a webhook whenever a resource changes state (consent or
payment flows). For security, treat each notification as a signal only:
always fetch the latest status using the id you receive — for a
consent that is a payment request or automatic payment request, or for a
payment leg (payment / automatic payment).
Webhook event envelope
Typical notification body shape:
{
"data": {
"id": "webhook123",
"subTenant": "subTenant123",
"webhookUrl": "http://example.com/webhook",
"type": "PAYMENT"
},
"message": "string",
"type": "success",
"statusCode": 0
}data fields
| Field | Description |
|---|---|
id | Identifier related to the state change — use it when polling the relevant GET API. |
subTenant | Sub-tenant business identifier. |
webhookUrl | URL configured to receive this notification. |
type | Event category (see table below). |
Event type values by product
type value | Product / journey |
|---|---|
CONSENT | Instant Pix, Scheduled Pix, and recurring scheduled Pix — consent / payment-request lifecycle. |
PAYMENT | Instant Pix, Scheduled Pix, and recurring scheduled Pix — payment lifecycle. |
AUTOMATIC_CONSENT | Automatic Pix — recurring consent / automatic payment request. |
AUTOMATIC_PAYMENT | Automatic Pix — automatic payment leg. |
JSR_ENROLLMENT | JSR (redirectless) — device enrollment lifecycle. |
Next steps
- Onboarding — sub-tenant and redirect domains before Pix journeys.
- Create a webhook — register your HTTPS endpoint and event subscription.