WhatsApp and conversational AI automation

How to accept payments through WhatsApp in South Africa using PayFast or Yoco

There is no native pay-inside-WhatsApp checkout in South Africa yet. What works today, and what we build for clients, is a Yoco or PayFast payment link sent directly in a chat, wired to an n8n workflow so that a successful payment automatically triggers a WhatsApp confirmation message and updates stock or CRM records without anyone touching a spreadsheet. That's the whole system in one sentence. The rest of this article explains how each piece fits together and what it costs to run.

What WhatsApp payments actually means in South Africa right now

People hear "WhatsApp payments" and picture something like WeChat Pay, where money moves inside the app itself. That doesn't exist here. What exists is link-based payment, and it works well if you set it up properly.

Link-in-chat vs native checkout: the real distinction

A native checkout means the customer never leaves the app; card details, OTP, and confirmation all happen inside WhatsApp. Meta hasn't built that for South African merchants, and neither PayFast nor Yoco has a certified in-chat payment button here. What you get instead is a payment link generated by your gateway, sent as a normal message. The customer taps it, lands on a hosted checkout page, pays, and gets redirected back. It's not glamorous, but it's reliable, PCI-compliant by default, and doesn't require you to touch card data at all.

Where Yoco fits: Payment Links and Payment Pages

Yoco's Payment Links product lets you generate a one-off or reusable link from the dashboard or via API, then paste it straight into a WhatsApp chat. Payment Pages go a step further, giving you a small hosted storefront with your logo and item list, useful if you're selling more than one product and don't want to generate a new link for every order.

Where PayFast fits: links plus the Payfast by Network municipal pilot

PayFast's equivalent is the "Pay Now" link, generated through the merchant dashboard or the API, and it behaves the same way: send it in chat, customer pays, you get notified. PayFast also has something more interesting happening at municipal level, which we cover further down, because it hints at where WhatsApp billing in South Africa is heading for larger-scale collections, not just retail.

Why Take App and similar storefronts blur the picture

Storefront apps like Take App sit on top of WhatsApp and generate their own checkout links, often using Yoco or PayFast as the underlying processor. This creates confusion because sellers think they're using "WhatsApp's payment system" when really they're using a third-party catalog tool that still redirects to the same gateway checkout page. Worth knowing so you don't pay for a layer you don't need.

Yoco vs PayFast for a WhatsApp-based seller

If you're sending links in chat, the gateway choice comes down to fees, settlement speed, and what payment methods you need to support.

Fees: Yoco's flat 2.95% vs PayFast's tiered 2 to 3.5% plus monthly fee

Yoco charges a flat 2.95% per transaction on Payment Links with no monthly fee on its pay-as-you-go plan. PayFast's card fee sits between 2% and 3.5% depending on your monthly volume, and some of its account tiers carry a small monthly fee on top. For a seller doing low volume, Yoco's flat rate is usually simpler to reason about. For a business already doing decent monthly turnover, PayFast's tiered rate can undercut Yoco once volume climbs.

Settlement times and what the discrepancies actually mean

Yoco typically settles into your bank account within 1 to 2 business days. PayFast's standard settlement is also around 1 to 2 business days for card payments, though EFT settlement can take longer depending on the bank's own clearing cycle. The discrepancy people run into isn't usually the gateway's fault; it's public holidays and weekend cutoffs pushing a Friday sale's payout to the following Tuesday. Build that into your cash flow expectations rather than treating it as a fault.

What Yoco doesn't support: EFT, Amex, recurring billing

Yoco's Payment Links support Visa and Mastercard only, no Amex, no instant EFT, and no built-in recurring billing. If you need customers to pay via bank transfer or you're running a subscription model, PayFast is the better fit because it supports instant EFT and has a recurring billing API. This is one of the more common gaps we see sellers hit only after they've already built their WhatsApp flow around Yoco.

Which one suits a solo seller vs a business already on POS

If you're a solo seller with no existing POS setup, Yoco is faster to get going with, especially if you already use a Yoco card machine and want the same dashboard for online links. If you're a business that needs EFT support, recurring billing, or you're already integrated with PayFast for a website, stick with PayFast rather than running two gateways for no reason.

