# Changelog > What changed in the Abuna API, newest first. Source: https://abuna.app/docs/changelog Every change to the API, newest first. [API changes](https://abuna.app/docs/api-changes.md) explains which changes come with notice. ## 18 November 2026: Checkout shows the code field when a code can be used Changed: checkout sessions and checkout links show **Add promotion code** while your app has at least 1 code a customer can use on the price. Before, only a session with `allow_promotion_codes: true` showed it. To keep codes off a session, send `allow_promotion_codes: false`. A session with `discounts` still has no code field. On the [session object](https://abuna.app/docs/api/sessions.md#object), `allow_promotion_codes` is now null for a checkout that didn't send it, including checkouts created before this change. See [Let customers type the code](https://abuna.app/docs/guides/promotion-codes.md#checkout). ## 13 November 2026: Prices in XOF and USD New: apps and prices can be in `XOF` or `USD` as well as `XAF`. USD amounts are in cents, so `1000` is $10.00. Customers still pay by mobile money in FCFA, in their network's currency. Between XOF and XAF the amount converts 1 to 1. A USD amount is charged at the day's exchange rate plus 2%, rounded up to a whole franc, and the 2% is part of what you receive. The customer sees the FCFA amount before approving the payment, and hosted pages show both, like `$10.00 ยท FCFA 6,039`. See [Paying in FCFA](https://abuna.app/docs/amounts-currencies-and-timestamps.md#paying-in-fcfa). New fields on the [payment object](https://abuna.app/docs/api/invoices-and-payments.md#payment-object): `original_amount`, `original_currency`, `exchange_rate`, `exchange_margin_bps` and `exchange_rate_at`. `amount` and `currency` still say what the customer was charged. Payments made before 13 November 2026 have the five new fields `null`. [`invoice.paid`](https://abuna.app/docs/api/events.md#invoice-paid) and [`invoice.payment_failed`](https://abuna.app/docs/api/events.md#invoice-payment-failed) now carry the payment as `payment`. The invoice's own `amount` and `currency` stay in the price's currency. New error: paying a USD invoice returns `503` with code [`exchange_rate_unavailable`](https://abuna.app/docs/errors.md#error-codes) when no recent exchange rate is available. Nothing is charged. Try again later. Plan changes between prices in different currencies are still refused with `price_not_eligible`. ## 8 November 2026: Delete a customer New: [`DELETE /v1/apps/{appID}/customers/{id}`](https://abuna.app/docs/api/customers.md#delete) deletes a customer when they ask you to delete their data. Their subscriptions end as if you canceled them, and their personal details are erased. Their invoices, payments, and amounts stay, so your totals don't change. New event: [`customer.deleted`](https://abuna.app/docs/api/events.md#customer-deleted). When you get it, delete your own copy of the customer's details. ## 31 October 2026: Checkout asks for a chat app before payment Changed: when your app has WhatsApp or Telegram on, the payment step asks the customer to connect one, and they can pay only once it is on. This replaces the choice on the done screen after payment, which now just says where reminders go. A customer whose saved details include a chat app, or who already gets your reminders on one, isn't asked again. With neither chat app on, or a session with `updates_channel` `email`, checkout pays as before with email reminders. Free trials still offer chat apps once they start. The first pay page of a subscription you create through the API asks too.`session.completed` for a paid checkout comes with the chat app already on. See [Where reminders go](https://abuna.app/docs/guides/customer-notifications.md#reminder-channel). ## 29 October 2026: Checkout asks for the phone on the payment step Changed: the first step of checkout asks only for the customer's email, with their name optional. The payment step asks for the phone number, and on Cameroon numbers the network comes from the number. A `customer.phone_number` you send on a checkout session becomes the payment step's number, and the customer can choose another there. A customer who came through checkout now has `phone_number` `null` until they pay, which after a free trial is the first invoice. Their first successful payment saves the number that paid and sends [`customer.updated`](https://abuna.app/docs/api/events.md#customer-updated) with `updated_by` `customer`. Accept a `null` phone number, and take the number from that event. [Charging an invoice](https://abuna.app/docs/api/invoices-and-payments.md#charge) for a customer with no phone number returns `422` `phone_required`. See [Prefill the customer](https://abuna.app/docs/guides/sessions.md#prefill-the-customer). ## 29 October 2026: Reminders are chosen after payment Changed: checkout no longer asks where reminders go, or confirms a WhatsApp number, before the customer pays. Once the first payment succeeds, or a free trial starts, the done screen offers your app's chat apps, with WhatsApp starting on the number that just paid. `updates_channel` now sets which chat app comes first, and `email` still offers none. `customer.updates_changed` also fires when the customer chooses there. See [Where reminders go](https://abuna.app/docs/guides/customer-notifications.md#reminder-channel). ## 29 October 2026: Test mode emails its codes Changed: in Test mode, three email codes now go out as in Live: the code that starts a free trial, the code that confirms a new email in the customer portal, and the code for a customer's saved details. They have the same limits as in Live. Every other Test message is still recorded and not sent. The code pages look the same as in Live and no longer show the code. In [`notification.captured`](https://abuna.app/docs/api/events.md#notification-captured), `sent` is now `true` for these codes, and a `profile_code` event has no `customer_id`. In Test, the [notices list](https://abuna.app/docs/api/notices.md) now holds the free trial and email change codes. See [Test mode](https://abuna.app/docs/guides/customer-notifications.md#test-mode). ## 19 October 2026: WhatsApp messages by plan Changed: on Plus, WhatsApp carries the messages that get renewals paid: the number's confirmation code, the renewal invoice, the last reminder before an unpaid subscription is canceled, and failed payments. Pro and Scale also send daily reminders, the heads-up before a renewal, receipts, cancellations and plan changes on WhatsApp. On Plus, those go by email, and a customer who wrote to Abuna on WhatsApp in the last 24 hours still gets their receipt there. In Test mode, every plan gets every message. Nothing in the API changed. See [WhatsApp by plan](https://abuna.app/docs/guides/plans-and-limits.md#whatsapp). ## 19 October 2026: New wording, same API Changed: the docs, the dashboard, customer pages, emails and chat messages now describe Abuna as recurring billing for the mobile money ecosystem, with one word for each idea. Nothing in the API changed: endpoints, fields, event types, error codes and webhook payloads stay the same. Your customers see shorter, clearer text in emails, on checkout and pay pages, and in Telegram. WhatsApp reminders read as before. ## 16 October 2026: Returning customers at checkout Changed: a customer who comes back to a checkout with the email they already subscribe with no longer starts a second subscription to the same product. Only the email counts, never the phone number. They go back to an unpaid first payment of the same price, or are refused with `already_subscribed` for a price they already pay for. For another price of the same product, Abuna emails them a link to switch their plan, and the page asks them to check their email. An unpaid subscription to another price of the product stays as it is. New: checkout sessions take `upgrade_timing`, `now` or `next_renewal`, for when a switch to a higher price takes effect, and the session object returns it. `subscription.updated` has the new change types `upgrade_scheduled` and `upgrade_undone`. A checkout session that switches a plan completes with the plan change fields and stays open as long as the plan change offer, up to 7 days. See [Returning customers](https://abuna.app/docs/api/sessions.md#returning-customers). ## 14 October 2026: Abuna payments New: a Live app can take payments without a provider account of your own, through Abuna payments. Abuna keeps 3.5% of each successful payment. It pays you the rest each day at 08:00 Cameroon time, for the previous day's payments, by mobile money, once your balance is above FCFA 100. The [app object](https://abuna.app/docs/api/apps.md#object) has `payments.abuna_payments`, and payments have `net`, what you get from a payment through Abuna payments. See [Abuna payments](https://abuna.app/docs/guides/payment-providers.md#abuna-payments). ## 10 October 2026: Choose your webhook events New: your webhook URL receives only the event types you choose in the dashboard, with a **Recommended** set for a standard integration. The [app object](https://abuna.app/docs/api/apps.md#object) has `webhook_events`, and `GET /v1/event-types` lists every event type and which ones are recommended. Webhook URLs you already had keep receiving every event type they received before. See [Choose your events](https://abuna.app/docs/guides/webhooks.md#choose-events). ## 9 October 2026: Payment accounts belong to your team Changed: payment provider accounts now belong to your team, not to one app. A team owner connects each account once, on the team's **Payment accounts** page, and any app in the same mode can use it, with one provider webhook URL for all of them. Accounts you had already connected keep their credentials and their provider webhook URL. See [Connect your account](https://abuna.app/docs/guides/payment-providers.md#connect). ## 7 October 2026: Accent color on customer pages New: the [app object](https://abuna.app/docs/api/apps.md#object) has `branding.accent_color`, the color your checkout, payment, and subscription pages and your invoices use for the main button, links, and selected choices. You set it in the dashboard. ## 6 October 2026: Copy products between Test and Live New: [`POST /v1/apps/{appID}/products/copy-from-test`](https://abuna.app/docs/api/products.md#copy-from-test) copies products and prices from an app's Test mode to its Live mode, and [`POST /v1/apps/{appID}/products/copy-from-live`](https://abuna.app/docs/api/products.md#copy-from-live) copies them from Live to Test. Copies are linked both ways: copying again, in either direction, updates them and never makes new ones. New error codes: `live_app_required`, `test_app_required`, and `test_app_missing`. ## 4 October 2026: Launch The Abuna API is live. Everything these docs describe is available in Test mode and Live mode.