For many in the FinTech world, embedded finance and banking-as-a-service (BaaS) are not new notions. Many user-facing companies have built their apps on top of a financial infrastructure provider. This way, they can focus on growing their product and getting more users.
As a response to increasing interest in crypto, FinTechs now want to build crypto wallets, exchanges, and cards into their own apps. Unfortunately, shifting regulations and complex technology end up creating long delays, unplanned costs, trouble with banking and financial institutions, and regulation scale.
In parallel, cryptocurrency adoption has been growing at a staggering rate over the last 2 years. Early adopters in general no longer consider banking and financial services to be complete if they don’t have integration with the digital asset world.
Enter Crypto-BaaS. A nascent industry that provides all the infrastructure for companies to integrate crypto and fiat features into their own apps. The market is starting to take shape: In the US, SolidFi is gaining ground against Synapse. For Europe, Striga is positioning itself to be the top player.
But enough context – The question here is: How does Striga compare to the average Crypto-BaaS?
Time to market is affected mainly by the features chosen to be integrated and the skill of the client’s developer team. Integrating just a wallet takes much less than launching a physical card program, where design and manufacturing are needed.
That said, most Crypto-BaaS, Striga included, usually take between 6 weeks and 3 months to fully deploy a product, from the moment you sign a contract. This is faster than all other categories of financial infrastructure providers out there.
Time to Market
1.5 – 3 months
1.5 – 3 months
The usual commercial structure is broken down into two:
Upfront Cost (EUR)
5,000
20,000 – 30,000
Monthly Minimum / Subscription Fee (EUR)
3,000
10,000
All blockchain infrastructure companies offer standard banking services, like IBAN accounts. What usually differentiates them is having some or all of the following 5:
Native Crypto Support
Yes
Yes
White Label Infrastructure
Yes
Sometimes
Card Issuing
Yes
Yes
Apple Pay & Google Pay
Yes
Yes
Product lifecycle management via dashboard
Yes
Yes
While financials and services are essential to make a product great, you need to integrate the APIs first. Ask any developer team: if the technical setup is not properly designed, a simple —even enjoyable— setup, can become a months-long nightmare.
Besides the documentation being high-quality, the 4 following elements make the technical setup friendlier:
Publicly Available Sandbox
Yes
No
Number of Partners Required to Go Live
1
1
Interactive Setup Guide
Yes
No
Public API Documentation
Yes
Yes
So, integrations were easy to connect, the app has all the features your user’s love, and it is actually making you money due to great financials. The only thing that could put a stop to it is making a regulatory mistake and getting shut down.
There are 3 things to know if you want to stay in business: Know your customer (KYC), Anti-money laundering (AML), and Licenses. The big question here is “who handles the KYC/AML process and holds the licenses”. Being in charge allows for more flexibility, but requires more resources and responsibility.
Outsourceable KYC
No
No
Outsourceable AML
No
No
Licenses or Commercial Registrations NOT Required
Yes
Yes
It really depends on what you are looking for.
If what you want is to operate straight away in the US market, you may explore fintech cryptocurrency providers in North America, as there are a couple of very good ones.
If you want to operate in the European market, and want to get both excellent financials and an easy technical setup, then Striga can be an ideal choice for you.
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |