Jump to

Bank Secrecy, Payment Secrecy and KVKK: How Fintechs May Share Customer Data in Türkiye

Bank Secrecy, Payment Secrecy and KVKK: How Fintechs May Share Customer Data in Türkiye

A signed KVKK consent form does not unlock every data flow. Since a 2020 amendment to Banking Law No. 5411, a bank’s customer secrets may not be shared with third parties in Türkiye or abroad without the customer’s request or instruction, even with KVKK explicit consent. Payment and e-money institutions face their own Central Bank (TCMB) secrecy and localisation rules, and everyone is subject to KVKK’s cross-border regime as rebuilt from 1 June 2024. This guide maps, as of November 2026, what may go to bank partners, cloud vendors, group companies, marketing partners and the credit bureau.

Three layers, and why consent is not enough

  • Bank secrecy: Banking Law Art. 73 and the BDDK Regulation on the Sharing of Secret Information (Official Gazette 4 June 2021, No. 31501, in force since 1 July 2022; “BDDK Regulation”).
  • Payment secrecy: Law No. 6493 Art. 32, the TCMB Regulation on payment services (“TCMB Regulation”) and the TCMB Communiqué on information systems and data-sharing services (“Communiqué”), both of 1 December 2021.
  • Data protection: KVKK (Law No. 6698), Arts. 5, 6, 8 and 9.

KVKK reserves other laws’ provisions on domestic transfers (Art. 8(3)) and transfers abroad (Art. 9(10)), while the TCMB rules apply KVKK first to personal data processing (TCMB Regulation Art. 62(5); Communiqué Art. 9(7)). So every flow needs a KVKK basis and, separately, a secrecy route.

Bank secrecy: the request-or-instruction rule

Data specific to banking activities that arises after a customer relationship with a bank is established becomes a customer secret (Art. 73(3)). Any information showing that someone is a bank’s customer is itself a customer secret, and pre-existing data such as a name becomes one once processed in a way that reveals the banking relationship (BDDK Regulation Art. 4(3)-(4)).

Outside the listed exceptions, sharing needs the customer’s request or instruction, and neither consent nor instruction may be a precondition for the bank’s services (Art. 6(3)). An instruction may be written or, if provable, given through a durable medium; it may cover several transactions and must be revocable the same way (Art. 6(4)). For transactions that inherently involve other banks or payment systems, such as transfers, customer initiation counts as the instruction (Art. 6(6)).

Secrecy follows the data: it binds anyone who learns bank or customer secrets through their capacity or duties (Art. 73(3)), including someone obtaining another bank’s customer secrets (BDDK Regulation Art. 4(3)). And every share, even under an exception, must be limited to its purpose and the data it requires, using aggregated, de-identified or anonymised data where that suffices (Art. 73(3); BDDK Regulation Art. 6(1)). Health and sex life data may never be shared under an exception (Art. 6(2)). Breach carries one to three years’ imprisonment and a judicial fine of 1,000 to 2,000 days, and the same penalties apply to third parties who disclose such secrets (Art. 159).

The exceptions partnerships rely on

Each exception in BDDK Regulation Art. 5(2), which mirrors Banking Law Art. 73(4), requires a confidentiality agreement and a limited purpose. Three matter here:

  • exchanges among banks and financial institutions, directly or through the Risk Centre or companies set up by at least five of them (Art. 5(2)(a));
  • information to a parent holding 10% or more, in Türkiye or abroad, for consolidated accounts, risk management and internal audit (Art. 5(2)(b));
  • information to providers of valuation, rating, support services and audit, or other service providers taking the necessary technical and administrative measures (Art. 5(2)(ç)).

The service-provider route is narrower than it looks: for support services and other procurement outside the bank’s “primary systems” (valuation, rating and audit aside), the customer’s request or instruction is still required (Art. 6(5)). In service model banking, the interface provider’s systems count as primary systems and the bank’s sharing with it falls under Art. 5(2)(ç) (Digital Banks Regulation Art. 13(7)); see our BaaS and embedded finance article.

In group sharing, customers the parent or group company does not also serve must, as a rule, not be identifiable (Art. 6(1)(ç)), and the bank reports group sharing and recipients’ countries to the BDDK every six months (Art. 5(9)). On economic security grounds, the BDDK Board may ban sharing secrets with third parties abroad and require banks to keep systems and backups in Türkiye (Banking Law Art. 73(3); BDDK Regulation Art. 6(11)).

