What already runs, and what we build
Most of the integrations we do are custom builds. Paystack is different: it's one of the payment gateways our platform already runs, so the payment side is existing code rather than a new project. What's specific to you is the conversation that decides when to ask for money and what happens next.
| Part | Status | What it means |
|---|---|---|
| Paystack hosted checkout | Runs | The customer pays on Paystack's own checkout page, opened from a link in the chat |
| Payment confirmation | Runs | Paystack's webhook tells us it's paid. If a webhook is late, the platform checks with Paystack again |
| Saved cards | Runs | Paystack saved cards are supported, including the 3-D Secure approval step when the bank asks for it |
| Split payouts | Runs | Paystack split payments through sub-accounts are supported. Tell us what needs splitting and we'll confirm it fits |
| Orders from a WhatsApp storefront | Runs | Checkout for orders placed through our WhatsApp store. If you sell on Shopify or Ecwid, the catalogue syncs in and paid orders are pushed to your shop (as a draft order in Shopify) |
| The payment conversation | Build | Our engineers write the logic: the amount, the wording, reminders, and the next step once paid |
| Updating your own systems | Build | Marking a job, booking or invoice as paid in your software, through its API. QuickBooks Online invoicing is already connected, and the build decides when an invoice is raised |
Typical flows in both directions
From WhatsApp to Paystack
- The customer asks to pay. "Can I pay the deposit now?" The conversation works out the amount, creates a Paystack checkout link for it and sends it in the chat.
- The conversation asks for payment. After a booking, quote acceptance or order, the next message carries the link, so the customer never has to look up banking details or send proof of payment.
- A returning customer pays with a saved card. Paystack saved cards are supported, including the bank's 3-D Secure step if it asks for one. We confirm during the build how this fits your flow.
From Paystack back to WhatsApp
- Paid, so carry on. When Paystack confirms the payment, the conversation picks up where it paused: "Payment received, you're booked for Thursday."
- Paid, so tell your systems. The same confirmation can raise a QuickBooks Online invoice, or, as a custom build, update your job card, booking system, CRM or spreadsheet.
- Not paid yet. We can build a reminder that goes out later with the link again. Outside the customer's 24-hour window, that reminder has to be an approved utility template.
How the build works
- Connect your WhatsApp numberYou connect your own WhatsApp account through Meta's Embedded Signup. Meta bills you directly, at Meta's rates.
- Add your Paystack keysYou add your Paystack API keys to your account on our platform. Payments settle into your Paystack account as normal, and Paystack's own fees and payout schedule apply.
- We write the conversationOur engineers build the flow for your business: what the customer is paying for, how the amount is worked out, the messages before and after, and any templates for reminders or receipts.
- The customer pays on PaystackThey tap the link, pay on Paystack's hosted checkout, and return to the chat. Card details are handled by Paystack, not typed into WhatsApp.
- Confirmation and next stepPaystack's webhook confirms the payment, with polling as a back-up if the webhook is slow. The conversation resumes and, if you want, your other systems are updated.
Setting up Paystack itself is not the long part, because it already runs. The time goes into the conversation and into any connection to your own software, which depends on what that software's API allows. For other systems, see connecting WhatsApp to your own software.
What it costs to run
Three separate bills, and we add nothing to the first two:
- Paystack. Paystack's transaction fees, on your own Paystack account. See Paystack's pricing page for current rates.
- Meta. A payment link sent while the customer's 24-hour window is open is a service message: US$0.0095 per delivered message in South Africa from 1 October 2026, after the first 1,000 service messages per number each month. A reminder or receipt sent outside the window is a utility template, also US$0.0095. Utility templates sent inside the window are charged too. See our pricing page for a rand calculator.
- Euphony. A one-off build from R15,000 ex VAT, plus R7,500 per integration, then a monthly fee from R4,950 ex VAT to run it.
Source: Pricing on the WhatsApp Business Platform, Meta for Developers (updated 30 September 2026) · Customer service windows
What you need to provide
- An activated Paystack business account that can take live payments, and its API keys.
- Your WhatsApp number, connected through Meta's Embedded Signup, and a payment method in WhatsApp Manager for Meta's message charges.
- What customers pay for and how the amount is set: a fixed fee, a price from your list, or an amount from your system.
- If payouts should be split, the Paystack sub-accounts and how the split should work.
- Where a confirmed payment should be recorded, and API access to that system if it isn't QuickBooks Online.
Good to know
- Today, payment links in the chat need exactly one gateway on your account. Choose Paystack or Yoco, not both.
- Ozow, PayFast, Stripe and Peach don't run on our platform today.
- The payment happens on Paystack's checkout page, opened from the chat. It is not a payment method built into WhatsApp.
- There's no do-it-yourself builder. Our engineers write and maintain the payment conversation for you.