The automation layer nobody explains: webhook to WhatsApp

This is the part most "how to accept WhatsApp payments" articles skip entirely, and it's the part that actually makes the system useful day to day.

How a Yoco or PayFast webhook triggers an n8n workflow

Both Yoco and PayFast can send a webhook, a server-to-server notification, the moment a payment succeeds. Point that webhook at an n8n workflow (self-hosted or cloud) and you have a trigger that fires in real time whenever money lands. From there n8n can branch into as many actions as you need: send a message, write to a spreadsheet, hit an API, log to a database.

Sending an automatic WhatsApp payment confirmation

Once the webhook fires, n8n calls the WhatsApp Business API to send the customer a confirmation message with order number, amount, and next steps, without a human touching the phone. This is the single highest-impact automation for a small seller because it replaces the manual "thanks, got your payment" message that eats up time during busy periods and gets forgotten during quiet ones. This is the core pattern behind our WhatsApp automation for South African businesses work.

Updating stock, CRM, or accounting software in the same flow

The same n8n workflow can decrement stock in your inventory system, create or update a contact in your CRM, and push a line item into your accounting software, all triggered by that one webhook. It's the same architecture we shipped in how MerchLab automated order and payment flows, where a single payment event now updates four separate systems without anyone re-typing an order.

POPIA-safe record-keeping for payment and customer data

POPIA requires you to have a lawful basis for storing customer data, keep it secure, and not hold it longer than necessary. In practice, that means your n8n workflow should store only what's needed to fulfil and support the order: phone number, order reference, amount, not full card details (which the gateway handles, not you), and should sit behind proper access control rather than an open spreadsheet link shared with five people. Gateway PCI compliance and your own data minimisation are two separate responsibilities, and both matter.

The Payfast by Network municipal WhatsApp pilot in Upington

Most WhatsApp payment content ignores this, but it's the clearest signal of where things are heading at scale.

What TsogaPay and Payfast by Network actually built

Payfast by Network partnered with TsogaPay to run a WhatsApp-based municipal billing pilot in Upington, letting residents receive their municipal statements and pay them via a WhatsApp-delivered payment link rather than queuing at a counter or using a separate portal. It's the same link-in-chat mechanic covered above, just applied to bill collection instead of retail.

Why this matters for WhatsApp bill collection at scale

Municipal billing has brutal collection rates in many South African towns, partly because paying is inconvenient. A WhatsApp link removes a step: no app download, no portal login, just a message the resident already has open. If this pilot scales, it validates link-based WhatsApp payment as infrastructure, not a retail gimmick, and it's a strong argument that the plumbing (webhook, confirmation, reconciliation) is worth building properly now rather than treating it as a stopgap.

What SA businesses can borrow from this model

The transferable lesson isn't the municipal use case, it's the pattern: recurring invoice or statement, sent via WhatsApp, with a link that reconciles automatically on payment. Any SA business running monthly billing, whether a gym, a school, or a small services company, can copy this exact flow instead of chasing payments manually every month.

Load shedding and the case for a link-based fallback

Load shedding isn't going away as a planning consideration, and it changes how you should think about payment methods.

Why card machines fail and links don't

A physical card machine needs power and often a live connection through your router or a SIM signal that can also drop during an outage. A payment link, by contrast, only needs the customer's phone to have data or Wi-Fi, and yours to have enough battery or backup power to view the confirmation. During stage 4 and up, this difference is the gap between completing a sale and losing it.

Setting up a standing payment link for outage days

Generate a reusable Yoco or PayFast link ahead of time, save it as a WhatsApp quick reply or a pinned message, and use it the moment your card machine goes down. Pair it with the n8n webhook flow above so payment confirmations still fire automatically even if you're manually keying in the amount rather than running it through a normal POS flow. It's a small setup cost that pays for itself the first time the power goes out mid-sale.

What this costs to run end to end

Numbers matter more than promises here, so here's a realistic breakdown.

Gateway fees vs WhatsApp Business API fees

Gateway fees (Yoco's 2.95% or PayFast's 2 to 3.5%) are charged per transaction and come out of the payment itself. WhatsApp Business API costs are separate and charged per conversation category (marketing, utility, service) by Meta, plus whatever your BSP (business solution provider) charges for hosting and sending. These are two different cost lines and shouldn't be confused; one is a payment processing cost, the other is a messaging cost.

