PAYMENTS AND CASH OPERATIONS POLICY

Last updated: 01.07.2026

1. General Provisions

1.1. This Payments and Cash Operations Policy sets out the basic rules governing the acceptance of payments, the payment of funds, cash operations, verification of payment details, payment rejections, delays and returns in connection with Transactions for the purchase and sale of Crypto-assets through the OurExchangeClub platform.

1.2. This Policy applies to all Users who create a request for a Transaction to purchase or sell Crypto-assets through the ourexchange.club Website, make or receive payments in Armenian drams, or use bank, card, EasyWallet, EasyPay, cash or other payment methods available on the Website.

1.3. This Policy forms an integral part of the OurExchangeClub Terms of Use, Privacy Policy, KYC/AML/CFT and Sanctions Compliance Policy, Crypto-asset Risk Disclosure Statement and other policies published on the Website.

1.4. The settlement currency for Transactions conducted through OurExchangeClub is the dram of the Republic of Armenia. The Company accepts or makes payments in Armenian drams in connection with Transactions using methods currently available on the Website and approved by the Company.

1.5. In a purchase Transaction, the User pays Armenian drams, and the Company transfers the relevant Crypto-asset to the Crypto Wallet Address specified by the User after receiving and verifying the payment and completing the necessary compliance checks.

1.6. In a sale Transaction, the User transfers the Crypto-asset to the Crypto Wallet Address provided by the Company, and the Company pays Armenian drams using the method selected by the User or approved by the Company after receiving the Crypto-asset, obtaining blockchain confirmations and completing the payment details and compliance checks.

1.7. The presence of a method for making or receiving payments on the Website does not mean that it is available or applicable to all Users, Transactions, amounts or situations. The availability of each payment method may depend on the Transaction type, amount, User identification results, risk profile, limits, technical capabilities, partner availability, and legal and compliance requirements.

1.8. The Company has the right to determine the methods available for making or receiving payments for each Transaction, impose additional requirements, require confirmation of payment details, reject certain payment instruments or offer another available method in accordance with the Terms of Use, this Policy and applicable law.

1.9. Making a payment or receiving funds does not in itself constitute final confirmation or completion of a Transaction. Each payment is subject to checks concerning receipt, identification, payment, technical matters, compliance, AML/CFT, sanctions, anti-corruption and fraud prevention, and any other necessary checks.

1.10. At any stage, the Company may suspend, reject, decline to accept or move a payment or Transaction to the return stage on legal, compliance, payment, technical, security, fraud prevention, third-party payment, uncertain source or risk management grounds.

1.11. The User must provide all details relating to payments and the receipt of funds in an accurate, complete and up-to-date form, follow the payment instructions displayed on the Website, comply with the specified deadlines and refrain from using third parties’ payment instruments unless their use has been disclosed in advance, substantiated and accepted by the Company.

1.12. If the User does not understand the meaning of the payment method, payment purpose, bank or card details, EasyWallet, EasyPay, a cash operation or the return procedure, the User must not proceed with the Transaction and must first contact the Company for clarification.

2. Available Methods for Making and Receiving Payments

2.1. The methods available for making or receiving payments in connection with Transactions through OurExchangeClub are determined by the Company and displayed on the Website, depending on the Transaction type, amount, User status, identification results, risk profile and other applicable conditions.

2.2. In a purchase Transaction, the User may pay Armenian drams only using payment methods available on the Website for that Transaction and approved by the Company.

2.3. In a sale Transaction, the Company may pay the User Armenian drams only using a method for receiving payment that is available on the Website for that Transaction and is either selected by the User or approved by the Company.

2.4. The methods available on the Website for making or receiving payments may include:

a) bank transfer or payment through a bank account;

b) payment by bank card or payment to a card;

c) payment through EasyWallet or payment to EasyWallet;

d) payment through an EasyPay terminal;

e) cash payment or receipt of cash funds;

f) other methods currently available on the Website and approved by the Company.

2.5. The availability of a method for making or receiving payments may be restricted or changed, taking into account the Transaction type, amount, limits, User identification level, payment service provider requirements, partner organisation availability, technical capabilities, and legal, AML/CFT, sanctions, anti-corruption, fraud prevention or other compliance requirements.

2.6. The Company is not obliged to make all methods for making or receiving payments available to all Users or for all Transactions.

