Turkey
TR
Regimes
2
Central Bank of the Republic of Turkey
Companies
8
8 active licences
Passporting in
0
0 home states
Activities
3
/ 25
PROVENANCE
0% registry0% document100% inferred
REGIMES IN THIS JURISDICTION
click a tier for its sourceREGIME · STATUTEACTSMIN CAPITALTIMELINEAPPLICATION FEE
Payment Institution Licence / Turkey / Law 6493Law No. 6493 on Payment and Secur… · Central Bank of the Republic of Turkey
Execute payment transactions (direct debits, card payments, credit transfers), Money remittance2/25 · 2 holders
TRY 30,000,000 source host unreachable
no data
no data
→Electronic Money Institution Licence / Turkey / Law 6493Law No. 6493 on Payment and Secur… · Central Bank of the Republic of Turkey
Issue electronic money1/25 · 6 holders
TRY 80,000,000 source host unreachable
no data
no data
→Licences issued here
8 activeSource: Central Bank of the Republic of Turkey’s public register, read 1 Sep 2026
| Company | Regulator | Licence | Covers | Granted |
|---|---|---|---|---|
| Aköde Elektronik Para ve Ödeme Hizmetleri A.Ş. | Central Bank of the Republic of Turkey | Electronic Money Institution Licence | E-money | not published |
| BRQ Link Elektronik Para ve Ödeme Hizmetleri A.Ş. | Central Bank of the Republic of Turkey | Payment Institution Licence | Payments | not published |
| İyzi Ödeme ve Elektronik Para Hizmetleri A.Ş. | Central Bank of the Republic of Turkey | Electronic Money Institution Licence | E-money | not published |
| MoneyGram Turkey Ödeme Hizmetleri A.Ş. | Central Bank of the Republic of Turkey | Payment Institution Licence | Payments | not published |
| Ozan Elektronik Para A.Ş. | Central Bank of the Republic of Turkey | Electronic Money Institution Licence | E-money | not published |
| Papara Elektronik Para A.Ş. | Central Bank of the Republic of Turkey | Electronic Money Institution Licence | E-money | not published |
| Sipay Elektronik Para ve Ödeme Hizmetleri A.Ş. | Central Bank of the Republic of Turkey | Electronic Money Institution Licence | E-money | not published |
| Turkcell Ödeme ve Elektronik Para Hizmetleri A.Ş. | Central Bank of the Republic of Turkey | Electronic Money Institution Licence | E-money | not published |
INBOUND PASSPORTING — REGIMES ELSEWHERE THAT REACH THIS MARKET
HOME REGIMENo inbound passporting reaches this jurisdiction.
ACTIVITIES PERMITTED IN THIS JURISDICTION
3Execute payment transactions (direct debits, card payments, credit transfers)Conferred by Payment Institution Licence / Turkey / Law 6493 (for consumer, sme, corporate, via-intermediary)
Issue electronic moneyConferred by Electronic Money Institution Licence / Turkey / Law 6493 (for consumer, sme, corporate, via-intermediary)
Money remittanceConferred by Payment Institution Licence / Turkey / Law 6493 (for consumer, sme, corporate, via-intermediary)
PRODUCTS AVAILABLE HERE
0PRODUCTCLIENT TYPESTATUSMISSING ACTIVITIES
Card issuingconsumer · SME · corporate · via intermediarynoneIssue payment instruments and/or acquire payment transactions, Issue card-based payment instruments (card issuing)
Cross-border remittanceconsumer · SME · corporate · via intermediarynoneCross-border remittance as a distinct commercial activity
Crypto off-ramp (crypto to fiat payout)consumer · SME · corporate · via intermediarynoneExchange crypto-assets for funds
Crypto on-ramp (fiat to crypto)consumer · SME · corporate · via intermediarynoneExchange crypto-assets for funds
IBAN accountsconsumer · SME · corporate · via intermediarynonePlace cash on a payment account, Cash withdrawal from a payment account, Issue IBAN accounts in the institution's own name
Merchant collectionsconsumer · SME · corporate · via intermediarynoneAcquire card-based payment transactions (card acquiring)
Payoutsconsumer · SME · corporate · via intermediarynoneCurrency conversion (FX) as a service
Stablecoin custodyconsumer · SME · corporate · via intermediarynoneProvide custody and administration of crypto-assets on behalf of clients
Stablecoin orchestrationconsumer · SME · corporate · via intermediarynoneProvide custody and administration of crypto-assets on behalf of clients, Exchange crypto-assets for funds
CHANGES
Nothing to show yet. A change log needs two snapshots to compare, and history only began being recorded on 2026-08-14 — the builds captured so far differ by zero values. Rather than back-fill invented history, this fills in as the corpus actually moves.
Need this implemented in your product?
I turn requirements like these into flows, vendor setups, tests and audit evidence.
Jurisdiction: Turkey