Rough monthly range for a small SA business

For a small business sending a few hundred payment confirmations and order updates a month, expect WhatsApp Business API costs in the low hundreds of rand monthly, plus gateway fees that scale with your sales volume. n8n hosting, if self-managed, adds a modest server cost; if you use n8n cloud, it's a fixed monthly subscription. We break the real numbers down properly in what WhatsApp automation actually costs, including where agencies inflate quotes.

Where the stats floating around online fall apart

A lot of blog posts quote flat "WhatsApp Business API costs X per month" figures that don't hold up because pricing depends on conversation category, message volume, and your BSP's markup, all of which vary by client. Treat any number without those three variables attached as a guess, not a quote.

Common questions

Do I need a website to accept WhatsApp payments? No. Both Yoco and PayFast generate hosted payment links and pages that work without you owning a website. You send the link directly in the WhatsApp chat, the customer pays on the gateway's own hosted page, and you get notified. A website helps with catalog browsing but isn't required for the payment itself.

How long does a Yoco or PayFast payment link take to pay out? Both typically settle card payments into your bank account within 1 to 2 business days. Weekends and public holidays push this out further since banks don't process on those days. PayFast's instant EFT can settle faster in some cases, while its standard EFT option depends on the paying bank's own clearing time.

Yoco vs PayFast, which is cheaper for a small WhatsApp seller? For low monthly volume, Yoco's flat 2.95% with no monthly fee is usually simpler and cheaper. PayFast's tiered 2 to 3.5% can beat Yoco once your volume grows, but some of its tiers carry a monthly fee. Run your actual expected volume through both fee structures before deciding, rather than assuming one is universally cheaper.

Does Yoco support EFT or bank transfer payments? No, Yoco's Payment Links only process Visa and Mastercard, not instant EFT or standard bank transfer. If your customers need to pay by EFT, use PayFast instead, since it supports instant EFT natively alongside card payments. This is a common gap sellers discover only after building a flow around Yoco.

Do I need a developer to set up WhatsApp payment links? Not for the basic link-sending part. Both Yoco and PayFast let you generate links from their dashboards with no code. You do need technical setup for the automation layer, webhook to n8n to WhatsApp confirmation, which is where most sellers either learn n8n themselves or bring in a builder like Sagentics.

Is WhatsApp Business API automation POPIA-compliant in South Africa? It can be, but compliance depends on how you configure it, not the API itself. You need a lawful basis for storing customer data, must minimise what you keep, secure access to your n8n instance and databases, and avoid retaining full payment card details, which the gateway already handles under its own PCI compliance.

How much does WhatsApp Business API cost in South Africa in 2026? Costs are per-conversation, based on category (marketing, utility, service), charged by Meta plus your BSP's fee on top. A small business sending a few hundred messages monthly typically lands in the low hundreds of rand. See what WhatsApp automation actually costs for a full breakdown rather than a flat estimate.

Can I automate order confirmation and payment notification on WhatsApp without hiring a developer? Basic link sending, yes. Full automation, webhook triggering an instant WhatsApp confirmation plus stock and CRM updates, generally needs someone comfortable with n8n and API setup. Some business owners learn this themselves over a few weekends; others bring in a builder to get it running correctly the first time, especially around error handling and POPIA-safe storage.

What happens during load shedding, can customers still pay by card or do I need a link fallback? Physical card machines can fail during outages if they lose power or network signal. A payment link only needs the customer's phone to have data, so keep a standing Yoco or PayFast link saved and ready to send as a fallback the moment your card machine goes down, and pair it with your usual automation so confirmations still fire.

For more on how the API differs from the regular app, see WhatsApp Business API vs the app, and for a look at the underlying automation approach across industries, our AI automation work covers more than payments alone. The pattern described here, webhook to confirmation to stock update, is also documented in the Antistatic case study if you want to see it running in production.

If you're weighing up Yoco against PayFast for your own WhatsApp setup, or want the webhook-to-confirmation flow built properly the first time, send us a message on WhatsApp and we'll talk through what fits your business.