AFSA FinTech Lab: AIFC regulatory sandbox application support
AFSA FinTech Lab provides a special route for testing innovative financial products under regulatory supervision. Before preparing an application, assess the service, the movement of funds and the risks. This guide explains the sandbox, application preparation, testing, ongoing obligations and exit planning.
What is the AFSA FinTech Lab regulatory sandbox?
AFSA describes FinTech Lab as a regulated environment for developing, testing and offering innovative financial and regulatory-technology solutions. Participants may receive temporary relief from certain requirements before moving to full authorisation. Activities remain subject to rules and regulatory supervision. Source: AFSA FinTech Lab.
The sandbox should not be treated as unrestricted permission to launch any financial service. Establish what the operator actually does, which permissions are required and which restrictions apply. Incorporating a company and authorising its activities serve different purposes.
Which projects may be considered?
AFSA’s overview includes digital-asset trading facilities, money services, brokerage, dealing, crowdfunding, security token offerings and other innovative models. Each proposal requires its own assessment. Digital-asset projects also need to consider the relevant activity categories and restrictions, including permitted assets. Source: Solutions Available for Testing.
Start by answering the following questions:
- Who is the customer, and where are they located?
- Who receives, holds and transfers money or digital assets?
- Does the company act for itself, for a client or only as a technology provider?
- Does it earn subscription revenue, commissions, a spread or another fee?
- Who is responsible for errors, fraud and operational failures?
Describing the business simply as an IT platform does not answer these questions. A diagram of one typical transaction, from onboarding to settlement and withdrawal, is a useful starting point.
Readiness for an AFSA FinTech Lab application
AFSA states that the testing regime may accommodate early-stage projects that do not yet meet the full set of regulatory requirements. Its benefits page also refers to evidence of adequate funds to cover at least 12 months of operating expenses. Assess the applicable requirements and calculations for the actual proposal. Source: Why Join FinTech Lab?.
For an internal readiness review, assemble the product description, funding plan, ownership structure and responsibilities. Distinguish between working functionality, demonstration-only features and development that remains to be completed. This makes the team’s capability and gaps easier to assess.
AFSA FinTech Lab: preparation stages
The following is a working sequence for organising legal preparation. It does not replace AFSA’s official process.
- Define the regulatory perimeter. Analyse services, contracts, clients, assets and geography.
- Plan the corporate structure. Identify the applicant, operator, owners and decision-makers.
- Develop the testing scenario. Set out the hypothesis, measures, proposed boundaries and stopping conditions.
- Prepare consistent documents. Align the model with funding, technology and operational procedures.
- Submit under the current process. Keep versions of submissions and organise responses to questions.
- Check licence conditions before operations. Explain the restrictions to the team and relevant service providers.
AFSA describes sandbox authorisation as a licence granting temporary relief from certain capital, IT-infrastructure and reporting requirements. The applicable permission and conditions determine what the business may actually do. Source: FTL Authorisation Process.
AFSA FinTech Lab application documents
AFSA publishes a FinTech Lab application, controller questionnaires, Approved Individual and Designated Individual forms, an invoice request and a testing-plan template. The forms required depend on the application structure. It also publishes an Exit Strategy template, to be signed at the application stage. Official application package.
For an initial consultation, prepare the following supporting working materials. This is not a statement that every document is mandatory in the same form for every applicant:
- A group structure and allocation of responsibilities.
- A funds-flow map and relationships with banks, platforms and contractors.
- Financial projections, funding sources and major costs.
- Technical architecture, access controls and failure-response arrangements.
- Draft user terms and risk disclosures.
- Questions concerning customer checks, sanctions and personal-data protection.
Preparing the AFSA FinTech Lab testing plan
A useful working plan makes the objective and assessment method clear. Before submission, agree on:
- The hypothesis: the specific problem the service is intended to solve.
- The scenario: what the customer, operator and contractors each do.
- The boundaries: proposed users, products, volumes and geography.
- The results: indicators that would demonstrate whether the solution works.
- The controls: how incidents, complaints and deviations are recorded.
- The stopping process: who decides to stop and what happens to unfinished transactions.
Do not copy the limits from someone else’s licence. Similar-looking products may differ materially in custody, execution and the customers they serve.
Supervision after authorisation
AFSA’s supervisory overview describes a case officer and reporting obligations. It lists monthly and quarterly reports, annual AML returns, IT audits, currency reporting and annual audit reports. Determine the applicable requirements and deadlines under current rules and the specific licence. Source: FinTech Lab Supervisory Regime.
Assign an owner to every obligation. Product teams need to understand the permission just as clearly as legal staff. Assess a proposed functionality change before implementing it, rather than assuming the existing licence covers it.
Exit planning and transition to full authorisation
AFSA explains that a participant must immediately implement its exit strategy when its licence is revoked, withdrawn or expires. Exit preparation is therefore part of planning the project. Source: Exit Strategy requirements.
Consider customer notices, unfinished transactions, return or transfer of assets where applicable, account access and record retention. The detailed arrangements depend on the service and contracts and require a separate review.
Under the full regime, AFSA expects compliance with the full regulatory requirements, including capital adequacy, cybersecurity, risk management and ongoing reporting. Successful testing should not be treated as automatic full authorisation. Source: transition to the full regime.
AFSA FinTech Lab preparation: timing and budget
Timing depends on product readiness, ownership, documentation and regulatory questions. A single timetable for every applicant would be misleading. Separate the team’s preparation, document work and external consideration in the project schedule.
Distinguish legal fees, regulatory payments, technology and security, control functions, audit and ongoing operating expenses. Check the applicable Fees Rules for current charges and agree the adviser’s scope in the engagement. Reduced regulatory fees do not make the overall project inexpensive by themselves.
FinTech Lab, Astana Hub and incorporation
AIFC company registration establishes a legal entity. FinTech Lab concerns testing a financial model under AFSA’s special regime. Astana Hub concerns technology-park participation. Start with the operator’s actual services, customers and transactions.
If a project combines software development and financial services, analyse those activities separately. A technology product alone does not determine the authorisation needed. See also AFSA licensing support.
Frequently asked questions
Can we operate immediately after incorporation?
First establish whether permission is required and what must be completed before starting. A certificate of incorporation does not replace this assessment.
Is the sandbox suitable for every crypto project?
The word crypto is not enough to determine a route. Analyse the actual transactions, assets, customers and restrictions.
Can we serve customers worldwide?
Assess geography separately. AFSA’s conditions and the law of the customer’s country may impose different obligations. Do not assume universal market access.
Can we start with an idea and no team?
An initial consultation can begin with an idea. Readiness for an official application depends on the proposal, resources and required evidence.
Does legal support guarantee a licence?
No. AFSA makes the decision. Preparation aims to make the model and documents clear, consistent and responsive to the applicable requirements.
Discuss the regulatory route with Benefits & Partners
Describe the proposed service, customers, company location and movement of funds. A general explanation is sufficient to frame an initial consultation. Do not send customer databases, access keys or unnecessary personal documents in the first message.
WhatsApp Business: +7 (707) 350 92 75 · Additional phone: +7 (705) 292 90 99 · Contacts
This material provides a general explanation and does not replace project-specific advice. Conclusions depend on current rules and licence conditions. Sources checked on 19 October 2026.