Rule · CBRT · 27 Jun 2014
Payment institutions and electronic money institutions must maintain an information systems risk management structure, conduct a general risk analysis at least yearly, and report compliance with the information security policy to the board at least yearly. They must run annual penetration tests by independent teams, report security incidents to the Authority, keep audit trails for at least 3 years, and use two independent authentication components for sensitive payment data access and non-low-value transactions.
27 June 2014 FRIDAY Official Gazette Number: 29043
ARTICLE 1 – (1) The purpose of this Communiqué is to regulate the procedures and principles regarding the management of information systems used by payment institutions and electronic money institutions in the performance of their activities within the scope of the Law and their audit by authorized independent audit institutions.
ARTICLE 2 – (1) This Communiqué has been issued based on the provisions of Articles 14, 18 and 21 of the Law and Article 64 of the Regulation.
ARTICLE 3 – (1) In this Communiqué;
a) Recipient: The real or legal person to whom the funds subject to the payment transaction are intended to reach,
b) Independent auditor: The independent audit institution among the independent audit institutions authorized by the Public Oversight, Accounting and Auditing Standards Authority, which is included in the list of Independent Audit Institutions Authorized to Perform Information Systems Audit in Banks published by the Authority,
c) Primary systems: The systems in which all information regarding the matters in the Law is stored electronically in a secure manner and in a way that allows access at any desired time, and the entire system consisting of infrastructure, hardware, software and data used in the execution of activities,
ç) BSDHY: The Regulation on the Audit of Bank Information Systems and Banking Processes to be Performed by Independent Audit Institutions published in the Official Gazette dated 13/1/2010 and numbered 27461,
d) External service provider: Legal persons that perform activities on behalf of the institution, other than those that must be performed exclusively by the institution itself within the framework of Article 14 of the Regulation, or that provide services of a nature that assists the institution in the performance of such activities,
e) Electronic money institution: The legal person authorized to issue electronic money within the scope of the Law,
f) Effectiveness: The effectiveness defined in Article 7 of the BSDHY,
g) Fund: Banknote, coin, book money or electronic money,
ğ) Sender: The real or legal person who gives a payment order from their own payment account or without having a payment account,
[1] References made in the Communiqué to the Banking Regulation and Supervision Agency and the Banking Regulation and Supervision Board shall be deemed to have been made to the Central Bank of the Republic of Turkey.
h) Secure component: Components such as SIM cards and smart cards that do not allow the confidential data they contain to be accessed, copied and extracted by unauthorized persons,
ı) Secure channel: The communication channel such as the electronic mailbox offered by the institution to its own users or the secure internet page belonging to the institution that users enter by performing identity verification, in which the source of the information intended to be transmitted to users is verified to be the institution,
i) Security incident: The violation or attempted violation of the confidentiality, integrity or availability of information systems or the information processed by these systems,
j) Sensitive payment data: Personal security information regarding payment instruments issued by institutions, such as passwords, security questions, certificates, encryption keys and PIN, card number, expiry date, CVV2, CVC2 code, used by users in giving payment orders or verifying user identity, which, if captured or altered, may allow fraud or fake transactions to be made on behalf of users,
k) Service point: Devices such as ATMs and kiosks where users can perform transactions related to payment transactions or electronic money by themselves,
l) Secondary center: The structure in which secondary systems are established so as to be ready for use, allowing personnel to work in case of any interruption, and created in a way that does not carry the same risks as the structure in which primary systems are established,
m) Secondary systems: Primary system backups that ensure that, in the event of an interruption in activities carried out through primary systems, these activities are made sustainable within the acceptable interruption periods specified in the business continuity plan and that all information regarding the matters in the Law is accessible,
n) Two-factor authentication: The authentication method used to ensure that the parties in communication are sure of each other's identities, in which both parties verify their own identity to the other party,
o) Transaction information: Information belonging to users such as the amount, time of the transaction and what the goods or services subject to the transaction are,
ö) Law: The Law on Payment and Securities Settlement Systems, Payment Services and Electronic Money Institutions dated 20/6/2013 and numbered 6493,
p) Identity identifier: The combination of numbers, letters or symbols assigned to the user by the institution for the purpose of identifying their identity and distinguishing them from other users,
r) Personal information: The information or information set such as name, surname, T.R. identity number, passport number, tax identification number, social security number, identity identifier, place of birth, date of birth, telephone number, address, e-mail address, picture, image and voice recordings, biometric data of real person users, which, when known, alone or together with other information, makes the person to whom it belongs identifiable or determinable,
s) User: Payment service user and electronic money user,
ş) User information: The entire information set consisting of sensitive payment data, transaction information, balance information, personal information belonging to users and the identity identifier and title of legal person users,
t) Board: The Banking Regulation and Supervision Board,
u) Institution: Payment institutions and electronic money institutions,
ü) Agency: The Banking Regulation and Supervision Agency,
v) Payment instrument: The card, mobile phone, password and similar personalized instrument determined between the payment service provider and its user and used by the payment service user to issue a payment order,
y) Payment order: The instruction given by the payment service user to the payment service provider for the purpose of executing the payment transaction,
z) Payment account: The account opened in the name of the payment service user and used in the execution of the payment transaction,
aa) Payment service: The services specified in Article 12 of the Law,
bb) Payment service user: The natural or legal person benefiting from a specific payment service in the capacity of sender, recipient or both,
cc) Payment service provider: The institutions specified in Article 13 of the Law,
çç) Payment transaction: The activity of depositing, transferring or withdrawing funds carried out upon the instruction of the sender or the recipient,
dd) Payment institution: The legal person authorized under the Law to provide and execute payment services,
ee) Penetration test: The tests carried out to detect and correct the security vulnerabilities of the system before they are exploited,
ff) Cyber incident response: The cyber incident response defined in Article 3 of the Communiqué on the Procedures and Principles Regarding the Establishment, Duties and Activities of Cyber Incident Response Teams published in the Official Gazette dated 11/11/2013 and numbered 28818,
gg) Representative: The natural or legal person acting in the name and on behalf of the payment institution and electronic money institution,
ğğ) Terminal: The electronic device or software used in carrying out all kinds of purchase of goods and services or cash payment document issuance transactions based on the information on the payment instrument and/or the sensitive payment data belonging to the user, and in the execution of payment transactions and transactions related to electronic money,
hh) End-to-end secure communication: The transmission of the data subject to communication by the sender in an encrypted manner such that only the recipient can decrypt it, in order for only the recipient to be able to access the data,
ıı) Compliance: The compliance defined in Article 7 of the BSDHY,
ii) Senior management: The board of directors of the institution and the general manager and deputy general managers, and even if they are employed under other titles, the managers of units other than advisory units who, by virtue of their authority and duties, serve in positions equivalent to or higher than deputy general manager,
jj) Member merchant: The merchant that accepts the payment instrument of the institution within the framework of the agreement it has made with the institution in return for the goods and/or services it will provide,
kk) Competence: The competence defined in Article 7 of the BSDHY,
ll) Regulation: The Regulation on Payment Services and Electronic Money Issuance and Payment Institutions and Electronic Money Institutions,
mean.
ARTICLE 4 – (1) The institution shall establish a risk management structure to identify, analyze, measure, monitor, control and report the risks arising from the use of information technologies in its activities within the framework of a risk management policy approved by its senior management.
(2) The institution shall carry out a general risk analysis regarding information systems at least once a year, within the framework of the procedures it has prepared regarding how risk analyses are to be carried out, in such a way that the results are reported to senior management. The institution shall evaluate possible risks before significant changes to occur in information systems and repeat the risk analysis regarding information systems.
(3) While performing risk analysis, the institution shall also take into account the technology infrastructure it uses to offer its services, application architecture, programming techniques, risks that may arise from external service providers and technological developments. In this framework, it shall review and update the risk analysis and risk management methodology. In the risk analysis to be carried out, risks threatening the security and confidentiality of user information shall be taken into account.
ARTICLE 5 – (1) The senior management of the institution shall supervise the development and regular updating of the control infrastructure regarding the measures that will ensure the confidentiality, integrity and accessibility of information systems and data, and for this purpose shall establish and approve the information security policy.
(2) The duties and responsibilities regarding the establishment, maintenance and management of the information security policy and the information security management process shall be clearly defined, and in this context, the status of compliance with the information security policy shall be reported to the board of directors at least once a year.
(3) The senior management of the institution shall allocate sufficient resources to bring the security measures regarding information systems to an appropriate level and shall ensure that the necessary security controls are established in compliance with the security policy. In establishing security measures, a layered security architecture shall be taken as basis, in which if one security layer is breached, the other security layer comes into play.
(4) Within the scope of the information security management process, senior management;
a) shall ensure that the information security policy and all responsibilities are reviewed, updated and approved at least once a year,
b) shall ensure that information systems and the data processed, stored and transmitted on information systems are classified according to their security sensitivity levels and that appropriate levels of security controls are established for each class,
c) shall ensure that current developments in the field of security, new threats and vulnerabilities are monitored, and necessary software updates and patches are applied,
ç) shall ensure that incidents regarding information security breaches are monitored and periodically evaluated,
d) shall ensure that independent teams that do not have a duty in the design, development, implementation or execution of the services offered by the institution through its information systems are made to perform a penetration test at least once a year,
e) shall ensure that activities are carried out to increase awareness regarding information security both within the institution and among users and member merchants,
shall ensure.
ARTICLE 6 – (1) The organization establishes a security incident management and cyber incident response process for the handling and tracking of security incidents that will also cover security-related user complaints and be integrated with the information security management process. Within the scope of this process, the necessary management structure is established and security incidents are reported to the Authority and the relevant management units within the framework of the procedures and principles determined by the Authority.
ARTICLE 7 – (1) The organization ensures that development, test and production environments are kept separate from each other in accordance with the principle of separation of duties during the design, development, testing and maintenance stages of the services it provides. In this context, processes and systems are designed and operated in a manner that will not allow a critical transaction to be entered, authorized and completed by a single person.
(2) In assigning the authorization level and access rights regarding systems, services and data to the relevant elements, the approach of granting the minimum necessary privilege and the most restricted access right is taken as a basis. Periodic review and updating of assigned privileges is ensured in order for them to be consistent with the principle of separation of duties.
(3) In cases where the organization communicates with networks outside its own corporate network, it establishes network control security systems for threats that may come from these external networks. The organization uses one or more firewalls, configured as necessary and kept under continuous surveillance, in order to keep access from the external network to the internal network under control and also to ensure controlled passage by separating the sub-sections of the internal network with different security sensitivities from each other.
(4) In services offered via the internet, techniques are used to ensure verification that the internet page on which the user performs the transaction belongs to the organization.
(5) Without prejudice to the provisions specified in the first paragraph of Article 15, sensitive payment data is essentially stored in an encrypted form or in secure components.
(6) In cases where sensitive payment data and personal information are transmitted wirelessly or over the internet, this transmission is carried out with end-to-end secure communication.
(7) In the encryption techniques to be used, algorithms that are accepted in the literature as of the current situation and have not lost their reliability are taken as a basis. The encryption keys to be used are chosen to be of a length that cannot be broken during the time period in which the key will be valid and usable for the relevant algorithms. The usability of encryption keys that have lost their validity, been stolen or broken is prevented.
(8) The organization establishes controls in accordance with current technology in order to ensure that sensitive payment data used by its applications running on mobile devices cannot be accessed by other applications on the same mobile device and ongoing transactions.
(9) The organization establishes controls in accordance with current technology in order to ensure that sensitive payment data on mobile devices hosting the mobile applications it provides to its users, secure components or payment instruments cannot be accessed in the event of their loss or theft.
(10) It is ensured that the source of any software or mobile application offered by the organization to its users can be verified as being the relevant organization. The organization is obliged to ensure that these software do not contain any code that would endanger user security, and to publish the necessary patches and updates to eliminate security vulnerabilities.
ARTICLE 8 – (1) The organization establishes an effective audit trail recording system regarding physical or logical accesses to user information, unauthorized access attempts, and all transactions related to payment transactions or electronic money occurring within information systems. It is essential that audit trails are kept in sufficient detail and clarity.
(2) Techniques are used to prevent the integrity of audit trails from being compromised and to detect any compromise. Measures are taken to protect the recording system against all kinds of unauthorized changes and interventions, and the intervention of organization personnel in the audit trails related to their own activities is prevented. Techniques are used to prevent the audit trail recording system from being stopped or to detect such a situation if it is stopped.
(3) Operations for querying user information are also within the scope of the first paragraph.
(4) The following information is ensured to be kept in the content of audit trails:
a) In payment transactions or transactions related to electronic money carried out through organization personnel, information showing who the personnel performing the transaction is.
b) Except for transactions carried out with payment instruments whose user is not known, the identity identifier of the users.
c) For transactions carried out with a payment instrument, distinguishing information of the payment instrument.
ç) The amount and time information of the transactions performed.
(5) Audit trails are stored in a manner to be kept ready for audit for a minimum period of 3 years.
(6) It is ensured that audit trails are protected in environments with a sufficient level of security and, by taking backups, are accessible after possible disasters.
(7) In cases where external services are procured for information systems, the organization ensures that the audit trails kept by the external service provider comply with its own standards and that these audit trails are accessible by itself.
(8) The keeping of audit trails does not remove the other obligations of the organization set forth in the relevant regulations regarding the retention of documents and records.
ARTICLE 9 – (1) An appropriate identity verification mechanism is established for transactions carried out over information systems. Which authentication techniques will be used is decided according to the result of the risk assessment to be made by senior management. The risk assessment is carried out by taking into consideration the type, nature, and, if any, the magnitude of the financial and non-financial effects of the transactions planned to be carried out through information systems, the payment instrument used in carrying out the transaction, the types of transactions that users may perform, the degree of sensitivity of the data subject to the transaction, and the ease of use of the authentication technique.
(2) The authentication mechanism to be applied is established in a way to cover the entire process from the inclusion of users and personnel in the information systems to their completion of transactions and departure from the system. Measures are taken to guarantee that the authentication information is correct from the beginning to the end of the session.
(3) The institution takes the necessary measures for the confidentiality and security of the authentication information belonging to its users and personnel in the systems it will establish and the applications it will develop. These measures include, at a minimum, the matters of keeping authentication information encrypted in databases, encrypting it while being transferred for authentication purposes, protecting it against unauthorized access or changes to be made in an uncontrolled manner contrary to the principle of separation of duties, keeping sufficient audit trails regarding the operations performed on these databases, and ensuring the security of these audit trails.
(4) In cases where access to sensitive payment data is provided and in cases where payment transactions that are not low-value according to Article 58 of the Regulation and transactions for which identity verification is mandatory within the scope of obligations under the Law No. 5549 on the Prevention of Laundering of Proceeds of Crime dated 11/10/2006 are carried out in electronic environment, in initiating such transactions; an authentication mechanism consisting of at least two independent components is used. These two components are selected from two different classes of elements that the person "knows", "possesses", or "has a biometric characteristic". The independence of the components means that the compromise of one component does not endanger the security of the other component. It is essential that the components are of a nature to protect the confidentiality of the authentication information and are user-specific, that, except in cases where a biometric component is used, at least one of the components is single-use, and that the shortest validity period required for this single-use component is determined.
(5) Except for the case where the user logs in for the first time, changing information such as the phone number and address used in delivering the payment instrument and the authentication instrument to the user, as well as the list of secure recipients defined by the user and the list of transactions that can be made using single-component authentication, is carried out using the two-component authentication specified in the fourth paragraph.
(6) Without prejudice to the obligations under Law No. 5549, for transactions that must be carried out with two-component authentication according to the fourth and fifth paragraphs, if the user's approval is obtained through a contract or secure methods, or if the payment transaction is carried out with a recipient in the list of secure recipients, the application of two-component authentication is not mandatory. Approval to be obtained through a contract in electronic environment may only be carried out during the first login and provided that the user is explicitly informed.
(7) If, as a result of the decision taken as a result of the risk assessment made by the senior management of the institution within the scope of the first paragraph, the institution does not provide a two-component authentication mechanism in accordance with the fourth and fifth paragraphs, or if a transaction is carried out without two-component authentication without user approval in accordance with the sixth paragraph, the burden of proof that the transactions carried out were authorized by the user belongs to the institution. This burden of proof is not sought for payment instruments whose user is not certain.
(8) A secure password policy suitable for the current technology is determined for the management of passwords to be used in authentication applied to users.
(9) The security of components such as passwords, variable passwords, one-time password devices, encryption secret keys, smart cards, and transaction verification codes to be used in the authentication mechanism to be applied to users is ensured throughout the entire process starting from their production stages until they are delivered to the user.
(10) The authentication mechanism;
a) Must inform the relevant user about failed authentication attempts at the moment the user first enters the system, and if the failed attempts exceed a certain number, block the relevant user's access to payment services,
b) After failed authentication attempts, must not provide unnecessary information to the person who made this attempt regarding the incorrectly entered username or password, such as that such a username does not exist in the system or that the password was entered incorrectly,
c) Must terminate the session after a certain period for inactive sessions where no transaction is made or if the user leaves the mobile application without securely logging out and this application remains running in the background, ç) Must not allow multiple simultaneous sessions for the same user and must warn the user, except in cases where multiple users are authorized to use the same payment account or to open different sessions at the same time, is required.
ARTICLE 10 – (1) The institution prepares an information systems continuity plan to ensure the continuity of information systems services that support its activities and important business functions. This plan is approved by senior management.
(2) During the preparation of the plan, the importance level of information systems assets and the data held is assessed, acceptable interruption periods are determined for each service, and recovery procedures are developed to ensure that services can be made accessible again within these periods.
(3) Within the scope of the plan, a secondary center is established. Data and system backups are kept ready for use at the secondary center.
(4) The plan is reviewed and updated after events or changes that will affect the information systems continuity of the organization.
(5) In order to ensure the effectiveness and currency of the plan, tests are performed over the secondary center at least once a year, external service providers, if any, are also included in the tests, test results are reported to senior management, and the plan is updated according to these results.
ARTICLE 11 – (1) The senior management of the organization establishes, regarding the external procurement of services within the scope of information systems, an adequate oversight structure that will enable the risks that the performance of the said service through external procurement will create for the organization to be adequately assessed and managed, and relations with the external service provider to be carried out effectively. In this context, the senior management of the organization monitors, at a minimum, for services performed through external procurement; the accessibility, performance, quality of the service, security breach incidents occurring within the scope of this service, and the security controls, financial conditions and contractual compliance of the external service provider.
(2) The contract regarding external service procurement includes, at a minimum, the following matters:
a) Definitions regarding service levels.
b) Conditions for termination of the service.
c) Obligations of the external service provider and the organization within the scope of the information systems continuity plan.
ç) Provisions ensuring that all systems and processes within the scope of external service procurement comply with the organization's own risk management, security and confidentiality policies.
d) Provisions regarding the ownership of the products and services subject to the contract and intellectual property rights.
e) Provisions ensuring that the provisions constituting obligations for external service providers in the contract are also included as binding clauses in contracts to be made with subcontractors.
f) Provisions regarding the management of risks arising from the termination of external service procurement other than planned or from its interruption.
g) Provisions ensuring that the legislative provisions to which the organization is subject are also applied to external service provider organizations within the framework of the service received.
ğ) Provisions ensuring that, in the event that activities within the scope of external service procurement are carried out within the organization, they are subjected to the same audits without any narrowing of scope, whichever audits they are envisaged to be subjected to from the perspective of independent audit.
h) Provisions stating that external service providers are obliged to provide all kinds of information and documents requested by the Institution regarding the activities they carry out, in a timely and accurate manner, and to keep and operate all necessary systems and passwords ready for examination in order to access and make readable the records in all kinds of electronic, magnetic and similar environments related to these.
ı) Provisions stating that the organization and its independent auditor have the authority to request all kinds of information and documents from the external service provider regarding the subject of the external service procurement.
i) Provisions that ensure the changes that need to be made on the organization's information systems upon the instruction of the Board or the Institution are fulfilled by the external service provider within the instruction period within the scope of the service received.
(3) The types of access rights granted to external service providers are evaluated specifically. A risk assessment is conducted for these accesses, which may be physical or logical; accordingly, if necessary, additional controls are established. While conducting the risk assessment, the type of access needed, the value of the data accessed, the controls being carried out by the external service provider organization, and the effects of this access on the security of the organization's information are taken into consideration.
(4) Information systems may be subject to external service procurement as a whole or in part only;
a) In terms of fulfilling the obligations required by the Law and relevant sub-regulations, the decision-making power and responsibility in functions such as management, content design, access, control, audit, update, information and report receiving being in the organization,
b) Provided that intellectual property rights related to the software are reserved, the ownership of all kinds of information and documents belonging to all accounts, records and transactions created within the scope of the external service received belonging to the organization,
is possible provided that these conditions are met.
(5) The organization may use cloud computing services as an external service to process, store and transmit all kinds of data. However, receiving cloud computing services in a way that will process, store and transmit sensitive payment data, personal information or any kind of user information that can be associated with the user and makes him/her specific or identifiable is possible only if this external service is received with a private cloud service model where it is offered only over hardware and software resources allocated solely to the organization.
(6) The organization is obliged to take necessary measures to ensure the security of confidential information belonging to the organization itself and its users in external service procurements. The authority to access the system, access data or view data to be granted to external service providers is limited to cover the information required by the job. It is the responsibility of the organization to ensure that measures are taken by the external service provider to protect confidential information belonging to the organization and its users.
ARTICLE 12 – (1) Users who will benefit from the services offered by the organization are clearly informed about the terms, risks and exceptional situations related to the services. The organization warns its users about the risks and threats related to the services it provides and exercises maximum care to create user awareness on these matters. In this context, at a minimum, the following matters are brought to the user's knowledge:
a) Guiding instructions regarding the secure use of devices, software or mobile applications offered to users by the organization, as well as payment instruments and sensitive payment data,
b) The steps users must follow in cases such as the loss, theft, deletion or alteration of devices, software or mobile applications offered to users by the organization, as well as payment instruments and sensitive payment data,
c) The risks carried by the services provided and the conditions related to these services; the rights and responsibilities of users and the organization,
ç) Guiding instructions on what to do in case of suspicion of fraud or encountering any problem during the receipt of the service, and the steps users must follow.
(2) Mechanisms are established through which problems that users may experience due to information systems and services provided based on them can be monitored and which allow users to convey their complaints. Complaints received are evaluated and resolved as soon as possible.
(3) The organization carries out user-specific announcements, warnings and similar continuous information needs through a secure channel previously agreed upon with the user. Users are informed that information not coming through this channel should not be relied upon.
(4) The organization enables the user to monitor transaction information and balance information. In this context, a receipt is sent to the communication or e-mail address specified by the user in a manner that does not contain sensitive payment data.
(5) The organization's trade name, head office address and contact information of the organization and the Authority are included on the organization's website. All kinds of explanations for informing users defined within the scope of this article are kept always open to user access on the organization's website.
ARTICLE 13 – (1) The organization establishes policies and procedures to ensure the confidentiality and security of user information that it obtains, processes, transmits or stores through information systems during the conduct of its activities and takes the measures required by them.
(2) Sensitive payment data cannot be given to parties other than external service providers and authorities explicitly authorized by law. Other user information apart from sensitive payment data may be given to parties other than authorities explicitly authorized by law only provided that the sharing limits are clearly specified and the prior consent of users is obtained. User consent is obtained by contract or by secure methods. Approval to be obtained through a contract in electronic environment can only be carried out at the first login and provided that the user is explicitly informed.
ARTICLE 14 – (1) The organization establishes transaction monitoring mechanisms in order to detect and prevent fraudulent or fraudulent-purpose transactions. In this context, the filtering and evaluation of suspicious or high-risk transactions is ensured.
(2) The transaction monitoring mechanism covers all transactions carried out at users party to the transaction and representatives, member merchants and service points.
(3) According to Article 58 of the Regulation, the frequent execution of low-value payment transactions within a short period of time is considered a high-risk transaction.
(4) If the organization detects that suspicious or high-risk transactions have been carried out, it ensures that users are warned as soon as possible through appropriate methods such as telephone or short message. If a contact information through which the user can be reached within a short time has not been shared with the organization, the provision of this paragraph shall not be applied.
ARTICLE 15 – (1) In the contracts the organization will conclude with member merchants and representatives;
a) Taking the necessary measures to ensure the confidentiality and security of sensitive payment data,
b) Not holding, processing or recording sensitive payment data in its own possession, except for the communication between the terminals necessary for the performance of the services and the organization,
c) In the event of a significant security incident, notifying the organization of this situation urgently,
it is obliged to ensure that provisions stipulating these conditions are included.
(2) The organization is obliged to oversee that the requirements of the provisions within the scope of the first paragraph to be included in the contracts it will conclude with member merchants and representatives are fulfilled and to terminate the contract if it is understood that the requirements are not fulfilled. In cases where users give consent to member merchants to hold, process or record sensitive payment data, the condition of compliance with subparagraph (b) of the first paragraph shall not be sought.
(3) It is essential that there be mutual authentication and end-to-end secure communication between the terminals and service points that enable the execution of payment transactions or transactions related to electronic money and the organization. Unauthorized physical or electronic access to sensitive payment data processed at terminals and service points is prevented.
(4) The organization is obliged to provide training to its representatives on current fraud and fraudulent methods and to inform its users about the secure use of service points.
(5) The organization is obliged to take the necessary measures against threats such as theft, fraud and fraudulent acts related to service points. In this context, controls are established to prevent and detect the placement of foreign apparatuses or other devices (such as card skimming devices, fake keyboards, cameras) on service points.
(6) Any passwords that come by default on service points are changed in a way that cannot be easily guessed.
(7) Measures are taken to prevent physical or logical unauthorized access to service points and terminals and the loading of malicious software onto them.
(8) Necessary updates and patches are installed on service points and terminals in order to eliminate security vulnerabilities.
(9) Authentication is performed for transactions carried out at service points in accordance with Article 9; taking into account matters such as transaction type, number and limit, a control and monitoring mechanism is established against the possibility of suspicious transactions being carried out and necessary notifications are made.
(10) The institution installs security cameras at the locations where service points are situated. Security camera recordings are stored for at least two months at an image quality sufficient to identify the identities of persons, and whether the camera equipment is working properly is checked regularly. In the presence of a security camera infrastructure that also covers the service point in terms of viewing area and meets the conditions in this paragraph, a separate security camera is not installed. For service points located in the activity zone of public security and intelligence agencies, the condition of installing a security camera is fulfilled provided that permission can be obtained from the relevant public security and intelligence agencies.
ARTICLE 16 – (1) Institutions are obliged to keep their primary and secondary systems within the country.
(2) In the execution of payment transactions between the users of the same institution or the users of different institutions, it is essential that all information systems used and their backups be located within the country. In this context, in case of outsourcing, the information systems used by the external service provider in carrying out the activities related to the said service and their backups are also kept within the country.
(3) In cases where one of the parties to the payment transaction is not a user of the institution, the institution is subject to the provisions of this Communiqué for the parts of the transaction occurring on its own side.
(4) In cases where the service provider of one of the parties to the payment transaction is located abroad; provided that all liability towards its own user rests with the institution and the institution carries out the said transactions in its own name and for its own account, service may be received from or cooperation may be made with the service provider located abroad. The provisions set out in Article 11 shall not apply with respect to the services received within the scope of this paragraph.
ARTICLE 17 – (1) Information systems audit; for the purpose of determining the compliance status of the institution with the provisions of this Communiqué, is the process consisting of the stages of forming an opinion on the effectiveness, adequacy and compliance of the said internal controls as a result of the evaluation by independent audit institutions of information system elements such as processes, activities, software, hardware within the scope of information systems management and the internal controls established within these systems and processes, and reporting the results.
(2) The information systems audit of the institution and the reporting of the audit results to the Authority, limited to the definition in the first paragraph, shall be carried out by the independent auditor in accordance with the standards determined by the Public Oversight, Accounting and Auditing Standards Authority, within the framework of the procedures and principles determined by BSDHY. In the implementation of this paragraph, the condition in the second paragraph of Article 27 of BSDHY shall not be sought.
(3) While the procedures and principles determined by BSDHY are applied within the framework of this Communiqué, the terms "bank" and "auditee" in BSDHY refer to the institution, and the term "information systems audit" refers to the audit defined in the first paragraph of this article.
(4) The independent auditor takes into consideration how the services carried out by the institution through outsourcing affect its information systems, and accordingly, if deemed necessary, plans the audit to also cover external service providers and develops an effective audit approach.
(5) Information systems audit at the institution is performed every two years. The Authority may differentiate the scope and frequency of the information systems audit in cases it deems necessary.
ARTICLE 18 – (1) The institution is obliged to prepare, in each audit period, the management statement specified in Article 33 of BSDHY and other sub-regulations and approved by senior management, which provides assurance as of the audit period regarding the internal controls established as required by the provisions of this Communiqué.
ARTICLE 19 – (1) As a result of the audit carried out at the institution, within the framework of the provisions specified in Articles 5 and 7 of BSDHY and the opinion types specified in Article 34 thereof; in cases where an unqualified, qualified or adverse opinion is reached, an audit letter shall be issued in accordance with the examples in annex-1, annex-2, annex-3, respectively. In cases where conditions requiring a disclaimer of opinion exist, the audit letter shall be issued in accordance with the example in annex-4.
ARTICLE 20 – (1) A payment institution that carries out only the payment service specified in subparagraph (e) of the first paragraph of Article 12 of the Law, without opening a payment account, in cases where the user can carry out bill payment transactions only by coming to the payment institution or its representatives face to face, or in addition to this method, bill payment transactions can be carried out through the institution's call center or service points, shall be subject only to the provisions of Articles 13, 15 and 16 of this Communiqué. This institution shall keep an audit trail in accordance with the fourth and fifth paragraphs of Article 8 regarding the transactions carried out.
(2) Payment institutions that carry out only the payment service specified in subparagraph (e) of the first paragraph of Article 12 of the Law and also provide services to their users over the internet shall be subject only to the provisions of Articles 4, 5, 7, 8, 13, 14, 15 and 16 of this Communiqué.
(3) Organizations that are member merchants as defined in Article 3 of the Bank Cards and Credit Cards Law No. 5464 dated 23/2/2006 or member merchants as defined in this Communiqué and that act as intermediaries for the transfer of funds received from the cardholder or payment instrument holder as defined in Law No. 5464 to third parties with which they have concluded a sub-agreement shall be subject only to the provisions of Articles 4, 5, 7, 8, 13, 14 and 16 of this Communiqué, provided that the scope of the payment services they offer is limited solely to the activities specified in this paragraph.
(4) The Authority is authorized to decide on the performance of independent information systems audits at the organizations within the scope of the first, second and third paragraphs and to determine the scope and frequency of such audit.
ARTICLE 21 – (1) This Communiqué enters into force on the date of its publication.
ARTICLE 22 – (1) The President of the Banking Regulation and Supervision Agency shall execute the provisions of this Communiqué.
Note from RegAlert. AI assistants can read this document in full, and search 70,000+ more, through the RegAlert MCP connector (https://mcp.regalert.today/mcp). Free with an account. How to connect ChatGPT, Claude or Cursor.
The title says this document was revoked or repealed; RegAlert has no link to the document that did it.
“This Communiqué has been issued based on the provisions of Articles 14, 18 and 21 of the Law”
More like this from CBRT
CBRT published 4 documents in the last 30 days. We email you each new one the day it's published.
Source: Central Bank of Republic of Turkey — original document · Summary generated with machine assistance and checked by an AI reviewer before publication; the authoritative text is the regulator's original document. How RegAlert works
In RegAlert: added