IN THIS ARTICLE▾
- 01The Provider Types You Are Really Comparing
- 02PCI DSS Level 1 in South Africa: What the Tier Actually Means
- 03SARB Compliance and PCI DSS Answer Different Questions
- 04Verify a PCI DSS Compliant Payment Processor in South Africa Before You Sign
- 05Your Responsibilities Don't End at the Provider's Attestation
- 06Red Flags and the Real Cost of the Cheapest Option
- 07Where Recurv Fits as a Compliant Recurring Billing Provider
- 08Frequently asked questions
Plenty of providers say they are PCI DSS compliant. Far fewer can hand you a dated document that proves it for the exact service you are buying.
If you collect dues, levies, rent or subscriptions every month, that gap matters. Your members' card numbers and bank details pass through whoever you pick. This guide shows you how to separate a PCI DSS compliant payment processor in South Africa from one that only says the words on its website.
The Provider Types You Are Really Comparing
Most buyers compare quotes from products that do different jobs. A cheap quote and an expensive one may not even cover the same work.
Between your business and the bank sits a third-party payment provider. You rarely connect to a bank or card network directly. The provider takes your payment instructions, passes them on, and returns the result. Whatever data it holds, it holds on your behalf, and that is why its security becomes your concern.
Provider type | Its role | Data it touches | What to check
Payment gateway | Passes card details from your checkout to the processor | Card data in transit | Does its attestation cover the exact gateway service you use?
Full processor | Gateway plus card settlement and often wider payment services | Card data, settlement data | Which of its services does the attestation actually list?
Debit order platform | Manages mandates, schedules and collects from bank accounts | Bank-account data, mandate records | What bank clearing and data protection arrangements are documented in writing?
Recurring billing platform | Runs the full cycle: authorise, schedule, collect, reconcile | Card and bank data, depending on setup | Are both payment flows in scope, and is the scope dated?
A gateway is built for a one-off checkout. A debit order platform is built for repeat collection from the same people month after month. If you want to see that difference played out, read how a dedicated recurring billing platform compares with a gateway, or weigh a full payments suite versus a recurring billing platform.
This article does not rank named providers. A compliance claim is only worth what its paperwork shows, and the paperwork is yours to request.
PCI DSS Level 1 in South Africa: What the Tier Actually Means
PCI DSS is the card industry's security standard, maintained by the PCI Security Standards Council. Wikipedia has a plain overview if you want the background. The part that matters for buying is the tier.
Level 1 Is a Validation Tier, Not a Badge
The card brands, not the provider and not the Council, set the tiers, and they base them on transaction volume. Merchants and service providers have separate tiers, so a Level 1 service provider and a Level 1 merchant are not the same thing.
Level 1 is the strictest route. It means an annual on-site assessment by a Qualified Security Assessor (QSA), who produces a Report on Compliance (ROC). The assessed company then signs an Attestation of Compliance (AOC) summarising the result.
Lower tiers can often validate with a self-assessment instead. That is a real difference in how hard the claim has been tested.
What a Current Attestation of Compliance Proves
A PCI DSS logo on a website proves nothing. An AOC proves something specific, and you can check it line by line.
Look for four things:
- the date, because compliance is validated annually and an old AOC describes an old state of affairs
- the legal entity named on it, which must be the company you are contracting with
- the services listed in scope, which must include the service you are buying
- the standard version, which is v4.0.1 on the PCI Security Standards Council site at the time of writing
A provider can be genuinely compliant for one product and silent on another. If your contract covers recurring card charges and the AOC lists only a checkout gateway, the attestation does not cover what you are buying.
SARB Compliance and PCI DSS Answer Different Questions
PCI DSS asks whether cardholder data is protected. SARB oversight asks a different thing: whether a provider operates properly inside the South African payment system. One does not stand in for the other, and a serious provider should be able to speak to both.
How a Secure Debit Order Processor Differs From Card Processing
PCI DSS governs cardholder data. Card-based recurring charges fall inside its scope.
Debit order collections run on bank-account data instead. They move under bank clearing rules managed through the Payments Association of South Africa (PASA), and the personal information involved falls under the Protection of Personal Information Act (POPIA).
Take a typical gym. It takes joining fees by card at reception and collects monthly memberships by debit order. The card side brings PCI DSS into play. The debit order side runs on clearing rules and POPIA. Each needs its own answer, and a provider that covers only one leaves you exposed on the other.
The debit order flow starts with a mandate. For the detail, see how debit order mandates get authorised in South Africa.
What SARB Compliant Should Mean in Practice
"SARB compliant" is not a certificate you can frame. It refers to the South African Reserve Bank's oversight of the National Payment System, and the useful question is what role the provider holds within it.
So ask the provider to state that role in writing. A provider that is genuinely operating within the system can describe it in a paragraph, name the arrangements it relies on, and say who is responsible for what. If all you get is a badge and a smile, treat that as an answer.
Be cautious about anyone who names a registration or licence type without being able to explain it. The phrase should come with a document or a clear written statement behind it.
Verify a PCI DSS Compliant Payment Processor in South Africa Before You Sign
You can run the same checks on any provider, and you can run them in one sitting. Most of them cost nothing but an email.
Questions to Ask About the Attestation and Scope
Request the current AOC and read it against these points:
- Validity date. Is it within the last year, and does it cover today?
- Named QSA. Check the assessor against the PCI Security Standards Council's published list of assessors.
- Entity and services. Is the contracting company named, and is the service you are buying listed?
- Flows covered. Are both card and debit order flows in scope, or only one?
- Responsibility matrix. Does the provider show which controls it owns and which stay with you?
That last item is the one most buyers skip. Without it, nobody can say who is responsible when something goes wrong.
Payment Processor Security Standards to Ask About
Walk each step of the billing cycle and ask the same four questions at each: what data does this step touch, how is it encrypted or tokenised, who can access it, and how is it returned or deleted when you leave?
- Authorise. The mandate captures bank details and consent, so ask where they are stored and who can read them.
- Schedule. Ask whether stored payment details are tokenised or sit in plain form behind the schedule.
- Collect. Ask what leaves the provider's environment when the instruction goes to the bank or card network.
- Reconcile. Ask whether results are matched inside the platform or exported to files you then manage yourself.
If you cannot get a clear answer at one step, that step is where the risk lives. Exit terms matter as much as onboarding, because your members' data is still out there after you cancel.
Your Responsibilities Don't End at the Provider's Attestation
A provider's attestation covers the provider's part of the environment. It says nothing about how you handle data on your side, and no compliant processor can change that.
This is shared responsibility. If your business accepts card payments, you still complete your own self-assessment questionnaire, and the provider's responsibility matrix tells you which of your controls remain yours. Choosing a compliant provider shrinks what you have to secure. It does not reduce it to zero, and it is not the right fit for anyone hoping to hand over responsibility entirely.
Where Spreadsheets and Exports Create New Risk
Picture a typical club treasurer. Each month she exports member bank details into a spreadsheet to chase fees. The sheet gets emailed to a committee member, saved on a laptop, and kept in a downloads folder for a year.
Every one of those is a copy of sensitive data outside any controlled system. The risk is yours, whatever your payment provider's attestation says. A managed platform reduces it because the data stays in one place with access controls, instead of travelling in files.
Red Flags and the Real Cost of the Cheapest Option
The cheapest headline fee is rarely the lowest real cost. A low per-transaction fee tells you about one line of the bill and nothing about the rest.
Count these alongside it:
- Compliance scope. If the provider's attestation leaves out your payment flow, you may carry the gap yourself.
- Holding balance requirements. Some debit order systems tie up a large balance, which can put them out of reach for smaller organisations. Read about debit order systems that work without a large holding balance before you rule yourself out.
- Arrears. Late and failed collections cost you cash flow, and chasing them costs staff time. See cutting membership fee arrears without manual chasing.
- Reconciliation time. Hours spent matching payments to members add up, and so do the errors.
A provider that looks cheap on the fee but leaves your bookkeeper matching payments by hand is not cheap. You are paying in a different currency.
The red flags themselves are easy to spot once you know them. Watch for a PCI badge with no attestation date, and for no named assessor. Be wary of a scope that leaves out the payment flows you actually use. And treat vague answers about who can access account data as a warning, because a provider that runs a clean operation can usually say it in one sentence.
Where Recurv Fits as a Compliant Recurring Billing Provider
Recurv is a South African payment collections platform built for recurring billing. It runs the whole cycle on one system: mandate authorisation, scheduling, collection and reconciliation. That replaces the manual chasing and spreadsheets described above.
Recurv also keeps its holding balance very small. That means smaller businesses that could never afford debit order processing on large balance requirements can run collections too.
Recurv's Stated Position and How to Test It
Recurv states that it is a SARB compliant payment platform and that it holds PCI DSS Level 1. That is Recurv's own position, and you should treat it the way you would treat any provider's: as a claim to verify.
The differentiator is the kind of evidence behind it. A Level 1 claim is dated, assessed by a QSA and tied to a defined scope. A bare "PCI DSS compliant" line on a website is none of those things.
Run Recurv through the same checklist as everyone else. Ask for its current attestation and scope statement, check the date and the services listed, and ask how it describes its SARB role in writing. Then go through the four stages of the cycle and ask what data each one touches.
Book a time to see the mandate-to-reconciliation flow in a live demo and test Recurv's Level 1 and SARB positioning against your checklist.
Frequently asked questions
Which are the third-party payment providers?
A third-party payment provider is any company that sits between your business and the bank or card network to move money for you. Gateways, full processors and debit order or recurring billing platforms all fit that description. What matters is which data they handle and whether their attestation covers that service.
What payment gateway is available in South Africa?
Several gateways and processors operate locally, and they differ in what they cover. Some focus on one-off card checkouts, others on debit orders or full recurring billing. Pick by the payment flows you actually run, then check each shortlisted provider's current Attestation of Compliance against that flow.
What are the three types of payment systems?
A practical split is card payments, bank-account payments such as debit orders and EFT, and cash or wallet-based payments. Card systems fall under PCI DSS. Bank-account systems run under clearing rules and POPIA. Recurring billing usually involves the first two, so your provider needs to cover both.
Which is the cheapest payment gateway?
The one with the lowest fee is not automatically the cheapest. Add up compliance scope, any holding balance requirement, failed collections and the hours you spend reconciling. Compare providers on that total, not on the per-transaction fee alone.



