Changelog

Pay-ins include the sender's details

Pay-in webhooks and pay-in responses now fill in the sender's details for bank inflows: customerAccountName, customerAccountNumber, customerBankName and sessionId. Before this fix, these fields could be empty.

Pay-ins show which account received the funds

Pay-in webhooks and pay-in responses now include a recipient object with the name and number of the account that was credited.

"recipient": {
  "accountName": "Ada Okafor",
  "accountNumber": "8012345678"
}

Either field is null when the provider does not return it. See the webhook events reference.

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.

FX swap

You can now convert NGN into USD, EUR or GBP:

• initiate a swap, then get a swap or list your swaps,
• check balances in each currency, and
• view rate history.

Swaps send FX_SWAP_CREATED and FX_SWAP_COMPLETED webhooks. Swaps can be limited to operating hours; outside them, the API returns an error with the next available time.

See the swaps guide.

Checkout payments send checkout events

Pay-in webhooks for payments made through checkout now set event_type to:

• CHECKOUT_COMPLETE when the payment succeeds, or
• CHECKOUT_FAILED when 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.