Regulatory Terminalszyma.co
terminal / c / binance-fze

Binance FZE

2 holdingsAE✓ 2 authorised
LEIno data
HOLDINGS
2
RENTED ROUTES
0
Markets covered
1
First recorded grant
2024-04-15

Licence stack

one row per holding
JURREGIMEREGISTER IDAuthorisedSTATUS
AEVA Exchange Services Licence / Dubai / VARAVL/24/04/001source text changedA2024-04-15authorised
AEVA Broker-Dealer Services Licence / Dubai / VARAVL/24/04/001source text changedA2024-04-15authorised
Not mapped yetLicences outside the regimes in our data are not shown for this company.

Company group

This record is not linked to a parent in the data. 4 other records in the corpus share this trading name. They are listed, not linked: a shared name is not evidence of ownership.
Binance Japan Inc.c:binance-japanlinked to a parent
Binance Holdings Limitedc:binance-holdingsparent of another record
Binance Bahrain B.S.C. (c)c:gap-binance-bhnot linked

What the stack covers

own licences and rented routes
AE
own licence / passportedunverifiedRvia partnerHhypothetical
Full breakdown by market
COVERED
Dubai (VARA virtual-asset scope, outside DIFC)2
Crypto exchange for funds
own licenceconsumer · SME · corporate
Crypto trading platform
own licenceconsumer · SME · corporate · regulated FIconditional
UNVERIFIED — CLAIMED, NOT TRACEABLE TO A LICENCE

No unverified rows.

Products it can offer

No product configuration resolves against this regime.

Where it relies on someone else’s licence

Nowhere. All coverage rests on licences this company holds itself.

History

register grant dates
2024-04-15
VA Exchange Services Licence / Dubai / VARA granted
2024-04-15
VA Broker-Dealer Services Licence / Dubai / VARA granted

Next steps

Need this implemented in your product?

I turn requirements like these into flows, vendor setups, tests and audit evidence.

Company: Binance FZE

Work with me