Regulatory Terminalszyma.co
Work with me
terminal / c / gap-binance-bh

Binance Bahrain B.S.C. (c)

1 holdingBH✓ 1 authorised
LEIno data
HOLDINGS
1
RENTED ROUTES
0
Markets covered
1
First recorded grant
no data

Licence stack

one row per holding
JURREGIMEREGISTER IDAuthorisedSTATUS
BHCrypto-Asset Services Module (CRA) Licence / Bahrain / CBBno datasource text changedAno dataauthorised
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 FZEc:binance-fzenot linked
Binance Japan Inc.c:binance-japanlinked to a parent
Binance Holdings Limitedc:binance-holdingsparent of another record
BINANCE SERVICES LATINOAMÉRICA S.A. DE C.V. -S.S.Ec:gap-binance-latam-arnot linked

What the stack covers

own licences and rented routes
BH
own licence / passportedunverifiedRvia partnerHhypothetical
Full breakdown by market
COVERED
Bahrain4
Crypto custody admin
own licenceconsumer · SME · corporateconditional
Crypto exchange for funds
own licenceconsumer · SME · corporateconditional
Crypto trading platform
own licenceconsumer · SME · corporateconditional
Crypto transfer services
own licenceconsumer · SME · corporateconditional
UNVERIFIED — CLAIMED, NOT TRACEABLE TO A LICENCE

No unverified rows.

Products it can offer

Stablecoin custody1

Where it relies on someone else’s licence

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

History

register grant dates
No grant dates stated by the registers

Next steps

Compare with your own footprintOpen the planner→See who else covers a marketCoverage matrix→
Is something wrong here? Send a correction.

Need this implemented in your product?

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

Company: Binance Bahrain B.S.C. (c)

Work with me