Atlas DocumentationChangelog
New features, improvements and fixes to the Atlas API and dashboard.
May 2026
Checkout webhooks use `event_type`
Checkout webhooks now send the event name in event_type, like every other Atlas webhook. The eventType field introduced on 22 May 2026 is no longer sent.
{
"event_type": "CHECKOUT_COMPLETED",
"data": { "...": "..." }
}What you need to do
Read event_type from checkout webhooks. If you read eventType, switch to event_type.
See the webhooks guide.
Dedicated checkout webhooks
Checkout payments now send a dedicated checkout webhook, with the checkout in the payload. The pay-in webhook is no longer sent for payments made through checkout.
Checkout webhooks use these events:
CHECKOUT_PROCESSED: the payment was received and is being processed.CHECKOUT_COMPLETED: the checkout was paid.CHECKOUT_FAILED: the payment failed or the checkout was cancelled.
On this date the event name was sent in an eventType field. It was renamed on 26 May 2026; see checkout webhooks use event_type.
What you need to do
Handle the checkout events above for checkout payments. Pay-in webhooks still arrive for inflows that are not linked to a checkout.
See the webhooks guide.
March 2026
Checkout payments send checkout events
Pay-in webhooks for payments made through checkout now set event_type to:
CHECKOUT_COMPLETEwhen the payment succeeds, orCHECKOUT_FAILEDwhen it fails.
Before this change they used IN_FLOW_SUCCESS_EVENT, the same event as other inflows. Pay-ins that are not linked to a checkout still use IN_FLOW_SUCCESS_EVENT. Checkout pay-in payloads also include checkoutReference.
These events were replaced on 22 May 2026; see dedicated checkout webhooks.
What you need to do
If you matched checkout payments on IN_FLOW_SUCCESS_EVENT, also handle CHECKOUT_COMPLETE and CHECKOUT_FAILED.