Webhooks
Webhooks allow you to receive real-time notifications when order or transaction statuses change — no need to poll the API.
Recommended approach
Use webhooks as your primary method for tracking order statuses. API endpoints like GET /orders/{id}/status have strict rate limits (3–5 req/min per order) and should only be used as a fallback.
Setup
- Go to the Partner Panel → Settings → Callback URLs
- Add your Webhook URL for both
SANDBOXandPRODUCTIONenvironments
Use separate URLs
Please use different URLs for SANDBOX and PRODUCTION environments to avoid mixing test and live data.
How it works
- We send a
POSTrequest to your Webhook URL with a JSON body - Your endpoint should respond with HTTP
200 OKto confirm receipt - If we don't receive a
200response, we will retry the webhook up to 3 times with increasing delays (1 min, 5 min, 15 min)
Event types
| Event type | Description | When it fires |
|---|---|---|
CHECKOUT_STATUS_CHANGED | Payment status update | Only if you use our payment system |
ORDER_STATUS_CHANGED | Order status update | For all partners — on every status change |
ORDER_CONFIRMATION_RECEIVED | PDF confirmation received | When the national provider sends the vignette confirmation file |
If you process payments yourself, skip the
Transactionssection and go to Orders.
Transactions
(Only for partners using our payment system)
"event_type": "CHECKOUT_STATUS_CHANGED"
| Status | Description |
|---|---|
CREATED | Payment URL has been created and provided to the partner |
SUCCESS | User's payment has been successfully captured |
FAILED | An error occurred during payment |
Example payload — single order:
Code
Example payload — multiple orders in one transaction:
Code
Orders
(For all partners)
Order status changes
"event_type": "ORDER_STATUS_CHANGED"
| Status | Description |
|---|---|
CREATED | Order is successfully paid and ready for registration with the national provider |
PENDING | Order has started authorization with the national provider |
DEFERRED | Order is scheduled for future activation |
ACTIVE | Order is successfully registered — vignette is valid |
REFUNDED | Order has been refunded (via cancel or chargeback) |
Example payload:
Code
Confirmation file received
"event_type": "ORDER_CONFIRMATION_RECEIVED"
This webhook is sent when we receive the official PDF confirmation from the national provider. The pdf_url field contains the direct link to the confirmation document.
Example payload:
Code
One webhook per order
If a transaction contains multiple orders, each order sends its own webhooks separately. One order webhook contains information about only one order.
Complete webhook flow
A typical order lifecycle produces the following webhooks in sequence:
Code
When to show confirmation to user
After receiving ORDER_STATUS_CHANGED → ACTIVE, the vignette is already valid and the user can drive. The ORDER_CONFIRMATION_RECEIVED webhook with pdf_url may arrive a few seconds to minutes later — use it to provide the official confirmation document to the user.
For more details on all available statuses, see Statuses list.