Guides
Customer messages
What your customers get by email, Telegram and WhatsApp, and when.
Abuna messages your customers about their subscription for you: what to pay, what they paid, and when their plan ends. You don't write or send any of these messages yourself.
Every message goes by email. It can also go to Telegram or WhatsApp, if the customer picks one. Telegram is on by default, on every plan. WhatsApp is off until you turn it on, and it needs the Plus plan or higher in Live.
Messages are in French or English, in the customer's language. A customer with no language set gets them in French. Amounts and dates follow the language: 5 000 FCFA and 4 oct. 2026 in French, FCFA 5,000 and 4 Oct 2026 in English.
What customers receive
Each message has a kind, shown here in parentheses. The Notices API uses the same names.
- Subscription started (
subscription_started): 30 minutes after a subscription is created, if the first period isn't paid by then. It asks the customer to pay for the first period and links to the pay link. A customer who pays at checkout gets only the receipt. In Test mode it is recorded when the subscription is created. - Payment received (
payment_received): a receipt, after every successful payment. When the payment puts an upgrade in force, the receipt also says the plan changed. For an invoice you marked paid, it says you recorded the payment. - Payment failed (
payment_failed): when a payment fails after the customer left the pay page, with the reason. For example, they never approved it on their phone. A decline the customer sees on the pay page sends nothing. The customer gets at most one an hour for the same invoice. - Renewal coming up (
renewal_upcoming): when the renewal invoice goes out before the paid period ends, 3 days before by default. It has the amount due, the pay-by date and the pay link, and the customer can pay right away. With daily reminders on and Renewal invoice at 0, or with a downgrade scheduled, it goes out 3 days before the period ends without a pay link. It then says the link comes on the renewal date. - Renewal due (
subscription_renewed): when a renewal invoice goes out as its period starts, with the amount due and a pay link. It asks the customer to pay to renew the plan. - Payment reminder (
payment_overdue): once a day while a renewal is unpaid, with daily reminders on. - Last reminder (
payment_final_notice): 1 day before an unpaid subscription is canceled, with daily reminders on. With 1 day to pay, it goes out halfway through that day. - Subscription ending (
subscription_cancel_scheduled): when you or the customer set a cancel for the end of the paid period. It says the date the subscription ends and how to keep it. - Subscription continues (
subscription_cancel_undone): when a scheduled cancel is undone. One short confirmation. - Subscription canceled (
subscription_canceled): when the subscription ends. That is right away when you or the customer cancel now, at the end of the paid period for a scheduled cancel, or when it ends unpaid. A first checkout that's never paid ends without a message. - Plan change offered (
plan_change_offered): when you offer the customer another plan from the dashboard, and each time you resend it. It names the new plan's amount after any discount the customer holds, and links to the page where they accept it. A plan change sessiondoesn't send it. - Plan switch requested (
plan_switch_requested): when a customer checks out another price of the product they subscribe to. It links to the page where they confirm the switch; nothing changes until they do. It goes by email only. See Switching plan at checkout. - Plan upgraded (
plan_upgraded): when an upgrade takes effect, with the new plan and the new billing date. If the new period still has to be paid, it has the amount due and the pay link. An upgrade that takes effect when the customer pays sends the receipt instead, so they get one message. - Upgrade to pay (
plan_upgrade_due): when an upgrade waits for the customer to pay the rest of the new plan, with the amount, the pay-by date and the pay link. It says the customer stays on their plan if they don't pay. If the upgrade replaced a scheduled cancel, it says the subscription still ends on its date. Nothing is sent when the upgrade lapses. - Downgrade scheduled (
plan_downgrade_scheduled): when a downgrade is set for the end of the paid period, with the new plan and the date it starts. - Downgrade undone (
plan_downgrade_undone): when you or the customer undo a scheduled downgrade. It says the customer keeps their plan, with the next billing date and amount. - Price change (
price_change_scheduled): when you schedule a new amount for a price and current subscribers will move to it, with the amount they will pay, after any discount, and the date it first applies to them. Customers get at least 14 days' notice. Customers who subscribe while the change is pending get it when they subscribe. - Price change canceled (
price_change_canceled): when you cancel that change, or replace it with one that keeps current subscribers on the old amount. It says their price stays the same. - Email code (
email_code): when the customer changes their email in the customer portal. It goes by email to the new address only, with a 6-digit code. Their email changes once they enter the code in the portal, within 15 minutes. - Contact details changed (
contact_changed): when the customer changes their email or phone number in the customer portal. It goes to their old email address and their connected Telegram chat, never to the new address. It shows the new email partly hidden. - Subscription links (
portal_links): when a customer asks for links to their subscriptions on your page. It goes by email only, at most once every 5 minutes.
Emails come from <your app's name> via Abuna, and customer replies go to your support email. Each email ends with your support email or support URL and a link to the customer portal. Until the customer connects Telegram, it also has a link to get the same messages there.
Emails about an ended subscription, subscription links and email codes leave out the portal and Telegram links. When you set your own terms, the footer links them. On the Free plan, the footer also says Billed with Abuna. Set your support email and terms in the dashboard, under Settings, General, Customer support.
Dates and times show in your app's time zone. New apps start on Cameroon time. Change it under Settings, General, Time zone.
When reminders go out
Renewals are billed in advance: the new period starts on the renewal date, even if the customer pays early. Set both numbers below in Settings, General, Renewals and days to pay.
- Renewal invoice: how many days before the paid period ends the invoice goes out. 3 by default, 0 to 7, and never earlier than halfway through the period. The customer can pay it from then.
- Days to pay: you set how many days customers have to pay, from 1 to 14, counted from the renewal date. If a renewal is still unpaid after that, Abuna cancels the subscription and tells the customer. New apps start at 3.
By default, a customer hears about each renewal twice:
- When the renewal invoice goes out, with its pay link: 3 days before the paid period ends, or on the renewal date with Renewal invoice at 0.
- If it's still unpaid when your days to pay run out, Abuna cancels the subscription and tells them.
Receipts and failed-payment messages go out as usual on top of these.
Daily reminders
Turn on Daily reminders in Settings, General, Customer messages to remind customers every day until they pay. On top of the two messages above:
- Each day after the renewal date, while the invoice is unpaid, they get a reminder.
- 1 day before the cancel, they get a last reminder instead.
- With Renewal invoice at 0, they also get a heads-up 3 days before the period ends, without a pay link.
For example, with 3 days to pay, that is a reminder 1 day after the renewal date, the last reminder at 2 days, and the cancel at 3 days. With 1 day to pay, the last reminder goes out 12 hours before the cancel.
Daily reminders are off for new apps. In Live they need the Plus plan or higher; on Free, Live apps send only the two messages. In Test mode they work on every plan, so you can try both schedules. A customer who pays, or whose subscription ends, gets no further reminders.
While a Live app can't take payments, for example with no payment provider connected, renewal invoices and reminders wait, and nobody is canceled for not paying. Once the app takes payments again, the customer gets the reminder that's due then, with the pay link.
Where reminders go
Email always goes out. When your app has WhatsApp or Telegram on, the payment step asks the customer to connect one under Payment reminders before they pay. Pay stays off until one is connected, so every customer who pays at checkout gets reminders on their phone. It shows each chat app only when your app has it on.
A customer has one chat app at a time: connecting WhatsApp disconnects Telegram, and connecting Telegram disconnects WhatsApp.
- The customer enters their details and goes on to the payment step.
- A customer who picks WhatsApp confirms their WhatsApp number with a code. See WhatsApp.
- A customer who picks Telegram taps Turn on Telegram reminders. Telegram opens in a new tab, where they tap Start. The bot confirms, and the payment step shows Telegram as on when they come back.
- The customer pays. The done screen says where their reminders go, then takes them to your success URL after a few seconds.
A customer whose saved details include WhatsApp or Telegram, or who already gets your reminders on one, isn't asked again: the payment step says where their reminders go and lets them change it. A chat app a customer connects while saving their details is saved with them, so their next checkout with any business on Abuna uses it.
When your app has neither chat app on, checkout doesn't ask, and customers pay and get reminders by email. A free trial doesn't ask before it starts either: its done screen offers your chat apps, and the customer may skip them. A subscription you create through the API does ask: its first pay page needs a chat app on before the customer pays.
After checkout, customers can turn WhatsApp or Telegram on or off, switch between them, or choose email only, under Payment reminders in their customer portal. The portal warns them before they turn a chat app off.
Turn each chat app on or off for the whole app in the dashboard, under Settings, General, Customer messages. While one is off, checkout doesn't offer it and its messages stop for every customer. They still get email.
In Live, Telegram works on every plan, Free included, and WhatsApp needs the Plus plan or higher. In Test mode, every plan can use both.
To choose which chat app the payment step shows first, send updates_channel when you create the session. whatsapp shows WhatsApp first, telegram shows Telegram first, email offers no chat app and sends email only, and ask, the default, shows your app's chat apps in the usual order. If your app can't offer the channel you send, the checkout still opens and works like ask.
curl https://api.abuna.app/v1/apps/8ddhXCDW/sessions \
-H "Authorization: Bearer sk_test_..." \
-H "Content-Type: application/json" \
-H "Idempotency-Key: 6f1c2b9e-4d3a-4c8e-9a7f-2e5b8d1c0a43" \
-d '{
"type": "checkout",
"price_id": "Zt6YbN3q",
"customer": {"email": "ana@example.com"},
"success_url": "https://example.com/welcome",
"updates_channel": "telegram"
}'Each customer has an updates object with the status of their Telegram and their WhatsApp: off, active or stopped. Telegram can also be pending until they turn it on, and WhatsApp can be failed. WhatsApp is never pending: it is active as soon as the customer confirms their number and chooses it.
The object never has a chat ID or a phone number. Every change to it sends a customer.updates_changed event, and the checkout's session.completed event carries the same updates.
While Telegram is pending, its connect_url is a link that turns it on: show it in your app as a Turn on reminders button. It is null in every other status.
Grant access from webhooks, not the success page
A customer may close the tab before checkout sends them to your success URL. Don't give access when the customer reaches your success page. Give it when subscription.paid reaches your webhook URL, and extend it on each invoice.paid.
Abuna sends both once the payment succeeds, whether or not the customer came back. See Webhooks for how to verify them.
// Inside the verified webhook handler from the Webhooks guide.
if (event.type === "subscription.paid") {
// The first payment went through, whether or not the customer came back to your site.
const { subscription, customer_id } = event.data;
await grantAccess(subscription.metadata.user_id, subscription.id, customer_id);
}
if (event.type === "invoice.paid") {
// Every payment, renewals included. Extend the access you gave.
await extendAccess(event.data.subscription_id);
}Telegram
Telegram is on by default for every app, on every plan. Each email has a Get your subscription messages on Telegram link. When the customer opens it and taps Start, Abuna's bot connects their chat.
From then on, each message goes to both their email and their Telegram. Subscription links still go by email only. Customers can also renew right from the chat, approving the payment on their phone.
- Each link works once. Once a chat is connected, emails stop carrying the link, so a forwarded email can't move the customer's messages to someone else's chat. The customer portal still shows it.
- Only private chats can connect. A group chat would show one customer's pay links to everyone in it.
- If the customer connects another Telegram account, messages move to it, and the old chat is told.
- The customer can send
stoporarrêtto the bot at any time, in any case. Messages then go by email only, and none still waiting go to Telegram. Their Telegram status becomesstoppeduntil they turn it on again.
WhatsApp is optional and off for new apps. Turn it on in the dashboard, under Settings, General, Customer messages. In Live it needs the Plus plan or higher; in Test mode it works on any plan.
The renewal invoice, the last reminder before an unpaid subscription is canceled, and failed payments always reach WhatsApp. On Pro and Scale, daily reminders, the heads-up before a renewal, receipts, cancellations and plan changes always reach it too. On Plus, those go by email only, except a receipt for a customer who wrote to Abuna on WhatsApp in the last 24 hours. See WhatsApp by plan.
Other messages, such as a price change, reach WhatsApp only if the customer wrote to Abuna there in the last 24 hours. Subscription links go by email only. Email still goes out for every message, so a customer without WhatsApp misses nothing.
WhatsApp messages come from Abuna's WhatsApp number and name your app and the customer's plan. For example, the renewal invoice reads “Abuna here. Your Premium plan with Mboa renews on 15 March 2026. Pay FCFA 5,000 by 14 March 2026, 18:00 to keep it.” with a Renew button. The customer can renew right from the chat, approving the payment on their phone.
- Once they have paid, or started their free trial, the customer chooses WhatsApp on the checkout's done screen. The WhatsApp number field starts with the number they just paid with, and they can use another one.
- They get a 6-digit code on WhatsApp and enter it on the page.
- Once the number is confirmed, their WhatsApp is
activeright away, and they go on to your success URL like any other customer.
Until the number is confirmed, WhatsApp isn't on and reminders go by email. Customers confirm the number each time they choose it, except the number they already get reminders on.
A code works for 10 minutes and allows 5 wrong tries. The customer can ask for a new code once a minute, up to 5 times a day for the same number.
- Customers can change their number, switch to Telegram, or stop WhatsApp in their customer portal. A new number is confirmed with a code, the same way as at checkout.
- A customer can send
stoporarrêtto the WhatsApp chat at any time. Their WhatsApp status becomesstopped, and reminders go by email until they confirm the number again in their customer portal. A stop applies to the number, so it also stops WhatsApp reminders from other apps that use Abuna. - If WhatsApp can't deliver to the number, the status becomes
failedand reminders go by email. The customer can enter another number in their customer portal. - Each change of their WhatsApp status sends a
customer.updates_changedevent.
Test mode
Test customers often have real email addresses and chats, so Test mode sends only the email codes a customer needs to finish on your pages, as Live does:
- The code that starts a free trial at checkout (
trial_email_code). - The code that confirms a new email in the customer portal (
email_code). It goes to the new address. - The code for a customer's saved details at checkout (
profile_code).
They have the same limits as in Live: one code a minute and five an hour for each email address. Each code works for 15 minutes. They go to the address typed on the page, so use an address you can read, or a made-up one.
No other message is sent. Abuna records every message, sent or not, as a notification.captured event, with its subject and text. sent is true for the three code emails and false for the rest. These events don't go to your webhook URL.
With a made-up address, read the code from the event's subject. List the events to check your flow:
curl "https://api.abuna.app/v1/apps/8ddhXCDW/events?type=notification.captured" \
-H "Authorization: Bearer sk_test_..."{
"id": "01J9ZQ8E1F2G3H4J5K6M7N8P9Q",
"type": "notification.captured",
"environment": "test",
"created_at": 1727600000,
"data": {
"customer_id": "Cu5tM8rA",
"kind": "payment_received",
"channel": "email",
"recipient": "ana@example.com",
"subject": "Receipt from My store: FCFA 5,000 paid",
"text": "...",
"sent": false
}
}Check what was sent
In Live mode, list your messages with GET/v1/apps/{appID}/notices. Filter by subscription_id or by status: pending, sending, sent, failed or withdrawn. In Test mode the list holds only the free trial and email change codes.
curl "https://api.abuna.app/v1/apps/Q7mKp2Rt/notices?subscription_id=x9QbL2sK" \
-H "Authorization: Bearer sk_live_..."A message that can't be delivered ends as failed. See Notices for each field.
Emails to your team
In Live mode, your team members get their own emails when a subscription starts, a payment is received, a payment fails, a subscription is canceled, or a customer changes plan. Scheduling a cancel for the end of the paid period, or undoing it, counts as a cancel. A plan change is an upgrade taking effect, or a downgrade scheduled or undone.
Each member picks which emails they want, and whether they come right away or once a day, under Notifications in their profile. A first payment or a paid upgrade is one email, not two. Team emails are in English.
A failed payment email goes out only when the customer didn't see the failure on the pay page, for example when a payment fails after they left it. A failure the customer sees on the pay page sends no email to them or to your team.
A renewal still unpaid when its paid period ends, so the subscription is past_due, appears in the daily summary of every member who chose A payment fails, even if they get their other emails right away.