2.7. The Company has the right, at any time, to add, remove, temporarily suspend, restrict or change any method for making or receiving payments for technical, operational, legal, compliance, security, partner-related, risk management or other justified reasons.

2.8. If the method previously selected for making or receiving payment for a Transaction becomes unavailable, restricted or risky, the Company may offer another available method, suspend or cancel the Transaction, or move it to the return stage in accordance with the Terms of Use and this Policy.

2.9. The User must use only the method for making or receiving payment displayed or approved on the Website for that Transaction. A payment made using another method or a payment request submitted with different details may be refused, subjected to additional checks, returned or serve as grounds for suspending, rejecting or cancelling the Transaction.

2.10. Selecting a method for making or receiving payment does not release the User from the obligation to undergo identification, submit additional documents, substantiate the payment source, explain the origin of funds and comply with other compliance requirements.

2.11. The Company may require the User to confirm ownership or control of, or the right to lawfully use, their bank account, bank card, EasyWallet, payment instrument or details relating to a cash operation.

2.12. Displaying a method for making or receiving payments on the Website does not constitute final confirmation of a Transaction by the Company, a guarantee that a payment will be accepted or an obligation to pay funds immediately.

3. Settlements in Armenian Drams and Restrictions on the Use of Foreign Currency

3.1. The settlement currency for Transactions for the purchase and sale of Crypto-assets through OurExchangeClub is the dram of the Republic of Armenia.

3.2. In a purchase Transaction, the User must pay in Armenian drams using the payment method and details, and within the period, displayed on the Website for that Transaction and approved by the Company.

3.3. In a sale Transaction, the Company pays the User in Armenian drams using a method for receiving payment that is available on the Website for that Transaction and is either selected by the User or approved by the Company.

3.4. If a Crypto-asset’s value, an indicative market figure, an equivalent value or a calculation is presented on the Website or during a Transaction in another currency or on the basis of another source, it is provided solely for informational or calculation purposes and does not mean that the Company undertakes to accept or make payment in that currency.

3.5. The Company does not accept payments or pay funds in foreign currency in connection with Transactions unless expressly provided otherwise in terms published on the Website and effective in accordance with applicable law.

3.6. If the User makes a payment in foreign currency, in the wrong currency, for an incorrect amount or using a method not approved on the Website, the Company may decline to accept the payment, suspend the Transaction, request additional explanations or documents, return the payment or cancel the Transaction in accordance with this Policy and the Terms of Use.

3.7. If a payment made in foreign currency, in the wrong currency or using the wrong method is returned, all bank, payment, conversion, intermediary, third-party or other costs actually incurred may be deducted from the amount returned.

3.8. If a payment service provider, bank, card system or other third party converts currency or applies an exchange rate, commission, hold, restriction, rejection or other payment condition during a payment, the User bears the resulting exchange rate differences, commissions, costs, delays or other adverse consequences, unless they were caused intentionally by the Company or by a culpable act of the Company proven in accordance with law.

4. Bank Transfers and Bank Cards

4.1. In connection with Transactions through OurExchangeClub, the Company may accept or make payments in Armenian drams by bank transfer, payment through a bank account, payment by bank card or payment to a bank card, if that method is available on the Website and approved for the Transaction.

4.2. When paying by bank transfer or through a bank account, the User must make payment only to the bank account number displayed on the Website for that Transaction, for the correct amount, with the correct payment purpose and within the specified period.

4.3. When paying by bank card or receiving payment to a card, the User must use only a bank card that belongs to them or that they lawfully use, unless the use of a third party’s card has been disclosed in advance, substantiated and accepted by the Company.

4.4. The Company may require the User to confirm ownership or control of, or the right to lawfully use, a bank account or bank card by means of a bank statement, partial confirmation of card details, a payment document, a declaration or another permissible document.

4.5. The User must ensure that payment is made from the bank account or card of the same person in whose name the Transaction was created, unless the Company has accepted a different arrangement in advance.

4.6. A payment from a third party’s bank account or card, or a request for payment to a third party’s account or card, may be refused, subjected to additional checks, returned, suspended or serve as grounds for rejecting or cancelling the Transaction.

4.7. In the case of bank transfers or card payments, a Transaction may proceed only after the payment has actually been received and identified, complies with the Transaction terms and has undergone the necessary payment, technical, compliance, AML/CFT, sanctions, anti-corruption and fraud prevention checks.

