SaaS payments in South Africa: how startups should collect

A South African SaaS startup usually needs three collection paths: card on file for self-serve sign-ups (local and international), debit order for local SMB customers on monthly plans who prefer not to use a card, and invoice with EFT or payment link for larger annual contracts. Put them behind one billing system that handles plans, VAT, failed payments and webhooks to your app, so product access always reflects payment status.

The earlier you set this up properly, the less painful it is to change later. Here's a practical blueprint.

Match payment methods to customer segments

Don't force enterprise customers through a card checkout, and don't send SMB customers invoices they have to remember to pay.

Pricing and plans

Our colleagues cover SaaS pricing pages, free trials and coupons in detail. From a payments point of view:

• Decide monthly and annual options; annual prepayment helps cash flow (see cash flow for subscription businesses).
• Decide VAT-inclusive or exclusive display. South African consumers expect inclusive prices; B2B often sees exclusive.
• Price in ZAR for local customers and consider USD (or other currencies) for international customers, rather than letting their bank convert a ZAR charge.
• Handle upgrades and downgrades with proration rules decided upfront.

VAT for SaaS

• South African SaaS companies register for VAT once taxable supplies exceed R2.3 million in 12 months (from 1 April 2026), or voluntarily above R120,000. See VAT registration threshold.
• Services to non-resident customers may be zero-rated in some cases; check the rules with a tax practitioner.
• Every renewal needs a compliant tax invoice once you're registered. See VAT on digital services.

Connect payments to product access

Your app needs to know, reliably, whether a customer has paid. The standard pattern:

1. Customer signs up in your app; you create a customer and subscription in your billing system via API.
2. The customer pays on a hosted checkout page (card, instant EFT) or signs a debit order mandate.
3. The billing system sends webhooks for events: subscription activated, invoice paid, payment failed, subscription cancelled.
4. Your app updates access based on those events, not on redirects from the checkout page.

Verify webhook signatures and make handlers idempotent. Our colleagues' guides on payment webhooks and webhook signature verification go deeper.

Failed payments: the SaaS silent killer

Involuntary churn from failed payments can be a significant share of total churn. Build recovery in from day one:

• Retry failed card payments on a schedule and email the customer with a link to update their card.
• For debit orders, act on unpaid reason codes (see unpaid debit order reason codes).
• Give a grace period before restricting access, then downgrade or suspend rather than deleting data.
• Measure recovery rate monthly.

B2B invoicing for bigger customers

• Issue an invoice at the start of the contract period with payment terms (for example 30 days).
• Include PO numbers and the customer's VAT number.
• Offer a payment link on the invoice so their finance team can pay by card or instant EFT if they prefer.
• Follow up with a consistent credit control process.

Metrics to track from month one

• Monthly recurring revenue (MRR) and annual recurring revenue (our colleagues explain MRR vs ARR).
• Churn, split into voluntary and involuntary.
• Failed payment rate and recovery rate.
• Days sales outstanding for invoiced customers.
• Revenue by payment method and currency.

Build vs buy

Building billing in-house seems simple until you need proration, VAT invoices, dunning, debit orders, multiple gateways, credit notes, accounting sync and a customer portal. Most early-stage SaaS teams are better off integrating a billing platform via API and spending engineering time on the product.

A launch checklist

• Plans and prices defined in ZAR (and other currencies if needed)
• Card gateway connected, debit order option for local customers
• Webhooks wired to product access, with signature verification
• VAT settings and tax invoice template ready
• Dunning schedule and card update flow in place
• Customer portal for invoices and payment details
• Accounting sync configured

How CentraPoint helps

CentraPoint gives SaaS teams a billing layer they can integrate rather than build: subscription packages and plans with trials and coupons, hosted checkout pages, card and instant EFT through gateways such as Paystack, PayFast, Peach, Yoco and Ozow, Netcash debit orders for local customers, dunning, a customer portal, VAT settings and branded invoices, all driven by a REST API and webhooks. See the developers page and quickstart.

Frequently asked questions

Which payment method is best for a South African SaaS startup?

Card on file is best for self-serve sign-ups, debit orders suit local SMB customers who prefer bank payments, and invoices with EFT or payment links suit larger annual contracts. Most SaaS businesses need at least two of these.

Can South African SaaS companies bill in US dollars?

Many gateways support multiple currencies for card payments. Check currency support, settlement currency and conversion fees with your gateway before pricing in foreign currencies.

How should my app know if a customer has paid?

Use webhooks from your billing system or gateway to update access when invoices are paid or payments fail, rather than relying on the customer returning to your site after checkout.

Do I need to charge VAT on SaaS subscriptions?

Once you're VAT registered, yes, at 15% on local supplies. Registration becomes compulsory when taxable supplies exceed R2.3 million in a 12-month period.