Choose a South African payment gateway on four things, in this order: the payment methods your customers actually use, the true cost of its fee structure at your average basket size, how fast it settles money into your bank account, and how cleanly it integrates with your website and accounting system. Headline percentages matter far less than these four.
Most comparison articles hand you a table of percentages and call it a decision. That table is the least durable part of the answer. Published rates change, they are negotiated at volume, and the cheapest headline rate routinely turns out to be the more expensive choice once you account for the flat fee, the settlement delay, and the twenty hours a month someone spends reconciling payouts by hand.
Here is the framework we use when we build checkout flows for South African clients.
What does a payment gateway actually do?
A payment gateway is the tollbooth between your website and the banking system. It collects the customer's payment details, passes them securely to the acquiring bank or payment scheme, gets an approve-or-decline back, and tells your website which one it got. Money then sits with the provider until it is paid out to you.
Three jobs, then: authorise, secure, and settle. Most of the differences between providers live in the third one and in what happens after settlement — which is exactly the part that comparison tables skip.
Which payment methods do South African customers actually use?
Cards remain the most-used way to pay online in South Africa, but they are no longer the whole story, and a checkout that only offers cards is leaving completed orders on the table.
The methods worth knowing:
- Credit and debit cards. Visa and Mastercard. Universal, familiar, and the default expectation. They carry chargeback risk for you as the merchant.
- Instant EFT (pay by bank). The customer selects their bank at checkout, logs in through the provider, and approves the payment. Funds are verified in real time instead of the 24–48 hours a manual EFT takes. Typically cheaper than cards and carries no chargeback risk.
- PayShap. South Africa's real-time interbank payment scheme, built by BankservAfrica under the Reserve Bank's Rapid Payments Programme. It lets customers pay instantly using a mobile number registered as a ShapID, and its request-to-pay feature, PayShap Request, launched in December 2024 — which is what makes it usable at a merchant checkout rather than only for person-to-person transfers.
- Digital wallets and buy-now-pay-later. Apple Pay, Google Pay, and BNPL options. Worth adding once your volumes justify the integration effort.
The practical rule: offer cards plus at least one bank-based method. If a meaningful share of your customers do not hold a credit card, that second method is not a nice-to-have — it is the difference between a sale and an abandoned cart.
How do payment gateway fees work in South Africa?
Nearly every South African gateway charges some combination of a percentage and a flat fee per transaction, usually quoted excluding VAT. Some also charge for payouts, refunds, or chargebacks.
Indicative market bands, at the time of writing:
| Payment method | Typical fee band | Chargeback risk | Notes |
|---|---|---|---|
| Credit / debit card | ~2.5%–3.5% + a flat fee | Yes | Rates commonly negotiable above roughly R200,000/month in volume |
| Instant EFT | ~1.5%–2.0%, often with a minimum | No | Frequently the cheapest option for higher-value baskets |
| PayShap | Varies by provider | No | Newer at checkout; confirm availability with your provider |
| Immediate / same-day payout | Additional fee on the amount withdrawn | — | Charged on top of the transaction fee |
Confirm current published rates directly with any provider before you build a business case on them — these move.
The flat fee is what actually decides this
Here is why the headline percentage misleads. Take a hypothetical card structure of 3.0% + R2.00 against a hypothetical instant EFT structure of 2.0%, and run the same order through both at different basket sizes:
| Basket value | Card fee (3.0% + R2) | Effective rate | Instant EFT fee (2.0%) | Effective rate |
|---|---|---|---|---|
| R150 | R6.50 | 4.33% | R3.00 | 2.00% |
| R500 | R17.00 | 3.40% | R10.00 | 2.00% |
| R1,500 | R47.00 | 3.13% | R30.00 | 2.00% |
| R5,000 | R152.00 | 3.04% | R100.00 | 2.00% |
| R25,000 | R752.00 | 3.01% | R500.00 | 2.00% |
Illustrative arithmetic on the stated hypothetical structures, excluding VAT.
On a R150 basket the R2 flat fee is worth more than a full percentage point on its own. On a R25,000 basket it rounds to nothing. If you sell low-value items at high volume, the flat fee is your real cost driver. If you sell high-value items, the percentage is.
Scale that up. A business doing 400 orders a month at an average basket of R450 pays roughly R6,200 a month under that card structure and roughly R3,600 under that EFT structure — about R31,000 a year in difference. That is not a rounding error. It is a junior salary's worth of margin, decided by a checkout configuration.
The move is not to abandon cards. It is to offer both, and let the mix shift naturally toward the cheaper rail.
How long until the money reaches your bank account?
Authorisation is instant. Settlement is not, and the gap between them is a cash flow decision that founders consistently underestimate.
Standard settlement in South Africa typically runs on a rolling cycle of a few business days. Most providers offer a faster payout for an extra fee charged on the amount withdrawn. Payfast, for example, publishes an Immediate Payout fee of 0.8% excluding VAT of the requested amount, with a flat R14.00 excluding VAT applied where 0.8% comes to less than R14.00.
Ask three questions before you sign:
- What is the standard settlement cycle, in business days?
- Is there a rolling reserve or holdback, and under what conditions?
- What does an accelerated payout cost, and is it available on demand or on a fixed schedule?
If you buy stock to fulfil orders, a three-day settlement cycle is working capital you have to fund yourself. Price that in.
Do I need to be PCI DSS compliant to take payments on my website?
Yes — but the scope depends entirely on how you build the checkout, and that is a decision worth making deliberately.
If you fully outsource card capture to your provider, so that the customer's card details never touch your servers, you generally validate against SAQ A, the lightest self-assessment questionnaire. To qualify, your site must serve or redirect to the payment page over HTTPS, and you must not have access to or control of the page or iframe where card data is entered.
Note that SAQ A is no longer a pure paperwork exercise. Under PCI DSS v4.0.1, external vulnerability scanning (Requirement 11.3.2) became mandatory for SAQ A merchants from 1 April 2025.
Build your own card form and post the details through your own backend, and your scope expands dramatically — along with your cost and your liability. For the overwhelming majority of South African businesses, that trade is not worth making. Let the provider hold the card data.
Alongside PCI DSS, remember that customer names, contact details, and order histories are personal information under POPIA. Our approach to POPIA-grade data handling sets out how we treat that in the systems we build.
Hosted checkout or embedded checkout?
This is the integration decision that most affects conversion.
- Hosted (redirect). The customer leaves your site for the provider's payment page, pays, and comes back. Simplest to build, lightest PCI scope, and the visual break can cost you a small percentage of completed checkouts.
- Embedded (iframe or drop-in). The payment form renders inside your page. The customer never appears to leave. Slightly more integration work, still SAQ A eligible provided you do not control the iframe contents.
- Direct API. Full control of the experience, full PCI burden. Justified for high-volume merchants with unusual flows, and rarely for anyone else.
For most South African businesses, embedded is the sweet spot: a checkout that feels like part of your site without inheriting the compliance weight of handling card data yourself. It is the default we build into our web design and development work.
Not sure which model your checkout needs? Book a no-obligation discovery call and we will map your payment flow before you commit to a provider.
Does the gateway need to talk to the rest of your business?
This is the question that separates a checkout that works from a checkout that quietly creates work.
A payment lands. Now what? Someone has to match it to an order, raise a tax-compliant invoice, update the customer record, recognise the revenue, and reconcile the payout — because providers settle in batches, not per transaction, so one deposit in your bank account represents dozens of orders minus fees.
Done manually, that is hours a week, every week, forever. Done properly, it is invisible.
What to look for:
- A real API and webhooks. Webhooks let the gateway notify your systems the moment payment status changes, rather than someone checking a dashboard.
- Settlement reports that reconcile. You need a payout broken down to the transaction, with fees itemised, or month-end becomes archaeology.
- Recurring billing and tokenisation, if you sell subscriptions or retainers. Card-on-file done securely by the provider, not by you.
- A clean path into your accounting. This is where Syniq Business OS accounting earns its place: payments flow into tax-compliant invoicing and reconciliation without a re-keying step, and the numbers surface on the executive dashboard the same day rather than six weeks later.
A gateway that authorises well but reports badly is a false economy. You save on rate and pay it back in admin.
Which gateway setup fits your business?
| If you are… | Prioritise | Watch out for |
|---|---|---|
| A new store, low volume, small baskets | No monthly fee, quick setup, low flat fee per transaction | Flat fees crushing margin on sub-R200 orders |
| Selling high-value items, low volume | Percentage rate, instant EFT availability, fraud tooling | Chargeback exposure on large card orders |
| High volume (R200k+/month) | Negotiated rates, settlement speed, reporting depth | Staying on default pricing when you have earned better |
| Subscription or retainer based | Recurring billing, tokenisation, failed-payment retries | Involuntary churn from expired cards |
| Selling into other markets | Multi-currency, cross-border settlement, FX cost | FX margin hidden inside the exchange rate |
| Running a marketplace or splitting payouts | Split payments, sub-merchant support | Providers that simply cannot do this — check first |
If your requirements do not fit any row cleanly — split payouts, unusual billing logic, deep integration into an existing system — that is a build conversation rather than a buy conversation, and it is what our custom software team does.
Five questions to ask before you sign
- What is the all-in cost at my actual average basket size? Not the headline rate. Run your real numbers through their real structure.
- What is the standard settlement cycle, and is there a reserve?
- Which payment methods are included, and which cost extra to enable?
- What does the API and webhook documentation look like? Ask your developer to read it before you commit. Good documentation is a reliable proxy for a good platform.
- What happens when something goes wrong? Local support, in your time zone, with a human on the end of it — this is worth more than ten basis points on your rate.
Frequently asked questions
How do I choose a payment gateway in South Africa? Start with the payment methods your customers use, then model the total fee cost at your actual average basket size, then check settlement speed against your working capital needs, and finally confirm it integrates cleanly with your website and accounting system. Headline rates are the last thing to compare, not the first.
Is instant EFT cheaper than card payments in South Africa? Usually, yes. Instant EFT typically sits in a lower fee band than cards and carries no chargeback risk. The saving is most pronounced on higher-value baskets. Offering both is the practical answer — some customers will only pay by card.
How long does a payment gateway take to pay out? Standard settlement generally runs on a rolling cycle of a few business days, though the exact cycle varies by provider and by your risk profile. Most providers offer a faster payout for an additional fee charged on the withdrawn amount. Confirm the standard cycle and any reserve terms in writing before you sign.
Do I need PCI DSS compliance for my website? Yes, but if card details never touch your servers you generally validate against SAQ A, the lightest self-assessment. That requires HTTPS and that you do not control the page or iframe where card data is entered. Since 1 April 2025, SAQ A merchants must also perform external vulnerability scanning under PCI DSS v4.0.1.
Can I use more than one payment gateway? Yes, and many South African businesses do — commonly one provider for cards and another for bank-based payments, or a second as failover. It adds reconciliation complexity, so make sure your accounting setup can handle multiple settlement streams before you add the second one.
What is PayShap and can I accept it on my website? PayShap is South Africa's real-time interbank payment scheme, run by BankservAfrica under the Reserve Bank's Rapid Payments Programme. Customers pay instantly using a mobile number registered as a ShapID. The PayShap Request feature, launched in December 2024, enables merchant-initiated payment requests. Availability at online checkout depends on your provider, so ask directly.
The short version
The right payment gateway is the one that matches how your customers pay, costs the least at your real basket size, settles fast enough to fund your operations, and hands clean data to the rest of your business. Get those four right and the difference between providers is measured in basis points. Get them wrong and you pay for it in margin and in hours.
If you want that mapped against your actual numbers rather than a generic table, book a discovery call. We will look at your basket sizes, your payment mix, and your existing systems, and tell you plainly what fits — including if that means the setup you already have. If the answer turns out to be a connected operations platform rather than a bolt-on, Syniq Business OS is where payments, invoicing, and reporting stop living in separate places.
Written by Mikhail for Syniq (Pty) Ltd. Syniq is a Cape Town software company building Business OS, websites and custom software for growing South African businesses. This article is general guidance, not legal or financial advice. Fee bands are indicative market ranges at the time of writing and worked examples are arithmetic on stated hypothetical structures — confirm current published rates with any provider directly.