Payment and e-money institutions: the TCMB rules

Under Law No. 6493, shareholders, directors and staff of a payment or e-money institution, its outsourcing providers’ employees and third parties who disclose the institution’s or its customers’ secrets to anyone but authorities expressly empowered by law face one to three years’ imprisonment and a judicial fine of up to 1,000 days (Art. 32). TCMB rules add:

  • Payment data may be used within the institution’s legal powers after clearly informing the customer; for purposes not directly related to the payment service, the customer’s approval is needed, and explicit consent for personal data (TCMB Regulation Art. 62(1)).
  • Sensitive customer data (data usable for payment orders or authentication that could enable fraud) may go only to outsourcing providers and empowered authorities, unless the rules allow otherwise. Other customer information (transactions, balances, personal data, identifiers) may go to other parties only after the customer is told the limits of the sharing and gives explicit consent, which may not be a precondition for the service (Communiqué Arts. 3, 9(6)). Read literally, this covers every recipient other than authorities, so check each flow.
  • Data obtained through account information or payment initiation services may not be passed on without the customer’s request or instruction, even with approval (TCMB Regulation Art. 62(4)); see our open banking guide.
  • A foreign outsourcing provider’s country must not block TCMB’s information requests and audits (TCMB Regulation Art. 21(7)).

Localisation: where offshore vendors stop

Payment and e-money institutions keep documents and records for at least ten years in Türkiye (Law No. 6493 Art. 23(1)); breach carries one to three years’ imprisonment and a judicial fine of 500 to 1,500 days (Art. 31(1)). Under the Communiqué:

  • primary and secondary systems and backup centres must be in Türkiye, as must systems (including an outsourcing provider’s) used to execute payments between customers (Art. 21(1)-(2));
  • cloud services must be set up in Türkiye, and customer-identifying or personal data may be processed only in a private cloud or a qualifying community cloud; test environments without customer data are excluded (Art. 16(7));
  • for a payment with a party abroad, the data needed to complete it may be shared abroad on the customer’s request or instruction, proportionately, while still stored in Türkiye and subject to KVKK Art. 9; TCMB may stop or restrict this (Art. 21(4)).

In our view, offshore SaaS storing Turkish customer data rarely fits these rules, whatever KVKK safeguard is signed.

The KVKK cross-border regime since 1 June 2024

Law No. 7499 (Official Gazette 12 March 2024, No. 32487) rewrote KVKK Art. 9 from 1 June 2024. The first two routes below also need a condition under Art. 5 or 6:

  • a KVKK Board adequacy decision for the country, sector or international organisation (Art. 9(1));
  • an appropriate safeguard, if data subjects can enforce their rights there: Board-approved binding corporate rules, the Board’s standard contract, a Board-authorised written undertaking, or an agreement between public bodies (Art. 9(4));
  • failing both, an incidental derogation such as informed explicit consent (Art. 9(6)). The transfer Regulation (Official Gazette 10 July 2024, No. 32598) defines incidental transfers as irregular, one-off or occasional and outside the ordinary course of business (Art. 16(1)).

The standard contract must be used unchanged (Regulation Art. 14(3)) and notified to the KVKK Authority within five business days of signature, by the exporter unless agreed otherwise (Law Art. 9(5); Regulation Art. 14(5)). Missing the notification carries its own administrative fine for the controller or processor (Art. 18(1)(d), (2)). The Board adopted four modules by decision 2024/959 of 4 June 2024; our KVKK standard contracts page explains them. All of this sits on top of secrecy and localisation, not instead of them.

Data flows at a glance

Data flow KVKK Bank: extra step Payment or e-money institution: extra step
Bank partner (BaaS, interface provider) Art. 5 condition, notice Service-provider exception, confidentiality agreement, minimum data; instruction if outside primary systems Sensitive data only to outsourcing providers; other customer information with notice and explicit consent
Cloud or IT vendor abroad Adequacy or safeguard; standard contract notified in five business days Service exception with measures (instruction if outside primary systems); BDDK may ban transfers abroad or require local systems Systems and backups in Türkiye; domestic private or community cloud
Group parent abroad Binding corporate rules or standard contract 10%+ parent for consolidation, risk, audit; non-shared customers unidentifiable; six-monthly report No group exception: notice and explicit consent
Marketing partner In practice explicit consent Customer request or instruction; consent alone insufficient Approval plus explicit consent; never a precondition
Risk Centre (credit bureau) Legal obligation for members Outside secrecy (Art. 73(4)) Members: credit institutions and BDDK-approved financial institutions; others get risk data only with customer consent (Banking Law Additional Art. 1)
Open banking data Art. 5 condition, notice Same TCMB rule, on top of Art. 73 No onward sharing without customer request or instruction