4.8. Incorrect or incomplete information in the payment order, transfer purpose, amount, account number, card details or other payment details may result in payment delays, an inability to identify the payment, suspension, rejection or cancellation of the Transaction, or a return in connection with it.

4.9. If the User has made a payment to the wrong account number or card, for the wrong amount, with the wrong payment purpose or other incorrect details, the Company may attempt to assist in identifying or returning the payment only if this is technically possible, lawful and consistent with compliance and security requirements.

4.10. Restrictions, delays, rejections, technical failures, commissions or other conditions applied by banks, card systems, payment and settlement organisations, the ArCa system or other payment infrastructure may affect the acceptance, verification, recording or return of a payment.

4.11. All actual bank, card, payment and settlement, intermediary, conversion, return or third-party costs relating to a bank or card transaction may be charged to the User or deducted from the amount returned if they were incurred in processing that transaction or accepting, verifying, rejecting or returning the payment.

4.12. A delay, rejection, partial execution, technical failure, hold, refund, return or restriction affecting a bank transfer or card payment does not constitute a breach of the Company’s obligations if it results from an act, omission or technical system of a bank, card system, the ArCa system, a payment and settlement organisation or another third party.

4.13. If a bank transfer or card payment is considered suspicious, inconsistent, unusual, made by a third party, made using incorrect details, or does not comply with the Transaction terms, the Company may suspend the Transaction, request additional documents or explanations, reject the payment, cancel the Transaction or move it to the return stage.

4.14. If the User requests payment to a bank account or bank card, the User must ensure the accuracy and availability of the details provided and their right to use them lawfully. The User bears the risk of delays, returns or losses resulting from an incorrect account number, incorrect card details, a closed or restricted account, third-party details or another error.

4.15. The Company may retain data relating to bank transfers, bank cards, payment orders, payment evidence, bank or card checks, returns, rejections and related communications for accounting, tax, legal, compliance, security, dispute resolution and evidentiary purposes.

5. EasyWallet and EasyPay Payments

5.1. In connection with Transactions through OurExchangeClub, the Company may accept or make payments in Armenian drams through EasyWallet and accept payments through an EasyPay terminal if those methods are available on the Website and approved for the Transaction.

5.2. When making or receiving payment through EasyWallet, the User must provide accurate and complete details of an EasyWallet that belongs to them or that they lawfully use, unless the use of a third party’s EasyWallet has been disclosed in advance, substantiated and accepted by the Company.

5.3. When paying through an EasyPay terminal, the User must make payment only using the details displayed on the Website for that Transaction, for the correct amount, with the correct payment purpose and identifier, and within the specified period.

5.4. The User must retain the receipt, electronic confirmation, transaction ID, and payment time and amount details for a payment made through EasyWallet or EasyPay and, where necessary, provide them to the Company for payment identification, verification or evidentiary purposes.

5.5. The Company may require the User to confirm ownership or control of, or the right to lawfully use, an EasyWallet, an EasyPay payment or other payment details, or to confirm the payment source, by means of additional documents, receipts, statements, declarations or other permissible evidence.

5.6. A payment from a third party’s EasyWallet, a request for an EasyWallet payment in favour of a third party, a payment made by a third party through an EasyPay terminal or other undisclosed third-party involvement may be refused, subjected to additional checks, returned, suspended or serve as grounds for rejecting or cancelling the Transaction.

5.7. A payment made through EasyWallet or EasyPay may be deemed received only from the time it has actually been reflected in the Company’s relevant recordkeeping or payment system, has been matched to the Transaction, complies with the Transaction terms and has undergone the necessary payment, technical, compliance, AML/CFT, sanctions, anti-corruption and fraud prevention checks.

5.8. Incorrect or incomplete EasyWallet or EasyPay payment details, use of an incorrect identifier, payment of an incorrect amount, an incorrect payment purpose, a payment delay or another technical error may make it impossible to identify the payment or result in delay, suspension, rejection or cancellation of the Transaction, or a return in connection with it.

5.9. Failures, restrictions, delays, rejections, holds, unavailability or technical errors affecting EasyWallet, EasyPay, a payment service provider, a terminal, a technical system, an internet connection or another third party may affect the acceptance, verification or recording of a payment, the payment of funds or a return.

5.10. Technical failures, delays, rejections, holds, restrictions or conditions imposed by third parties in connection with EasyWallet or EasyPay do not constitute a breach of the Company’s obligations if they result from circumstances beyond the Company’s direct control.

