ASFI and ETF readiness
Assess classification, licensing route, adequacy needs, operational controls, and documentation gaps.
Know your ASFI and ETF path before you launch
Vado Bolivia helps exchanges, wallets, PSAVs/VASPs, payment platforms, and fintech teams review their regulatory exposure, ASFI adecuacion and licensing path, and operating controls before launch.
Where we help
From product concept to regulated operations
Exchanges, wallets, and payment platforms need to know what they are under ASFI and UIF rules before they build the launch around it.
PSAV/VASP and UIF compliance
Build AML/KYC, due diligence, transaction monitoring, reporting, and recordkeeping procedures.
Wallet and exchange operations
Map custody, transfers, conversion, fees, user communications, risk controls, and provider responsibilities.
Payment-system analysis
Review payment instruments, settlement, interoperability, BCB relevance, and consumer protection.
Sandbox or partner path
Evaluate whether to test through ECP, launch through a regulated partner, or pursue direct authorization.
Launch documentation
Prepare policies, terms, contracts, diagrams, operating manuals, and board-ready launch materials.
Why this matters
What you are determines what you can build
Most fintech problems in Bolivia trace back to one unanswered question: what are you under the rules? A wallet, an exchange, a payment platform, and a PSAV/VASP carry different obligations, and the classification shapes your licensing, your AML/KYC program, your custody model, and your provider contracts. Build the product first and discover the classification later, and you end up rebuilding under pressure.
The framework is also still maturing, which cuts both ways. There is room to lead the interpretation, but the responsibility lands on you to do it carefully and document it. ASFI now expects bank-level traceability and controls from operators in this space, and a clean filing path is what keeps a launch from stalling.
Vado Bolivia combines the legal and the technical so you get one coherent answer. We advise, we do not move money or run a desk, so the analysis is about your product, not about selling you a rail. We map the legal path, close the documentation gap, and give you a launch that regulators, partners, and banks can follow.
Deliverables
What a fintech engagement leaves you with
Advice becomes the documented file ASFI, UIF, partners, and your board expect.
Classification and licensing roadmap:
Where you sit under ASFI and ETF rules, the route to authorization, and the open questions.
AML/KYC and UIF program:
Due diligence, monitoring, reporting, and recordkeeping procedures your team can run.
Operations and controls map:
Custody, transfers, conversion, fees, and provider responsibilities, documented end to end.
Launch documentation pack:
Policies, terms, contracts, diagrams, and operating manuals ready for filing and launch.
FAQ
Fintech, PSAV, and VASP compliance in Bolivia
Is my fintech a PSAV or VASP under Bolivian rules?
That classification drives everything else. We assess your product flow, user roles, custody model, and currencies against ASFI and ETF categories to determine whether you are a PSAV/VASP, a payment service, or something outside the perimeter, and what that means for licensing.
What does the ASFI adecuacion path involve?
We map the licensing route, adequacy needs, operational controls, and documentation gaps, then build the file: the narrative, diagrams, policies, and evidence ASFI expects. The aim is a defensible path rather than a one-off memo.
Should we launch directly, through a partner, or in a sandbox?
It depends on your model and risk appetite. We evaluate whether to test through the ECP sandbox, launch through a regulated partner, or pursue direct authorization, and we lay out the trade-offs so you can choose with clear eyes.
What does the first engagement look like?
Most clients start with a paid Diagnostic. Bring the product flow, user roles, providers, currencies, custody model, volumes, and filing status. We map the legal path and the documentation gap, then help you close it.
Next step
Know what you are before you launch
Bring the product flow, user roles, providers, currencies, custody model, volumes, and filing status. We will map the legal path and documentation gap.
