Changelog

Opay on checkout

Customers can now pay with Opay on the hosted checkout page.

See the checkout guide.

Amounts are always positive

amount is now always a positive number in transaction, payout, checkout, card, payment link and FX swap responses. Use the transaction type to tell money in from money out.

What you need to do

If you relied on a negative amount for outflows, use the transaction type instead.

Checkout redirects fall back to your redirect URL

When a checkout has no redirect_url, customers are now sent to the redirect URL set on your account after they pay. Atlas adds checkoutReference to the query string so you can match the customer to the checkout.

https://example.com/payment-complete?checkoutReference=CHK_123456

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.

More ways to look up a checkout

New checkout endpoints:

• verify a checkout by reference,
• verify a checkout by source reference, and
• list a checkout's transactions by reference.

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.

Checkout transactions confirm faster

Checkout transactions now show successful as soon as Atlas is notified of the inflow, instead of waiting for the inflow to be fully resolved.

What you need to do

Nothing. If you poll checkout status, you see successful sooner.

Checkout amount must be at least 100

The amount you send to initiate a checkout must now be at least 100. Smaller amounts fail validation.

What you need to do

Check amounts before you initiate a checkout, and don't offer checkout for totals under 100.

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.

`source_reference` is required for checkouts and API payouts

source_reference is now required when you:

• initiate a checkout, and
• create a bank transfer payout through the API.

Requests without it fail validation.

What you need to do

Send your own ID for the request as source_reference, and store it so you can look the record up later.

{
  "amount": 5000,
  "currency": "NGN",
  "source_reference": "order_10234"
}

Look up checkouts and payouts by your source reference

You can now find records using source_reference, the ID you assign when you create them.

• List checkout transactions by source reference.
• Get a payout transaction by source reference.
• List payouts and get a payout by reference.

Payout and transaction responses now include sourceReference.

Card payments on checkout

Customers can now pay by card on the hosted checkout page.

Card payments have to be enabled for your business before they appear on checkout. Contact the Atlas team to turn them on.

See the checkout guide.

Checkout transactions include the session ID

Checkout transaction responses now include sessionId, the session ID the bank assigns to the transfer. Use it to trace a payment with the paying bank.

See the checkout guide.

Atlas is live in Nigeria

Atlas is now available to businesses in Nigeria. You can integrate through the API or work directly in the dashboard.

• Checkout: start a checkout and let customers pay by bank transfer. See the checkout guide.
• Payouts: send NGN to any Nigerian bank account. See the payout quickstart.
• Customers: create, update, blacklist and reactivate the customers you transact with.
• Transactions: list your transactions or look one up by reference.
• Wallets: check your wallet balance.
• Banking: fetch the list of supported banks and confirm an account name before you pay out.