5.11. All payment, intermediary, return, third-party or other costs actually incurred in connection with a payment, return, incorrect payment or payment identification involving EasyWallet or EasyPay may be charged to the User or deducted from the amount returned.

5.12. If a payment made through EasyWallet or EasyPay is considered suspicious, inconsistent, unusual, made by a third party, made using incorrect details, or does not comply with the Transaction terms, the Company may suspend the Transaction, request additional documents or explanations, reject the payment, cancel the Transaction or move it to the return stage.

5.13. The Company may retain data relating to EasyWallet, EasyPay, payment receipts, transaction IDs, payment evidence, returns, rejections, checks and related communications for accounting, tax, legal, compliance, security, dispute resolution and evidentiary purposes.

6. Cash Operations and the Partner Organisation

6.1. In connection with Transactions through OurExchangeClub, the acceptance, collection or disbursement of cash funds or related ancillary actions may be carried out by the Company or through a partner organisation engaged by the Company, to the extent permitted by law and in accordance with the procedure established by the Company.

6.2. The Company determines whether cash payment or receipt of cash funds is available for each Transaction, taking into account the Transaction type, amount, User identification results, risk profile, limits, partner organisation availability, technical capabilities, and legal and compliance requirements.

6.3. A cash operation may be carried out only if the cash method is available on the Website for that Transaction, has been approved by the Company and does not conflict with applicable law, limits, AML/CFT, sanctions, anti-corruption, fraud prevention or other compliance requirements.

6.4. In a purchase Transaction, a cash payment may be accepted only in accordance with the procedure, at the location, within the period, in the amount and on the terms approved on the Website for that Transaction.

6.5. In a sale Transaction, cash funds may be disbursed only after the Crypto-asset transferred by the User has actually been received at the Crypto Wallet Address provided by the Company, the necessary blockchain confirmations have been obtained, the payment, technical and compliance checks have been completed, and the Transaction has been confirmed for payment.

6.6. During a cash operation, the User must present an identity document and, where necessary, sign or confirm documents, receipts, formal records or electronic confirmations attesting to the payment, receipt, handover or acceptance of cash or the material terms of the Transaction.

6.7. A cash operation may be documented by a receipt, formal record, electronic record, signature, video recording, partner organisation’s report, payment document or other evidence permitted by law.

6.8. The partner organisation may carry out only actions permitted by applicable law, the agreement between the Company and the partner organisation, and the approved terms of the Transaction.

6.9. Conducting a cash operation through a partner organisation does not release the User from the obligations under the Terms of Use, this Policy, Website procedures and applicable law, including the obligations to undergo identification, submit additional documents, explain the purpose of the Transaction and substantiate the origin of funds or Crypto-assets.

6.10. The Company has the right to reject, suspend or cancel a cash operation if the User fails to provide the necessary documents, refuses to sign or confirm the necessary documents, the Transaction exceeds the established limits, the cash operation details are inconsistent or suspicious, there are legal, compliance, security, AML/CFT, sanctions, anti-corruption, fraud prevention or other risks, or the cash operation is currently unavailable.

6.11. The availability of a cash operation does not entitle the User to demand cash servicing for any amount, at any location, at any time or on any terms. The Company has the right to determine the locations, times, limits, prior approval procedure and other terms for cash operations.

6.12. Delays resulting from a partner organisation’s technical, operational, time, location, security or other restrictions relating to cash operations do not constitute a breach of the Company’s obligations if the Company has acted in good faith and within the limits permitted by law.

6.13. If a cash operation cannot be carried out for legal, technical, compliance, security, partner organisation availability or other reasons, the Company may offer another available method for making or receiving payment, suspend or cancel the Transaction, or move it to the return stage in accordance with the Terms of Use and this Policy.

6.14. The User agrees that personal, identification, Transaction and payment data necessary for conducting cash operations may be transferred to the partner organisation to the extent necessary for execution of the operation, identification, recordkeeping, security, compliance and evidentiary purposes.

6.15. Documents, receipts, formal records, signatures, video recordings, partner organisation reports, communications and other data relating to cash operations may be retained for accounting, tax, legal, compliance, security, dispute resolution and evidentiary purposes.

7. Accuracy of Payment Details, Third-Party Involvement and Incorrect Payments

7.1. Before making any payment or submitting details for receiving payment, the User must independently check that all payment details are accurate, complete and consistent with the terms of the Transaction.

