The main risk is submitting a commercial description that does not match the actual operations. This guide sets out a preparation method for project owners, but it does not replace official forms or legal advice. The exact requirements must be confirmed based on the activity and the rules applicable when the business launches.
In brief
- Aviso No. 2/2024 establishes prior registration for professional activities involving virtual assets within its scope.
- The application must clearly explain the organization, responsible individuals, flows and control mechanisms.
- Submitting an application does not constitute approval: starting operations on the basis of administrative silence can lead to a serious mistake.
Crypto regulation in Cape Verde: map the functions
Start by mapping what the customer can actually do. Our guide to the criteria and legal statuses of African platforms provides a useful framework for distinguishing purchases, exchanges, transfers and custody. Calling a business a fintech does not replace any of these categories. A company may combine several of them, with different responsibilities at each stage.
The official text of Aviso No. 2/2024 is the key working reference here. It covers, among other things, exchanges against currency, exchanges between virtual assets, transfers, and the custody or administration of assets or instruments enabling their control. The analysis must therefore follow the actual operating model, including tasks assigned to partners.
Consider a fictional project that charges a commission to purchase assets on behalf of clients while an overseas partner holds the keys. The absence of an in-house wallet does not eliminate the other functions. The application must show who receives orders, who collects funds, who executes transactions and who is responsible if something goes wrong. An outsourcing agreement does not remove the need to understand this division of responsibilities.
Next, describe the project’s territorial connection with Cape Verde. The text covers several forms of presence or activity, not merely an application hosted locally. Incorporation, domicile, establishment and certain reporting obligations may fall within its scope. A foreign structure should therefore not automatically assume that a remote sale is outside any local analysis.
This mapping also helps identify other regulatory issues. A payment service, the collection of repayable funds or an investment product may require a separate assessment. The presence of a virtual asset in a transaction flow does not turn every financial function into a single category. Have these boundaries reviewed before calculating launch costs.
Prepare an application that describes a verifiable business
Preparation is easier when it begins with a document inventory. Gather the entity’s identity, ownership structure, beneficial owners, directors and control officers. Each document should correspond to a specific piece of information. A decorative organization chart with no connection to decision-making powers will not show who actually runs the operations.
The business model also deserves a concrete description: target customers, geographic areas, services, revenue and expenses. The text notably requires business-plan elements and projections for the first years. A forecast does not prove future profitability; it should show the assumptions, funding needs and how the company would withstand activity below expectations.
In a fictional educational example, a company expects 1,000 monthly transactions generating 100 CVE each. It therefore anticipates 100,000 CVE in gross revenue. With 70,000 CVE in fixed costs and 20,000 CVE in variable costs, 10,000 CVE would remain before other unmodeled items. This scenario is neither an industry budget nor a regulatory threshold.
If volume falls to 500 transactions and the unit variable cost remains 20 CVE, revenue drops to 50,000 CVE against 80,000 CVE in modeled costs. The deficit reaches 30,000 CVE. A sound projection explains who will fund that shortfall without treating client assets as available working capital. This is a question of economic consistency before any marketing promise is made.
Also set out skills and responsibilities. Who authorizes an exceptional withdrawal? Which officer handles an alert? Who is responsible for changing a destination address? The answers must match technical access rights and procedures. Naming someone on paper without giving them the resources or availability required does not create effective control.
Connect vigilance, IT architecture and payments
The BCV communication on the framework recalls its purpose of preventing money laundering and terrorist financing. A vigilance policy must therefore explain how the service knows its customers, assesses risk and handles problematic situations. Copying a foreign procedure that has no connection to local flows does not demonstrate this.
Our analysis of KYC and data protection helps distinguish necessary collection from unjustified accumulation. Define the documents requested, internal access rights and transmission channels. Sales teams do not need to receive sensitive documents in their personal messaging accounts simply to answer a pricing question.
The technical architecture should describe custody, logs, backups and external dependencies. A failure affecting an identity provider or payment system should not trigger uncontrolled manual approvals. Instead, provide for a documented suspended state, clear information for the customer and verifiable restart rules.
For keys, document what actions can be taken rather than listing only software names. Our guide to wallets and their security mechanisms distinguishes account access from the ability to sign. A company’s application must go further: separation of duties, an emergency procedure and a process for the departure of an employee with critical access.
Bank payments require their own framework. The BCV presents the framework for payment institutions separately. Do not assume that registration related to virtual assets automatically authorizes payment activity or the issuance of electronic money. A banking partner should not have to discover the true nature of the flows after they begin.
Follow the procedure without inventing tacit approval
The regulatory timetable is not the same as the timetable for a fundraising round or advertising campaign. Aviso provides for review periods and the possibility of requests for additional information. In the version examined, silence at the end of the stated maximum period does not mean acceptance: the text provides for a presumption of refusal. A project should therefore not announce that it has been authorized simply because it has been waiting for a long time.
Formal requirements also matter. The article on language provides for Portuguese in forms and several documents, along with specific requirements for foreign documents and their translations. Prepare for these constraints before filing. An application submitted in an unsuitable format or language can waste time without advancing the substantive review.
Keep a version log: submission date, list of documents, official recipient and responses received. Every change should be traceable to the original application. A team that mixes three contradictory commercial presentations may no longer know which activity it actually described to the authority.
The text also provides for notifications concerning changes and record-keeping obligations for originals submitted with applications. The seven-year period mentioned in this context should not be turned into an improvised universal rule for all customer data. Each document category requires its own legal basis, purpose and retention conditions.
Before making any public communication, review the wording used. An application submitted, registration obtained and authorization covering a specific activity do not describe the same situation. A sales team must be able to respond without presenting an ongoing formality as an acquired guarantee. This discipline also reduces misunderstandings with partners.
Plan for changes and closure from the outset
An activity evolves after launch: new countries, additional assets, a change of director or a new custody provider. The framework provides for different treatments of modifications, particularly when they change the type of activity or certain risks. Introduce a prior review of new developments rather than relying on an annual review that discovers changes only after they have gone live.
Economic monitoring complements legal oversight. Our method for calculating crypto fees in Africa can help test whether promised prices are consistent with the costs incurred. If a promotional price requires delaying withdrawals to preserve cash flow, the issue goes beyond marketing. Service terms must remain sustainable without depending on a constant influx of new customers.
Also prepare a wind-down procedure: communication, stopping new transactions, restitution in accordance with the contracts and preservation of evidence. A closure should not leave users staring at a blank screen. Those responsible must know which commitments remain outstanding and which contacts will take over when commercial activity ends.
Tax, corporate law, contracts and data protection do not disappear behind the crypto application. Consult qualified professionals for the specific project. This guide is neither an exhaustive list of obligations nor an individual assessment. Official sources and exchanges with the authority must remain the reference points when decisions are made.
The most useful deliverable before launch is ultimately a coherent file: actual functions, identified responsible individuals, explained flows, addressed risks and demonstrated status. If two documents give different answers about ownership of funds or control of keys, correct the contradiction before receiving the first payment. Accurate documentation is worth more than a compliance promise that cannot be verified.
