what to look for in a South African orchestration platform
South Africa requires a locally registered licensed partner in order to accept payments at all, and that single rule shapes the whole build. The platform that serves this market well is the one already treating that partner as a first-class connector rather than an exception to be routed around, and the same integration should then open the rest of the continent without a second build.
CoralCommerce chose Africa as its first market. South Africa is the sophistication benchmark we measure other African connectors against: cards, bank transfer rails, wallets, the licensed-partner rule, and forex. Leading payment orchestrator providers for e-commerce in South Africa are, in practice, the ones that sit on top of that licensed layer and are clear about where their own role ends and the licensed partner's begins.
what "18 payment types" actually forces you to design
A card-only checkout in Johannesburg leaves EFT, store-of-value and wallet behaviour on the table. A wallet-only checkout (the right default in Nairobi) leaves the card-mature South African consumer behind. Orchestration is how one merchant API presents the right instrument without a new integration per type. CoralCommerce connectors cover card acquirers, bank transfer rails and wallet providers on the same path used for Safaricom mPesa, MTN MoMo, Airtel Money, Orange Money, Vodacom, Cell C, Glo, Telkom, Tigo, Vodafone, Expresso, Wave and Zamtel elsewhere on the continent.
the licensed-partner rule
South Africa requires a locally registered licensed partner for accepting payments. Nigeria tightly controls its payment infrastructure and licensed operators. Those two sentences are why Africa is not a region you "turn on." CoralCommerce does not seek or hold those licenses. We orchestrate across the partners who do. Merchant-owned commercials still apply: the client negotiates and holds the agreement with the South African sponsor; we manage the technical relationship.
forex, then the rest of Africa
South African forex controls limit how settlement leaves the country. Design that flow before the first live transaction, not after the first reconciliation break. Once the South African connector is live, activating Kenya or Nigeria is a connector configuration on the same API, not a second platform. The continental brief is payment orchestration in Africa. The same orchestration-not-custody model is how we run Latin America.
we did not add South Africa to a European product. we built for this market, then expanded. 21 African countries sit on the same integration a Cape Town merchant already has.