← insights
02 / 06·2 min read·6 July 2026

Card acquiring in South Africa: what actually determines approval rates

Everyone negotiates fees. The serious money is in approval rates, and approval rates are an accumulation of small correctness.

by Warren Ross

When merchants evaluate acquiring, the conversation always starts with price. I get it, fees are visible and negotiable and easy to put in a spreadsheet. But a basis point saved on fees is noise next to a percentage point of approval rate, because a decline isn't a discount. It's zero revenue, plus a customer who now believes your product doesn't work.

After years of living inside South African card acceptance, here is what I've actually seen move approval rates. None of it is glamorous.

Domestic presentment is the biggest single lever, and it isn't close. The same customer, same card, same amount can succeed as a domestic transaction and fail as a cross-border one. Foreign-acquired e-commerce is where issuers concentrate their suspicion: harsher fraud scoring, more step-up challenges, and on some debit portfolios, outright throttling of foreign online activity. If your transactions arrive in South Africa as foreign, you are fighting every issuer's risk model before the customer even enters the picture.

South Africa is a debit-first market, and that shapes everything. Debit products carry tighter card-not-present rules, different recurring behaviour, and issuer logic that was designed for point-of-sale first. A checkout and billing setup tuned for credit cards in Europe or the US quietly underperforms here and nobody can see why from the outside.

Merchant category codes matter more than people think. Miscode your MCC, deliberately or lazily, and you inherit the approval profile of whatever category you're pretending to be, along with scheme trouble when it's noticed. Honest coding is both compliance and yield.

Then there's 3D Secure. Done properly, with risk-based authentication and sensible routing, it lifts approvals by shifting liability and giving issuers confidence. Done crudely, it's an OTP wall that customers abandon. The difference between those two outcomes is configuration and acquirer capability, not luck.

Recurring transactions have their own hygiene. Initial and subsequent charges must be flagged correctly as merchant-initiated, credentials should be tokenised, expired and reissued cards need automatic refresh, and retries need discipline. Hammering a declined card daily doesn't recover revenue, it teaches the issuer's fraud model that you look like a bot. Spacing, decline-code awareness and knowing when to stop all show up in your approval rate a month later.

And the quiet one: statement descriptors. A customer who doesn't recognise a charge disputes it. Disputes accumulate against your merchant profile, and issuers see that history when deciding whether to approve your next transaction. Recognition on the statement line feeds back into authorisation. Very few merchants ever connect those dots.

What ties all of this together is that approval rate isn't a feature you buy, it's a posture you maintain: domestic presentment, honest coding, correct recurring flags, tuned authentication, disciplined retries, recognisable descriptors, and someone actually reading the decline codes every week. Each item is small. Together they're the difference between a market that works and a market you gave up on.

end.