7.2. Payment details may include, without limitation, the method for making or receiving payment, amount, payment purpose, Transaction identifier, bank account number, bank card details, EasyWallet details, EasyPay payment details, cash operation terms and other necessary information displayed on the Website.

7.3. The User must make payments or submit details for receiving payment only using payment instruments in their own name, under their control and lawfully used by them, unless third-party involvement has been disclosed in advance, substantiated and accepted by the Company.

7.4. Third-party involvement includes payment from another person’s bank account or card, payment from another person’s EasyWallet, payment by another person through an EasyPay terminal, a request for payment in favour of another person, and the undisclosed involvement of the economic beneficiary of the Transaction or the payment source.

7.5. The User must notify the Company in advance if a third party is involved in the Transaction in any way and provide documents or explanations substantiating the legal, economic and factual grounds for that third party’s involvement.

7.6. The Company may decline to accept or confirm, or subject to additional checks, any payment, request to receive payment or payment details if the attribution of the payer, recipient, Transaction beneficiary, payment source or payment instrument is unclear, inconsistent or does not match the User’s details.

7.7. If the User has made an incorrect payment, paid an incorrect amount, specified an incorrect payment purpose, used an incorrect identifier, provided incorrect details for receiving payment or made another payment error, the User must immediately notify the Company and provide all necessary details and documents evidencing the error.

7.8. An incorrect payment or incorrect payment details may be corrected only if correction is technically possible and lawful, there is a sufficient match to the Transaction, and correction does not conflict with compliance or security requirements or requirements concerning third parties’ rights.

7.9. If the User has underpaid, the Company may require payment of the difference, offer new Transaction terms, suspend or cancel the Transaction, taking into account its status, the exchange rate validity period and compliance requirements.

7.10. If the User has overpaid, the Company may return the excess amount, account for it under new Transaction terms or apply another reasonable solution in a manner that is permitted by law, technically possible and consistent with compliance requirements.

7.11. In the event of a duplicate payment, an unidentified payment, a payment to the wrong recipient or an unclear payment flow, the Company may extend the checks, request additional documents, temporarily refrain from executing the Transaction or return the amount in accordance with this Policy.

7.12. The User bears the risk of delays, returns, commissions, costs, non-execution of the Transaction or other adverse consequences resulting from the User’s use of payment details that are incorrect, incomplete, provided late, unconfirmed or relate to a third party, unless those consequences were caused intentionally by the Company or by a culpable act of the Company proven in accordance with law.

7.13. The Company may retain data relating to incorrect payments, unidentified payments, third-party involvement, correction of payment details, returns and related communications for accounting, tax, legal, compliance, security, dispute resolution and evidentiary purposes.

8. Payment Verification, Delays, Rejections and Returns

8.1. A payment in connection with a Transaction is deemed received by the Company only from the time the relevant amount has actually been reflected in the Company’s recordkeeping, banking, payment or partner system and can be matched to that Transaction.

8.2. The User’s submission of a payment receipt, bank statement, screenshot, transaction identification number (Transaction ID) or other evidence does not in itself mean that the payment has been finally received, accepted or confirmed by the Company.

8.3. The Company may verify a payment by comparing the details of the Transaction created on the Website, the details of actual receipt of payment, the amount, time, payment purpose, payer or recipient details, payment method and other material information.

8.4. When verifying a payment, the Company may await the final recording of banking, payment, partner or internal recordkeeping data and the completion of additional technical or compliance checks.

8.5. The time required to verify a payment may depend on the payment method, the operating hours of the bank or payment system, technical availability, payment volume, Transaction risk level, the need for additional documents and other circumstances.

8.6. A delay in verifying or recording a payment does not constitute a breach of the Company’s obligations if it is due to banking, payment, technical, partner-related, compliance, security or other circumstances beyond the Company’s direct control.

8.7. The Company may reject a payment or decline to link it to the Transaction if the payment does not comply with the Transaction terms approved on the Website, cannot be identified, is not reflected in the relevant recordkeeping system, is at the dispute, refund, hold or cancellation stage, or there are doubts as to the finality of the payment.

8.8. If a payment is subject to a hold, dispute, refund, reversal, chargeback or another non-final status with a bank, payment system, card system, partner organisation or other third party, the Company may refrain from executing or suspend the Transaction until the payment’s final status is clarified.

