The NAGA Wallet is backed by one of the fastest growing FinTech companies in Germany, and we are listed on the German Stock Exchange. Thus, we have a naturally high responsibility in regards to each product we have built and which we operate.


We are here to stay. We have successfully raised over $80m in Capital, have a European-wide team and are listed on one of the largest stock exchanges in the world with a market capitalization north of $250m. We only started our journey 2,5 years ago and we are quickly gaining traction now. We are a reliable service provider, dedicated to every customer and user that connects to NAGA!


We highly recommend that you use the Multi-Factor-Authentication (MFA) to further secure your account. If MFA is active, you will be asked to enter your security code everytime you login or withdraw. Furthermore, SMS and E-mail verification will be enabled soon.

You will be able to manage how many levels of security you want to apply to your withdrawal operations.

For example, you can say: Only allow a withdrawal if I have entered my MFA Code, have entered a unique SMS Code and confirmed the withdrawal request via e-mail. This coupled with the login via your username and password, will give you 4 levels of security.


The Wallet development has been tested intensively by several hacker groups. Also, we consulted professional expert firms such as Voltium Security AB who support the world's largest music streaming service, Spotify.


A2:2017-Broken Authentication
A3:2017-Sensitive Data Exposure
A4:2017-XML External Entities (XXE)
A5:2017-Broken Access Control
A6:2017-Security Misconfiguration
A7:2017-Cross-Site Scripting (XSS)
A8:2017-Insecure Deserialisation
A9:2017-Using Components with known vulnerabilities
A10:2017-Insufficient Logging & Monitoring


We have undergone extensive advanced penetration tests, checks on our cloud security and amended our entire internal security architecture based on all findings.

But it doesn't stop here, we are constantly arranging internal Hackathons in order to find any possible point of vulnerability.

P.S. If you think you've found any bug or security issue/breach, please contact a member of our staff. 

We hope this guide was helpful. Read more articles in the Help Center. If you still have questions contact Support Center directly via [email protected]

Did this answer your question?