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 identifiers in the payload — for
example paymentRequestId / paymentId on payment webhooks, or the
relevant id for consent and automatic-payment-request events.
Webhook event payload (example)
For payment notifications (including Automatic Pix legs), the body is often a compact JSON object with ids and timestamps. Use these values to call the matching GET APIs and read the current status — do not treat the webhook as the source of truth for settlement details.
{
"paymentId": "a9d0f040-4db9-48da-8ef5-de1d831ec75f",
"paymentRequestId": "d03cb57a-62d0-444d-8689-ebab21173e0e",
"paymentType": "AUTOMATIC_PAYMENTS",
"statusUpdateDateTime": "2025-09-25T15:27:46.544Z",
"rejectReason": null
}Payload fields
| Field | Description |
|---|---|
paymentId | Unique id of the payment leg whose status changed (automatic payment installment or single payment row). Use this when calling payment-scoped GET endpoints. |
paymentRequestId | Id of the parent payment request (consent / request container). Use it with Get payment request or the equivalent API for your journey. |
paymentType | Product lane for this notification (for example AUTOMATIC_PAYMENTS for Automatic Pix). Other values may appear for Instant Pix, scheduled Pix, etc. |
statusUpdateDateTime | ISO 8601 timestamp when Lina recorded this status transition on its side. |
rejectReason | Optional human-readable or coded reason from the account holder when a payment is rejected; null when the update is not a rejection or no reason was supplied. |
When you create a webhook, you choose which
event categories the URL receives. Those categories are not the same as
paymentType in the body; they describe what resource changed.
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.