8.9. In the event of rejection or cancellation of a Transaction, an incorrect payment, an overpayment, an unidentified payment or another situation requiring a return, the return is made after the Company has completed its checks, in a manner that is permitted by law, technically possible and consistent with compliance requirements.

8.10. A return may be made using the same payment method as the original payment or another method accepted by the Company if a return using the original method is impossible, restricted or risky.

8.11. A return may be delayed if it is necessary to establish the payment source, the identity of the payer or recipient, to whom the payment details belong, or the connection between the Transaction and the payment, or if legal, compliance, tax, accounting, technical or security restrictions apply.

8.12. Bank, payment, card, intermediary, conversion, cash servicing, partner, return or other third-party costs actually incurred may be deducted from the amount returned if they apply to the situation concerned.

8.13. The Company does not pay interest, penalties, fines, compensation or other additional amounts for payment verification, delays, return processing, bank or payment system delays or non-execution of a Transaction, unless these were caused intentionally by the Company or by a culpable act of the Company proven in accordance with law.

8.14. If a return cannot be made using the details provided by the User, the User must provide new or corrected payment details and, where necessary, confirm that they belong to the User or that the User has the right to use them lawfully.

8.15. A return is deemed executed from the time the Company sends the return instruction to the relevant bank, payment system, partner organisation or other applicable payment infrastructure, unless the Company has expressly confirmed otherwise for the situation concerned.

8.16. The actual crediting of the returned amount to the User’s account, card, EasyWallet or other payment instrument may depend on the internal rules, time frames and technical processes of the relevant bank, payment system, partner organisation or other third party.

8.17. The Company may retain a complete history of payment verifications, delays, rejections, returns, refunds, disputes, recordkeeping data and related communications for accounting, tax, legal, compliance, security, dispute resolution and evidentiary purposes.

9. Limits, Amendments and Final Provisions

9.1. The Company has the right to set minimum and maximum amounts applicable to payments, receipt of payments, cash operations, bank, card, EasyWallet, EasyPay or other payment methods, daily, monthly or other periodic limits, and individual restrictions for each Transaction.

9.2. Limits may vary depending on the Transaction type, the method for making or receiving payment, the User’s identification level, risk profile and Transaction history, payment infrastructure capabilities, the partner organisation’s terms, and applicable legal or compliance requirements.

9.3. The limits, available payment methods and conditions for their use displayed on the Website, during the Transaction procedure or through the Company’s official communications are binding on the User for that Transaction.

9.4. The Company may temporarily or permanently change, reduce, increase, suspend or remove certain limits or payment methods, taking into account technical, operational, partner-related, legal, compliance, security, market or risk management circumstances.

9.5. Exceeding a limit or the unavailability of a payment method does not oblige the Company to confirm or execute the Transaction or continue it on the same terms.

9.6. This Policy applies in conjunction with the Terms of Use, Privacy Policy, KYC/AML/CFT and Sanctions Compliance Policy, Crypto-asset Risk Disclosure Statement, and the tariffs, limits and other rules published on the Website.

9.7. If a provision of this Policy conflicts with a provision of another document published on the Website, the provision specifically governing the payment, cash or return relationship concerned shall apply, unless the Company has expressly provided otherwise.

9.8. The Company has the right to amend, supplement or update this Policy at any time, taking into account changes in legislation, regulation, technology, operations, payment infrastructure, partner organisations, security, compliance or internal policies.

9.9. The amended Policy is published on the Website or made available through the Company’s official communication channels and takes effect upon publication or on another date specified in the Policy.

9.10. The User must regularly review the current version of this Policy and the payment terms, tariffs and limits published on the Website. Continued use of the Website, user account or OurExchangeClub services after amendments constitutes the User’s acceptance of the amended Policy.

9.11. A finding that any provision of this Policy is invalid, unlawful or inapplicable does not affect the validity, legality or applicability of its remaining provisions.

9.12. The Armenian version of this Policy is the primary and prevailing version. In the event of any conflict, difference or discrepancy in interpretation between the Armenian version and translations into English, Russian or any other language, the Armenian version shall prevail.

9.13. Provisions of this Policy which, by their nature, should continue to apply after the completion, rejection or cancellation of a Transaction, a return in connection with it, a request to close a user account or cessation of use of the services shall continue to apply to the extent necessary for legal, accounting, tax, compliance, security, dispute resolution and evidentiary purposes.