TL;DR: Pick your WooCommerce payment gateway before your platform — the wrong call quietly costs a small SA store 0.4–0.8% of revenue. We compare PayFast, Peach Payments, Paystack and Ozow on real rand fees and fit: PayFast is the safe SA default, Peach suits scale, Paystack goes Africa-wide, and Ozow owns instant EFT. Match the gateway to how your customers actually pay.
Every WooCommerce store I audit in South Africa runs the same gauntlet within the first six months: PayFast vs Peach Payments, and whether to bolt on Paystack or Ozow alongside. The wrong call costs a small store about 0.4–0.8% of revenue a year in needless fees, plus the integration time of switching gateways midstream once the math becomes obvious. This is what I tell SA SMB clients before they pick — written from actual integrations, not the gateway marketing pages.
The headline is that all four are credible options for an SA-domiciled WooCommerce store in 2026, but they don’t compete on the same axes. PayFast and Peach Payments are full gateways covering cards, instant EFT, and recurring billing. Paystack is a full gateway too, but its SA merchant network and brand recognition still trail PayFast by a wide margin. Ozow is an instant-EFT specialist that complements one of the others — it isn’t trying to be a card processor. Picking between PayFast vs Peach Payments is therefore your primary decision; Paystack and Ozow are secondary.
The four-horse race at a glance: PayFast, Peach Payments, Paystack, Ozow: payfast vs peach payments
Before any deep PayFast vs Peach Payments breakdown, here’s how the four common SA WooCommerce gateways line up on the dimensions that actually drive a buying decision: fees, settlement, what they accept, and how long they take to wire into WooCommerce.
| Gateway | Card fee (2026) | Instant EFT fee | Settlement | WooCommerce setup |
|---|---|---|---|---|
| PayFast | 3.5% + R2 | R2 flat (under R2,000) | T+2 working days | Official plugin, ~30 min |
| Peach Payments | 2.95% + R1 (negotiable on volume) | ~1.5% via partner | T+1 to T+2 | Official plugin, ~45 min |
| Paystack | 2.9% + R1 (local cards) | via partner | T+1 | Official plugin, ~30 min |
| Ozow | n/a (no cards) | 1.5% (capped at R49) | T+1 | Official plugin, ~20 min |
Those headline numbers move in negotiation. Once you cross R150,000–R200,000 in monthly volume, every gateway will discount the percentage. PayFast will quietly drop to ~2.95%; Peach Payments will go to 2.5% or below for serious volume; Paystack has the most aggressive enterprise pricing if you can show consistent growth.
Transaction fees in rand: what payfast vs peach payments actually costs
The list price comparison hides the picture. Let me show the math on a realistic SA SMB scenario: a small e-commerce store doing R75,000 a month across 300 orders, average order value R250, with 70% card payments and 30% instant EFT.
- PayFast monthly cost: 210 card orders × (3.5% × R250 + R2) = R2,257; 90 EFT orders × R2 = R180. Total: R2,437 / month.
- Peach Payments monthly cost: 210 card orders × (2.95% × R250 + R1) = R1,759; 90 EFT orders × (1.5% × R250) = R338. Total: R2,097 / month.
- Paystack monthly cost: 210 card orders × (2.9% × R250 + R1) = R1,733; 90 EFT orders routed via Ozow at 1.5% capped = R338. Total: R2,071 / month.
- PayFast + Ozow combo: 210 card orders on PayFast = R2,257; 90 EFT orders on Ozow at 1.5% = R338. Total: R2,595 / month — worse than PayFast alone at this volume because Ozow’s percentage is higher than PayFast’s flat R2 below R2,000.
The math flips when the average order value rises. At an AOV of R3,500 instead of R250, PayFast’s flat R2 EFT fee dominates, and PayFast + manual EFT becomes the cheapest combination. This is why the PayFast vs Peach Payments call cannot be made on percentages alone — you have to know your store’s AOV distribution and split between cards and EFT.
PayFast: the SA default, and when it's the right call
PayFast is the South African default for a reason. It’s the one your buyer has used before — Takealot redirected them to it years ago, Yuppiechef did, half the small SA stores they’ve bought from did. That recognition is worth something at checkout: a known brand reduces cart abandonment relative to an unfamiliar gateway, especially with older or less e-commerce-savvy buyers. PayFast also bundles instant EFT (the bank’s “Pay Now” flow) at a flat R2 below R2,000, which is the cheapest EFT pricing among the four for low-AOV stores.
Where PayFast loses ground in the PayFast vs Peach Payments comparison: the dashboard UX is dated, the recurring billing module is functional but not best-in-class, and the headline card rate is the highest of the four. If your store does subscriptions, memberships, or tokenised repeat purchases, PayFast is rarely the right primary call.
Peach Payments: enterprise-grade tokenisation and recurring billing
Peach Payments is the gateway I recommend for any SA store running subscriptions, memberships, B2B repeat orders, or any flow that benefits from PCI-DSS Level 1 tokenisation. The vault stores card credentials so the customer doesn’t re-enter them; the recurring billing engine handles dunning, smart retries, and grace periods properly. For a store doing R150k+ monthly with a serious repeat-purchase rate, Peach Payments pays for itself in lower involuntary churn alone.
Where Peach Payments loses in the PayFast vs Peach Payments call: the small-volume merchant gets less personalised onboarding, the brand recognition at checkout is lower than PayFast (an issue for an older SA demographic), and the instant EFT flow goes via a partner rather than being native, which adds a touchpoint. For a store doing under R30k/month of one-off purchases with no subscription element, PayFast is usually the cleaner pick.
Paystack: the Africa-wide play and what that means if you're SA-only
Paystack came into South Africa with a developer-first ethos and the strongest API in the market. If you have engineering capacity, Paystack’s webhooks, idempotency keys, and test mode are simply better thought through than PayFast or Peach Payments. For a store building a custom checkout, custom subscription logic, or anything that strays from the standard WooCommerce flow, Paystack is the lowest-friction option.
The asterisk: Paystack’s South African merchant network is still smaller than PayFast’s. Buyers don’t recognise the redirect page as readily; “Why am I being sent to Paystack?” is a real support email I’ve seen at SMB clients. If your customer base is older, less digital, or skews to traditional SA SMB B2C, that brand recognition gap matters. If you’re targeting cross-border African customers — Nigerian or Kenyan buyers especially — Paystack instantly becomes the right call.
Ozow: instant EFT specialist — a complement, not a replacement
Ozow doesn’t compete in the PayFast vs Peach Payments race because it’s not a card processor at all. It’s a specialised bank-to-bank instant EFT gateway — the buyer authenticates in their banking app, the money lands in your account on T+1. No card fees because there’s no card. For a buyer who doesn’t have a credit card, doesn’t trust card-not-present transactions, or just wants the cheapest path, Ozow is the right primary option.
The honest limitation: Ozow’s 1.5% (capped at R49) beats PayFast’s card rate but loses to PayFast’s R2 flat EFT below R2,000. So adding Ozow on top of PayFast only makes sense if your AOV is high (R2,000+) and you have a customer segment that prefers bank-app authentication over card entry. Add Ozow to a Peach Payments setup more readily — Peach’s EFT goes via a partner anyway, and Ozow’s UX is genuinely better.
WooCommerce integration: setup time and the gotchas per gateway
All four publish official WooCommerce plugins, but “30 minutes to install” is not the same as “ready for live transactions.” Here are the integration gotchas I’ve hit repeatedly:
- PayFast (woocommerce payfast integration): the ITN (Instant Transaction Notification) webhook expects to reach your server from PayFast’s IP range. Cloudflare or aggressive WAF rules block it silently — orders flip to processing but never to completed. Whitelist PayFast IPs in your firewall before testing.
- Peach Payments (woocommerce peach payments setup): the sandbox and production environments have separate credentials and separate plugin entries. The most common SA SMB mistake is keeping sandbox keys live for weeks after launch. Take 5 minutes after go-live to confirm the entityId points at production, not test.
- Paystack: the test card numbers in the docs work locally; in some hosting environments the Paystack popup is blocked by aggressive CSP headers. If the modal won’t open, check the browser console before assuming the plugin is broken.
- Ozow: the post-back URL needs to be reachable over HTTPS with a valid certificate. Local certificates (Let’s Encrypt expired, self-signed) silently fail. Confirm SSL cleanliness before launch.
Across all four, the single biggest WooCommerce integration mistake is launching without ever running a real test transaction in production mode with a real card. Sandbox tests don’t catch firewall, CSP, or SSL issues. Budget 10 minutes for a R10 live test purchase, then refund it. If the store itself was built on shaky foundations, the gateway integration won’t save it — the ecommerce website development best practices for South Africa piece covers the platform-level decisions that have to be right before gateway choice matters.
POPIA and PCI-DSS: what the gateway carries on your behalf
Both PayFast and Peach Payments are PCI-DSS Level 1 certified, which means the card data never touches your WooCommerce server — the buyer enters card details on the gateway’s hosted page, and your server only ever sees a transaction reference. This is the right architecture for every SA SMB; running PCI-DSS compliance on your own infrastructure costs more than your gateway will ever charge you. Paystack and Ozow are similarly compliant. In the PayFast vs Peach Payments comparison, this is a draw — neither exposes you to PCI scope.
POPIA is more nuanced. The gateway processes the cardholder data as an Operator on your behalf; you remain the Responsible Party for the customer relationship and the order data on your WooCommerce database. A POPIA-compliant SA WooCommerce store needs an updated privacy policy that names the gateway, a clear consent flow at checkout, and a documented retention policy for order data. The Information Regulator’s POPIA guidance is the authoritative source if you want to read the framework end-to-end.
Which combination works for which SA store
Compressed decision tree based on what I see across actual SA WooCommerce stores:
- Low AOV, high volume, one-off purchases (under R30k/month, AOV under R500): PayFast alone. The flat R2 EFT below R2,000 wins; the volume isn’t yet enough to negotiate Peach down.
- Mid-volume mixed (R30k–R150k/month): Peach Payments primary, optionally Ozow on top. The card-fee differential becomes material; the better dashboard pays back in admin time.
- Subscription / membership / B2B repeat (any volume): Peach Payments — the tokenisation and recurring billing is materially better than PayFast’s. This is the strongest case for Peach in the PayFast vs Peach Payments comparison.
- Cross-border African customers (NG, KE, GH): Paystack primary, PayFast or Peach Payments for SA-domiciled cards only. Buyer recognition outside SA tilts the call.
- Engineering-heavy custom checkout: Paystack. The API and webhooks are best-in-class.
- High-AOV (R2,000+) one-off purchases: PayFast + Ozow. PayFast cards, Ozow EFT (Ozow’s percentage beats PayFast’s percentage at high AOV).
If you’re stuck between PayFast and Peach Payments specifically and your volume sits in the grey middle (R30k–R80k/month), the practical move is start on PayFast because of buyer recognition, then re-quote Peach Payments at the six-month mark with real volume data. The switch costs you a weekend; staying on the wrong gateway costs you 0.4–0.8% of revenue annually. The right e-commerce platform underpins all of this — if you’re still on the fence about WooCommerce vs Shopify, read the WooCommerce vs Shopify South Africa breakdown first; gateway choice is downstream of platform choice. And whichever gateway you settle on, the checkout that sits behind it determines what percentage of clicks actually convert — our high-converting website design playbook walks through the structural changes that lift checkout conversion by 20–40%.
FAQ
Is PayFast cheaper than Peach Payments for a small SA store?
For a store under R30k/month with low AOV and mostly card payments, the difference is roughly 0.5% — about R150/month on R30k turnover. PayFast wins on EFT pricing below R2,000; Peach wins on card percentage. The PayFast vs Peach Payments call below R30k/month is usually decided by checkout recognition and dashboard ergonomics, not raw fees.
Do I need both Ozow and PayFast?
Only if your AOV is above R2,000 and a meaningful slice of customers prefer bank-app authentication to card entry. Below that, PayFast alone covers both rails more cheaply.
Does Stripe work for SA WooCommerce stores in 2026?
Stripe accepts SA-issued cards but does not have an SA-domiciled merchant account flow. You’d need a US or UK entity to onboard. For an SA-incorporated store, PayFast, Peach Payments, Paystack, and Ozow are the realistic options.
Yoco vs these gateways for ecommerce?
Yoco is built for in-person card-present transactions and offers an online gateway as a secondary product. The online fees (2.95%) are competitive but the WooCommerce plugin and dashboard are less mature than PayFast or Peach Payments. If you run both a physical and online store and need a single dashboard, Yoco’s worth a look; for online-only, the dedicated gateways are stronger.
How long does PayFast vs Peach Payments take to switch over once a store is live?
About a weekend, done properly. Friday afternoon: install the new plugin in test mode, run sandbox transactions. Saturday: do a R10 live test, refund it, monitor for 24 hours. Sunday night: disable the old plugin, switch the new one to live, run another R10 test. The gateway switch itself is technical; the harder work is updating the privacy policy and any customer-facing communication that names the old gateway.
Key takeaways
- PayFast vs Peach Payments is the primary call; Paystack and Ozow are secondary or complementary picks.
- Headline percentages mislead — run the math against your store’s actual AOV and card-vs-EFT split before deciding.
- PayFast wins on buyer recognition and flat-R2 EFT below R2,000. Peach Payments wins on tokenisation, recurring billing, and card percentage at volume.
- Paystack is the right call for cross-border African customers or engineering-heavy custom checkouts.
- Ozow is a complement, not a replacement — it sits on top of one of the others for high-AOV instant EFT.
- Run a real R10 live test before considering any integration done. Sandbox doesn’t catch firewall, CSP, or SSL issues.
- POPIA compliance is a privacy-policy and consent-flow problem; PCI-DSS is the gateway’s problem if you use any of these four.
Related reading
- Ecommerce Website Development South Africa: Ma
- 8 Winning UX/UI Strategies for Boosting E-comm
- How Headless Commerce is Changing the Future o
- Choosing an eCommerce CMS in 2025- 5 Options
Ready to put this into action?
If you’d rather have a team that does this every day, we’re here. Book a free 20-minute consult and we’ll give you the three highest-impact next steps for your business — no obligation.