Crypto businesses expanding into or through South Africa encounter a specific and underappreciated risk: correspondent banking access – the chain of interbank relationships that allows fiat to move across borders – is not guaranteed by holding a licence, registering a company, or passing KYC with a local bank. For a digital-asset business, losing or never obtaining that chain means frozen payment rails, stranded client funds and an inability to settle in the currency your users actually need. The Financial Sector Conduct Authority (FSCA), which supervises crypto assets as a category of financial products under the applicable FSCA framework, does not itself open bank accounts. Licensing and banking are two separate problems, and operators who conflate them pay the price.
This page addresses the practical legal and structural question directly: how does a digital-asset business – whether a VASP (virtual asset service provider), a payment platform or a cross-border remittance operator – secure and protect correspondent banking access in South Africa, and what does the cross-border interaction with tax, EMI onboarding and regulatory compliance look like in practice?
The regulatory basis for crypto and payments in South Africa
South Africa's FSCA has designated crypto assets as financial products, meaning that any person providing crypto asset services to the public requires a licence under the applicable FSCA regime. This designation marked a structural shift: previously, crypto businesses operated in a registration-only environment; now they face full conduct and compliance obligations. The South African Reserve Bank (SARB) retains authority over payment systems and currency flows, making the SARB the second critical regulator for any business with a fiat settlement layer.
The distinction between these two regulatory bodies matters enormously for banking. The FSCA licence confirms that your business is legally authorised to deal in crypto assets. It does not tell a correspondent bank that your AML controls are sufficient, that your beneficial ownership structure is acceptable, or that your cross-border flows will not trigger currency-control concerns under South Africa's exchange-control framework. Those questions are answered separately, by the business's compliance posture and by how counsel structures the entity from the outset.
For inbound operators – businesses licensed elsewhere that want to serve South African users or route fiat through South African rails – the cross-border layering problem is acute. An operator sitting in, say, Malta or Lithuania under a transitional CASP authorisation still faces South Africa's own FSCA requirements for local activity, SARB exchange-control approval for cross-border capital flows, and the domestic banks' own correspondent due-diligence requirements. Three regimes, one payment chain.
The SARB's exchange-control framework governs capital flows in and out of South Africa. For digital-asset businesses, this framework introduces an additional layer of pre-approval or reporting that many operators discover only after a banking relationship has already been declined or terminated. Structuring that layer correctly – at entity formation rather than after the first wire rejection – is one of the primary ways counsel adds concrete value early.
CTA #1 — Early-stage reader
The process above describes the standard regulatory path. Your specific facts – the entity's domicile, the user base's currency exposure, the cross-border flow pattern – change the analysis materially. Map your options with OBOLUS before the first banking conversation.
Why correspondent access breaks – and what the legal record shows
Banks close or decline crypto company accounts for reasons that are largely structural, not accidental, and understanding those reasons is the starting point for solving the problem. In our practice across banking and payments mandates, the pattern is consistent: a business presents a locally registered and licensed entity, but the bank's correspondent compliance team looks through that entity to the underlying business model, the jurisdiction of counterparties, the transaction volumes and the anticipated currency flows. If any of those elements triggers an internal risk threshold, the account is declined or terminated – often with no substantive explanation.
South Africa-specific pressure points include three recurring issues. First, the SARB exchange-control requirements mean that a crypto business's outbound flows can look, to an automated transaction-monitoring system, like speculative capital flight rather than legitimate business settlement. Without a legal opinion and a pre-cleared flow architecture, that flag is difficult to reverse. Second, South African correspondent banks face their own de-risking pressure from their own USD or EUR correspondent banks – primarily US, UK and European institutions that have tightened onboarding criteria for downstream crypto-exposed customers. A local bank that wants your account may find it cannot hold it without jeopardising its own upstream relationships. Third, beneficial ownership and group structure scrutiny has intensified under the Financial Intelligence Centre Act (FICA), the primary AML/CFT regime applicable in South Africa. A complex offshore holding structure – even a legitimate one – can stall onboarding indefinitely if it is not pre-documented to the bank's satisfaction.
The solution is not to conceal complexity. It is to translate complexity into bank-grade documentation before the onboarding meeting: a legal memorandum on the regulatory status of the entity, a beneficial ownership map with source-of-funds narrative, a compliance summary referencing FATF Recommendation 15 (which covers virtual assets and their service providers under FATF's global standards), and – where SARB exchange-control approval is required – evidence that approval has been obtained or applied for.
How does EMI onboarding work as an alternative fiat rail?
For digital-asset businesses that cannot secure a domestic bank account quickly, an EMI (electronic money institution) – a licensed payment institution that holds client funds and provides IBANs without being a full commercial bank – offers a workable interim or permanent fiat rail. The EMI onboarding process is structurally similar to bank onboarding but typically operates under a more flexible risk appetite, particularly for regulated crypto businesses that can demonstrate a clean compliance posture.
EMIs relevant to South Africa-connected businesses are almost always licensed outside South Africa itself – typically in the EU under MiCA's transitional provisions or under a national payment institution regime, or in the UK under the Financial Conduct Authority (FCA). That means the South African crypto operator is pairing a domestic FSCA licence with an offshore EMI relationship. This pairing works, but it introduces two legal questions that must be managed proactively.
The first question is SARB exchange-control treatment of the EMI relationship. Funds held at an offshore EMI and subsequently remitted to South Africa may require exchange-control approval or fall within a specific dispensation. The structure of that flow – whether it is treated as an inward investment, a service payment, or a loan – affects both the regulatory treatment and the tax characterisation. Getting those two questions wrong in sequence is common; addressing them together at the outset is the more defensible approach.
The second question is the EMI's own AML/CTF requirements under its home jurisdiction's rules. A UK FCA-registered EMI, for example, applies the Travel Rule (the obligation to pass originator and beneficiary identifying information with a transfer) to qualifying transactions. A South African VASP onboarding with that EMI must be able to demonstrate Travel Rule compliance on its side of the transaction – which requires either a VASP-to-VASP Travel Rule solution or documented policy for handling transfers involving non-compliant counterparties. In our practice, we regularly advise operators who discover this requirement only at the point of EMI onboarding, when the practical window for structural adjustment has narrowed.
The cross-border layering problem: licence, banking and tax as one structure
A common assumption among operators building into South Africa is that the licensing question and the banking question can be solved sequentially – first obtain the FSCA authorisation, then approach banks. That sequencing is understandable but systematically produces delays and rejections. The practical reality is that the entity structure required to satisfy the FSCA differs in some material respects from the structure that will satisfy a correspondent bank's due-diligence requirements, which in turn differs from the structure that produces an optimal tax outcome under South Africa's controlled-foreign-company and transfer-pricing rules.
Consider the most common profile we encounter: a European-licensed operator (Malta or Lithuania, under transitional MiCA CASP authorisation) seeking to serve South African retail and institutional users. That operator needs, at minimum, a South African FSCA-licensed entity or a local representative arrangement; a SARB exchange-control mechanism for moving fiat between the South African entity and the European parent; a banking or EMI relationship capable of handling both ZAR settlement and USD/EUR correspondent flows; and a transfer-pricing policy governing intercompany service fees. Each of those elements is a separate legal and regulatory task. None of them can be completed without reference to the others.
The practical consequence of not integrating these tasks is that a structure optimised at the licensing layer creates problems at the banking layer, which in turn creates problems at the tax layer. We have seen businesses obtain FSCA authorisation only to discover that the licence entity's ownership structure triggered enhanced due diligence under FICA that no local bank was willing to process within the operator's launch timeline. The structural fix was straightforward; the timing cost was not.
In a recent cross-border mandate, an EMI payments platform licensed in the EU sought to route ZAR settlement through a South African subsidiary. We identified that the proposed intercompany structure would have been treated as a controlled capital transaction requiring SARB approval – a step the client had not anticipated. We restructured the intragroup agreement and prepared the SARB submission in parallel with the FSCA onboarding package. The banking relationship opened within the expected commercial timeline, and the tax position was confirmed before the first settlement. The integrated approach did not cost more time; it saved the delay that would have followed a sequential one.
CTA #2 — Reader who has already attempted onboarding
If a prior banking application stalled or an EMI declined onboarding, the structural reason is almost always identifiable in retrospect. A second read of the entity's documentation can surface the issue and the route back. Map your options with OBOLUS.
What does the onboarding process look like in practice?
The practical onboarding process for a South African crypto business seeking correspondent banking access moves through five sequential stages, each with its own legal preparation requirements. No stage can be safely skipped, and later stages depend on work done in the earlier ones.
The first stage is entity and structure review. Counsel assesses the existing or proposed entity structure against three criteria: FSCA licensing eligibility, SARB exchange-control compatibility, and bank due-diligence readiness. This review identifies any structural issues – ownership opacity, cross-border flow characterisation, intercompany arrangements – before they surface in a bank's compliance process.
The second stage is FSCA licensing or recognition. Where the business requires FSCA authorisation, counsel prepares and submits the application package, including the required compliance policies (AML/KYC/CFT, complaint handling, cybersecurity and operational risk). Where the business is licensed offshore and seeks to rely on a local representative or affiliate arrangement, counsel structures that arrangement to meet the FSCA's expectations without creating unintended regulatory perimeters.
The third stage is SARB exchange-control engagement. For businesses with cross-border fiat flows, this stage involves either confirming that a relevant dispensation applies or preparing and submitting an exchange-control approval application. Timing this stage in parallel with FSCA licensing, rather than after it, is the single most effective way to compress the overall onboarding timeline.
The fourth stage is bank and EMI pre-qualification. Before a formal onboarding application, counsel prepares a legal memorandum package tailored to the target institution's known due-diligence requirements. This package typically includes a regulatory status opinion, a beneficial ownership analysis, a compliance programme summary, and – for crypto-specific concerns – a transaction monitoring and Travel Rule compliance statement.
The fifth stage is ongoing compliance architecture. Once banking access is established, the structure must be maintained. FICA reporting obligations, SARB ongoing reporting, and the FSCA's continuing conduct requirements all apply. In our practice, we regularly advise clients on structuring their compliance function so that ongoing obligations are managed without requiring external counsel on routine matters.
Which structure fits which operator profile?
Not every digital-asset business entering the South African market faces the same structural question. The right approach depends on the operator's profile, its existing licensing footprint and its primary commercial objective.
A European-licensed CASP seeking to serve South African users without establishing a full local subsidiary should assess whether the FSCA's current position on cross-border activity permits a representative or introducer arrangement. That profile avoids the cost of a full South African entity but accepts a constrained service perimeter and limited ability to hold ZAR client funds locally. The timeline is shorter; the banking relationship will typically be EMI-only.
A standalone South African VASP seeking to operate domestically with full ZAR settlement should prioritise full FSCA authorisation, a local banking relationship and SARB exchange-control clearance for any offshore connectivity. This profile supports the broadest domestic service perimeter and the strongest banking relationship, but requires the most preparation and the most sustained compliance investment. The timeline is longer; the commercial position once established is more durable.
A cross-border payments operator routing fiat between South Africa and other markets – a remittance business or a stablecoin-enabled payment corridor – faces the most complex structure. It requires FSCA authorisation for the crypto layer, SARB approval for the cross-border payment layer, and typically an EMI or correspondent banking relationship in the destination currency jurisdiction. Allied counsel in the relevant offshore jurisdictions is essential for this profile. The timeline is the longest of the three; the regulatory risk of attempting this profile without an integrated structure is also the highest.
What mistakes does OBOLUS see most often in South African banking mandates?
The most common mistake is treating the bank as the last step rather than an active design constraint. Operators frequently complete FSCA licensing, select a corporate structure and negotiate commercial terms with local partners before approaching a bank. At that point, the structure is fixed, and any bank-level compliance issue requires a structural change that is costly and time-consuming. The solution is to involve banking counsel at the same time as licensing counsel – which is why we structure these as a single integrated mandate.
The second common mistake is underestimating FICA's beneficial ownership requirements. South Africa's AML regime has materially strengthened its UBO (ultimate beneficial owner) tracing requirements in recent years, and banks apply those requirements with increasing rigour. A structure with nominee directors, multi-layer offshore holding companies or trust interpositions will face enhanced scrutiny – sometimes refusal – regardless of its legitimacy. Pre-cleaning the ownership structure before the first banking conversation, or documenting it with sufficient legal opinion coverage, is the standard mitigation.
A third mistake – specific to operators who have read about South Africa's fintech environment and expect a permissive regulatory approach – is the assumption that a single offshore licence is enough to serve South African clients globally. South Africa maintains its own licensing requirements for activity directed at South African users. An FSCA-licensed competitor operating in the same market has a structural advantage in banking access, compliance posture and regulatory durability. The offshore-only approach works until it doesn't, and the failure mode – enforcement, account closure, user claims – tends to be abrupt.
Related at OBOLUS
Related at OBOLUS
- Banking, Payments & EMI Onboarding for Digital-Asset Businesses – end-to-end banking access strategy for licensed VASPs and payment operators
- Client-Funds Safeguarding for Established Operators – structuring segregation and safeguarding obligations across payment and custody layers
- Economic Substance for Licensed VASPs: A Cross-Jurisdiction Comparison – how substance requirements interact with the banking and licensing stack
FAQ
Why do banks close crypto company accounts?
Banks close crypto company accounts primarily because of de-risking pressure from their own upstream correspondent relationships, automated transaction-monitoring flags triggered by crypto-associated flows, and insufficient documentation of beneficial ownership and compliance controls at the point of onboarding. In South Africa, SARB exchange-control concerns add a further dimension: outbound flows associated with crypto settlement can trigger currency-control review if the flow architecture has not been pre-cleared. The solution is structural preparation before the first banking conversation, not after the account closure.
How can a VASP onboard with an EMI?
A VASP onboards with an EMI (electronic money institution) by submitting a due-diligence package that demonstrates regulatory status, beneficial ownership clarity, AML/CFT programme strength and Travel Rule compliance capability. Most EMIs relevant to South African operators are licensed in the EU or UK and apply their home-jurisdiction AML requirements to all customers. The VASP must also address SARB exchange-control treatment of any offshore EMI relationship before funds flow. Counsel prepares the onboarding package and advises on the exchange-control structure in parallel.
What does client-money safeguarding require?
Client-money safeguarding requires a licensed operator to hold client funds in accounts that are legally segregated from the operator's own assets and identifiable as client funds in the event of the operator's insolvency. Under most payment and custody regimes – including those applicable in South Africa's FSCA environment – the safeguarding obligation requires a specific account structure, documented trust or statutory construct, and regular reconciliation. The precise requirements vary by licence category and by the jurisdiction of the banking or EMI partner holding the funds. Counsel confirms the correct structure before client funds are received.
About OBOLUS
OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and payment operators on licensing across 70+ jurisdictions, on disputes and on-chain asset recovery across 25+ forums, and on the tax, banking and compliance that sit around them. In the South African and cross-border African context, we map the licence, banking and tax stack as one integrated mandate – not three disconnected workstreams. Digital assets are the whole of our practice. To discuss your situation, contact info@oboluslaw.com.
CTA #3
To map the licence, banking and exchange-control stack for your South Africa build, write to info@oboluslaw.com or message us via t.me/oboluslaw.
By Victor Olsen, Regulatory & Compliance Analyst – specialising in cross-border VASP licensing, AML/CFT compliance structuring and banking access for digital-asset businesses entering regulated markets.
This publication is general information about the law and does not constitute legal advice. It is not a substitute for advice tailored to your circumstances. OBOLUS accepts no liability for action taken or not taken on the basis of this material. For advice on your situation, contact info@oboluslaw.com.