Skip to main content
  • Retail Payment Services and Card Schemes Regulation

    C 15/2021 Effective from 6/6/2021
    • Introduction

      The Regulation (‘RPSCS Regulation’) lays down the rules and conditions established by the Central Bank for granting a License for the provision of Retail Payment Services. The Retail Payment Services are digital payment services in the State and comprise nine categories, namely Payment Account Issuance Services, Payment Instrument Issuance Services, Merchant Acquiring Services, Payment Aggregation Services, Domestic and Cross-border Fund Transfer Services, Payment Token Services, Payment Initiation Services and Payment Account Information Services. It also requires Card Schemes to obtain a License from the Central Bank and sets out the conditions for granting such License as well as the ongoing obligations of Card Schemes. The Central Bank has furthermore been given the right to receive information on the fees and charges of Card Schemes, and regulate such fees and charges if the Central Bank considers it appropriate. In addition, proper contractual arrangements are required between Banks or other Payment Service Providers providing Payment Account Issuance Services, on one hand, and Payment Service Providers providing Payment Initiation and Payment Account Information Services, on the other hand. Payment Service Providers wishing to participate in wages distribution and be given access to the Wages Protection System are subject to a set of on-going requirements.

      The Central Bank Law requires providing money transfer services, electronic retail payments, and digital money services to be subject to a licensing regime administered by the Central Bank and provides the statutory basis for the powers of the Central Bank in relation to the licensing and ongoing supervision of Payment Service Providers and Card Schemes.

    • Scope and Objectives

      This Regulation sets out the requirements concerning:

      • conditions for granting and maintaining a License for the provision of Retail Payment Services;
         
      • rights and obligations of Retail Payment Service Users and Payment Service Providers;
         
      • proper contractual arrangements allowing Payment Service Providers providing Payment Initiation and Payment Account Information Services to access Payment Accounts held with Banks and other Payment Service Providers providing Payment Account Issuance Services;
         
      • conditions for granting a License to Card Schemes;
         
      • conditions for participating and obtaining an access to the Wages Protection System;
         
      • powers of the Central Bank with regard to the supervision of Payment Service Providers and the on-going reporting requirements for Card Schemes.
         

      In exercising its powers and functions under this Regulation, the Central Bank has regard to the following objectives:

      • ensuring the safety, soundness and efficiency of Retail Payment Services;
         
      • adoption of effective and risk-based licensing requirements for Payment Service Providers;
         
      • promoting the reliability and efficiency of Card Schemes as well as public confidence in Card-based Payment Transactions;
         
      • promoting innovation and creating a level playing field for market participants; and
         
      • reinforcing the UAE’s status as a leading payment hub in the region.
         
    • Exclusions

      This Regulation shall not apply to the following:

      1. Payment Transactions involving Stored Value Facilities;
         
      2. Transactions involving Commodity or Security Tokens;
         
      3. Transactions involving Virtual Asset Tokens;
         
      4. Payment Transactions involving Remittances;
         
      5. Currency exchange operations where the funds are not held on a Payment Account;
         
      6. Any service other than Payment Initiation and Payment Account Information Service, including (but not limited to) any of the following:
         
        1. 6.1. services, provided by any technical service provider that supports the provision of any payment service, but does not at any time enter into possession of any money under that payment service;
           
        2. 6.2. the service of processing or storing data;
           
        3. 6.3. any information technology security, trust or privacy protection service;
           
        4. 6.4. any data or entity authentication service;
           
        5. 6.5. any information technology service;
           
        6. 6.6. the service of providing a communication network; and
           
        7. 6.7. the service of providing and maintaining any terminal or device used for any payment service.
           
      7. Payment Transactions carried out within a payment system or securities settlement system between Payment Service Providers and settlement agents, central counterparties, clearing houses, central banks or other participants in such system including central securities depositories;
         
      8. Payment Transactions and related services between a parent undertaking and its subsidiary or between subsidiaries of the same parent undertaking, without any intermediary intervention by a Payment Service Provider other than an undertaking belonging to the same group; and
         
      9. Any other relevant activity that may be designated by the Central Bank.
         
    • Article (1): Definitions

      1. Agent: means a juridical Person providing Retail Payment Services on behalf of a Payment Service Provider.
         
      2. AML/CFT: means Anti-Money Laundering and Combating the Financing of Terrorism.
         
      3. AML Law: means Decree Federal Law No. (20) of 2018 on Anti-Money Laundering and Combating the Financing of Terrorism and Illegal Organizations and Cabinet Decision No. (10) of 2019 Concerning the Implementing Regulation of Decree Federal Law No. (20) of 2018 on Anti-Money Laundering and Combating the Financing of Terrorism and Illegal Organizations, as may be amended from time to time, and any instructions, guidelines and notices issued by the Central Bank relating to their implementation or issued in this regard.
         
      4. Annex I: means the list of Retail Payment Services that a Payment Service Provider may provide subject to the requirements of this Regulation.
         
      5. Annex II: means the Guidance on the best practices for technology risk and information security.
         
      6. Annex III: means the minimum level of information to be reported by Card Schemes to the Central Bank.
         
      7. Applicant: means a juridical Person duly incorporated in the State in accordance with Federal Law No. 2 of 2015 on Commercial Companies and as provided for under Article (74) of the Central Bank Law, which files an Application with the Central Bank for the granting of a License for the provision of one or more Retail Payment Services, operation of a Card Scheme or the modification of the scope of a granted License.
         
      8. Application: means a written request for obtaining a License for the provision of one or more Retail Payment Services submitted by an Applicant which contains the information and documents specified in this Regulation or by the Central Bank, and is in the form specified by the Central Bank’s Licensing Division, including a written request for obtaining a modification to the scope of a granted License.
         
      9. Auditor: means an independent juridical Person that has been appointed to audit the accounts and financial statements of a Payment Service Provider in accordance with Article (10) (7).
         
      10. Bank: any juridical person licensed in accordance with the provisions of the Central Bank Law, to primarily carry on the activity of taking deposits, and any other Licensed Financial Activities.
         
      11. Beneficial Owner: means the natural person who owns or exercises effective ultimate control, directly or indirectly, over a Retail Payment Service User (client) or the natural person on whose behalf a transaction is being conducted or, the natural person who exercises effective ultimate control over a legal person or legal arrangement.
         
      12. Branded: means having any digital name, term, sign, logo, symbol or combination thereof that is capable of differentiating the Card Scheme under which Payment Transactions are executed.
         
      13. Board: means the board of directors of an Applicant, Payment Service Provider or a Card Scheme in accordance with applicable corporate law.
         
      14. Business Day: means a day other than Friday, Saturday, public holiday or other non-working holiday or day in the State.
         
      15. Card-based Payment Transactions: means a service based on a Card Scheme's infrastructure and business rules to make Payment Transactions by means of any card, telecommunication, digital or IT device or software if this results in a debit or a credit card transaction.
         
      16. Card Issuer: means a category of Payment Service Provider providing a Payer with a Payment Instrument to initiate and process the Payer’s Card-based Payment Transactions.
         
      17. Cardholder: means a Person who holds a Payment Instrument, physical or otherwise, issued by a Card Issuer based on a contract for the provision of an electronic payment instrument.
         
      18. Card Scheme: means a single set of rules, practices and standards that enable a holder of a Payment Instrument to effect the execution of Card-based Payment Transactions within the State which is separated from any infrastructure of payment system that supports its operation, and includes the Card Scheme Governing Body. For the avoidance of doubt, a Card Scheme may be operated by a private or Public Sector Entity.
         
      19. Card Scheme License: means a License for operating as a Card Scheme, as referred to in Article (18).
         
      20. Card Scheme Governing Body: means the juridical Person responsible and/or accountable for the functioning and operation of a Card Scheme.
         
      21. Category I License: means a License for the provision of the Retail Payment Services referred to in Article (3) (2).
         
      22. Category II License means a License for the provision of the Retail Payment Services referred to in Article (3) (3).
         
      23. Category III License means a License for the provision of the Retail Payment Services referred to in Article (3) (4).
         
      24. Category IV License means a License for the provision of the Retail Payment Services referred to in Article (3) (5).
         
      25. Central Bank: means the Central Bank of the United Arab Emirates.
         
      26. Central Bank Law: means the Decretal Federal Law No. (14) of 2018 Regarding the Central Bank and Organization of Financial Institutions and Services, as may be amended or substituted from time to time.
         
      27. Co-Branded: means having the inclusion of at least one payment brand and one non-payment brand on the same Payment Instrument.
         
      28. Controller: means a natural or juridical Person that alone or together with the Person’s associates has an interest in at least 20% of the shares in a Payment Service Providers or is in a position to control at least 20% of the votes in a Payment Service Provider.
         
      29. Commodity Token: means a type of Crypto-Asset that grants its holder an access to a current or prospective product or service, and is only accepted by the issuer of that token. Commodity token can also be referred to as utility token
         
      30. Complaint: Means an expression of dissatisfaction by a consumer with a product, service, policy, procedure or actions by the licensed financial institution that is presented to an Employee of the licensed financial institution in writing or verbally.
         
      31. Cross-Border Fund Transfer Service: means a Retail Payment Service for the transfer of funds in which the Payment Service Providers of the Payer and the Payee are located in different jurisdictions/countries.
         
      32. Crypto-Assets: means cryptographically secured digital representations of value or contractual rights that use a form of Distributed Ledger Technology and can be transferred, stored or traded electronically.
         
      33. Customer Due Diligence or CDD: means the process of identifying or verifying the information of a Retail Payment Service User or Beneficial Owner, whether a natural or legal person or a legal arrangement, and the nature of its activity and the purpose of the business relationship and the ownership structure and control over it.
         
      34. Custodian Services: means the safekeeping or controlling, on behalf of third parties, of Payment Tokens, the means of access to such tokens, where applicable in the form of private cryptographic keys.
         
      35. Data Breach: means an intrusion into an IT system where unauthorized disclosure or theft, modification or destruction of Cardholder or Retail Payment Service User data is suspected and such is likely to result in a loss for the Cardholder or Retail Payment Service User.
         
      36. Data Subject: means an identified or identifiable natural Person who is the subject of Personal Data.
         
      37. Digital Money Services: means, for the purposes of this Regulation, the business activity related to the provision of Payment Token Services.
         
      38. Distributed Ledger Technology: means a class of technologies that supports the distributed recording of encrypted data across a network and which is a type of decentralized database of which there are multiple identical copies distributed among multiple participants and accessible across different sites and locations, and which are updated in a synchronized manner by consensus of the participants, eliminating the need for a central authority or intermediary to process, validate or authenticate transactions or other types of data exchanges.
         
      39. Domestic Fund Transfer Service: means the Retail Payment Service of accepting money for the purpose of executing, or arranging for the execution of Payment Transactions between a Payer in the State and a Payee in the State.
         
      40. Electronic Payment Service: means any and each of the Retail Payment Services listed in points (1) to (4) and (8) to (9) of Annex I.
         
      41. Employer: means a Person using the Wages Protection System for the payment of wages.
         
      42. Exchange House: means an exchange business that has been licensed under the Regulations re Licensing and Monitoring of Exchange Business.
         
      43. Exempted Person: means any Person who is exempted from the requirement to hold a License as per Article (2) of this Regulation.
         
      44. Facilitating the Exchange of Payment Tokens: means a Retail Payment Service related to establishing or operating a Payment Token exchange, in a case where the person that establishes or operates that exchange, for the purposes of an offer or invitation made or to be made on that Payment Token exchange, to buy or sell any Payment Token in exchange for Fiat Currency or Payment Token, whether of the same or a different type, comes into possession of any Fiat Currency or Payment Token, whether at the time that offer or invitation is made or otherwise.
         
      45. FATF: an inter-government body which sets international standards that aim to prevent global money laundering and terrorist financing activities.
         
      46. Fiat Currency: means a currency that is controlled by the respective central bank, has the status of legal tender and is required to be accepted within a given jurisdiction.
         
      47. Financial Free Zones: means free zones subject to the provisions of Federal Law No (8) of 2004, regarding Financial Free Zones, as may be amended or supplemented from time to time.
         
      48. Four Party Card Scheme: means a Card Scheme in which Card-based Payment Transactions are made from the payment account of a Payer to the payment account of a payee through the intermediation of the scheme, an issuer (on the payer’s side) and an acquirer (on the Payee’s side).
         
      49. Framework Agreement: means a payment service agreement for the provision of Retail Payment Services which governs the future execution of individual and successive Payment Transactions and which may contain the terms and conditions for opening a Payment Account.
         
      50. Group: means a corporate group which consists of a parent entity and its subsidiaries, and the entities in which the parent entity or its subsidiaries hold, directly or indirectly, 5% or more of the shares, or are otherwise linked by a joint venture relationship.
         
      51. Legal Form: means the legal form of Applicants established in accordance with Article (74) of the Central Bank Law.
         
      52. Level 2 Acts: means any written act that may be adopted or issued by the Central Bank complementing the implementation of this Regulation, such as, without being limited to, rules, directives, decisions, instructions, notices, circulars, standards, and rulebooks.
         
      53. License: means a License issued by the Central Bank to an Applicant to provide Retail Payment Services or operate a Card Scheme in the State. The License is valid unless it is withdrawn, suspended or revoked by the Central Bank.
         
      54. Licensed Financial Activities: means the financial activities subject to Central Bank licensing and supervision, which are specified in Article (65) of the Central Bank Law.
         
      55. Major Regulatory Requirement: means any requirement of this Regulation or Level 2 Acts the violation of which is capable of compromising and/or negatively affecting the attainment of the Central Bank’s objectives pursued under this Regulation, as determined at the discretion of the Central Bank.
         
      56. Management: means the Applicant, Payment Service Provider, Agent and Card Scheme’s senior officers that are involved in the daily management, supervision and control of the business services of the entity, typically including the chief executive officer, his or her alternate(s) and each person directly reporting to that officer. The chief executive officer and his or her alternate(s) shall be a natural person who are ordinarily residing in the State whereas the remaining members of Management shall be based in the State unless the Central Bank allows otherwise.
         
      57. Means of Distance Communication: means a method which may be used for the conclusion of a payment services agreement without the simultaneous physical presence of the Payment Service Provider and the Retail Payment Service User.
         
      58. Merchant: means a Person who accepts Payment Instruments as a mode of payment for the purchase and sale of goods and services.
         
      59. Merchant Acquirer: means a category of Payment Service Provider providing Merchant Acquiring Services.
         
      60. Merchant Acquiring Service: means a Retail Payment Service provided by a Payment Service Provider contracting with a Payee to accept and process Payment Transactions, which results in a transfer of funds to the Payee.
         
      61. Money Transfer Services: means the Domestic and Cross-border Fund Transfers Services, excluding Remittances.
         
      62. Money’s Worth: means value added onto an SVF by the customer; value received on the customer’s SVF account; and value redeemed by the customer including not only “money” in the primary sense but also other forms of monetary consideration or assets such as values, reward points, Crypto-Assets, or Virtual Assets. For example, a value top-up of an SVF account may take the form of values, reward points, Crypto-Assets, or Virtual Assets earned by the SVF customer from making purchases of goods and services. Similarly, value received on the account of the SVF customer may take the form of an on-line transfer of value, reward points, Crypto-Assets, or Virtual Assets between fellow SVF customers.
         
      63. Payment Account: means an account with a Payment Service Provider held in the name of at least one Retail Payment Service User which is used for the execution of Payment Transactions.
         
      64. Payment Account Information Service: means a Retail Payment Service to provide consolidated information on one or more Payment Accounts held by a Retail Payment Service User with either another Payment Service Provider or with more than one Payment Service Providers. For the avoidance of doubt, the Payment Account Information Service does not involve the holding of Retail Payment Service User’s funds at any time.
         
      65. Payment Account Issuance Service: means a Retail Payment Service, other than Domestic and Cross-border Fund Transfer Services, enabling (i) the opening of a Payment Account; (ii) cash to be placed on a Payment Account; (iii) cash to be withdrawn from a Payment Account; and (iv) all necessary operations for operating a Payment Account. The Payment Account is only used for holding fund/cash in transit and not allowed to store and maintain fund/cash.
         
      66. Payment Aggregation Service: means a Retail Payment Service facilitating e-commerce websites and Merchants to accept various Payment Instruments from the Retail Payment Service Users for completion of their payment obligations without the need for Merchants to create a separate payment integration system of their own. Payment aggregation facilitates Merchants to connect with Merchant acquirers; in the process, they receive payments from Retail Payment Service Users, pool and transfer them on to the Merchants after a time period.
         
      67. Payment Data: means any information related to a Retail Payment Service User, including financial data and excluding Personal Data.
         
      68. Payment Initiation Service: means a Retail Payment Service to initiate a Payment Order at the request of the Retail Payment Service User with respect to a Payment Account held at another Payment Service Provider. For the avoidance of doubt, the Payment Initiation Service does not involve the holding and maintenance of Payer’s funds at any time.
         
      69. Payment Instrument: means a personalized device(s), a payment card and/or set of procedures agreed between the Retail Payment Service User and the Payment Service Provider, and used in order to initiate a Payment Order.
         
      70. Payment Instrument Issuance Service: means a Retail Payment Service related to the provision of a Payment Instrument to a Retail Payment Service User which enables it to initiate Payment Orders as well as the Processing of the Retail Payment Service User’s Payment Transactions.
         
      71. Payment Service Provider: means a legal Person that has been licensed in accordance with this Regulation to provide one or more Retail Payment Services and has been included in the Register as per Article (73) of the Central Bank Law.
         
      72. Payment Token Issuing: means a Retail Payment Service related to the issuing of Payment Tokens by a Payment Service Provider. For the avoidance of doubt, Payment Tokens may not be offered to the public or segments thereof unless the Payment Service Provider issuing the Payment Tokens has obtained a Category I License, drafted a White Paper in respect of those Payment Tokens and received an approval by the Central Bank prior to offering such tokens to the public.
         
      73. Payment Token: means a type of Crypto-Asset that is backed by one or more Fiat Currencies, can be digitally traded and functions as (i) a medium of exchange; and/or (ii) a unit of account; and/or (iii) a store of value, but does not have legal tender status in any jurisdiction. A Payment Token is neither issued nor guaranteed by any jurisdiction, and fulfils the above functions only by agreement within the community of users of the Payment Token. For the avoidance of doubt, a Payment Token does not represent any equity or debt claim.
         
      74. Payment Token Buying: means the buying of Payment Tokens in exchange for any Fiat Currency or Payment Token.
         
      75. Payment Token Selling: means the selling of Payment Tokens in exchange for any Fiat Currency or Payment Token.
         
      76. Payment Token Services: means the Retail Payment Services consisting of any of the following activities related to Payment Tokens: (i) Payment Token Issuing; (ii) Payment Token Buying; (iii) Payment Token Selling; (iv) Facilitating the Exchange of Payment Tokens; (v) enabling payments to Merchants and/or enabling peer-to-peer payments; and (vi) Custodian Services. For the avoidance of doubt, a Payment Service Provider may provide only one of the Retail Payment Services referred to in points (v) and (vi); if it wishes to provide both and allows Retail Payment Service Users to redeem the Payment Tokens with any Fiat Currency under a contractual arrangement, it must comply with the respective SVF requirements.
         
      77. Payment Transaction: means an act initiated by the Payer or on his behalf or by the Payee of placing, transferring or withdrawing funds, irrespective of any underlying obligations between the Payer and the Payee.
         
      78. Payee: means a Person who is the intended recipient of funds which have been the subject of a Payment Transaction.
         
      79. Payer: means a Person who holds a Payment Account and allows a Payment Order from that Payment Account, or, where there is no Payment Account, a Person who gives a Payment Order.
         
      80. Person means any natural or legal Person.
         
      81. Personal Data: means any information which are related to an identified or identifiable natural Person.
         
      82. Processing: means Payment Transaction processing necessary for the handling of an instruction, including clearing and settlement, between the Merchant Acquirer and the Card Issuer.
         
      83. Promotion: means any form of communication, by any means, aimed at inviting or offering to enter into an agreement related to any Retail Payment Service. For the avoidance of doubt, any Person that has been mandated to provide or engage in Promotion activities by a Person providing Retail Payment Services without holding a License shall not be held liable under this Regulation.
         
      84. Public Sector Entity: means the Federal Government, Governments of the Union’s member Emirates, public institutions and organizations.
         
      85. Register: means the Register referred to in Article (73) of the Central Bank Law.
         
      86. Regulation: means the Retail Payment Services and Card Schemes Regulation.
         
      87. Remittance: means the receipt of funds from a Payer without any Payment Accounts being created in the name of the Payer or the Payee.
         
      88. Reserve of Assets: means the pool of Fiat Currencies that are legal tender backing the value of a Payment Token.
         
      89. Retail Payment Service: means any business activity set out in Annex I.
         
      90. Retail Payment Service User: means a Person who intends to make use of or makes use of a Retail Payment Service in the capacity of a Payer, Payee or both.
         
      91. Sensitive Payment Data: means data, including personalized security credentials which can be used to carry out unauthorized activities. For the purposes of Payment Initiation and Payment Account Information Services, the name of the Payment Account owner and Payment Account number shall not constitute Sensitive Payment Data.
         
      92. Single Retail Payment Agreement: means an agreement which governs the execution of an individual Payment Transaction.
         
      93. State: means the United Arab Emirates.
         
      94. Security Token: means a type of Crypto-Asset that provides its holder with rights and obligations that represent a debt or equity claim against the issuer of that token.
         
      95. Stored Value Facility or SVF: means a facility (other than cash) for or in relation to which a Customer, or another person on the Customer’s behalf, pays a sum of money (including Money’s Worth such as values, reward points, Crypto-Assets or Virtual Assets) to the issuer, whether directly or indirectly, in exchange for: (a) the storage of the value of that money (including Money’s Worth such as values, reward points, Crypto-Assets or Virtual Assets), whether in whole or in part, on the facility; and (b) the “Relevant Undertaking”. SVF includes Devicebased Stored Value Facility and Non-device based Stored Value Facility.
         
      96. Third country: means a country other than the UAE.
         
      97. Three Party Card Scheme: means a Card Scheme in which the scheme itself provides Merchant Acquiring and Payment Instrument Issuing Services and Card-based Payment Transactions are made from the Payment Account of a Payer to the Payment Account of a Payee within the Card Scheme. When a Three Party Card Scheme licenses other Payment Service Providers for the issuance of Card-based Payment Instruments or the Merchant Acquiring of Card-based Payment Transactions, or both, or issues Card-based Payment Instruments with a co-branding partner or through an agent, it is considered to be a Four Party Card Scheme.
         
      98. UAE: means the United Arab Emirates.
         
      99. Unauthorized Payment Transaction: means a Payment Transaction for the execution of which the Payer has not given consent. Consent to execute a Payment Transaction or a series of Payment Transactions shall be given in the form agreed between the Payer and the Payment Service Provider. Consent to execute a Payment Transaction may also be given via the Payee or the Payment Initiation Service Provider.
         
      100. Virtual Assets: A Virtual Asset is a digital representation of value that can be digitally traded, or transferred, and can be used for payment or investment purposes. Virtual Assets do not include digital representations of Fiat Currencies, securities and other financial assets that are already covered elsewhere in the FATF Recommendations.
         
      101. Virtual Assets Service Providers: Virtual Asset Service Provider means any natural or legal person who is not covered elsewhere under the FATF Recommendations, and as a business conducts one or more of the following activities or operations for or on behalf of another natural or legal person: (i) exchange between Virtual Assets and Fiat Currencies; (ii) exchange between one or more forms of Virtual Assets; (iii) transfer of Virtual Assets; (iv.) safekeeping and/or administration of Virtual Assets or instruments enabling control over Virtual Assets; and (v) participation in and provision of financial services related to an issuer’s offer and/or sale of a Virtual Asset.
         
      102. Virtual Asset Token: means a type of Crypto-Asset that can be digitally traded and functions as (i) a unit of account; and/or (ii) a store of value. Although some Virtual Asset Tokens may be accepted as a means of payment, they are generally not accepted as a medium of exchange, may not have an issuer and do not have legal tender status in any jurisdiction. A Virtual Asset Token is neither issued nor guaranteed by any jurisdiction, and fulfils the above functions only by agreement within the community of users of the Virtual Asset Token. For the avoidance of doubt, a Virtual Asset Token does not represent any equity or debt claim, and it is not backed by any Fiat Currency.
         
      103. Virtual Asset Token Services: means any of the following services: (i) enabling peer-to-peer Virtual Asset Token transfers, and (ii) custodian services of Virtual Asset Tokens.
         
      104. Wages Protection System or WPS: means a reconciliation system implemented at the Central Bank aimed at providing a safe, secure, efficient and robust mechanism for streamlining the timely and efficient payment of wages.
         
      105. Wire Transfer: means any transaction carried out on behalf of an originator through a financial institution by electronic means with a view to making an amount of funds available to a beneficiary person at a beneficiary financial institution, irrespective of whether the originator and the beneficiary are the same person
         
      106. WPS Payment Account: means a WPS account opened in the infrastructure of the Central Bank and held for the purposes of holding and payment of wages.
         
      107. WPS Payment Account Holder: means a holder of a Payment Account held with a Payment Service Provider who has been given access to the Wages Protection System for the purpose of executing transfers of wages.
         
      108. White Paper: means a detailed description in Arabic and English of: (i) the Payment Service Provider issuing a Payment Token and a presentation of the main participants involved in the project’s design and development; (ii) a detailed description of the project and the type of Payment Token that will be offered to the public; (iii) the number of Payment Tokens that will be issued and the issue price; (iv) a detailed description of the rights and obligations attached to the Payment Token and the procedures and conditions for exercising those rights; (v) information on the underlying technology and standards applied by the Payment Service Provider issuing the Payment Token allowing for the holding, storing and transfer of those Payment Tokens; (vi) a detailed description of the risks relating to the Payment Service Provider issuing Payment Tokens, the Payment Tokens, the offer to the public and the implementation of the project, and other disclosures that the Central Bank may specify; (vii) detailed description of the Payment Service Provider’s governance arrangements, including a description of the role, responsibilities and accountability of the third-parties responsible for operating, investment and custody of the Reserve of Assets, and, where applicable, the distribution of the Payment Tokens; (viii) a detailed description of the Reserve of Assets; (ix) a detailed description of the custody arrangements for the Reserve of Assets, including the segregation of the assets; (x) in case of an investment of the Reserve of Assets, a detailed description of the investment policy; and (xi) information on the nature and enforceability of rights, including any direct redemption right or any claims that holders of Payment Tokens may have on the Reserve of Assets or against the Payment Service Provider issuing the Payment Tokens, including how such rights may be treated in insolvency procedures. For the avoidance of doubt, the White Paper shall be written in a simple, easy to understand and non-misleading language, and shall be dated. The White Paper shall be endorsed by the Payment Service Provider’s Management and published on the Payment Service Provider’s website after receipt of an approval by the Central Bank.
         
    • Article (2): Licensing

      1. No Person shall provide or engage in the Promotion within the State of any of the Retail Payment Services set out in Annex I without obtaining a prior License from the Central Bank unless this Person is an exempted Person.
         

      Exempted Persons

      1. Banks licensed in accordance with the Central Bank Law shall be deemed licensed to provide Retail Payment Services and shall therefore be exempt from the prohibition laid down in paragraph (1). Nevertheless, Banks shall be required to notify the Central Bank in writing if they intend to provide the Retail Payment Services referred to in points (3) to (4) and (7) to (9) of Annex I and obtain a No Objection Letter prior to commencing the provision of such services. Banks are exempted from the No Objection Letter requirement and any licensing requirements for providing the Retail Payment Services referred to in points (1), (2), (5) and (6) of Annex I.
         
      2. For the avoidance of doubt, Banks providing Retail Payment Services other than the Retail Payment Services referred to in points (1), (2), (5) and (6) of Annex I, shall be required to comply only with the requirements set out in Article (11) on Payment Token Services, Article (12) on Anti-Money Laundering and Combating the Financing of Terrorism and Illegal Organizations, Article (13) on Technology Risk and Information Security, and Article (14) on Obligations Towards Retail Payment Service Users.
         
      3. Finance companies licensed in accordance with the finance companies Regulation shall be exempt from the prohibition laid down in paragraph (1) for the service of issuance of credit cards. For the avoidance of doubt, except issuance of credit cards, finance companies that intend to provide Retail Payment Services shall be required to obtain a prior License from the Central Bank.
         
      4. The Central Bank may request from a Person or Exempted Person the provision of any information or documentation that it considers necessary to determine the eligibility for exemption or continued exemption, respectively.
         
      5. The Central Bank reserves the right to withdraw an exemption granted under this Article 2.
         
    • Article (3): License Categories

      1. A Person that intends to provide Retail Payment Services shall apply for one of the following categories of License:
         
        1. 1.1. Category I License;
           
        2. 1.2. Category II License;
           
        3. 1.3. Category III License; and
           
        4. 1.4. Category IV License
           
      2. An Applicant shall apply for a Category I License where it intends to provide one or more of the following Retail Payment Services:
         
        1. 2.1. Payment Account Issuance Services;
           
        2. 2.2. Payment Instrument Issuance Services;
           
        3. 2.3. Merchant Acquiring Services;
           
        4. 2.4. Payment Aggregation Services;
           
        5. 2.5. Domestic Fund Transfer Services;
           
        6. 2.6. Cross-border Fund Transfer Services; and
           
        7. 2.7. Payment Token Services.
           
      3. An Applicant shall apply for a Category II License where it intends to provide one or more of the following Retail Payment Services:
         
        1. 3.1. Payment Account Issuance Services;
           
        2. 3.2. Payment Instrument Issuance Services;
           
        3. 3.3. Merchant Acquiring Services;
           
        4. 3.4. Payment Aggregation Services;
           
        5. 3.5. Domestic Fund Transfer Services; and
           
        6. 3.6. Cross-border Fund Transfer Services.
           
      4. An Applicant shall apply for a Category III License where it intends to provide one or more of the following Retail Payment Services:
         
        1. 4.1. Payment Account Issuance Services;
           
        2. 4.2. Payment Instrument Issuance Services;
           
        3. 4.3. Merchant Acquiring Services;
           
        4. 4.4. Payment Aggregation Services; and
           
        5. 4.5. Domestic Fund Transfer Services.
           
      5. An Applicant shall apply for a Category IV License where it intends to provide one or all of the following Retail Payment Services:
         
        1. 5.1. Payment Initiation Services; and
           
        2. 5.2. Payment Account Information Services.
           
    • Article (4): License Conditions

      1. To be granted a License, an Applicant shall, at the time of submitting an Application:
         
        1. 1.1. fulfil the Legal Form;
           
        2. 1.2. meet the respective initial capital requirements per License Category specified in Article (6); and
           
        3. 1.3. provide the necessary documents and information specified in the Central Bank application form as provided by the Licensing Division.
           
      2. In addition to the requirements set out in paragraph (1) to be granted a Category I License, an Applicant shall, at the time of submitting an Application, provide a list of all Payment Tokens that it intends to issue and obtain a legal opinion on the assessment for all Payment Tokens.
         
      3. In addition to the requirements set out in paragraph (1), to be granted a Category IV License, an Applicant shall, at the time of submitting an Application, hold a professional indemnity insurance as per Article (10) paragraphs (14) to (16).
         
    • Article (5): Licensing Procedure

      1. The licensing of Applicants shall be subject to the procedure envisaged in the Central Bank’s Licensing Guidelines.
         
      2. The Management of an Applicant is encouraged to meet with the Central Bank’s Licensing Division before submitting a formal Application.
         
    • Article (6): Initial Capital

      1. An Applicant shall hold, upon being granted a License by the Central Bank, initial capital as per the below:
         
        1. 1.1. for obtaining a Category I License:
           
          1. 1.1.1. initial capital of at least three (3) million Dirhams where the monthly average value of Payment Transactions amounts to ten (10) million Dirhams or above; or
             
          2. 1.1.2. initial capital of at least one and a half (1.5) million Dirhams where the monthly average value of Payment Transactions amounts to less than ten (10) million Dirhams.
             
        2. 1.2. for obtaining a Category II License:
           
          1. 1.2.1. initial capital of at least two (2) million Dirhams where the monthly average value of Payment Transactions amounts to ten (10) million Dirhams or above; or
             
          2. 1.2.2. initial capital of at least one (1) million Dirhams where the monthly average value of Payment Transactions amounts to less than ten (10) million Dirhams.
             
        3. 1.3. for obtaining a Category III License:
           
          1. 1.3.1. initial capital of at least one (1) million Dirhams where the monthly average value of Payment Transactions amounts to ten (10) million Dirhams or above; or
             
          2. 1.3.2. initial capital of at least five hundred thousand (500,000) Dirhams where the monthly average value of Payment Transactions amounts to less than ten (10) million Dirhams.
             
        4. 1.4. for obtaining a Category IV License: initial capital of at least one hundred thousand (100,000) Dirhams regardless of the monthly average value of Payment Transactions.
           
      2. An Applicant shall provide information to the Central Bank on the source(s) of funds that constitute the initial capital as per paragraph (1).
         

      Calculation Method

      1. The monthly average value of Payment Transactions referred to in paragraph (1) shall be calculated on the basis of the moving average of the preceding (3) months or, where such data does not exist at the time of being granted a License by the Central Bank, on the basis of the business plan and financial projections provided.
         
    • Article (7): Aggregate Capital Funds

      1. A Payment Service Provider shall hold and maintain at all times aggregate capital funds that do not fall below the initial capital requirements laid down in Article (6), taking into consideration the applicable License category.
         
      2. The Central Bank may impose aggregate capital funds requirements higher than the ones referred to in paragraph (1) if, taking into consideration the scale and complexity of the Payment Service Provider’s business, it considers such higher requirements essential to ensuring that the Payment Service Provider has the ability to fulfil its obligations under this Regulation.
         
      3. Where the monthly average value of Payment Transactions calculated in accordance with Article (6) (3) exceeds the Payment Transaction threshold of ten (10) million Dirhams in (3) consecutive months, Payment Service Providers shall report this fact to the Central Bank and become automatically subject to the higher aggregate capital funds requirements determined by the Central Bank under paragraph (2).
         
      4. The aggregate capital funds referred to in paragraph (1) shall be comprised of one or more of the capital items provided for in paragraphs (5) and (6).
         

      Capital Items

      1. A Payment Service Provider’s aggregate capital funds shall consist of:
         
        1. 5.1. Paid-up capital;
           
        2. 5.2. Reserves, excluding revaluation reserves; and
           
        3. 5.3. Retained earnings.
           
      2. The following items shall be deducted from the aggregate capital funds:
         
        1. 6.1. Accumulated losses; and
           
        2. 6.2. Goodwill.
           
    • Article (8): Control of Controllers

      1. A Person shall not become a Controller in a Payment Service Provider without obtaining a prior approval from the Central Bank.
         
      2. The Central Bank shall grant an approval under paragraph (1) if it considers that:
         
        1. 2.1. having regard to the likely influence of the Controller, the Payment Service Provider will remain compliant with the requirements of this Regulation and Level 2 Acts; and
           
        2. 2.2. the Controller meets the fit and proper requirements specified by the Central Bank.
           
      3. The approval under paragraph (2) may be granted subject to any conditions that the Central Bank may impose on the Person, including but not limited to:
         
        1. 3.1. conditions restricting the Person’s disposal or further acquisition of shares or voting powers in the Payment Service Provider; and
           
        2. 3.2. conditions restricting the Person’s exercise of voting power in the Payment Service Provider.
           
    • Article (9): Principal Business

      1. The principal business of a Payment Service Provider shall be the provision of the Retail Payment Service(s) for which it has been granted a License.
         
      2. Where a Payment Service Provider intends to provide ancillary service(s) falling outside the scope of its License, it shall obtain the approval of the Central Bank prior to commencing the provision of such service(s).
         
      3. The Central Bank requires prior approval for the provision of any ancillary service(s) by a Payment Service Provider, and may require a Payment Service Provider that intends to provide ancillary service(s), to create a separate entity for the provision of such services, if it believes that the conduct of the ancillary activities may have a negative impact on the Payment Service Provider’s ability to comply with the requirements of this Regulation and Level 2 Acts.
         
    • Article (10): On-Going Requirements

      Corporate Governance

      1. Payment Service Providers must comply with the below requirements on corporate governance.
         
      2. Payment Service Providers must have and maintain effective, robust and well-documented corporate governance arrangements, including a clear organizational structure with well-defined, transparent and consistent lines of responsibility.
         
      3. The corporate governance arrangements referred to in paragraph (2) must be comprehensive and proportionate to the nature, scale and complexity of the Retail Payment Services provided, and shall contain, at a minimum:
         
        1. 3.1. an organization chart showing each division, department or unit, indicating the name of each responsible individual accompanied by a description of the respective function and responsibilities;
           
        2. 3.2. controls on conflicts of interest;
           
        3. 3.3. controls on integrity and transparency of the Payment Service Provider’s operations;
           
        4. 3.4. controls to ensure compliance with applicable laws and regulations;
           
        5. 3.5. methods for maintaining confidentiality of information; and
           
        6. 3.6. procedures for regular monitoring and auditing of all corporate governance arrangements.
           

      Risk Management

      1. Payment Service Providers must have and maintain robust and comprehensive policies and procedures to identify, manage, monitor and report the risks arising from the provision of Retail Payment Services to which they are or might become exposed, and adequate internal control mechanisms, including sound administrative and accounting procedures.
         
      2. Payment Service Providers’ risk management policies and procedures shall be:
         
        1. 5.1. kept up-to-date;
           
        2. 5.2. reviewed annually; and
           
        3. 5.3. proportionate to the nature, scale and complexity of the Retail Payment Services provided.
           
      3. Payment Service Providers must establish a risk management function, an internal audit function and a compliance function.
         

      Accounting and Audit

      1. Payment Service Providers must appoint an Auditor to audit on an annual basis:
         
        1. 7.1. the financial statements or consolidated financial statements of the Payment Service Provider prepared in accordance with the accepted accounting standards and practices; and
           
        2. 7.2. the systems and controls of the Retail Payment Services provided by the Payment Service Provider, separately from any audit on non-Retail Payment Services.
           
      2. Upon request by the Central Bank, the appointed Auditor shall submit, directly or through the Payment Service Provider, a report of the audit in a form and within a timeframe acceptable to the Central Bank.
         
      3. In addition to the report of audit, the Central Bank may request from the Auditor to:
         
        1. 9.1. submit any additional information in relation to the audit, if the Central Bank considers it necessary;
           
        2. 9.2. enlarge or extend the scope of the audit;
           
        3. 9.3. carry out any other examination.
           

      Record Keeping

      1. Payment Service Providers shall keep all necessary records on Personal and Payment Data for a period of (5) years from the date of receipt of such data, unless otherwise required by other applicable laws or the Central Bank.
         

      Notification Requirements

      1. Where any material change affects the accuracy and completeness of information provided in an Application, the Applicant or Payment Service Provider, as the case may be, shall immediately notify the Central Bank of such change and provide all necessary information and documents.
         
      2. A Payment Service Provider shall immediately notify the Central Bank of any violation or potential violation of a Major Regulatory Requirement of this Regulation or Level 2 Acts.
         
      3. A Payment Service Provider shall immediately notify the Central Bank if it becomes aware that any of the following events have occurred or are likely to occur:
         
        1. 13.1. any event that prevents access to or disrupts the operations of the Payment Service Provider;
           
        2. 13.2. any legal action taken against the Payment Service Provider either in the State or in a Third Country;
           
        3. 13.3. the commencement of any insolvency, winding up, liquidation or equivalent proceedings, or the appointment of any receiver, administrator or provisional liquidator under the laws of any country;
           
        4. 13.4. any disciplinary measure or sanction taken against the Payment Service Provider or imposed on it by a regulatory body other than the Central Bank, whether in the State or in a Third Country;
           
        5. 13.5. any change in regulatory requirements to which it is subject beyond those of the Central Bank, whether in the State or in a Third Country; and
           
        6. 13.6. any other event specified by the Central Bank.
           

      Professional Indemnity Insurance

      1. Payment Service Providers providing Payment Initiation and Payment Account Information Services shall hold a professional indemnity insurance whose amount shall be decided upon by the Central Bank.
         
      2. The professional indemnity insurance of Payment Service Providers providing Payment Initiation Services referred to in paragraph (14) shall cover these Payment Service Providers’ liabilities for Unauthorized Payment Transactions and non-execution, defective or late execution of Payment Transactions.
         
      3. The professional indemnity insurance of Payment Service Providers providing Payment Account Information Services referred to in paragraph (14) shall cover these Payment Service Providers’ liability vis-à-vis the Payment Service Provider providing Account Issuance Services or the Retail Payment Service User resulting from non-authorized or fraudulent access to or non-authorized or fraudulent use of Payment Account information.
         
    • Article (11) Payment Token Services

      1. This Article (11) is without prejudice to other provisions of this Regulation that are relevant to Payment Service Providers providing Payment Token Services.
         
      2. For the avoidance of doubt, Payment Token Services do not include Security Token, Commodity Token and Virtual Asset Token and the provision of services associated with the same.
         
      3. Security Token and Commodity Token fall within the jurisdiction of the Securities and Commodities Authority and as such are regulated by the Securities and Commodities Authority.
         
      4. Virtual Asset Tokens, although may be accepted as a means of payment, are not generally accepted as a medium of exchange due to the lack of stability and high volatility in their market value. As a result, any services associated with Virtual Asset Tokens, including Virtual Asset Token Services, fall outside the scope of this Regulation.
         

      Anti-Money Laundering and Combating the Financing of Terrorism and Illicit Organizations

      1. Payment Token Services shall be considered to carry high money laundering and terrorist financing risk due to their speed, anonymity and cross-border nature. In line with the FATF standards, Payment Services Providers providing Payment Token Services shall undertake risk assessment and take appropriate measures to manage and mitigate the identified risks in accordance with applicable legal and regulatory requirements. Payment Service Providers providing Payment Token Services shall comply with the FATF Guidance for a Risk-based Approach to Virtual Assets and Virtual Assets Service Providers, as may be supplemented from time to time, or any related standards or guidance in assessing and managing risks in Payment Token Services.
         

      Technology Risk and Information Security

      Security Requirements

      1. A Payment Service Provider providing Payment Token Services shall have a good understanding of the security risks and vulnerabilities of each Payment Token provided. It shall carry out a security risk assessment for each Payment Token.
         

      Cyber Security Risk

      1. Payment Service Providers providing Payment Token Services whose monthly average value of Payment Transactions amounts to ten (10) million Dirhams or above shall regularly assess the necessity to perform penetration and cyber-attack simulation testing. Coverage and scope of testing shall be based on the cyber security risk profile, cyber intelligence information available, covering not only networks (both external and internal) and application systems but also social engineering and emerging cyber threats. A Payment Service Provider shall also take appropriate actions to mitigate the issues, threats and vulnerabilities identified in penetration and cyber-attack simulation testing in a timely manner, based on the impact and risk exposure analysis.
         

      Specific Obligations for Providing Retail Payment Service on Payment Tokens

      Reserve of Assets

      1. Payment Service Providers issuing Payment Tokens shall keep and maintain at all times a Reserve of Assets per category of Payment Token issued.
         
      2. Payment Service Providers issuing Payment Tokens shall ensure effective and prudent management of the Reserve of Assets. They shall ensure that the creation and destruction of Payment Tokens is matched by a corresponding increase or decrease in the Reserve of Assets and that such increase or decrease is adequately managed to avoid any adverse impacts on the market of the Reserve Assets.
         

      Stabilisation Mechanism

      1. Payment Service Providers issuing Payment Tokens shall have and maintain a clear and detailed policy on the selected stabilisation mechanism. That policy and procedure shall in particular:
         
        1. 10.1. describe the type, allocation and composition of the reference assets the value of which aims at stabilising the value of the Payment Tokens;
           
        2. 10.2. contain a detailed assessment of the risks, including credit risk, counterparty risk, market risk and liquidity risk, resulting from the Reserve of Assets;
           
        3. 10.3. describe the procedure for the creation and destruction of Payment Tokens and the consequence of such creation or destruction on the increase and decrease of the Reserve of Assets;
           
        4. 10.4. provide information on whether the Reserve of Assets is invested, and where part of the Reserve of Assets is invested, describe in detail the investment policy and contain an assessment of how that investment policy can affect the value of the Reserve of Assets; and
           
        5. 10.5. describe the procedure to purchase and redeem Payment Tokens against the Reserve of Assets, and list the persons who are entitled to such redemption.
           
      2. Payment Service Providers issuing Payment Tokens shall ensure an independent audit of the Reserve of Assets on a bi-annual basis as from the receipt of the Central Bank’s approval of the White Paper with respect of the Payment Tokens.
         

      Custody

      1. Payment Service Providers issuing Payment Tokens shall establish, maintain and implement custody policies, procedures and contractual arrangements for each category of issued Payment Tokens that ensure at all times that:
         
        1. 12.1. the Reserve of Assets is segregated from the Payment Service Provider’s own assets;
           
        2. 12.2. the Reserve of Assets is not encumbered or pledged;
           
        3. 12.3. the Reserve of Assets is held in custody in accordance with paragraph (14); and
           
        4. 12.4. the Payment Service Providers have prompt access to the Reserve of Assets to meet any redemption requests from the holders of Payment Token.
           
      2. The assets received in exchange for the Payment Tokens shall be held in custody by no later than (5) Business Days after the issuance of the Payment Tokens by:
         
        1. 13.1. Bank; or
           
        2. 13.2. Payment Service Provider providing Payment Token Custody.
           

      Investment of the Reserve of Assets

      1. Payment Service Providers issuing Payment Tokens that invest a portion of the Reserve of Assets shall invest those assets only in highly liquid financial instruments with minimal market and credit risk. The investments shall be capable of being liquidated rapidly with minimal adverse price effect.
         
      2. All profits or losses, including fluctuations in the value of the financial instruments referred to in paragraph (14), and any counterparty or operational risks that result from the investment of the assets shall be borne by Payment Service Providers issuing the Payment Tokens.
         

      Pre-Trade Transparency

      1. Payment Service Providers that engage in Facilitating the Exchange of Payment Tokens shall disclose to its Retail Payment Service Users and the public as appropriate, on a continuous basis during normal trading, the following information relating to trading of each accepted Payment Tokens on their platform:
         
        1. 16.1. the current bid, offer prices and volume;
           
        2. 16.2. the depth of trading interest shown at the prices and volumes advertised through their systems for the accepted Payment Tokens; and
           
        3. 16.3. any other information relating to accepted Payment Tokens which would promote transparency relating to trading.
           
      2. Payment Service Providers that engage in Facilitating the Exchange of Payment Tokens shall use appropriate mechanisms to enable pre-trade information to be made available to the public in an easy to access and uninterrupted manner.
         

      Post-Trade Transparency

      1. Payment Service Providers that engage in Facilitating the Exchange of Payment Tokens shall disclose the price, volume and time of the Payment Transactions executed in respect of accepted Payment Tokens to the public as close to real-time as is technically possible on a nondiscretionary basis. They shall use adequate mechanisms to enable post-trade information to be made available to the public in an easy to access and uninterrupted manner, at least during business hours.
         
    • Article (12) Anti-Money Laundering and Combating the Financing of Terrorism and Illicit Organizations

      1. Payment Service Providers must comply with the relevant UAE AML Laws and Regulations and address money laundering and terrorist financing risks through appropriate preventive measures to deter abuse of the sector as a conduit for illicit funds, and detect money laundering and terrorist financing activities and report any suspicious transactions to the Financial Intelligence Department at the Central Bank.
         
      2. Payment Service Providers must have comprehensive and effective internal AML/CFT policies, procedures and controls in place. Payment Service Providers shall be prohibited from invoking banking, professional or contractual secrecy as a pretext for refusing to perform their statutory reporting obligation in regard to suspicious activity.
         
      3. Payment Service Providers must identify, assess, and understand the ML/FT risks to which they are exposed and conduct enterprise-level and business relationship-specific risk assessments. Accordingly, all AML/CFT CDD, monitoring and controls must be risk-based and aligned to the risk assessments.
         
      4. Payment Service Providers shall undertake periodic risk profiling of Retail Payment Service Users and assessment based on the AML/CFT requirements.
         
      5. Payment Service Providers shall assess whether a business relationship presents a higher money laundering and terrorist financing risk and assign a related risk rating. Payment Service Providers shall be prohibited from dealing in any way with shell banks or other shell financial institutions and from establishing or maintaining any business relationship or conducting any Payment Transaction under an anonymous or fictitious name or by pseudonym or number.
         
      6. Payment Service Providers shall ensure that their CDD models are designed to address the specific risks posed by a Retail Payment Service User profile and Payment Instrument features. Payment Service Providers shall be prohibited from establishing or maintaining any business relationship or executing any Payment Transaction in the event that they are unable to complete adequate risk-based CDD measures for any reason.
         
      7. Payment Service Providers providing Retail Payment Services must undertake certain CDD measures concerning Wire Transfers as stipulated in the relevant provisions of the AML Law if Wire Transfer services are provided by Payment Service Providers. Payment Service Providers should introduce appropriate systems for screening, as part of the CDD process, on all parties involved in a transaction against all applicable sanction lists (i.e. the UN sanction lists and the names contained in the ‘search notices’/’search and freeze notices’ issued by the Central Bank).
         
      8. If Payment Service Providers provide the service of Wire Transfers, they should take freezing action and prohibit conducting transactions with designated persons and entities, as per the obligations set out in the Central Bank’s Notice 103/2020 on the Implementation of United Nations Security Council (UNSC) and the UAE Cabinet Resolutions regarding UNSC and Local Lists, as amended from time to time.
         
      9. Payment Service Providers should also be guided by the Financial Action Task Force (FATF) Standards on anti-money laundering and countering the financing of terrorism and proliferation. Payment Service Providers should incorporate the regular review of ML/FT trends and typologies into their compliance training programmes as well as into their risk identification and assessment procedures.
         
    • Article (13) Technology Risk and Information Security

      1. Payment Service Providers shall comply with this Article (13) and are encouraged to consult Annex II for the Guidance on the best practices for technology risk and information security.
         

      Technology Risk

      1. Payment Service Providers are expected to take into account international best practices and standards when designing and implementing the technology and specific risk management systems and processes.
         
      2. A Payment Service Provider shall establish an effective technology and cyber security risk management framework to ensure the adequacy of IT controls, cyber resilience, the quality and security, including the reliability, robustness, stability and availability, of its computer systems, and the safety and efficiency of the operations of Retail Payment Services. The framework shall be “fit for purpose” and commensurate with the risks associated with the nature, size, complexity and types of business and operations, the technologies adopted and the overall risk management system of the Payment Service Provider. Consideration shall be given to adopting recognized international standards and practices when formulating such risk management framework.
         
      3. A Payment Service Provider’s effective technology risk management framework shall comprise proper IT governance, a continuous technology risk management process and implementation of sound IT control practices.
         
      4. A Payment Service Provider shall establish a general framework for management of major technology-related projects, such as in-house software development and acquisition of information systems. This framework shall specify, among other things, the project management methodology to be adopted and applied to these projects.
         
      5. Payment Service Provider shall apply and meet at a minimum the UAE Information Assurance Standards, as may be amended from time to time.
         

      IT Governance

      1. A Payment Service Provider shall establish a proper IT governance framework. IT governance shall cover various aspects, including a clear structure of IT functions and the establishment of IT control policies. While there could be different constructs, the major functions shall include an effective IT function, a robust technology risk management function, and an independent technology audit function.
         
      2. The Board, or a committee designated by the Board shall be responsible for ensuring that a sound and robust risk management framework is established and maintained to manage technology risks in a manner that is commensurate with the risks posed by the Payment Service Provider’s Retail Payment Activities.
         

      Security Requirements

      1. A Payment Service Provider must define clearly its security requirements in the early stage of system development or acquisition as part of business requirements and adequately built during the system development stage.
         
      2. A Payment Service Provider using the Agile methods to accelerate software development must incorporate adequate security practices to ensure the software is not compromised at any stage in its development process.
         
      3. A Payment Service Provider that develops an Application Programming Interface (API) or provides an API shall establish safeguards to manage the development and provision of the APIs to secure the interaction and exchange of data between various software applications.
         

      Network and Infrastructure Management

      1. A Payment Service Provider whose monthly average value of Payment Transactions amounts to ten (10) million Dirhams or above shall clearly assign overall responsibility for network management to individuals who are equipped with expertise to fulfil their duties. Network standards, design, diagrams and operating procedures shall be formally documented, kept up-to-date, communicated to all relevant network staff and reviewed periodically.
         
      2. A Payment Service Provider shall establish a security administration function and a set of formal procedures for administering the allocation of access rights to system resources and application systems, and monitoring the use of system resources to detect any unusual or unauthorized activities.
         
      3. Payment Service Providers shall exercise due care when controlling the use of and access to privileged and emergency IDs. The necessary control procedures include:
         
        1. 14.1. changing the default password;
           
        2. 14.2. implement strong password control, with minimum password length and history, password complexity as well as maximum validity period;
           
        3. 14.3. restricting the number of privileged users;
           
        4. 14.4. implementing strong controls over remote access by privileged users;
           
        5. 14.5. granting of authorities that are strictly necessary to privileged and emergency IDs;
           
        6. 14.6. formal approval by appropriate senior personnel prior to being released for usage;
           
        7. 14.7. logging, preserving and monitoring of the activities performed by privileged and emergency IDs (e.g. peer reviews of activity logs);
           
        8. 14.8. prohibiting sharing of privileged accounts;
           
        9. 14.9. proper safeguard of privileged and emergency IDs and passwords (e.g. kept in a sealed envelope and locked up inside the data center); and
           
        10. 14.10.changing of privileged and emergency IDs’ passwords immediately upon return by the requesters.
           

      Cyber Security Risk

      1. Where a Payment Service Provider is heavily reliant on Internet and mobile technologies to deliver the Retail Payment Services it provides, cyber security risks shall be adequately managed through the Payment Service Provider’s technology risk management process. The Payment Service Provider shall also commit adequate skilled resources to ensure its capability to identify the risk, protect its critical services against the attack, contain the impact of cyber security incidents and restore the services.
         
      2. A Payment Service Provider shall establish a cyber incident response and management plan to swiftly isolate and neutralize a cyber threat and to resume affected services as soon as possible. The plan shall describe procedures to respond to plausible cyber threat scenarios
         
      3. Payment Service Providers whose monthly average value of Payment Transactions amounts to ten (10) million Dirhams or above shall regularly assess the necessity to perform penetration and cyber-attack simulation testing. Coverage and scope of testing shall be based on the cyber security risk profile, cyber intelligence information available, covering not only networks (both external and internal) and application systems but also social engineering and emerging cyber threats. A Payment Service Provider shall also take appropriate actions to mitigate the issues, threats and vulnerabilities identified in penetration and cyber-attack simulation testing in a timely manner, based on the impact and risk exposure analysis.
         

      Retail Payment Service User Authentication

      1. A Payment Service Provider shall select and implement reliable and effective authentication techniques to validate the identity and authority of its Retail Payment Service Users. Multi-factor authentication shall be required for high-risk transactions.
         
      2. End-to-end encryption shall be implemented for the transmission of Retail Payment Service User passwords so that they are not exposed at any intermediate nodes between the Retail Payment Service User mobile application or browser and the system where passwords are verified.
         

      Login Attempts and Session Management

      1. A Payment Service Provider shall implement effective controls to limit the number of login or authentication attempts (e.g. wrong password entries), implementing time-out controls and setting time limits for the validity of authentication. If one-time password is used for authentication purpose, a Payment Service Provider shall ensure that the validity period of such passwords is limited to the strict minimum necessary.
         
      2. A Payment Service Provider shall have processes in place ensuring that all Payment Transactions are logged with an appropriate audit trail.
         

      Administration of Retail Payment Service User Accounts

      1. Where a Payment Service Provider providing Payment Account Issuance Services allows a Retail Payment Service User to open a Payment Account through an online channel, a reliable method shall be adopted to authenticate the identity of that Retail Payment Service User. In general, the electronic know your customer (i.e. Retail Payment Service User) (eKYC) processes accepted by the Central Bank for Banks is acceptable for the customer verification and validation processes of Payment Account Issuance Services.
         
      2. A Payment Service Provider shall perform adequate identity checks when any Retail Payment Service User requests a change to the Retail Payment Service User’s Payment Account information or contact details that are useful for the Retail Payment Service User to receive important information or monitor the activities of the Retail Payment Service User’s Payment Accounts.
         
      3. A Payment Service Provider shall implement effective controls such as two-factor authentication, to re-authenticate the Retail Payment Service User before effecting each high-risk transaction. High-risk transactions shall, at least, include:
         
        1. 24.1. Payment Transactions that exceeded the predefined transaction limit(s);
           
        2. 24.2. Change of personal contact details; and
           
        3. 24.3. Unless it is not practicable to implement, Payment Transactions that exceeded the aggregate rolling limit(s) (i.e. total value of Payment Transactions over a period of time).
           

      Business Continuity

      1. A Payment Service Provider shall have in place an adequate business continuity management program to ensure continuation, timely recovery, or in extreme situations orderly scaledown of critical operations in the event of major disruptions caused by different contingent scenarios. An adequate business continuity management program comprises business impact analysis, recovery strategies, a business continuity plan and alternative sites for business and IT recovery.
         
      2. A Payment Service Provider shall put in place a set of recovery strategies to ensure that all critical business functions identified in a business impact analysis can be recovered in accordance with the predefined recovery timeframe. These recovery strategies shall be clearly documented, thoroughly tested and regularly reviewed to ensure achievement of recovery targets.
         
      3. A Payment Service Provider shall put in place effective measures to ensure that all business records, in particular Retail Payment Service User records, can be timely restored in case they are lost, damaged, or destroyed. A Payment Service Provider shall also allow Retail Payment Service Users to access their own records in a timely manner. A Payment Service Provider shall notify Retail Payment Service Users of any loss in their records through an operational failure or through theft, and make reasonable effort to ensure that personal records so lost are not used wrongfully.
         
      4. A Payment Service Provider shall develop a business continuity plan based on the business impact analysis and related recovery strategies. A business continuity plan shall comprise, at a minimum:
         
        1. 28.1. detailed recovery procedures to ensure full accomplishment of the service recovery strategies;
           
        2. 28.2. escalation procedures and crisis management protocol (e.g. set up of a command center, timely reporting to the Central Bank, etc.) in case of severe or prolonged service disruptions;
           
        3. 28.3. proactive communication strategies (e.g. Retail Payment Service User notification, media response, etc.);
           
        4. 28.4. updated contact details of key personnel involved in the business continuity plan; and
           
        5. 28.5. assignment of primary and alternate personnel responsible for recovery of critical systems.
           
      5. A Payment Service Provider shall conduct testing of its business continuity plan at least annually. Its Management, primary and alternate relevant personnel shall participate in the annual testing to familiarize themselves with their recovery responsibilities.
         
      6. A Payment Service Provider shall review all business continuity planning-related risks and assumptions for relevancy and appropriateness as part of the annual planning of testing. Formal testing documentation, including a test plan, scenarios, procedures and results, shall be produced. A post mortem review report shall be prepared for formal sign-off by Management
         

      Alternate Sites for Business and IT Recovery

      1. A Payment Service Provider shall examine the extent to which key business functions are concentrated in the same or adjacent locations and the proximity of the alternate sites to primary sites. Alternate sites shall be sufficiently distanced to avoid any shared risk and being affected by the same disaster.
         
      2. A Payment Service Provider’s alternate site shall be readily accessible, installed with appropriate facilities and available for occupancy within the time requirement specified in its business continuity plan. Appropriate physical access controls shall be implemented. If certain recovery staff are required to work from home in the event of a disaster, adequate computer systems and communication facilities shall be made available in advance.
         
      3. Alternate sites for IT recovery shall have sufficient technical equipment, including communication facilities, of an appropriate standard and capacity to meet recovery requirements.
         
      4. A Payment Service Provider shall avoid placing excessive reliance on external vendors in providing business continuity management support, including the provision of the disaster recovery site and back-up equipment and facilities. A Payment Service Provider shall satisfy itself that each vendor has the capacity to provide the services when needed, and that the contractual responsibilities of the vendors, including the lead-time to provide necessary emergency services, types of support and capacity, are clearly specified.
         
      5. Where a Payment Service Provider is reliant on shared computing services provided by external providers, such as cloud computing, to support its disaster recovery, it shall manage the risk associated with these services.
         

      Reputation Risk Management

      1. A Payment Service Provider shall establish and implement an effective process for managing reputational risk that is appropriate for the size and complexity of its operations.
         
    • Article (14): Obligations Towards Retail Payment Service Users

      1. Payment Service Providers must be operated prudently and with competence in a manner that will not adversely affect the interests of the Retail Payment Service Users or potential Retail Payment Service Users. In addition, they must also observe and comply with the relevant regulatory requirements and standards on consumer protection of the Central Bank. For the avoidance of doubt, in case of discrepancies between this Regulation and the Central Bank’s requirements and standards on consumer protection, the respective provisions of this Regulation shall prevail.
         

      Safeguarding of Funds In-Transit

      1. At no time shall Payment Service Providers hold funds of Retail Payment Service Users unless these are funds in transit.
         
      2. Payment Service Providers that settle Payment Transactions within twenty four (24) hours shall segregate Retail Payment Service Users’ funds in the following ways:
         
        1. 3.1. funds shall not be commingled at any time with the funds of any Person other than the Retail Payment Service Users on whose behalf the funds are held; and/or
           
        2. 3.2. funds shall be insulated in the interest of the Retail Payment Service Users against the claims of other creditors of the Payment Service Provider, in particular in the event of insolvency.
           
      3. Payment Service Providers that settle Payment Transactions after twenty-four (24) hours shall segregate Retail Payment Service Users’ funds in the following ways:
         
        1. 4.1. open a separate escrow account with a Bank and restrict any operations and transactions on this account save for the transfer of the deposited Retail Payment Service Users’ funds to the end beneficiary; and/or
           
        2. 4.2. funds shall be covered by an insurance policy or by a bank guarantee from a regulated insurance company or Bank which does not belong to the same Group as the Payment Service Provider.
           
        3. 4.3. While Banks, acting as Retail Payment Service Provider, are not required to establish a separate escrow account, an insurance policy or a bank guarantee to safeguard Retail Payment Service Users’ funds, a separate bank account under the name of the concerned Retail Payment Service Users must be set up for protecting the funds.
           

      Transparency of Contractual Terms

      1. Payment Service Providers shall provide the terms and conditions governing their contractual relationship with:
         
        1. 5.1. each new Retail Payment Service User, sufficiently in advance of entering into the contractual relationship as to allow the Retail Payment Service User to make an informed decision; and
           
        2. 5.2. each existing Retail Payment Service User, at their request in writing and delivered as per the Retail Payment Service User’s preference, including through an e-mail, mobile application or any other electronic manner.
           
      2. The terms and conditions referred to in paragraph (5) shall be written in a clear, plain and understandable language, in a manner that is not misleading and shall be provided to the Retail Payment Service User in both Arabic and English, as may be requested by the Retail Payment Service User.
         
      3. Any changes to the terms and conditions referred to in paragraph (5) shall be communicated to the Retail Payment Service User by the Payment Service Provider sufficiently in advance and at least 30 calendar days prior to any such change becoming effective.
         
      4. A Retail Payment Service User shall be entitled to terminate its contractual relationship with a Payment Service Provider at no charge where it does not agree with the revised terms and conditions referred to in paragraph (7).
         

      Single Retail Payment Service Agreements

      1. For transactions that are to be concluded under a Single Retail Payment Service Agreement, Payment Service Providers shall provide Retail Payment Service Users with the following information before the entry into a contractual relationship:
         
        1. 9.1. schedule of fees, charges and commissions, including conversion rates and withdrawal charges, where applicable;
           
        2. 9.2. contact details of the Payment Service Provider, including legal name and registered address, including the address of the agent or branch, where applicable;
           
        3. 9.3. the form and procedure for giving consent to the initiation of a Payment Order or execution of a Payment Transaction and for the withdrawal of consent;
           
        4. 9.4. the communication channel between the Payment Service Provider and the Retail Payment Service User;
           
        5. 9.5. the manner in safeguarding of funds as per Article 14(3) and (4) and Reserve of Assets as per Article 11(9);
           
        6. 9.6. the manner and timeline for notification by the Retail Payment Service User to the Payment Service Provider in case of Unauthorized or incorrectly initiated or executed Payment Transaction;
           
        7. 9.7. information on Payment Service Provider’s and Retail Payment Service User’s liability for Unauthorized Payment Transactions;
           
        8. 9.8. the service level for the provision of the Retail Payment Service;
           
        9. 9.9. information on the Payment Service Provider’s complaint procedure; and
           
        10. 9.10. the Payment Service Provider’s procedure for reporting of Unauthorized Payment Transactions.
           
      2. The information required in paragraph (9) shall be provided immediately after the execution of the Payment Transaction where it is concluded at a Payment Service User’s request using a Means of Distance Communication which does not allow for the provision of such information before the entry into a contractual relationship.
         

      Framework Agreements

      1. For transactions that are concluded under a Framework Agreement, Payment Service Providers shall provide to Retail Payment Service Users the following information before the Retail Payment Service User consents to the entry into a Payment Transaction as well as at any other time the Retail Payment Service User requests this information, and within (5) Business Days of such request:
         
        1. 11.1. schedule of fees, charges and commissions, including conversion rates and withdrawal charges, where applicable;
           
        2. 11.2. contact details of the Payment Service Provider, including legal name and registered address, including address of the agent or branch, where applicable;
           
        3. 11.3. the form and procedure for giving consent to the initiation of a Payment Order or execution of a Payment Transaction and for the withdrawal of consent;
           
        4. 11.4. the communication channel between the Payment Service Provider and the Retail Payment Service User;
           
        5. 11.5. the manner in safeguarding of funds as per Article 14(3) and (4) and Reserve of Assets as per Article 11(9);
           
        6. 11.6. the manner and timeline for notification by the Retail Payment Service User to the Payment Service Provider in case of Unauthorized or incorrectly initiated or executed Payment Transaction;
           
        7. 11.7. information on Payment Service Provider’s and Retail Payment Service User’s liability for Unauthorized Payment Transactions;
           
        8. 11.8. information relating to terms under which a Payment Service User may be deemed to have accepted changes to the terms and conditions, the duration of the contract and the rights of the parties to terminate the Framework Agreement;
           
        9. 11.9. the service level for the execution of the Retail Payment Service;
           
        10. 11.10.information on the Payment Service Provider’s complaint procedure; and
           
        11. 11.11.the Payment Service Provider’s procedure for reporting of Unauthorized Payment Transactions.
           
      2. The information required in paragraph (11) shall be provided immediately after the execution of the Payment Transaction where it is concluded at a Payment Service User’s request using a Means of Distance Communication which does not allow for the provision of such information before the entry into a contractual relationship.
         
      3. Payment Service Providers shall provide Retail Payment Service Users with a written statement of the Payment Transactions under a Framework Agreement at least once per month free of charge, including details of the amounts, fees, charges and commissions, the dates and times of execution and the reference numbers for each Payment Transaction.
         

      Information Requirements

      1. Immediately after the receipt of an order for a Payment Transaction, the Payment Service Provider of the Payer shall provide a receipt for Retail Payment Service Users with:
         
        1. 14.1. confirmation of the successful or unsuccessful initiation and execution of the Payment Transaction;
           
        2. 14.2. acknowledgement and reference number to track the status of the Payment Transaction, including:
           
          1. 14.2.1. the date and amount of the Payment Transaction; and
             
          2. 14.2.2. information relating to the Payee;
             
        3. 14.3. the amount of the Payment Transaction, any related fees or charges, including the actual currency and conversion rates used, and withdrawal charges, where applicable; and
           
        4. 14.4. the date on which the Payment Service Provider received the Payment Order.
           
      2. The Payee’s Payment Service Provider shall, immediately after the execution of the Payment Transaction, provide to the Payee with a statement with the following information:
         
        1. 15.1. reference enabling the Payee to identify the Payment Transaction and, where appropriate, the Payer and any information transferred with the Payment Transaction;
           
        2. 15.2. the amount of the Payment Transaction in the currency in which the funds are to be dispersed disbursed to the Payee;
           
        3. 15.3. the amount of any fees or charges for the Payment Transaction payable by the Payee;
           
        4. 15.4. where applicable, the currency exchange rate used in the Payment Transaction by the Payee’s Payment Service Provider; and
           
        5. 15.5. the date on which the amount of a Payment Transaction is credited to a Payee’s Payment Account.
           
      3. The Payer’s Payment Service Provider shall ensure that Payment Orders are accompanied by the necessary information so that they can be processed accurately and completely, and also, be easily identified, verified, reviewed, audited and for any subsequent investigation if needed.
         
      4. The Payee’s Payment Service Provider shall implement procedures to detect when any necessary information is missing or inaccurate for a Payment Transaction.
         

      Protection of Payment and Personal Data

      1. Payment Service Providers shall have in place and maintain adequate policies and procedures to protect:
         
        1. 18.1. Payment Data and identify, prevent and resolve any data security breaches; and
           
        2. 18.2. Personal Data.
           
      2. Payment Service Providers may disclose Payment and Personal Data to:
         
        1. 19.1. a third party where the disclosure is made with the prior written consent of the Retail Payment Service User or is required pursuant to applicable laws;
           
        2. 19.2. to the Central Bank;
           
        3. 19.3. other regulatory authorities upon request/following prior approval of the Central Bank;
           
        4. 19.4. a court of law; and
           
        5. 19.5. other government bodies who have lawfully authorized rights of access.
           
      3. In addition to the envisaged in paragraph (19), Payment Service Providers may also disclose Personal Data to its corresponding Data Subject.
         
      4. Payment Service Providers shall have in place and maintain Payment and Personal Data protection controls.
         
      5. Personal and Payment Data shall be stored and maintained in the State. Payment Service Providers must also establish a safe and secure backup of all Personal and Payment Data in a separate location for the required period of retention of (5) years.
         
      6. Payment Service Providers shall comply with applicable regulatory requirements and standards on data protection. They shall control, process and retain only Personal Data that is necessary for the provision of Retail Payment Services and upon obtaining the explicit consent of the Retail Payment Service User.
         

      Liability for Unauthorized Payment Transactions and Refunds

      1. Payment Service Providers shall be fully liable for any fraudulent or Unauthorized Payment Transaction, whether before or after the Payer informs the Payment Service Provider of any potential or suspected fraud, except where there is evidence that:
         
        1. 24.1. the Payer acts fraudulently; or
           
        2. 24.2. the Payer acted with gross negligence and did not take reasonable steps to keep its personalized security credentials safe.
           

      Refunds

      1. The Payment Service Provider shall refund the amount of the Unauthorized Payment Transaction to the Payer and, where applicable, restore the debited Payment Account to the state it would have been in had the Unauthorized Payment Transaction not taken place.
         
      2. The Payment Service Provider shall provide a refund under paragraph (25) as soon as practicable and in any event no later than the end of the Business Day following the day on which it becomes aware of the Unauthorized Payment Transaction.
         
      3. Paragraphs (25), (26) and (30) do not apply where the Payment Service Provider has reasonable grounds to suspect fraudulent behavior by the Retail Payment Service User and notifies the Central Bank of those grounds in writing.
         
      4. When crediting a Payment Account under paragraph (30), a Payment Service Provider shall ensure that the date on which the amount of a Payment Transaction is credited to a Payee’s Payment Account is no later than the date on which the amount of the Unauthorized Payment Transaction was debited.
         
      5. Where an Unauthorized Payment Transaction was initiated through a Payment Initiation Service Provider, the Payment Service Provider providing Payment Account Issuance Services shall comply with paragraph (30). In addition, if the Payment Initiation Service Provider is liable for the Unauthorized Payment Transaction, it shall, on the request of the Payment Service Provider providing Payment Account Issuing Services, compensate the Payment Service Provider providing Payment Account Issuing Services immediately for the losses incurred or sums paid as a result of complying with paragraph (30), including the amount of the Unauthorized Payment Transaction.
         
      6. Other than in relation to the circumstances contemplated in paragraphs (25) to (29), on conclusion of an investigation by a Payment Service Provider into an error or Complaint, a Payment Service Provider shall pay any refund or monetary compensation due to a customer within (7) calendar days of such conclusion or instruction. In case of a delay in payment of any refund or compensation, the Payment Service Provider shall update the customer with the expected time for crediting the amount due, along with a justification for the delay.
         
    • Article (15): Use of Agents and Branches

      1. Where a Payment Service Provider intends to provide Retail Payment Services through an Agent or branch, it must conduct an assessment of such arrangement and provide a report on an annual basis to the Central Bank of the following:
         
        1. 1.1. name and address of the Agent or branch;
           
        2. 1.2. assessment of the adequacy of the internal control mechanisms that will be used by the Agent in order to comply with AML/CTF requirements;
           
        3. 1.3. assessment of the Persons responsible for the Management of the Agent or branch, and evidence that they fulfil the fit and proper requirements specified by the Central Bank; and
           
        4. 1.4. the scope of Retail Payment Services for which the Agent or branch is mandated.
           
      2. Payment Service Providers shall contractually ensure that Agents acting on their behalf disclose this fact to the Retail Payment Service Users.
         
      3. Payment Service Providers shall immediately notify the Central Bank of any change regarding the use of Agents or branches.
         
    • Article (16): Outsourcing

      1. Payment Service Providers outsourcing services and processes to service providers, Agents or Group entities shall be obliged to contractually ensure that such third parties comply with the requirements of this Regulation, Level 2 Acts and other relevant laws.
         
      2. The outsourcing under paragraph (1) shall be subject to the prior approval of the Central Bank. Furthermore, Payment Service Providers shall provide details on all outsourcing under paragraph (1) in a report on an annual basis to the Central Bank.
         
      3. Payment Service Providers shall remain fully liable for any acts of any Agent, branch or service provider to which a Retail Payment Service has been outsourced.
         
      4. Payment Service Providers shall be responsible for ensuring and maintaining appropriate training and qualifications of their Agents.
         
    • Article (17): Contractual Arrangements

      Access to Payment Accounts

      1. Payment Service Providers providing Payment Account Issuance Services and/or Banks may agree to contract with Payment Service Providers providing Payment Initiation and Payment Account Information Services for the provision of access, direct or indirect, to the Payment Accounts held with them in order to allow such Payment Service Providers to provide Payment Initiation and Payment Account Information Services in an unhindered and efficient manner.
         
      2. The contractual arrangements under paragraph (1) shall:
         
        1. 2.1. have a sound legal basis and be legally enforceable;
           
        2. 2.2. clearly describe the rights and obligations of the counterparties;
           
        3. 2.3. clearly define the allocation of liability between the counterparties, including in cases of fraud, unauthorized access or Data Breach, in a manner that each counterparty takes responsibility for the respective parts of the Payment Transaction under its control;
           
        4. 2.4. specify the reasons for denying access to Payment Accounts related to unauthorized or fraudulent access by Payment Service Providers providing Payment Initiation and Payment Account Information Services; and
           
        5. 2.5. explicitly oblige the counterparties to comply with Article (13) on Technology Risk and Information Security.
           
      3. The choice of Payment Service Providers providing Payment Initiation and Payment Account Information Services shall be at the sole discretion of the Payment Service Providers providing Payment Account Issuance Services and/or Banks.
         
      4. Payment Service Providers providing Payment Initiation and Payment Account Information Services shall:
         
        1. 4.1. provide services only where based on the Retail Payment Service User’s explicit consent;
           
        2. 4.2. ensure that the personalized security credentials of the Retail Payment Service User are not, with the exception of the Retail Payment Service User and the issuer of the personalized security credentials, accessible to other parties and that they are transmitted through safe and efficient channels;
           
        3. 4.3. not request or store Sensitive Payment Data of the Retail Payment Service User;
           
        4. 4.4. not use, access or store any data for purposes other than for the provision of the Payment Initiation or Payment Account Information Services, as explicitly requested by the Retail Payment Service User; and
           
        5. 4.5. comply with the requirements of Article (13) on Technology Risk and Information Security where the Payer initiates an electronic Payment Transaction or carries out any action through a remote channel which may imply a risk of payment fraud or other abuses.
           
      5. In addition to the requirements set out in paragraph (4), Payment Service Providers providing Payment Account Information Services shall access only the information from designated Payment Accounts and associated Payment Transactions.
         
      6. In addition to the requirements set out in paragraph (4), Payment Service Providers providing Payment Initiation Services shall not modify the amount, the Payee or any other feature of the Payment Transaction.
         
    • Article (18): Card Schemes

      Card Scheme License

      1. Card Schemes operating within the State shall obtain a License by the Central Bank prior to commencing operations.
         
      2. Applicants shall be subject to the procedure envisaged in the Central Bank’s Licensing Guidelines.
         
      3. The Central Bank shall determine whether to grant or refuse to grant a License to a Card Scheme Applicant and indicate this in writing to the Applicant within (90) calendar days from the receipt of the full set of documents and information requested under the Application.
         
      4. The Central Bank may grant a License under paragraph (1) with or without conditions or restrictions attached to it, or refuse to grant a License at its discretion.
         
      5. The Central Bank shall notify the Card Scheme of the decision taken under paragraph (3). In case of a refusal to grant a License, the Central Bank shall indicate the reasons for such refusal.
         
      6. The Central Bank reserves the sole right to issue Card Issuer (Bank) Identification Numbers (BIN) in accordance with ISO/IEC 7812, as may be amended or supplemented from time to time.
         

      License Conditions

      1. The Central Bank shall grant a License to a Card Scheme under this Article (18) upon the fulfilment of the following conditions:
         
        1. 7.1. the Central Bank has been provided with all necessary documents and information as it may request, in the form and within the timeframe specified by it, to allow it to assess the adequacy, efficiency and soundness of a Card Scheme, including:
           
          1. 7.1.1. the business model and business strategy;
             
          2. 7.1.2. the corporate governance structure;
             
          3. 7.1.3. the Management contact details;
             
          4. 7.1.4. the ownership and Group structure;
             
          5. 7.1.5. the financial and operational resources; and
             
          6. 7.1.6. the description of key risks, including conduct of business and money laundering and terrorist financing risks;
             
        2. 7.2. the Management of the Card Scheme fulfil the fit and proper requirements specified by the Central Bank, including that each member of Management:
           
          1. 7.2.1. possesses the necessary knowledge, skills, and experience;
             
          2. 7.2.2. has a record of integrity and good repute;
             
          3. 7.2.3. has sufficient time to fully discharge the responsibilities under this Regulation and Level 2 Acts; and
             
          4. 7.2.4. has a record of financial soundness.
             

      Reporting Requirements

      1. A Card Scheme that has been granted a License shall:
         
        1. 8.1. report to the Central Bank the information contained in Annex III on a quarterly basis;
           
        2. 8.2. provide additional information or become subject to more frequent reporting, as deemed necessary by the Central Bank; and
           
        3. 8.3. report immediately any changes that affect or are likely to affect its business model or financial viability, or which may otherwise be deemed to be material in nature such as significant increase or decrease in transaction volumes.
           

      Ongoing Requirements

      Governance

      1. The Board and Management of a Card Scheme shall be responsible for ensuring that a licensed Card Scheme has an internal control framework that is adequate to establish a properly controlled operating environment for the conduct of its business, taking into account its risk profile.
         
      2. Management shall be responsible for developing an internal control framework that identifies, measures, monitors and controls all risks faced by the Card Scheme.
         
      3. Licensed Card Schemes shall have organizational structures that incorporate a “three lines of defense” approach comprising the business lines, the support and control functions and an independent internal audit function.
         

      Compliance Function

      1. The Board shall be responsible for ensuring that a Card Scheme has an independent, permanent and effective compliance function to monitor and report on observance of all applicable laws, regulations and standards and on adherence by staff and members of the Board to legal requirements, proper codes of conduct and policy on conflicts of interest.
         
      2. The Card Payment Scheme shall have a Boardapproved compliance policy that is communicated to all staff specifying the purpose, standing and authority of the compliance function within the Card Scheme.
         
      3. Card Schemes shall establish appropriate policies, procedures and controls pertaining to the internal reporting by their Management and staff of suspicious transactions, including the provision of the necessary records and data, to the designated Anti-Money Laundering and Combating the Financing of Terrorism compliance officer for further analysis and reporting decisions. Card Schemes shall report transactions to the competent authority when there are suspicions, or reasonable grounds to suspect, that the proceeds are related to a crime, or to the attempt or intention to use funds or proceeds for the purpose of committing, concealing or benefitting from a crime.
         

      Internal Audit Function

      1. The Board shall be responsible for ensuring that the Card Scheme has an independent, permanent and effective internal audit function commensurate with the size, nature of operations and complexity of its organization.
         
      2. The internal audit function shall provide independent assurance to the Board and Management on the quality and effectiveness of the Card Scheme’s internal controls, risk management, compliance, corporate governance, and the systems and processes created by the business units, support and control functions.
         
      3. The Card Scheme shall have an internal audit charter approved by the Board audit committee that articulates the purpose, standing and authority of the internal audit function within the Card Scheme.
         

      Risk Management

      1. Card Schemes shall have an adequately resourced risk management function headed by a chief risk officer or equivalent. The function shall be independent of the management and decision-making of the Card Scheme’s risktaking functions. The risk management function shall include policies, procedures, systems and controls for monitoring and reporting risks, and to ensure that risk exposures are aligned with the entity’s strategy and business plan.
         

      Risk Strategy

      1. Card Schemes shall have a clearly defined business strategy, risk appetite and defined corporate culture that has been approved by the Board and reviewed at least annually. Management shall ensure full compliance of this articulated strategy across all business lines and the Board will be ultimately responsible for such compliance.
         

      Information Security

      1. A Card Scheme shall apply and meet at a minimum the Payment Card Industry Data Security Standard (‘PCI DSS’) and UAE Information Assurance Standards, as may be amended from time to time.
         
      2. A compliance report regarding the Card Scheme’s adherence to the standards referred to in paragraph (20) shall be presented to the Board at least annually as well as transmitted to the Central Bank.
         
      3. In the case of a Data Breach, the Card Scheme shall notify the Central Bank without undue delay and not later than (72) hours after having become aware of such Data Breach.
         

      Disaster Recovery and Business Continuity Management

      1. Card Schemes shall have disaster recovery and business continuity plans in place to ensure their ability to operate on an ongoing basis and limit losses in the event of a severe business disruption. Such plans must be commensurate with the risk profile, nature, size and complexity of the Card Scheme’s business and structure and take into account different scenarios to which the Card Scheme may be vulnerable.
         
      2. Disaster recovery and business continuity plans shall ensure that critical business functions of the Card Scheme can be maintained and recovered in a timely manner to minimize the financial, legal, regulatory, reputational and other risks that may arise from a disruption.
         
      3. The Board shall ensure there is a periodic independent review of the Card Scheme’s disaster recovery and business continuity plans to ensure adequacy and consistency with current operations, risks and threats, recovery levels and priorities.
         

      Risk Assessment

      1. Card Schemes shall regularly assess risks through the identification of new risks, measurement of known risks and prioritization of risks through thorough understanding of the business and the market.
         

      Risk Mitigation

      1. Card Schemes shall mitigate risks through the implementation of:
         
        1. 27.1. risk mitigation programs and technologies;
           
        2. 27.2. the effective management of risk principles; operation with risk management in mind; and
           
        3. 27.3. outsourcing of risk functions that cannot be performed in-house.
           

      Monitoring

      1. Card Schemes shall perform regular monitoring of all risks and mitigation programs on at least an annual basis to ensure the robustness of the risk management procedures and programs. Continuous monitoring reports, including dashboards, shall be presented to the Management and the Board to ensure that all levels of management are aware of the current risk situation, including potential fraud, in the Card Scheme.
         

      Assurance

      1. Card Schemes shall give assurance to all stakeholders through external and internal audits.
         

      Winding Down

      1. Where a Card Scheme intends to terminate its operation in the State, it shall obtain an approval from the Central Bank to this effect.
         
      2. A Card Scheme shall notify the Central Bank in advance of (3) months from the intended termination of its operations, and provide an orderly wind-down plan.
         

      Supervisory Examinations

      1. The Central Bank may conduct periodic examinations of the operation of Card Schemes to ensure their financial soundness and compliance with the requirements of this Regulation and Level 2 Acts.
         
      2. Card Schemes shall provide the Central Bank with full and unrestricted access to their accounts, records and documents, and shall supply such information and facilities as may be required to conduct the examination referred to in paragraph (32).
         

      Fees and Charges

      1. The Central Bank has the right to receive information on any fees and charges of Card Schemes and regulate such fees and charges as it considers appropriate.
         
      2. The Central Bank may publicly disclose the fees and charges of Card Schemes referred to in paragraph (34).
         
    • Article (19): Access to the Wages Protection System

      Eligibility and Conditions

      1. Payment Service Providers are eligible to apply to the Central Bank to participate in and, be given access to the Wages Protection System. They shall be given access to the Wages Protection System subject to an approval granted by the Central Bank.
         
      2. To allow wages to be credited to an account that can store and maintain the funds, Payment Service Providers may engage with an SVF scheme or a Bank for the provision of such account. Payment Service Providers that apply for participation in and access to the Wages Protection System shall demonstrate, among other things, that they have stringent security measures put in place so as to minimize the risks to the Wages Protection System.
         
      3. Upon being given access to the Wages Protection System, Payment Service Providers shall be entitled to open WPS Payment Accounts.
         
      4. The requirements in this Article (19) are without prejudice to other requirements of this Regulation to which Payment Service Providers are subject.
         

      Obligations

      1. Payment Service Providers that have been given access to the Wages Protection System under paragraph (1) shall:
         
        1. 5.1. organize marketing campaigns targeting the unbanked and underbanked segments with the objective of educating WPS Payment Account Holders on the benefits and risks associated with the services provided by the Payment Service Providers;
           
        2. 5.2. conduct workshops with the objective of raising awareness of Employers on the salary information file (SIF) format to be submitted, penalties and related procedures and regulatory requirements;
           
        3. 5.3. ensure that they provide WPS Payment Account Holders with a transaction statement in a timely manner;
           
        4. 5.4. execute the payments to WPS Payment Account Holders in a timely manner and acknowledge such execution in accordance with the WPS Rulebook;
           
        5. 5.5. not hold WPS Payment Account Holders liable for any fraudulent or Unauthorized Payment Transactions, and shall guarantee the full amount of funds; and
           
        6. 5.6. provide a dedicated Retail Payment Service User service and complaints team for WPS Payment Account Holders that are separate from the equivalent teams servicing other Retail Payment Services that may be provided by the Payment Service Providers.
           
      2. Payment Service Providers that fail to comply with the requirements of paragraph (5.4) shall be subject to the penalties specified in the WPS Rulebook.
         
      3. The Central Bank may request from the Payment Service Providers that have been given access to the Wages Protection System under paragraph (1) to:
         
        1. 7.1. prepare and provide quarterly reports on the average Payment Transactions value per WPS Payment Account Holder; and
           
        2. 7.2. prepare and provide quarterly reports on the number of WPS Payment Account Holders being serviced.
           
    • Article (20): Enforcement and Sanctions

      Violation of any provision of this Regulation or committing any of the violations provided for under the Central Bank Law may subject the Payment Service Provider or Card Scheme to administrative and financial sanctions and penalties as deemed appropriate by the Central Bank.

    • Article (21): Transition Period

      A one-year transitional period will commence on the date this Regulation comes into force. The Central Bank may order the cessation of provision of the Retail Payment Services or the operations of the Card Scheme if the Payment Service Provider or the Card Scheme concerned has not obtained the relevant License from the Central Bank before the end of the transition period. The Central Bank may extend the transition period for the Applicant at its own discretion.

    • Article (22): Interpretation of Regulation

      The Regulatory Development Division of the Central Bank shall be the reference for interpretation of the provisions of this Regulation.

    • Article (23): Publication & Application

      1. This Regulation shall be published in the Official Gazette in both Arabic and English and shall come into effect one month from the date of publication. In case of any discrepancy between the Arabic and the English, the Arabic version will prevail.

    • Annex I: Retail Payment Services

      1. Payment Account Issuance Service
         
      2. Payment Instrument Issuance Service
         
      3. Merchant Acquiring Service
         
      4. Payment Aggregation Service
         
      5. Domestic Fund Transfer Service
         
      6. Cross-border Fund Transfer Service
         
      7. Payment Token Service
         
      8. Payment Initiation Service
         
      9. Payment Account Information Service
         
    • Annex II: Guidance on the Best Practices for Technology Risk and Information Security

      The following best practices will enable Payment Service Providers to operate adaptive and responsive cyber resilience processes. Payment Service Providers are encouraged to discuss and consider their application to improve their technology risk, information security and cyber resilience preparedness.

      Technology Risk

      An incident management framework with sufficient management oversight to ensure effective incident response and management capability to deal with significant incidents properly should include:

      1. (i) timely reporting to the Central Bank of any confirmed technology-related fraud cases or major security breaches, including cyberattacks, cases of prolonged disruption of service and systemic incidents where Retail Payment Service Users suffer from monetary loss or Retail Payment Service Users’ interests are being affected (e.g. data leakage); and
         
      2. (ii) a communication strategy to address the concerns any stakeholders may have arising from the incidents and restore the reputational damage that the incidents may cause.
         

      Change Management

      Payment Service Providers whose monthly average value of Payment Transactions amounts to (10) million Dirham or above are encouraged to:

      1. (i) develop a formal change management process to ensure the integrity and reliability of the production environment and that the changes to application systems, system software (e.g. operating systems and utilities), hardware, network systems and other IT facilities and equipment, are proper and do not have any undesirable impact on the production environment. Formal procedures for managing emergency changes (including the record keeping and endorsement arrangement) should also be established to enable unforeseen problems to be addressed in a timely and controlled manner; and
         
      2. (ii) adequately and accurately document control procedures and baseline security requirements, including all configurations and settings of operating systems, system software, databases, servers and network devices. They are also expected to perform periodic reviews on the compliance of the security settings with the baseline standards.
         

      Project Life Cycle

      A full project life cycle methodology governing the process of developing, implementing and maintaining major computer should be established.

      Where a software package is acquired from vendors, a formal software package acquisition process should be established to manage risks associated with acquisitions, such as breach of software license agreement or patent infringement.

      Quality assurance reviews of major technology-related projects by an independent party, with the assistance of the legal and compliance functions should be conducted.

      IT Governance

      A set of IT control policies that fits the business model and technology applications should be implemented. The IT control policies which establish the ground rules for IT controls should be formally approved by Management and properly implemented among IT functions and business units. Processes used to verify compliance with IT control policies and the process for seeking appropriate approval by Management for dispensation from IT control policies are also be clearly specified, and consequences associated with any failure to adhere to these processes should be effected.

      Security Requirements

      Guidelines and standards for software development are adopted with reference to industry generally accepted practices on secure development. Source code reviews (e.g. peer review and automated analysis review), which could be risk-based, as part of a software quality assurance process should be conducted.

      Formal testing and acceptance processes should be conducted to ensure that only properly tested and approved systems are promoted to the production environment. The scope of tests covers business logic, security controls and system performance under various stress-load scenarios and recovery conditions.

      Segregated environments for development, testing and production purposes should be maintained. System testing and user acceptance testing (UAT) should be properly carried out in the testing environment. Production data should not be used in development or acceptance testing unless the data has been desensitized and prior approval from the information owner has been obtained.

      A segregation of duties among IT teams should be introduced. Developers should not be permitted to access to production libraries and promote programming code into the production environment. If automated tools are used for the promotion of programming code, adequate monitoring, reviews and checks by independent teams should be done. Vendor accesses to the UAT environment, if necessary, should be closely monitored.

      An inventory of end-user developed applications and where necessary, control practices and responsibilities with respect to end-user computing to cover areas such as ownership, development standards, data security, documentation, data/file storage and backup, system recovery, audit responsibilities and training should be established.

      A problem management process to identify, classify, prioritize and address all IT problems in a timely manner should be established. It should perform a trend analysis of past incidents regularly to facilitate the identification and prevention of similar problems.

      Network and Infrastructure Management

      Network security devices such as firewalls at critical junctures of its IT infrastructure should be installed to secure the connection to untrusted external networks, such as the Internet and connections with third parties.

      Where mobile devices are provided to employees, policies and procedures covering, among others, requisition, authentication, hardening, encryption, data backup and retention should be established.

      Adequate measures to maintain appropriate segregation of databases for different purposes to prevent unauthorized or unintended access or retrieval and robust access controls should be enforced to ensure the confidentiality and integrity of the databases. In respect of any Personal Data of Retail Payment Service Users, including Merchants, the relevant data protection laws as well as any relevant codes of practice, guidelines or best practice issued by the Central Bank or any other relevant authorities should be assessed from time to time.

      Access to the information and application systems should be restricted by an adequate authentication mechanism associated with access control rules. A role-based access control framework should be adopted and access rights should be granted on a need-to-have basis.

      Cyber Security Risk

      The trends in cyber threats should be considered, including subscribing to quality cyber threat intelligence services, which are relevant to the provision of Retail Payment Services to enhance ability to precisely respond to new type of threats in a timely manner. The Payment Service Provider may also seek opportunities to collaborate with other organizations to share and gather cyber threat intelligence with the aim of facilitating the Retail Payment Services industry to better prepare and manage cyber security risks.

      Monitoring or surveillance systems to ensure being alerted to any suspicious or malicious system activities such as multiple sessions of same account from different geographic locations should be carried out. Real-time monitoring of cyber events for critical systems should be performed to facilitate the prompt detection of anomalous activities.

      Close attention should be paid to evolving risks related to accessing critical IT infrastructure and appropriate measures are accordingly taken.

      Payment Acceptance Devices

      Retail Payment Service User devices should be assumed to be exposed to security vulnerabilities and appropriate measures when designing, developing and maintaining Retail Payment Services should be taken. Security measures to guard against different compromising situations, including unauthorized device access, malware or virus attack, compromised or unsecure status of mobile device and unauthorized mobile applications should be taken.

      Where Merchants use mobile devices to accept a Payment Service Provider’s Retail Payment Services, additional security measures should be implemented to safeguard the mobile payment acceptance solution, including the detection of abnormal activities and logging them in reports, and the provision of Merchant identification for Retail Payment Service Users to validate identity.

      Retail Payment Service User Authentication

      Retail Payment Service User authentication based on a multi-factor authentication by combining any two or more of the following three factors is adopted:

      1. (i) verification information specified by Retail Payment Service User knows (e.g. user IDs and passwords);
         
      2. (ii) verification information a Retail Payment Service User has provided or possesses (e.g. one-time passwords generated by a security token or a Payment Service Provider’s security systems); and
         
      3. (iii) physical verification information belonging to a Retail Payment Service User (e.g. retina, fingerprint or voice recognition).
         

      If a password (including a personal identification number) is used as one factor of authentication, adequate controls related to the strength of the password (e.g. minimum password length) should be put in place.

      Login attempts and session management

      Robust log files allowing retrieval of historical data including a full audit trail of additions, modifications or deletions of transactions are provided. Access to such tools, including privileged responsibilities, should only be available to authorized personnel and is appropriately logged.

      Retail Payment Service Users should be provided with channels to check their Past Payment Transactions.

      Fraud Detection Systems

      Payment Transaction monitoring mechanisms designed to prevent, detect and block fraudulent Payment Transactions should be operated by Payment Service Providers providing Payment Token Services and Payment Service Providers whose monthly average value of Payment Transactions amounts to ten (10) million Dirhams or above. Suspicious or high-risk transactions are subject to a specific screening, filtration and evaluation procedure.

    • Annex III: Information to be Reported by Card Schemes in English and Arabic

      I. ATM data:

      Field NameMax SizeTypeField Details
      Primary Account Number (PAN)16-19NumericPAN is a series of digits used to identify a Retail Payment Service User account or relationship
      Transaction Code2NumericTransaction Code - 31 (Balance Enquiry), 01 (Cash Withdrawal).
      Transaction Amount12NumericTransaction amount gives the value of the funds requested by the cardholder in the local currency of the acquirer or source location of the transaction.
      Transaction Currency Code3Alphabet (or) NumericIdentifies the local currency of the acquirer or source location of the transaction. See ISO 4217.
      Transmission Date and Time10NumericMM/DD/hh/mm/ss format
      The date used is the current calendar day in Greenwich Mean Time (GMT) that the transaction occurred (not Business Day)
      Systems Trace Audit Number6NumericContains a number assigned by the transaction acquirer to identify uniquely a transaction. The trace number remains unchanged for all messages throughout the life of the transaction.
      Merchant’s Type4NumericContains the classification of the merchant's type (ATM/web/etc) of business product or service.
      Acquiring Institution Country Code3NumericContains the code of the country where the acquiring institution is located (see ISO 3166)
      Point of Service Entry Mode3NumericContains two numeric to indicate the method by which the primary account number was entered into the system and one numeric to indicate the PIN entry capabilities.
      Acquiring Institution Identification Component11NumericContains a code identifying the acquiring institution (e.g. merchant bank) or its agent.
      Card Acceptor Name/Location40Alpha Numeric Special CharContains the name and location of the card acceptor (i.e. the merchant or ATM).
      Card Acceptor Terminal Identification15Alpha Numeric Special CharContains a unique code identifying a terminal at the card acceptor location.
      Authorization Identification Response6Alpha NumericContains the response identification assigned by the authorizing institution.
      This field is often referred to as "auth-code".
      Response Code2Alpha NumericContains a code, which defines the disposition of a message.


       

      II. PoS data:

      Field NameMax SizeTypeField Details
      Primary Account Number (PAN)16-19NumericPAN is a series of digits used to identify a Retail Payment Service User account or relationship
      Transaction Code2NumericTransaction Code - 00 (Purchase/Sale), 20 (Refund), 31 (Balance Enquiry).
      Transaction Amount12NumericAmount of funds requested by the cardholder.
      Transaction Currency Code3NumericCode that indicates the local currency of the acquirer or source location of the transaction. This defines the currency that applies to the transaction amount.
      Transmission Date and Time10NumericMMDDhhmmss format
      Generated and sent by the message initiator. It is expressed in GMT.
      Systems Trace Audit Number6NumericUnique identifier assigned to the transaction by the message sender. It remains unchanged for all messages within a transaction between the two parties. This is used to provide an audit trail for every message sent by the acquirer for a given business date.
      Merchant Category Code4NumericContains the classification of the merchant's type of business product or service.
      Acquiring Institution Country Code3NumericContains the code of the country where the acquiring institution is located (see ISO 3166)
      Point of Service Entry Mode3NumericContains two numeric to indicate the method by which the primary account number was entered into the system and one numeric to indicate the PIN entry capabilities.
      POS Condition Code2NumericContains an identification of the condition under which the transaction takes place at the point of service.
      00 - Normal Presentment
      59 - eCommerce
      Authorization Identification Response6Alpha NumericContains the response identification assigned by the authorizing institution.
      This field is often referred to as "auth-code".
      Card Acceptor Terminal ID16Alpha Numeric Special CharUnique code identifying the terminals at the acquirer location
      Card Acceptor Identification Code15Alpha Numeric Special CharUnique code identifying the card acceptor
      Card Acceptor Name and Location40Alpha Numeric Special CharUsed to hold the name and location of the card acceptor as known to the cardholder.
      Response Code2Alpha NumericContains a code, which defines the disposition of a message.


       

      III. Fraud data:

      Field NameMax SizeTypeField Details
      Primary Account Number (PAN)16-19NumericPAN is a series of digits used to identify a Retail Payment Service User account or relationship
      Transaction Code2NumericTransaction Code - 00 (Purchase/Sale), 20 (Refund), 31 (Balance Enquiry).
      Transaction Amount12NumericAmount of funds requested by the cardholder.
      Transaction Currency Code3NumericCode that indicates the local currency of the acquirer or source location of the transaction. This defines the currency that applies to the transaction amount.
      Transmission Date and Time10NumericMMDDhhmmss format
      Generated and sent by the message initiator. It is expressed in GMT.
      Systems Trace Audit Number6NumericUnique identifier assigned to the transaction by the message sender. It remains unchanged for all messages within a transaction between the two parties. This is used to provide an audit trail for every message sent by the acquirer for a given business date.
      Merchant Category Code4NumericContains the classification of the merchant's type of business product or service.
      Acquiring Institution Country Code3NumericContains the code of the country where the acquiring institution is located (see ISO 3166)
      Point of Service Entry Mode3NumericContains two numeric to indicate the method by which the primary account number was entered into the system and one numeric to indicate the PIN entry capabilities.
      POS Condition Code2NumericContains an identification of the condition under which the transaction takes place at the point of service.
      00 - Normal Presentment
      59 - eCommerce
      Authorization Identification Response6Alpha NumericContains the response identification assigned by the authorizing institution.
      This field is often referred to as "auth-code".
      Card Acceptor Terminal ID16Alpha Numeric Special CharUnique code identifying the terminals at the acquirer location
      Card Acceptor Identification Code15Alpha Numeric Special CharUnique code identifying the card acceptor
      Card Acceptor Name and Location40Alpha Numeric Special CharUsed to hold the name and location of the card acceptor as known to the cardholder.
      Response Code2Alpha NumericContains a code, which defines the disposition of a message.