Stay away from Mister Tango, it's not worth the trouble there are other EMI's which may work much better and are easier to comply to in regards to paperwork.
I couldn't resist and opened a new account with Mister Tango yesterday. We are still in some verification process because they rejected my bank statement which they wanted to verify.
I researched Internet but can't find any reason negatives. You guys sure it's all about fraud?
They are working at least.
But recently they started to request a lot of documents (e.g. bank statements, payslips) and also the TIN.
I think they will start reporting under CRS soon.
They already report under CRS - search in the forum for people asking about MIEGLT21 (Mistertango SWIFT Code) because they received post from there local tax authority it even don't know which financial institution is behind.
Regarding the publicity of personal data. During the investigation it has been determined than the website with the list of payments processed by MisterTango UAB were visible for more than 2 days (9-10 July 2018). The payments made by the customers of different bank institutions through the payment initiation service system of MisterTango UAB and personal data of such customers were made public. Besides, more than 9,000 SSs with the pages of details of the payment sessions of the customers of 12 different banks in different countries were made publicly available. Furthermore, it︀ has been determined that management, installation and maintenance of the IT infrastructure (hardware and software)︁ of MisterTango UAB were carried out by one employee. One employee fulfilled the contradictory functions.︂ Consequently, proper minimisation of possible unauthorised or unintentional modifications and implementation of proper personal data︃ protection policy were not ensured. Thus, MisterTango UAB has failed to choose the appropriate technical︄ or organisational measures which would help to ensure a level of security appropriate to the︅ risk, including protection against unlawful processing, disclosure, thus, breaching Articles 5 and 32 of the︆ GDPR.