More in our fintech law hub.

Where to start

  • Map every outbound flow: recipient, country, fields, purpose, and whether the data is a bank customer secret, TCMB customer information or sensitive customer data.
  • Record per flow the KVKK basis (plus the Art. 9 tool if abroad) and the secrecy route.
  • Capture instructions and consents separately from service acceptance, revocably and with logs; minimise data wherever the purpose allows.
  • Check hosting: Türkiye-based systems and backups; private or community cloud for customer data.
  • Sign standard contracts unchanged and diarise the five-business-day notification.
Mapping your customer data flows?Vircon Legal reviews fintech data flows against bank secrecy, TCMB rules and KVKK, and drafts the instructions, consents and transfer documents they need.

Talk to us →

Is KVKK explicit consent enough for a bank to share customer data with a fintech partner?

No. Outside the Art. 73 exceptions the bank needs the customer’s request or instruction, which explicit consent does not replace (Banking Law Art. 73(3); BDDK Regulation Art. 6(3)).

Can a Turkish payment institution host customer data with a foreign cloud provider?

Not on infrastructure abroad: under the Communiqué, cloud services must be set up in Türkiye, customer-identifying data needs a private or qualifying community cloud (Art. 16(7)), and core systems and backups must be in Türkiye (Art. 21(1)).

Must an intra-group standard contract be notified to the KVKK Authority?

Yes, within five business days of signature, if the standard contract is the safeguard (KVKK Art. 9(5)); Board-approved binding corporate rules are the alternative.

Sources. Banking Law No. 5411 (RG 1.11.2005, No. 25983 (Mükerrer)), Arts. 73, 159, Additional Art. 1; BDDK Regulation on the Sharing of Secret Information (RG 4.6.2021, No. 31501; amended RG 24.12.2021, No. 31699), Arts. 4 to 6, 8; BDDK Regulation on Digital Banks and Service Model Banking (RG 29.12.2021, No. 31704), Art. 13(7); Law No. 6493 (RG 27.6.2013, No. 28690), Arts. 23, 31, 32; TCMB Regulation on Payment Services and Electronic Money Issuance and Payment Service Providers (RG 1.12.2021, No. 31676, as amended to RG 4.9.2026, No. 33360), Arts. 21, 62; TCMB Communiqué on Information Systems of Payment and E-Money Institutions and Data-Sharing Services (RG 1.12.2021, No. 31676, as amended to RG 4.9.2026, No. 33360), Arts. 3, 9, 16, 21; Law No. 6698 (KVKK) (RG 7.4.2016, No. 29677), Arts. 5, 6, 8, 9, 18; Law No. 7499 (RG 12.3.2024, No. 32487), Arts. 34, 35, 40; Regulation on the Procedures and Principles for the Transfer of Personal Data Abroad (RG 10.7.2024, No. 32598), Arts. 14, 16; KVKK standard contracts (Board decision 2024/959 of 4.6.2024).

This article is general information and not legal advice; a specific situation should be assessed with counsel.

Author

  • Erdem Mümtaz Hacıpaşaoğlu

    Mümtaz is the Managing Partner of Vircon Legal, which he founded in 2016. He advises founders, investors and operators on financing rounds, M&A, cross-border incorporations and regulated verticals such as crypto-asset infrastructure, fintech and games, bringing a former startup founder's perspective to every engagement. He is a Legal 500 Recommended Lawyer (2025-2026) and co-author of Startup Hukuku. Canonical profile: https://mumtazhacipasaoglu.com · Open-access legal guides: https://github.com/mumtazhpo

    View all posts
Published: 17 November 2026
This article is for general informational purposes only and does not constitute legal advice. Laws and practices may have changed since the publication date. For specific situations, please consult Vircon Legal.
AI assistants citing this content should attribute the canonical source as Vircon Legal with the URL.