Public Offer | Uzbekistan Help Center

PUBLIC OFFER

for the Conclusion of a Contract

for Services Involving the Storage, Receipt

and Sending of Crypto-Assets

(for Individuals)

Tashkent August 7, 2026

Joint Venture “CITY PAY GATE” organized as a Limited Liability Company (Taxpayer Identification Number 311606433), acting on the basis of its Charter and the crypto-depository license CD No. 0004 and crypto-shop license CS No. 0012 issued by the National Agency for Perspective Projects of the Republic of Uzbekistan on February 24, 2025 (hereinafter referred to as “CityPay” or the “Service Provider”), hereby addresses this official proposal (public offer) to legally capable natural persons (hereinafter referred to as the “User”) to enter into a contract on the terms and conditions set forth below (hereinafter referred to as the “Contract” or the “Offer”).

The subject of this Offer is the provision by CityPay of services for the custodial storage, receipt (deposit) and sending (withdrawal/transfer) of supported crypto-assets using the CityPay crypto-wallet integrated into the software products and user interfaces of CityPay’s partners.

CityPay provides services in accordance with the legislation of the Republic of Uzbekistan and the regulatory acts of authorized bodies governing activities with crypto-assets. Access to the Services is provided through the website [https://citypay.uz/](link). The procedure for and the moment of acceptance are set forth in Section 1 of this Offer and require an explicit expression of consent in the web interface.

1 GENERAL PROVISIONS

1.1. This Public Offer is addressed to legally capable natural persons and contains all material terms of a contract within the meaning of Article 369 of the Civil Code of the Republic of Uzbekistan.

1.2. The current version of the Offer is posted on the website [https://citypay.uz/](link) (hereinafter — the “Site”).

1.3. Procedure and moment of acceptance. The User’s familiarisation with the terms and conditions of this Offer, made publicly available by CityPay, shall be deemed its acceptance. No actions implying acceptance (conclusive actions) shall constitute acceptance. Prior to acceptance, the functionality for performing transactions is unavailable.

Acceptance of the Offer signifies the User’s consent to the terms of the Contract; however, it does not, by itself, result in the unconditional provision of access to all Services and does not mean the automatic opening of a Custodial Crypto-Wallet. CityPay shall have the right, before the commencement of servicing or in the course of performance of the Contract, to require the User to undergo additional identification and verification procedures, including the completion of a KYC questionnaire, in order to comply with the requirements of the legislation of the Republic of Uzbekistan, AML/CFT/FP measures and sanctions compliance. Should CityPay send such a request, it shall be mandatory for the User to undergo the relevant procedures, including the KYC questionnaire. Until the requested procedures are completed, CityPay shall have the right:

• not to open the Custodial Crypto-Wallet;

• to restrict access to the functionality;

• to suspend the execution of transactions or refuse to process them — without such actions being regarded as a breach of the Contract.

1.4. Acceptance means the User’s full and unconditional consent to the terms and conditions of this Offer, the Privacy Policy, the Cookie Policy, the Regulation on the Procedure for Refund, Cancellation, Suspension and Processing of Crypto-Assets, as well as other applicable technical, operational and compliance regulations of CityPay posted on the Site.

1.5. Scope of services. Under this Offer, CityPay provides services for the custodial storage, receipt (deposit) and sending (withdrawal/transfer) of supported crypto-assets by means of the CityPay crypto-wallet integrated into the software products and user interfaces of CityPay’s partners. The Custodial Crypto-Wallet shall be deemed provided to the User upon acceptance of the Offer and completion of the KYC procedures specified in Section 4.

1.6. Method of access. Access to the Services shall be provided through the CityPay crypto-wallet, including its use within software solutions and technical infrastructure supported by CityPay.

1.7. Age and legal status. Services shall be provided to natural persons who have reached the age of 18, possess full legal capacity and comply with the requirements of the legislation of the Republic of Uzbekistan and the regulatory acts of authorized bodies (including identification and measures to counter the legalization of proceeds from crime, the financing of terrorism and the financing of proliferation of weapons of mass destruction, as well as sanctions compliance), including mandatory completion of the KYC questionnaire and/or provision of information/documents at CityPay’s request.

1.8. Communications and notifications. CityPay’s interaction with the User, including the sending of informational messages, notifications, information on transaction statuses and legally significant information, shall be carried out using the software and user interfaces within which the CityPay crypto-wallet operates, including integrated third-party interfaces.

Notifications of the posting of a new version of this Offer may be brought to the User’s attention, inter alia, by means of push notifications, system messages or other electronic means of notification used within the relevant interface.

The fact of sending and/or displaying such a notification shall be deemed due notice to the User of the new version of the Offer, confirmation of the User’s familiarization with it and acceptance of the new version of the Offer from the moment of the first use of the CityPay crypto-wallet after the relevant notification has been sent (displayed).

1.9. Electronic documents. Transaction records, action logs, information on transaction statuses and other electronic records generated by CityPay in the course of providing the Services shall be recognized by the Parties as proper evidence of the actions taken and shall have legal force to the extent permitted by the legislation of the Republic of Uzbekistan.

1.10. Personal data and localization. Processing of personal data shall be carried out in accordance with the legislation of the Republic of Uzbekistan and CityPay’s Privacy Policy. The storage of the respective data shall be ensured on servers located in the territory of the Republic of Uzbekistan. The retention period shall be no less than five (5) years from the date of termination of the relationship with the User, or another period established by law.

1.11. Specifics of blockchain technologies. Transactions in distributed ledgers (blockchain networks) are irrevocable/irreversible in nature and depend on network confirmations. Additional terms and risks are disclosed in Sections 4, 5 and 9 hereof, as well as in Appendix 1 hereto.

1.12. Precedence of documents. The terms and conditions of the Offer shall prevail over any informational/marketing publications on the Site.

1.13. Amendments to the Offer. CityPay shall have the right to unilaterally amend this Offer by posting a new version in public access. The new version of the Offer shall apply from the moment of its publication, unless otherwise expressly stated in the text.

Continued use of the CityPay crypto-wallet after the publication of a new version of the Offer shall signify the User’s consent to the amendments made.

1.14. Transaction processing times. Each transaction for the receipt, sending and intra-system transfer of crypto-assets shall be processed within up to twenty-four (24) hours.

2 DEFINITIONS

In this Offer, capitalized terms shall have the meanings set out below, unless the context otherwise requires.

2.1. CityPay — JV LLC “CITY PAY GATE” (TIN 311606433), acting on the basis of its Charter and crypto-depository license CD No. 0004 and crypto-shop license CS No. 0012 issued by the National Agency for Perspective Projects of the Republic of Uzbekistan on February 24, 2025, providing the Services under this Offer.

2.2. Site — the official website of CityPay [https://citypay.uz/](link)

2.3. User — a legally capable natural person who has completed registration/identification and accepted this Offer.

2.4. CityPay Crypto-Wallet — the custodial software and technical infrastructure of CityPay designed for the storage, accounting, receipt and sending of Supported Crypto-Assets, operating independently or integrated into the software products and user interfaces of third parties.

2.5. Crypto-Asset — a property right in the form of digital records in a distributed ledger (blockchain) having value and an owner within the meaning of the legislation of the Republic of Uzbekistan. Supported Crypto-Assets and networks are specified in Appendix 2. Anonymous (privacy) tokens are not supported.

2.6. Supported Networks — blockchain networks through which CityPay technically ensures the deposit/withdrawal/transfer of the respective Supported Crypto-Assets. The list of networks is provided in Appendix 2 and may be changed on security and compliance grounds.

2.7. User Interface — the software interface of Partners (including mobile applications, web interfaces, SDK, API and other solutions) through which the User accesses the CityPay Crypto-Wallet, generates Orders and receives notifications.

2.8. Address (wallet address) — a unique identifier (public key/address) for receiving/sending a Crypto-Asset in the respective network.

2.9. Transaction — an operation with a Crypto-Asset initiated by the User through the User Interface of the CityPay Crypto-Wallet, including receipt (deposit) and sending (withdrawal/transfer).

2.10. Intra-System Transfer — the sending of a Crypto-Asset between wallets maintained within the CityPay infrastructure (off-chain/internal clearing). No CityPay Fee is charged and no Network Fee is applied to Intra-System Transfers.

2.11. External Transfer — the sending of a Crypto-Asset to an external address not maintained within the CityPay infrastructure (on-chain). The Network Fee under the rules of the respective network shall apply to External Transfers.

2.12. Order — an expression of the User’s will in electronic form to execute a Transaction specifying the parameters of the operation (Crypto-Asset, network, amount, recipient’s address, estimated Network Fee and other details), generated through the User Interface.

2.13. Network Fee — a fee paid to validators/miners of the respective network for the inclusion of a transaction in the blockchain; the fee amount is determined by the network’s rules and is not set by CityPay. In the case of an External Transfer, CityPay shall deduct the amount of the Network Fee from the User and pay it to the network.

2.14. Identification (KYC) — procedures for establishing the User’s identity, including the verification of information and documents, as well as the completion of a KYC questionnaire, carried out at CityPay’s request to the extent provided for by the legislation of the Republic of Uzbekistan and CityPay’s internal rules.

Completion of KYC shall be mandatory from the moment CityPay sends the respective request.

2.15. AML/CFT/FP Controls — measures to counter the legalization of proceeds from crime (Anti-Money Laundering, AML), the financing of terrorism (Counter-Financing of Terrorism, CFT) and the financing of proliferation of weapons of mass destruction (Financing of Proliferation, FP), including sanctions screening and transaction monitoring.

2.16. Authorization Means — technical and software mechanisms used within the User Interface to confirm Orders and protect access to the CityPay Crypto-Wallet.

2.17. Push Notification on the Offer — an electronic system message displayed to the User through the User Interface regarding the posting or update of the version of this Offer. The fact of sending and/or displaying such a notification shall be deemed due notice to the User and confirmation of the User’s familiarization with the new version of the Offer.

2.18. Limits — quantitative/value restrictions on transactions established by CityPay and applicable equally to all Users, denominated in USDT:

(a) single sending — up to 6,000 USDT;

(b) single receipt — up to 20,000 USDT;

(d) monthly aggregate volume (sending and receipt) — up to 100,000 USDT;

(e) maximum 30 transactions within 24 hours.

If a transaction is executed in another Crypto-Asset, for the purposes of monitoring the Limits its volume shall be recalculated into USDT at the market quotation used by CityPay at the time the transaction is registered in the system. Day/month shall be calculated according to Tashkent time (UTC+5).

2.19. Minimum Sending Amount — the minimum permissible amount of an Order for the external sending of a Supported Crypto-Asset, which shall be:

(a) for TRX on the Tron network — the amount of TRX equivalent to 5 USDT;

(b) for other Supported Crypto-Assets — the amount of the respective Crypto-Asset equivalent to 10 USDT.

The equivalent in USDT shall be determined at CityPay’s settlement rate displayed in the User Interface at the moment the User confirms the Order. The applicable Minimum Sending Amount shall be displayed to the User before confirmation of the Order.

2.20. Minimum Receipt Amount — the minimum volume of a Crypto-Asset required for its crediting within the CityPay infrastructure. The list of minimum receipt amounts for each Supported Crypto-Asset and network shall be specified in Appendix 2 to the Offer and may be changed by CityPay in accordance with the procedure provided for in this Offer.

2.21. Supported Crypto-Asset — a crypto-asset which, at the time of the respective transaction, simultaneously:

(a) is expressly listed in Appendix 2 to this Offer and in the User Interface;

(b) is supported by CityPay for the respective type of transaction, including receipt, sending, storage, purchase or sale;

(d) in the case of a token — based on the results of CityPay’s technical identification, has a Unique Technical Identifier corresponding to CityPay’s internal technical support parameters for the selected Crypto-Asset and the respective blockchain network.

The coincidence of a name, ticker, logo, image, declared or displayed value does not, in and of itself, confirm that the respective crypto-asset is supported by CityPay.

2.22. Unique Technical Identifier of a Crypto-Asset — the address, number, identifier or other technical detail in the respective blockchain network enabling CityPay to uniquely identify a specific Crypto-Asset and distinguish it from other crypto-assets having an identical or similar name, ticker or logo.

Depending on the respective blockchain network, such identifier may be the address of the token’s smart contract, the unique address of the token’s issuance, the address of the token’s master contract, the identifier of the Crypto-Asset or another analogous technical identifier.

The Unique Technical Identifier shall be used by CityPay for the automated and/or manual technical identification of the actually received token based on the data of the respective blockchain network and CityPay’s internal technical support parameters.

The Unique Technical Identifier shall not apply to the native Crypto-Asset of a blockchain network that is not issued through a separate smart contract.

2.23. Unsupported Crypto-Asset — any crypto-asset not meeting at least one of the conditions provided for in clause 2.21 of this Offer, including:

(a) a crypto-asset not listed in Appendix 2;

(b) a crypto-asset sent via a blockchain network not supported by CityPay for such crypto-asset;

(c) a token whose Unique Technical Identifier, based on the results of CityPay’s technical identification, does not correspond to CityPay’s internal technical support parameters for the selected Crypto-Asset and blockchain network;

(d) a token using an identical or similar name, ticker or logo of a Supported Crypto-Asset but having a different Unique Technical Identifier and not corresponding to the Crypto-Asset selected by the User in the User Interface;

(e) a derivative, wrapped, synthetic, issued or transferred via a cross-chain bridge or other analogous token, unless expressly listed in Appendix 2;

(f) an unknown, unwanted, imitating, potentially harmful or potentially fraudulent crypto-asset;

(g) a crypto-asset not recognized or not supported by CityPay’s internal accounting system, blockchain monitoring tools, custodial or other technical infrastructure.

2.24. Crypto-Asset with Signs of Counterfeiting or Misleading — a Crypto-Asset which fully or partially reproduces the name, ticker, logo, description or other distinctive features of another Crypto-Asset, but has a different Unique Technical Identifier, has been issued by a different person or does not correspond to the official information about the issuer and CityPay’s internal technical support parameters.

A Crypto-Asset with signs of counterfeiting or misleading shall be an Unsupported Crypto-Asset regardless of the blockchain network in which it is issued or circulated.

2.25. Erroneous Incoming Transaction — a transaction as a result of which the following has been sent to the blockchain address provided by CityPay for the receipt of a specific Supported Crypto-Asset:

(a) an Unsupported Crypto-Asset;

(b) a crypto-asset via an incorrect or unsupported blockchain network;

(c) a token whose Unique Technical Identifier does not correspond to the Supported Crypto-Asset selected by the User in the User Interface;

(d) a crypto-asset without a mandatory comment, tag, number or other necessary requisite;

(e) a crypto-asset to an incorrect, inactive or inappropriate blockchain address.

3SUBJECT MATTER OF THE CONTRACT

3.1. Scope of Services. Under this Offer, CityPay shall provide the User, via the Site, with the following Services in respect of Supported Crypto-Assets:

(a) custodial storage of the User’s Crypto-Assets;

(b) receipt (deposit) of Crypto-Assets to addresses/wallets maintained by CityPay’s infrastructure;

(c) sending (withdrawal/transfer) of Crypto-Assets from addresses/wallets maintained by CityPay’s infrastructure to internal addresses (wallets maintained by CityPay) or to external addresses in Supported Networks.

The provision of particular Services, as well as the scope of available functionality, may be conditional upon the User’s fulfillment of identification requirements, compliance checks and/or completion of a KYC questionnaire, where such requirements have been requested by CityPay in accordance with the legislation of the Republic of Uzbekistan and CityPay’s internal rules.

3.2. Custodial model and title to assets. Custodial storage shall be carried out by CityPay as a licensed crypto-depository. The private keys of the respective addresses/wallets shall be under the control of CityPay. In this regard:

(a) the right of ownership of the Crypto-Assets shall at all times belong to the User;

(b) the User’s Crypto-Assets shall not be the property of CityPay, shall not be included in CityPay’s insolvency estate, shall not be encumbered by the rights of third parties, and shall not be used by CityPay (including by way of loan/pledge) without the User’s Order.

3.3. Receipt (deposit) of Crypto-Assets.

(a) A deposit shall be effected by crediting a confirmed transaction in a Supported Network to the User’s designated address (wallet) maintained by CityPay’s infrastructure.

(b) Crediting may require a minimum number of network confirmations and/or the specification of attributes required by the network (e.g., memo/tag, comment).

(c) The fact of crediting shall be reflected in the User Interface once the requirements of sub-clause 3.3(b) have been met.

(d) CityPay accepts, records and credits exclusively Supported Crypto-Assets. The list of Supported Crypto-Assets and blockchain networks is exhaustive and shall be determined by Appendix 2 and the User Interface. Technical identification of the actually received token shall be carried out by CityPay on the basis of its Unique Technical Identifier, the data of the respective blockchain network and CityPay’s internal technical support parameters.

(e) Each blockchain address is provided for the receipt of a specific Supported Crypto-Asset via a specific blockchain network. CityPay’s support for a given blockchain network for one crypto-asset does not mean support for other crypto-assets or tokens operating on the same network.

(f) The technical possibility of sending another crypto-asset to the provided blockchain address does not mean that such crypto-asset is supported or accepted by CityPay under this Contract.

(g) An Unsupported Crypto-Asset shall not be subject to automatic crediting, reflection in the User’s balance, purchase, sale, exchange or use in the provision of CityPay’s services.

(h) The existence of a record in the blockchain network of the sending of an Unsupported Crypto-Asset to an address provided by CityPay does not, in and of itself, confirm the acceptance of such crypto-asset by CityPay under this Contract and does not create an obligation to credit the User with another crypto-asset or its cash equivalent.

(i) CityPay shall not replace an Unsupported Crypto-Asset with a Supported Crypto-Asset and shall not compensate for its nominal, declared, displayed or presumed value.

3.4. Sending (withdrawal/transfer) of Crypto-Assets.

(a) Sending shall be carried out on the basis of a User’s Order generated through the User Interface, specifying the Supported Asset/network, volume and recipient’s address.

(b) External Transfers. External Transfers shall be subject to a Network Fee, the amount of which shall be determined by the rules of the respective blockchain network and communicated to the User before confirmation of the Order. CityPay shall deduct the amount of the Network Fee from the User and remit it to the respective network on its own behalf;

(c) Intra-System Transfers. Transfers between wallets maintained within CityPay’s infrastructure shall be executed without charging a CityPay Fee and without a Network Fee (off-chain/internal clearing).

(d) Transactions sent to the network are irrevocable and irreversible. CityPay cannot cancel or alter a transaction after it has been transmitted to the network. The User shall bear the risks of errors in the address/network/parameters.

3.5. Supported assets and networks. The list of Supported Crypto-Assets and networks is set out in Appendix 2 and may be amended by CityPay on the grounds of legislation, acts of authorized bodies, security and compliance requirements, as well as technological expediency. Anonymous (privacy) tokens are not supported.

3.6. Addresses and details. The User confirms that each recipient’s address (external or internal) indicated by the User is intended for the receipt of the respective Supported Asset in the respective network and is under the control of its lawful owner. CityPay is not obliged to verify the ownership/correctness of addresses and shall not be liable for the consequences of the User’s errors.

3.7. Informational support. Information on the status of receipt, sending and transfers of Crypto-Assets, as well as other technical information, shall be provided to the User through the User Interface in which the CityPay Crypto-Wallet is integrated.

3.8. Execution timeframes. CityPay shall execute receipt (deposit), sending (withdrawal/transfer) and intra-system transfers within up to twenty-four (24) hours from the moment of a correct Order/receipt of funds to the respective address. Actual timeframes depend on the network and security/compliance checks and may vary. For External Transfers, the moment of inclusion of the transaction in the blockchain shall be determined by the network’s rules.

3.9. Refusal/suspension of execution. CityPay shall have the right to refuse to execute an Order or to suspend/freeze/cancel a transaction and block an account in the cases provided for by this Offer and legislation, including measures to counter money laundering (AML), terrorist financing (CFT) and financing of proliferation of weapons of mass destruction (FP), sanctions compliance, orders of authorized bodies, as well as in the event of reasonable technical risks/incidents or suspicion of the User’s violation of the law and/or the terms of the Offer.

4 TERMS OF SERVICE

4.1. Registration and Access. Access to the Services shall be provided to the User using the CityPay Crypto-Wallet integrated into the User Interfaces. The functionality for performing transactions shall be unavailable prior to acceptance. The Contract shall be deemed concluded, and the User shall be deemed to have commenced using the Services, from the moment of acceptance of this Offer in accordance with the procedure set out in Section 1. Acceptance of the Offer and commencement of use of the Services shall not mean the unconditional provision of access to all functions: CityPay shall have the right to establish restrictions and additional conditions of access, including requesting identification and compliance checks.

4.2. Identification (KYC) and Compliance.

4.2.1. CityPay shall have the right, at any time, before the commencement of servicing or in the course of performance of the Contract, to request that the User undergo identification, including by means of requests through the User Interface and/or through CityPay’s support service, including the completion of a KYC questionnaire and the provision of information and documents necessary for compliance with the requirements of the legislation of the Republic of Uzbekistan, AML/CFT/FP and sanctions compliance.

4.2.2. From the moment CityPay sends a request to undergo identification and/or complete a KYC questionnaire, the fulfilment of such request shall be mandatory for the User.

Failure to provide information, refusal to complete the KYC questionnaire or the provision of unreliable data shall result in refusal of service, suspension of transactions and/or termination of the Contract.

4.2.3. CityPay shall have the right to carry out continuous monitoring of transactions and repeat identification and verification to the extent provided for by the legislation of the Republic of Uzbekistan and internal rules.

4.3. Authorization Means and Security.

4.3.1. The User shall be obliged to ensure the security of the devices and accounts through which access to the CityPay Crypto-Wallet in the User Interface is carried out, including the safekeeping of access codes, PIN codes, passwords and other authorization/confirmation mechanisms.

4.3.2. Actions performed using correct authorization means and/or in the User Interface shall be deemed to have been performed by the User, unless proven otherwise.

4.3.3. The User shall be obliged to immediately notify CityPay through CityPay’s communication channels of any facts of compromise, suspicion of unauthorized access or loss of control over the device/account.

4.3.4. Temporary inability of the User to access the functionality of the CityPay Crypto-Wallet as a result of a technical failure shall not be considered a compromise of the Authorization Means. For the period of rectification of such failure, CityPay shall have the right to temporarily suspend transactions for sending Crypto-Assets in order to ensure their safekeeping.

4.4. Generation of Orders.

4.4.1. An Order shall be generated by the User in the User Interface where the CityPay Crypto-Wallet is integrated, and shall contain the mandatory parameters (asset, network, volume, recipient’s/sender’s address, and, where necessary, memo/tag/other network attributes).

4.4.2. Prior to confirmation of the Order, the applicable transaction parameters, including the estimated amount of the Network Fee for external transfers, shall be displayed to the User.

4.4.3. A confirmed Order shall be sent for execution and may be suspended/rejected on the grounds set out in clause 4.10.

4.5. Receipt (Deposit) of Crypto-Assets.

4.5.1. The address provided to the User in the User Interface shall be used for the deposit. The User shall be obliged to use the current address and the correct network.

4.5.2. A minimum required number of network confirmations and/or mandatory attributes (memo/tag), if required by the respective network, may apply to crediting.

4.5.3. Transfers to an incorrect network/asset, to an outdated address, without a mandatory memo/tag may not be credited; the risk of such consequences shall be borne by the User.

4.5.4. Exceeding the limit upon receipt. If an incoming transaction exceeds the single receipt limit of 20,000 USDT (or results in the daily/monthly limit being exceeded), the amount shall not be subject to crediting. CityPay shall have the right to: (a) return the assets to the sender (where technically possible) less the network fee and unavoidable expenses; or (b) temporarily freeze the assets until the completion of checks/receipt of documents; (c) apply clause 4.16 where there are signs of elevated/prohibited risk. For transactions in other assets, the excess shall be determined based on the USDT equivalent at the time the transaction is registered.

4.5.5. Minimum Receipt Amount

A minimum receipt amount required for crediting a Crypto-Asset within CityPay’s infrastructure may be established for each Supported Crypto-Asset and network.

If the amount of an incoming transaction is less than the established minimum receipt amount:

(a) CityPay shall have the right not to credit such transaction to the User’s Crypto-Wallet;

(b) CityPay shall not be obliged to return such transaction if return is technically impossible or economically inexpedient given the size of the network fee;

(c) such amounts may not be reflected in the User’s available balance until the minimum receipt threshold is reached or until CityPay makes a different decision.

Minimum receipt amounts are specified in Appendix 2 to this Offer.

4.5.6. Before sending a crypto-asset, the User shall be obliged to verify:

(a) the name and ticker of the Crypto-Asset indicated in the CityPay User Interface;

(b) that the crypto-asset selected on the sender’s side corresponds to the Crypto-Asset indicated in the CityPay User Interface;

(c) that the blockchain network selected on the sender’s side corresponds to the blockchain network indicated in the CityPay User Interface;

(d) the current receiving address;

(e) the presence and correctness of the mandatory comment, memo, tag, number or other necessary requisite.

4.5.7. The User shall not be entitled to send other crypto-assets to the address provided by CityPay, including assets with an identical or similar name, ticker or logo. If in doubt, the User shall be obliged to refrain from executing the transaction and first contact CityPay’s support service.

4.5.8. The User shall independently bear the risk of an Erroneous Incoming Transaction if CityPay has provided correct and sufficient information about the Supported Crypto-Asset, the blockchain network, the current receiving address and the mandatory memo, tag or other requisite, and the User or another sender has sent a different Crypto-Asset, used a different blockchain network, an incorrect address or failed to specify a mandatory requisite.

Technical identification of the actually received token on the basis of its Unique Technical Identifier shall be carried out by CityPay.

4.6. Sending (Withdrawal/Transfer) of Crypto-Assets.

4.6.1. Intra-System Transfers (between wallets maintained by CityPay’s infrastructure) shall be carried out without charging a CityPay Fee and without a Network Fee (off-chain clearing).

4.6.2. External Transfers (to addresses outside CityPay’s infrastructure) shall require payment of a Network Fee determined by the rules of the respective network; the amount of the Network Fee shall be displayed before confirmation of the Order. CityPay shall deduct the said amount of the Network Fee from the User and remit it to the network’s validators/miners;

4.6.3. After a transaction is released to the network, the operation is irrevocable and irreversible. CityPay shall not be obliged to cancel/alter on-chain transactions.

4.6.4. Exceeding the limits upon sending. Orders exceeding the single/daily/monthly limit, or the limit on the number of transactions (see clause 2.18), shall not be accepted or shall be suspended. For transactions in other assets, compliance with the limits shall be assessed based on the USDT equivalent at the time the transaction is registered.

4.6.5. Minimum Sending Amount. Orders for “sending” the amount of which is less than the minimum sending amount shall not be accepted or shall be rejected. For transactions in other crypto-assets, compliance with the minimum sending amount shall be assessed based on the USDT equivalent at the time the transaction is registered.

4.7. Technical Requirements for Transactions.

4.7.1. CityPay shall not accept or process transactions with unsupported assets/networks.

4.7.2. CityPay shall have the right to reject transactions that do not meet the technical requirements of the network (including the absence of a mandatory memo/tag, incorrect address format and the like).

4.8. Display of Statuses.

Transaction statuses shall be displayed in the User Interface in which the CityPay Crypto-Wallet is integrated.

4.8.1. Notifications related to transaction statuses, restrictions and other servicing events may be sent to the User by means of push notifications and other messages in the User Interface (where technically possible), as well as through CityPay’s support service in the cases provided for by the Offer and the law.

4.9. Execution Timeframes.

4.9.1. CityPay shall execute receipt (deposit), sending (withdrawal/transfer) and intra-system transfers within up to twenty-four (24) hours from the moment of a correct Order and/or receipt of crypto-assets to the respective address.

4.9.2. For External Transfers, the moment of inclusion of the transaction in the blockchain shall be determined by the network’s rules and may depend on network congestion. In this case, CityPay’s sending Order shall be generated and transmitted to the network within the timeframe specified in clause 4.9.1. The timeframes are indicative and depend on the network and checks.

4.9.3. In the event of a confirmed technical failure, the running of the timeframes for execution of transactions shall be suspended for the period of rectification of such failure and shall resume after the restoration of the normal operation of the service.

4.10. Grounds for Suspension/Refusal/Freezing/Cancellation of Assets. CityPay shall have the right to suspend/freeze or refuse to execute Orders, restrict access to the CityPay Crypto-Wallet and/or its functionality in the User Interface, suspend transactions on wallets/account and freeze Crypto-Assets, if:

(a) it is revealed that the User has provided unreliable/incomplete information and the User’s failure to comply with identification/verification procedures;

(b) this is expressly provided for by the legislation of the Republic of Uzbekistan and/or orders of authorized bodies;

(c) this is required in accordance with the Internal Control Rules for combating money laundering, terrorist financing and financing of proliferation of weapons of mass destruction (AML/CFT/FP), including sanctions screening and transaction monitoring;

(d) the User, the User’s transactions/counterparties are associated with lists of persons involved or suspected of involvement in terrorist activity or proliferation of weapons of mass destruction — in such case CityPay shall freeze the assets in accordance with the procedure and for the period provided for by law;

(e) transactions/deals suspected of money laundering, terrorist financing or proliferation of weapons of mass destruction, as well as those associated with gambling, are identified — measures shall also be applied in accordance with CityPay’s internal documents;

(f) there are technical risks/incidents, signs of compromise of authorization means, non-compliance with the technical requirements of the network/Appendices, exceeding of limits or insufficient balance;

(g) the User has failed to comply with CityPay’s request for the submission of documents/information as provided for in clauses 4.2.1 and 4.2.4 of this Offer.

(h) the User has specified an incorrect network/asset/address or there is an absence of a mandatory memo/tag;

(i) other cases provided for by the Offer and the law.

(j) the amount of the “sending” Order is less than the Minimum Sending Amount.

(k) a confirmed technical failure, software error or carrying out of remedial works in CityPay’s infrastructure is identified.

Notification of suspension/freezing shall be given in the manner and to the extent provided for by the legislation of the Republic of Uzbekistan, unless such notification is prohibited by law.

Information on suspension/refusal shall be provided in the User Interface.

4.11. Responsibility for Details. The User shall be responsible for the correctness of the addresses, network, asset, memo/tags and other parameters indicated. CityPay shall not be obliged to verify the ownership of the recipient’s addresses and shall not be liable for the consequences of the User’s errors.

4.12. Changeability of the List of Assets/Networks and Functions. CityPay shall have the right to change the list of Supported Crypto-Assets/networks and suspend/resume the deposit/withdrawal of individual assets on the grounds of security, compliance, regulatory requirements and/or technological expediency.

4.13. Addition and Removal of Crypto-Assets

4.13.1. General Provisions.

CityPay shall independently determine the list of Supported Crypto-Assets and networks, guided by the requirements of the legislation of the Republic of Uzbekistan, the acts of the National Agency for Perspective Projects, as well as internal security and compliance policies.

The addition (listing) and removal (delisting) of crypto-assets/networks shall be carried out without the separate consent of Users and shall be deemed non-material amendments to the terms of the Offer within the meaning of clause 12.1(c).

4.13.2. Addition (Listing) of Crypto-Assets.

(a) The decision to add (list) a Crypto-Asset or network shall be made by CityPay based on an assessment of:

• compliance with legislation and NAPP requirements;

• the stability and technical reliability of the network;

• the availability of liquidity and stable operation of the infrastructure;

• the level of AML/CFT/FP and sanctions compliance risks;

• technical integrability into the CityPay platform.

(b) Upon making the decision, CityPay shall update Appendix 2, notify Users by posting information on the CityPay Site and/or via notifications in the User Interface, and indicate the date of commencement of support for the new crypto-asset/network.

4.13.3. Removal (Delisting) of Crypto-Assets.

(a) Removal (delisting) of crypto-assets means the termination of technical and operational support for the crypto-asset/network.

(b) Grounds for removal (delisting) of crypto-assets:

• orders of NAPP or other state bodies;

• violation of legal/sanctions requirements or the emergence of compliance risks;

• significant technical failures of the network, termination of support by validators;

• loss of liquidity or objective impossibility of safe maintenance;

• CityPay’s decision to terminate support for internal security or operational efficiency reasons.

(c) When removing (delisting) crypto-assets, CityPay shall notify Users by posting information on the CityPay Site and/or via notifications in the User Interface no less than thirty (30) calendar days prior to the termination of support, indicating the date after which deposit/withdrawal of the crypto-asset will become unavailable.

(d) During the notice period, the User shall have the right to transfer the respective crypto-assets to an external address.

(e) Upon expiry of the said period, transactions with the crypto-asset shall be terminated. Where withdrawal is technically impossible or there are legal restrictions, the assets shall be frozen pending the Users’ contact with CityPay’s support service.

(f) In emergency cases — sanctions, failures, network compromise, orders of regulators — CityPay shall have the right to remove (delist) crypto-assets immediately without prior notice, with the subsequent posting of information on the Site and/or via notifications in the User Interface.

4.13.4. Legal Consequences.

(a) Removal (delisting) of crypto-assets carried out under this clause shall not constitute a breach of CityPay’s obligations.

(b) After the date of removal (delisting) of crypto-assets, transactions with the crypto-asset shall be unavailable. CityPay shall keep records of the respective balances until their lawful withdrawal or disposal in accordance with the procedure established by law.

(c) The return or freezing of assets upon removal (delisting) of crypto-assets shall be performed in accordance with clause 4.16 and orders of authorized bodies.

(d) CityPay shall not carry out automatic conversion of removed (delisted) crypto-assets into other assets or stablecoins and shall not provide exchange services, unless otherwise expressly required by law or the regulator.

4.13.5. Precedence of Legislation.

All decisions on addition (listing) and removal (delisting) shall be made and executed strictly in accordance with the legislation of the Republic of Uzbekistan.

4.14. Service and Support. Enquiries shall be accepted through CityPay’s communication channels published on the CityPay Site and/or communicated to the User in the User Interface. Response times depend on the complexity of the enquiry and the operational mode.

4.15. Localization and Storage of Transaction Data. Transaction records and logging data (date/time, IP/identifiers, Order parameters) shall be maintained and stored by CityPay to the extent and for the periods established by the legislation of the Republic of Uzbekistan and internal rules (no less than 5 years or another period as required by law).

4.16. Special AML/CFT/FP Rules: Return/Non-Return and Freezing of Assets.

4.16.1. Classification of Sources/Destinations. When monitoring transactions, CityPay shall use internal algorithms and external blockchain analytics providers. Categories identified shall include, among others:

— High-Risk (Illicit Activity): darknet markets, mixers, scam/phishing schemes and similar sources of obfuscation;

— Prohibited: sanctioned addresses/entities, sale of drugs, illegal gambling, terrorist financing, child sexual abuse material (CSAM), DPRK and other categories expressly prohibited by law (Obfuscating & Misc., Gambling, Sanctioned, TF & CSAM, DPRK, etc.).

4.16.2. Incoming Transactions (Receipt).

(a) If a transaction has been received from a high-risk source (Illicit Activity), CityPay shall have the right not to credit the assets, to freeze them and shall have the right to return or not return them to the sender (where technically possible) less the network fee and other unavoidable expenses.

(b) If a transaction has been received from a prohibited source (sanctions, drugs, illegal gambling, TF, CSAM, DPRK, etc.), the assets shall be frozen and shall not be returned; CityPay shall act in accordance with the requirements of the legislation and orders of authorized bodies.

4.16.3. Outgoing Transactions (Sending).

(a) If an Order is directed to a high-risk source (Illicit Activity), CityPay shall have the right not to execute it, to freeze it and shall have the right to return or not return the assets to the User (less the network fee/unavoidable expenses), suspending transactions pending the completion of checks.

(b) If an Order is directed to a prohibited source, the assets intended for sending shall be frozen and shall not be returned, and the transaction shall not be executed; further actions shall be in accordance with the requirements of legislation.

4.16.4. Account Blocking and Freezing of Assets. If the signs specified in clauses 4.16.2–4.16.3 are identified, as well as in the event of failure to provide the required documents/explanations, CityPay shall have the right to restrict access to the CityPay Crypto-Wallet and/or its functionality (in whole or in part) and freeze assets until the completion of checks/receipt of orders. Prior notification of the User shall not be required, unless otherwise mandated by law.

4.16.5. Precedence of Law. Return/non-return of assets, as well as their freezing/seizure, shall be carried out in strict compliance with the legislation and orders of competent authorities.

4.16.6. Additional conditions and the procedure for return, cancellation, suspension and processing of transactions with crypto-assets shall be determined by a separate Regulation of CityPay posted on the Site, which shall form an integral part of this Offer.

4.17. Technical Failures and Errors. Temporary Loss of Access to the Crypto-Wallet and Restoration of Crypto-Asset Records

4.17.1. Definition of Technical Failure or Error. A technical failure or error caused by the fault of CityPay shall mean a CityPay-confirmed disruption of the correct operation of software, internal IT infrastructure, key storage systems, operational processes for processing Orders or intra-system clearing, which are under the control of CityPay, that occurred:

• prior to the transmission of the transaction to the respective blockchain network; and/or

• in the course of an Intra-System Transfer; and/or

• in the course of internal accounting of Crypto-Assets within CityPay’s custodial infrastructure, and that resulted in one or more of the following consequences:

(a) unlawful debiting of the User’s Crypto-Assets;

(b) incorrect reflection of the balance, transaction history or Order status in the CityPay Crypto-Wallet;

(d) temporary inability of the User to access the CityPay Crypto-Wallet (including the inability to view the balance or transaction history);

(e) desynchronization of Crypto-Asset accounting data between CityPay’s internal systems;

(f) other similar errors directly affecting the correctness of the accounting of the User’s Crypto-Assets within CityPay’s infrastructure.

4.17.2. Measures of CityPay in the Event of a Confirmed Technical Failure

Upon confirmation of a technical failure or error, CityPay shall undertake, within a reasonable period, taking into account the nature of the failure, information security requirements and the legislation of the Republic of Uzbekistan, to take proportionate measures, including one or more of the following actions:

(a) restore the correct accounting of the User’s Crypto-Assets; and/or

(b) restore the User’s access to the CityPay Crypto-Wallet; and/or

(d) adjust internal records, balances and transaction statuses.

4.17.3. Temporary Loss of Access

The temporary inability of the User to access the CityPay Crypto-Wallet as a result of a technical failure shall not constitute a loss of Crypto-Assets if such Crypto-Assets are safe and accounted for within CityPay’s custodial infrastructure.

The User’s right of ownership of the Crypto-Assets shall be preserved in full in such case.

4.17.4. Procedure for Restoration of Access

CityPay shall take reasonable and proportionate measures to restore the User’s access to the CityPay Crypto-Wallet within a period determined by the nature of the technical failure, the scope of remedial works and security requirements.

Until access is restored, CityPay shall have the right to temporarily suspend transactions for sending Crypto-Assets, as well as the use of individual functions of the Crypto-Wallet, in order to protect the User’s assets and prevent unauthorized actions.

4.17.5. Limit of Compensation

Compensation under this clause shall be provided exclusively in the amount of the respective Crypto-Asset actually unlawfully debited or lost as a result of a confirmed technical failure and shall not include compensation for:

(a) changes in the market value of the Crypto-Asset;

(b) lost profits;

(d) moral harm;

(e) indirect, consequential or punitive damages.

4.17.6. Exclusion of Liability for Blockchain

If an Order has been duly transmitted by CityPay to the respective blockchain network (which is confirmed by the assignment of a transaction identifier — TxID), CityPay’s obligation shall be deemed performed in accordance with clause 8.3 of this Offer. Subsequent events related to the functioning of the blockchain network, validators, protocols or third-party infrastructure shall not constitute technical failures caused by the fault of CityPay.

4.17.7. Limitations on Application

The provisions of this clause shall not apply and/or their performance shall be suspended if the restoration, return or access to Crypto-Assets:

(a) is restricted or prohibited by the legislation of the Republic of Uzbekistan;

(b) is carried out on the basis of orders of authorized bodies;

5 FEES AND CHARGES

5.1. General Principle.

Only the Network Fee — a fee to validators/miners of the respective blockchain network — shall apply to Transactions under this Offer. The amount of the Network Fee is determined by the network’s rules and is not set by CityPay.

CityPay shall deduct the Network Fee from the User and remit it to the respective network.

5.2. Intra-System Transfers.

Transfers of Crypto-Assets between wallets maintained by CityPay’s infrastructure shall be carried out without charging a CityPay Fee and without a Network Fee (internal clearing).

5.3. Receipt (Deposit) of Crypto-Assets.

Crediting of incoming transfers to addresses/wallets maintained by CityPay shall be carried out without a CityPay fee. The Network Fee when generating an incoming transaction shall be paid by the sender (external address), if provided for by the network’s rules.

5.4. Sending to an External Address (External Transfers).

(a) The Network Fee, the amount of which dynamically depends on network load and the rules for inclusion of transactions in a block/slot, shall apply to External Transfers; CityPay does not control or set this fee.

(b) The method of deduction of the Network Fee (from the sent amount or in the network’s base token) shall be determined by the rules of the respective network and displayed to the User in the User Interface before confirmation of the Order.

5.5. Transparency Prior to Confirmation.

Prior to confirmation of the Order, the following shall be displayed in the User Interface: Transaction type, asset/network, volume, recipient’s address, estimate of the Network Fee and the final amount to be sent/received. Confirmation of the Order signifies consent to the said parameters.

5.6. Dynamic Nature of the Network Fee.

The estimate of the Network Fee displayed prior to confirmation is indicative and may differ from the actually deducted value due to changes in network parameters at the time the transaction is sent. In such cases, the amount of the Network Fee may be adjusted in accordance with the network’s rules. If the User’s balance has insufficient Crypto-Assets to deduct the actual Network Fee (in the required network token), the Order may be rejected or suspended until the balance is topped up.

5.7. Minimum Network Amounts and Rounding.

If the network’s rules provide for minimum transfer/balance amounts (e.g., “dust”, rent-exempt, etc.), Orders below the network threshold may be rejected. Amounts may be rounded within the technical precision of the respective network/token. The application of such network restrictions and rounding shall not constitute a breach of CityPay’s obligations and shall not entail an obligation on CityPay to compensate for any losses caused by the rules of the respective network.

6 RIGHTS AND OBLIGATIONS OF THE PARTIES

6.1. CityPay shall be obliged to:

(a) provide the Services properly within the functionality of the Offer (custodial storage, receipt, sending/transfer);

(b) apply organizational and technical protection measures;

(c) comply with the legislation of the Republic of Uzbekistan, including measures to counter the legalization of proceeds from crime, the financing of terrorism and the financing of proliferation of weapons of mass destruction, as well as requirements for personal data and orders of authorized bodies;

(d) ensure display in the User Interface of transaction statuses and the amount of the applied Network Fee;

(e) store information and documents for the period and to the extent established by law and the Offer.

6.2. CityPay shall have the right to:

(a) request information/documents from the User, conduct repeat identification and ongoing monitoring of transactions;

(b) establish and change technical parameters of transactions and processing modes necessary for the safe and stable operation of the service;

(c) suspend/reject/freeze/cancel Orders, block assets and/or access to the CityPay Crypto-Wallet in whole or in part in the cases provided for by the Offer and the law (sanctions screening, signs of fraud, violation of the Offer, orders of authorities, technical incidents, etc.);

(d) temporarily restrict functionality, deposit/withdrawal of individual assets/networks for reasons of security, compliance, regulatory requirements or maintenance;

(e) change the list of Supported Crypto-Assets/networks (Appendix 2) on the grounds specified in the Offer;

(f) send legally significant messages in electronic form by posting them in the User Interface through which the CityPay Crypto-Wallet is used, as well as by other means permitted by law;

(g) request that the User undergo a KYC questionnaire and other identification procedures; suspend access to the Services until they are completed or to refuse service if the User refuses.

6.3. The User shall be obliged to:

(a) provide accurate data during registration/identification and update it in a timely manner;

(b) use the Services personally, on their own behalf and in their own interests, being the beneficial owner of the Crypto-Assets;

(c) comply with the Offer and the legislation of the Republic of Uzbekistan, including measures to counter the legalization of proceeds from crime, the financing of terrorism and the financing of proliferation of weapons of mass destruction, as well as sanctions restrictions;

(d) ensure the confidentiality of Authorization Means and the security of devices/browser; to immediately inform CityPay of any compromise;

(e) specify correct Order parameters (asset, network, address, memo/tag, etc.) and verify them before confirmation;

(f) not to use the service for activities prohibited by law, including transactions with illegal goods/services;

(g) independently monitor transaction statuses and other messages displayed in the User Interface through which the CityPay Crypto-Wallet is used;

(h) upon CityPay’s request, undergo identification procedures, including completion of a KYC questionnaire, and provide accurate information and documents within the established timeframes.

6.4. The User shall have the right to:

(a) obtain access to the Services through the CityPay Crypto-Wallet integrated into the User Interface after acceptance of the Offer and completion of the necessary checks;

(b) generate Orders for the receipt/sending of Crypto-Assets subject to compliance with technical requirements;

(d) contact CityPay support on servicing issues in accordance with the procedure established by the Offer.

6.5. Responsibility for Details and Confirmations.

All actions performed using correct Authorization Means and confirmed in the interface shall be deemed actions of the User. The User shall bear the risks of incorrect specification of the network/address/tag, sending of an unsupported asset and the irrevocability of on-chain transactions.

6.6. Restrictions on Use of the Service:

(a) attempts to interfere with the operation of the CityPay Crypto-Wallet, its API, server infrastructure, as well as circumvention of technical restrictions, DDoS attacks, scraping, reverse engineering and other actions aimed at disrupting the stability or security of the service are prohibited;

(b) use of the service for transactions that directly or indirectly violate the law, third-party rights or the sanctions regime is prohibited;

(c) transfer of access to third parties, assignment of the account and other actions creating a risk of unauthorized access are prohibited.

6.7. Cooperation and Documents.

At CityPay’s request, the User shall be obliged to promptly provide the required information/documents. Failure to provide or refusal – grounds for suspension/refusal of transactions and/or termination of the Contract.

6.8. Communications.

The User undertakes to independently monitor information posted in the User Interface through which the CityPay Crypto-Wallet is used, including notifications of amendments to the Offer, transaction statuses and restrictions.

Posting of information in such interface shall be deemed due notice to the User, unless otherwise expressly provided for by the legislation of the Republic of Uzbekistan.

6.9. Evidence.

CityPay’s electronic logs (metadata, authorization and confirmation logs, technical fingerprints) may be used as proper evidence of the facts of actions taken between the parties to the extent permitted by law.

6.10. Use through Third-Party Interfaces.

The User confirms that the CityPay Crypto-Wallet may be used through the software products and user interfaces of CityPay’s partners. The specifics of the operation of such interfaces, including methods of displaying information, technical limitations or user experience, shall not constitute a breach of CityPay’s obligations if the transactions with Crypto-Assets themselves are carried out correctly within CityPay’s infrastructure.

7 REPRESENTATIONS AND WARRANTIES OF THE USER

By accepting this Offer and using the CityPay Crypto-Wallet, the User confirms, represents and warrants that as of the date of acceptance and throughout the entire term of the Contract the following is true:

7.1. Identity and Legal Capacity.

(a) The User has reached the age of 18, possesses full legal capacity and is entitled to enter into and perform this Contract.

(b) The User acts on their own behalf and in their own interests, is the beneficial owner of the Crypto-Assets and does not act on behalf of/in the interests of a third party without lawful grounds.

7.2. Accuracy of Information.

(a) All data and documents provided during registration/identification and in the course of servicing are accurate, reliable, current and complete.

(b) The User shall promptly update the information in the event of any changes thereto.

(c) The source of origin of the Crypto-Assets/funds is lawful; the assets are not encumbered by the rights of third parties.

7.3. Compliance with Law, Sanctions and Compliance Measures.

(a) The User is not included in national/international sanctions lists or other restriction lists and is not subject to prohibitions making servicing impossible.

(b) The User shall not use the Services for activities prohibited by legislation, including money laundering, terrorist financing and financing of proliferation of weapons of mass destruction, fraud, violation of export controls and the sanctions regime.

(c) At CityPay’s request, the User shall provide documents and information necessary for identification (KYC) procedures and checks for combating money laundering, terrorist financing and financing of proliferation of weapons of mass destruction (AML/CFT/FP), and shall facilitate their conduct.

The User confirms that they understand and accept CityPay’s right to request completion of a KYC questionnaire and other identification procedures, and agrees that refusal to undergo them may result in refusal to provide the Services or termination of the Contract.

7.4. Details and Addresses.

(a) Each address and other details specified by the User: (i) are intended for the respective Supported Crypto-Asset and network; (ii) belong to the User and are under their control; (iii) are correct and have been verified by the User before confirmation of the Order.

(b) The User acknowledges that errors in the address/network/memo (tag) may result in the irretrievable loss of assets; the risk of such consequences shall be borne by the User.

7.5. Technological Risks and Irreversibility.

(a) Transactions in blockchain networks are irrevocable and irreversible. The speed/cost/possibility depend on the rules and congestion of the respective network.

(b) The Network Fee, which is not set by CityPay and is dynamic in nature, shall apply to External Transfers; the estimate of the fee prior to confirmation of the Order is indicative.

(d) The User accepts the risks of technical network failures, blockchain congestion, suspension of validator operations and other events beyond CityPay’s control.

7.6. Access Security.

The User shall ensure the confidentiality of the Authorization Means, shall not transfer access to third parties, shall use reliable security settings for devices/browser and shall immediately notify CityPay of any compromise.

7.7. Use through Third-Party Interfaces

The User confirms that the CityPay Crypto-Wallet may be used through the software products and user interfaces of third parties (CityPay’s partners).

The User understands that:

• the specifics of the partner’s user interface do not constitute a breach of CityPay’s obligations;

• information is displayed within the framework of the integration;

• the technical implementation of the interface does not affect the legal nature of the relationship between the User and CityPay.

7.8. Communications

The User shall independently monitor the information and notifications displayed in the interface through which the CityPay Crypto-Wallet is used.

Posting of information in such interface shall be deemed due notice to the User, unless otherwise provided for by legislation.

7.9. Full Familiarization.

The User confirms that they:

• have familiarized themselves with the terms of the Offer;

• understand the nature of the Services provided;

• accept the custodial storage model;

• are aware of the technological and legal risks associated with the use of Crypto-Assets.

7.10. Breach of Warranties.

A breach of any of the representations/warranties set out in this Section shall constitute a material breach of the Contract and shall give CityPay the right, to the extent permitted by law and the Offer, to suspend/refuse transactions, freeze assets/access, unilaterally terminate the Contract, as well as demand compensation for losses and the application of other measures provided for by legislation.

8 MATERIAL TERMS OF EXECUTION OF ORDERS

8.1. Moment of Performance by CityPay for “Deposit” (Crediting) Operations.

8.1.1. CityPay’s obligation to credit Crypto-Assets shall be deemed performed from the moment the receipt of the respective transaction is reflected in the internal accounting of CityPay’s custodial infrastructure after the requirements of the respective network and internal security checks have been met, including, where necessary: the minimum number of network confirmations, verification of the correctness of the selected network/asset/memo (tag), as well as the implementation of measures to counter money laundering, terrorist financing and financing of proliferation of weapons of mass destruction (AML/CFT/FP).

8.1.2. Prior to the moment specified in clause 8.1.1, crediting may be temporarily suspended until the identified risks/non-compliances are remedied or additional information/documents are received from the User.

8.2. Moment of Performance by CityPay for Intra-System Transfers.

8.2.1. CityPay’s obligation shall be deemed performed at the moment of the internal record (posting) in CityPay’s accounting systems with the simultaneous debiting of the Crypto-Asset from the sender and crediting to the recipient.

8.2.2. No CityPay Fee shall be charged, and no Network Fee shall apply to Intra-System Transfers.

8.3. Moment of Performance by CityPay for External Transfers.

8.3.1. CityPay’s obligation for an External Transfer shall be deemed performed at the moment the transaction is transmitted to the respective blockchain network (assignment of a transaction identifier/TxID with this event being recorded in CityPay’s logs).

8.3.2. From that moment, all risks associated with the confirmation of the transaction, the time of inclusion in a block, the possible retransmission of the transaction to the network due to protocol conditions and other network events shall pass to the User.

8.3.3. The Network Fee for the External Transfer shall be deducted from the User by CityPay and then paid to the respective network in accordance with the procedure established by Section 5 of this Offer; the actual amount may differ from the preliminary estimate due to network dynamics.

8.4. Grounds for Suspension/Refusal of Execution.

An Order may be suspended/rejected, and assets temporarily blocked, if:

(a) the Order does not meet the network’s requirements (e.g., the network/asset/address is incorrectly specified or a memo/tag is mandatory but not provided);

(b) AML/CFT/FP risks, sanctions risks or links to high-risk sources are identified;

(c) the information requested for identification, verification of the source of funds/assets is absent/insufficient, including refusal to complete a KYC questionnaire or failure to provide information requested by CityPay as part of identification;

(d) there is a technical incident or suspicion of compromise of authorization means;

(e) an order of an authorized body has been received or the law so requires.

Information on the current status of the Order shall be displayed in the interface through which the CityPay Crypto-Wallet is used.

8.5. Irreversibility and Impossibility of Revocation.

8.5.1. External transactions in blockchain networks are irrevocable and irreversible.

8.5.2. Intra-System Transfers may be cancelled by CityPay only before the moment of the internal posting; after the debit/credit has been reflected, cancellation is impossible, except for the correction of an obvious technical error of CityPay.

8.6. Service Availability.

8.6.1. CityPay shall take reasonable measures to ensure the stable operation of the custodial infrastructure.

8.6.2. CityPay does not guarantee the uninterrupted and error-free operation of the service, given its dependence on:

• blockchain networks,

• data centres,

• communication channels,

• third-party technology providers.

8.6.3. Temporary unavailability of the Crypto-Wallet, delay in displaying the balance or transaction history shall not in itself indicate the loss of Crypto-Assets.

8.6.4. In the event of technical failures, the procedure established by clause 4.17 of this Offer shall apply.

8.7. Notification Procedure.

The statuses of Orders (accepted, in processing, executed/TxID, rejected, suspended) shall be displayed in the user interface through which the CityPay Crypto-Wallet is used.

Separate written notifications may not be sent, unless otherwise provided for by law.

8.8. Precedence of Law and Orders.

In the event of a conflict between the terms of the Order and the mandatory requirements of the legislation of the Republic of Uzbekistan/orders of authorized bodies, execution shall be carried out to the extent strictly required by such legislation/orders.

8.9. Execution Period.

8.9.1. The usual period for execution of Orders for “sending”, “receipt (deposit)” and “intra-system transfer” operations shall be no later than twenty-four (24) hours respectively:

— for “sending” — from the moment the Order is registered in CityPay’s system;

— for “deposit” — from the moment the transaction is received on the network at an address maintained by CityPay, subject to the fulfilment of the network’s requirements and internal checks;

— for “intra-system transfer” — from the moment the Order is registered.

8.9.2. For the period of lawful suspension in accordance with clause 8.4 (including AML/CFT/FP checks, orders of authorities and other grounds provided for by law), the running of the said period shall be suspended until the grounds for suspension are eliminated.

8.10. Limits and Refusal to Accept/Execute.

Transactions resulting in the Limits being exceeded shall not be accepted or shall be suspended. For incoming transactions exceeding 20,000 USDT, clause 4.5.4 and, where necessary, clause 4.16 shall apply. For transactions in other assets, limit control shall be carried out based on the USDT equivalent at the time the transaction is registered.

9 LIMITATIONS AND LIABILITY

9.1. General Principle.

The Services are provided “as is” within the functionality described in the Offer (custodial storage, receipt, sending/transfer). To the extent permitted by the legislation of the Republic of Uzbekistan, CityPay shall be liable only for direct actual damage caused to the User as a result of culpable (intent or gross negligence) acts/omissions of CityPay. Liability for lost profits, moral harm, indirect/consequential damages and punitive sanctions is excluded.

CityPay’s liability for the consequences of technical failures caused by the fault of CityPay shall be determined exclusively in accordance with clause 4.17 of this Offer.

9.2. Circumstances for which CityPay is Not Liable.

CityPay shall not be liable, inter alia, for:

(a) the User’s acts/errors (incorrect address, choice of network/asset, absence of a mandatory memo/tag, sending of an unsupported asset, compromise of authorization means, malware on devices, etc.);

(b) the operation of blockchain networks (congestion, changes in network rules and fees, delays in inclusion of transactions in a block, forks and other protocol-specific features);

(c) the Network Fee and its amount/method of deduction: it is determined by the rules of the respective network, deducted by CityPay from the User and then paid to the network itself on behalf of CityPay;

(d) the external infrastructure of third parties (communications/data centre providers, certification services, KYC/AML verification providers, postal and SMS operators, etc.);

(e) lawful restrictions and requirements of authorized bodies, as well as measures to counter money laundering, terrorist financing and financing of proliferation of weapons of mass destruction (AML/CFT/FP), as a result of which a transaction is suspended/rejected/assets are temporarily frozen;

(f) temporary unavailability of the CityPay Crypto-Wallet, if such unavailability is caused by scheduled maintenance, security incidents, failure of external infrastructure or other circumstances specified in Sections 8 and 10;

(g) volatility of the value of Crypto-Assets and any losses due to changes in their market price;

(h) non-crediting, inability to use, absence of confirmed value or liquidity, or impossibility of technical return of an Unsupported Crypto-Asset, if the User or another sender has sent another Crypto-Asset, used an unsupported blockchain network, an incorrect address or failed to specify a mandatory memo, tag or other requisite contrary to the information and warnings provided by CityPay.

CityPay’s support for a respective blockchain network for a specific crypto-asset does not mean that CityPay supports all crypto-assets and tokens that can technically operate or be sent on such network.

CityPay shall not be liable for restrictions imposed by the software code of an Unsupported Crypto-Asset, its issuer, a smart contract or the respective blockchain network, if such circumstances are beyond CityPay’s reasonable control.

9.3. Irreversibility of Transactions.

External transactions in blockchain networks are irrevocable after their transmission to the network. CityPay is not obliged to and, as a rule, cannot cancel or return such a transaction. The User shall bear the risks of specifying incorrect parameters.

9.4. Limitation of Liability.

9.4.1. CityPay’s aggregate liability for each transaction shall be limited to the lesser of the following:

(a) the volume of the respective Crypto-Asset unlawfully debited as a result of CityPay’s confirmed fault; or

(b) the amount of direct actual damage proven by the User and directly causally related to CityPay’s culpable actions.

9.4.2. In the event of a technical failure caused by the fault of CityPay, the maximum scope of liability shall be limited to the restoration of correct accounting or the crediting of an equivalent quantity of the respective Crypto-Asset.

9.4.3. Compensation for changes in the market value of the Crypto-Asset shall not be made.

9.5. Actions of Third Parties.

CityPay shall not be liable for acts/omissions of third parties not under its control (owners of external addresses, network/communications providers, banks, payment systems, verification services, etc.), or for consequences occurring after CityPay’s proper performance of its obligations under the Order.

9.6. Execution Timeframes.

The period for execution of “sending”, “receipt (deposit)” and “intra-system transfer” operations shall be no later than twenty-four (24) hours in accordance with the procedure established by clause 8.9. A delay in confirmation specifically in the blockchain network (after transmission of the transaction to the network) and/or a lawful suspension on the grounds set out in clause 8.4 shall not give rise to liability of CityPay.

9.7. Investment/Brokerage/Insurance Disclaimers.

CityPay does not provide investment, tax or legal advice; is not a broker/dealer/bank; the accounting of Crypto-Assets is not a bank deposit and is not covered by the deposit guarantee system. Any information on the Site is for reference purposes only.

9.8. Indemnification of CityPay.

The User undertakes to indemnify CityPay for documented losses, expenses and fines arising as a result of the User’s violation of the law and/or the terms of the Offer (including non-compliance with AML/CFT/FP requirements, provision of inaccurate data, unauthorized use of the service), to the extent permitted by the legislation of the Republic of Uzbekistan.

10 FORCE MAJEURE (CIRCUMSTANCES OF INSURMOUNTABLE FORCE)

10.1. Definition and General Principle.

The Parties shall be released from liability for the full or partial non-performance of this Offer if such non-performance is caused by circumstances arising after acceptance, beyond the will of the Parties and outside their reasonable control (hereinafter — “Force Majeure”), provided that reasonable measures are taken to mitigate the consequences.

10.2. List of Force Majeure Events.

Force Majeure shall include, in particular: natural disasters; epidemics/pandemics and mandatory acts of health authorities; wars, terrorist acts, armed conflicts, mass disturbances, strikes; mandatory acts/decisions of state bodies, changes in legislation rendering performance illegal or effectively impossible; prolonged accidents/interruptions of power systems, communications, data centres, large-scale failures of Internet infrastructure; systemic technical incidents of blockchain networks (mempool congestion, stoppage/defect of protocol, forks, “51%+1” attacks, etc.) that are not dependent on CityPay. A change in the market value of Crypto-Assets shall not, in and of itself, constitute Force Majeure.

10.3. Notification Procedure.

10.3.1. Upon the occurrence of Force Majeure, CityPay shall post information on the nature and anticipated duration of such circumstances:

• on the official website of CityPay; and/or

• in the interfaces through which the CityPay Crypto-Wallet is used.

10.3.2. Posting of such information shall be deemed due notice to Users. Individual distribution of messages shall not be carried out, unless otherwise required by legislation.

10.4. Confirmation.

The fact and duration of Force Majeure may be confirmed by documents of competent authorities (including the Chamber of Commerce and Industry of the Republic of Uzbekistan) and other proper evidence (official statements of regulators/infrastructure providers, public reports of network failures, etc.).

10.5. Consequences.

For the duration of Force Majeure, the performance of the affected obligations under the Offer shall be suspended for the period of such circumstances and a reasonable time for the elimination of their consequences. The timeframes for performance shall be extended proportionately. Monetary obligations arising before the occurrence of Force Majeure shall remain in force if their performance has not become illegal or objectively impossible.

10.6. Mitigation and Resumption.

10.6.1. The Party invoking Force Majeure shall take reasonable and proportionate measures to mitigate the consequences (damage) and restore the performance of obligations under this Offer.

10.6.2. CityPay, within the limits of technical capability and in the absence of prohibition by law/orders of authorized bodies, shall take measures to ensure the safekeeping of Users’ Crypto-Assets in the custodial infrastructure for the duration of Force Majeure.

10.6.3. Upon the cessation of the Force Majeure circumstances, CityPay shall post information on the resumption of normal operations and (where necessary) on the amended processing times for transactions:

• on the official website of CityPay; and/or

• in the interfaces through which the CityPay Crypto-Wallet is used.

10.6.4. Posting of information in accordance with clause 10.6.3 shall be deemed due notice to Users.

10.7. Prolonged Force Majeure.

If Force Majeure continues for more than thirty (30) consecutive calendar days, either Party shall be entitled to terminate the Contract unilaterally without penalties by posting the relevant information on the Site and/or in the interfaces through which the CityPay Crypto-Wallet is used. In such case, CityPay shall complete the operations permitted by law and technically possible for the return to the User of the Crypto-Assets belonging to them in a manner not prohibited by law and orders of authorities, taking into account the applicable restrictions.

10.8. Precedence of Mandatory Norms and Time.

Nothing in this Section shall limit CityPay’s performance of mandatory requirements of the legislation of the Republic of Uzbekistan and orders of authorized bodies. The periods specified in this Section shall be calculated according to Tashkent time (UTC+5), unless expressly stated otherwise.

11 PERSONAL DATA

11.1. Legal Grounds for Processing.

Processing of the User’s personal data (hereinafter — “PD”) shall be carried out by CityPay in accordance with the legislation of the Republic of Uzbekistan, including the Law of the Republic of Uzbekistan “On Personal Data”, as well as the laws on countering the legalization of proceeds from crime, the financing of terrorism and the financing of proliferation of weapons of mass destruction, on the following grounds:

(a) performance of this Offer — provision of access to the CityPay Crypto-Wallet, accounting of Crypto-Assets, receipt and sending of Crypto-Assets, display of transaction statuses in the service usage interfaces;

(b) compliance with legal requirements — identification (KYC), compliance control under AML/CFT/FP and sanctions, storage of documents and logs, responses to requests of authorized bodies.

11.2. Purposes of Processing.

PD shall be processed to the extent necessary for:

(a) registration of the User and provision of access to the CityPay Crypto-Wallet (including through partners’ interfaces);

(b) execution of Orders (receipt/sending of Crypto-Assets), display of transaction statuses in the service usage interfaces;

(c) conduct of identification/verification (KYC), including verification of documents/identity, sanctions and other compliance screening;

(d) prevention of fraud, ensuring security, event logging and incident investigation;

(e) fulfillment of lawful requests of authorized bodies;

(f) improvement of service quality and stability of the Site based on anonymized/aggregated data;

(g) notification of the User of material changes to the terms of service, including the posting of a new version of the Offer, by means of posting information on the Site and/or through the User Interface.

11.3. Composition of PD and Sources.

The following may be processed:

(a) identification data: full name, date of birth, citizenship, TIN/PINFL, details of identity document;

(b) contact data: telephone, e-mail, address of residence/stay;

(c) data on transactions/Orders: asset/network, volumes, sender/recipient addresses, TxID/hash, statuses, applied network fees;

(d) technical data: IP address, date/time, information on browser/device, cookies/session tokens, authorization and confirmation logs;

(e) results of compliance checks (sanctions screening, signs of high-risk sources) — to the extent provided for by law;

(f) correspondence and support enquiries.

Sources: the User themselves; authorized KYC/AML verification providers; publicly available and/or state registers within the limits of the law; CityPay’s technical systems.

11.4. Transfer to Third Parties.

PD shall not be disclosed to third parties, except in cases provided for by law and/or this Offer, including:

(a) identification/verification (KYC), sanctions and compliance screening providers;

(b) IT providers (data centres, clouds, security means) to the extent necessary for the provision of the Services;

(d) authorized state bodies — in the cases and procedure established by legislation.

Transfer shall be carried out subject to confidentiality and security measures.

11.5. Localization and Cross-Border Transfer.

Collection, systematization and storage of PD of citizens of the Republic of Uzbekistan shall be carried out in databases located in the territory of the Republic of Uzbekistan to the extent established by law. Cross-border transfer of PD shall be allowed only in the cases and procedure provided for by legislation.

11.6. Retention Periods.

PD shall be stored for the duration of the Contract, and after its termination — for the periods established by legislation and/or necessary for the protection of the rights and legitimate interests of CityPay (including AML/CFT/FP requirements and limitation periods). The minimum period for the storage of documents and transaction logs shall be no less than five (5) years or another period as required by law.

11.7. Security of PD.

CityPay shall apply the necessary organizational and technical measures for the protection of PD: access control, encryption, event logging and monitoring, perimeter protection, vulnerability management, backup, personnel training, access audit, etc. The User shall comply with the requirements of clause 4.3 and Section 6.

11.8. Cookies and Technical Tracking.

The Site uses cookies and similar technologies (local storage, web beacons) for login, saving of settings, security and analytics in anonymized form. Cookie management is in browser settings.

11.9. Rights of the Data Subject and Procedure for Exercise.

The User shall have the right, to the extent established by legislation:

(a) to receive information about their PD and the purposes/grounds for its processing;

(b) to demand rectification (updating, correction) of PD if it is incomplete or inaccurate;

(d) to withdraw consent — for those purposes where consent is the basis for processing (does not affect the lawfulness of processing before withdrawal and does not apply to processing mandatory by law/Contract, including AML/CFT/FP).

Requests shall be sent via the contacts on the Site. CityPay shall consider them within the timeframes established by law, if necessary — after identification of the applicant.

12 AMENDMENT AND TERMINATION OF THE CONTRACT

12.1. Procedure for Amendment of the Offer.

(a) CityPay shall have the right to unilaterally amend, supplement or restate this Offer by posting the updated version on the Site.

(b) The new version shall enter into force on the date of its posting on the Site, unless a different date is expressly stated in the text of the Offer.

(c) Information on amendments may additionally be brought to the User’s attention by means of notifications in the interfaces of the software products of CityPay’s partners through which the CityPay Crypto-Wallet is used.

(d) Continued use of the CityPay Crypto-Wallet after the effective date of the new version of the Offer shall be deemed the User’s consent to the amended terms.

12.2. Material Amendments

(a) CityPay shall have the right to amend any provisions of the Offer, including terms on the scope of Services, the procedure for their provision, the allocation of risks, the grounds for suspension and blocking, limits, technical requirements and other parameters.

(b) Material amendments may, in particular, include:

• introduction of a CityPay fee;

• change in the asset storage model;

• change in the procedure for blocking, freezing or returning assets;

• change in limits;

• amendments caused by the requirements of legislation or the regulator.

(c) In the event of disagreement with the amendments, the User shall be obliged to cease using the CityPay Crypto-Wallet and withdraw the Crypto-Assets belonging to them before the date of cessation of use.

12.3. Amendments Caused by Law or Risks

If amendments are caused by:

• requirements of legislation;

• orders of authorized bodies;

• sanctions restrictions;

• AML/CFT/FP measures;

• security incidents;

• a threat to the stability or integrity of the infrastructure,

CityPay shall have the right to apply such amendments immediately, without prior notification of the User.

12.4. Termination at CityPay’s Initiative.

CityPay shall have the right to unilaterally suspend servicing and/or terminate the Contract in whole or in part if:

(a) the User violates legislation or the terms of the Offer;

(b) the User has not undergone KYC or has refused to provide the requested information;

(d) a mandatory order of an authorized body is received;

(e) there are technical incidents or security threats;

(f) CityPay’s license is terminated or restricted;

(g) servicing the User creates compliance risks or risks of liability for CityPay.

In cases where this is permitted by legislation, prior notification may not be sent.

12.5. Termination at the User’s Initiative.

The User shall have the right to cease using the Services at any time.

Before ceasing use, the User shall be obliged to transfer all Crypto-Assets belonging to them to an external address, unless otherwise restricted by law or AML/CFT/FP measures.

12.6. Consequences of Termination.

(a) From the date of termination of the Contract, CityPay shall cease execution of new Orders of the User.

(b) CityPay shall have the right to retain the User’s access to information on asset balances exclusively to the extent necessary for their lawful withdrawal.

(c) If assets are frozen by virtue of law, orders of authorities or AML/CFT/FP measures, their return shall be effected only after the respective restrictions are lifted.

(d) Obligations to store information, protect personal data, comply with legal requirements and provisions on liability shall survive termination of the Contract.

12.7. Revocation of the Offer.

CityPay shall have the right to revoke this public offer for new users at any time by removing it from the Site.

The revocation of the Offer shall not affect previously existing contractual relations, unless they are terminated in accordance with the established procedure.

13 FINAL PROVISIONS

13.1. Applicable Law.

This Offer, the Contract and the relations of the Parties shall be governed by the legislation of the Republic of Uzbekistan.

13.2. Dispute Resolution.

(a) The Parties shall observe the pre-court procedure: a claim shall be sent electronically to CityPay’s e-mail. The period for consideration of a claim shall be thirty (30) calendar days.

(b) If no agreement is reached, the dispute shall be subject to resolution in the competent courts at the place of registration of CityPay, unless mandatory norms prescribe otherwise.

13.3. Entry into Force and Term.

(a) This Offer shall enter into force from the moment of its posting on the Site and shall remain in effect until its revocation or replacement by a new version.

(b) The Contract between CityPay and the User shall be deemed concluded from the moment the User familiarizes themselves with this Offer and commences use of the CityPay Crypto-Wallet.

(c) Continued use of the CityPay Crypto-Wallet after the publication of a new version of the Offer shall be deemed the User’s consent to its terms.

(d) The Contract shall be valid indefinitely until its termination in accordance with the procedure established by Section 12.

13.4. Electronic Form and Legally Significant Messages.

(a) The Parties recognize the legal force of electronic documents, transaction logs, authorization logs, technical metadata and other electronic records generated within CityPay’s infrastructure, to the extent permitted by the legislation of the Republic of Uzbekistan.

(b) Notifications and legally significant messages may be brought to the User’s attention by posting on the Site and/or by displaying notifications in the software products and user interfaces of CityPay’s partners.

(c) Dates and periods specified in the Offer shall be calculated according to Tashkent time (UTC+5), unless expressly stated otherwise.

13.5. Contact Details.

JV LLC “City Pay Gate” (TIN 311606433)

Address: Building 53B, Shota Rustaveli Street, Mukhandislar MFY, Yakkasaray District, Tashkent, 100100, Republic of Uzbekistan

Website: [https://citypay.uz](link)

E-mail: [uzsupport@citypay.io](link)

13.6. Language.

The Offer is provided in Uzbek, Russian and English. In the event of discrepancies, the Russian version shall prevail, unless otherwise expressly stated in the notice of publication of the version.

13.7. Entire Agreement.

13.7.1. This Offer, the Appendices hereto, the Privacy Policy, the Regulation on the Procedure for Refund, Cancellation, Suspension and Processing of Crypto-Assets, as well as other documents of CityPay posted on the Site and expressly governing the use of the CityPay Crypto-Wallet, constitute the entire agreement between the Parties and shall be interpreted and applied jointly.

13.8. Severability.

The recognition by a court of any provision of the Offer as invalid/ unenforceable shall not affect the validity of the remaining provisions. Such provision shall be interpreted/replaced to the maximum extent permitted by law to achieve the original purpose.

**Appendix 1 to the Public Offer of JV LLC “City Pay Gate” dated August 7, 2026**

SERVICES FOR CUSTODIAL STORAGE OF CRYPTO-ASSETS

AND THE PROCEDURE FOR CONDUCTING TRANSACTIONS

1. Description of Services

CityPay shall provide the User with services for the custodial storage of Supported Crypto-Assets, the maintenance of their internal accounting, as well as the execution of the User’s instructions for the receipt and movement of Supported Crypto-Assets within CityPay’s custodial infrastructure.

Access to the Services may be provided through the software products and user interfaces of CityPay’s partners. Unless otherwise expressly provided for by the respective contract or interface, such partner shall provide exclusively technical access to the Services, and the service provider and custodian of the Crypto-Assets shall be CityPay.

The following Services shall be provided under this Offer:

• the creation and maintenance of a custodial crypto-wallet for Supported Crypto-Assets (list — in Appendix 2), with the ability to view balances and transaction history;

• the receipt (crediting) of Crypto-Assets to addresses maintained by CityPay’s infrastructure;

• transfers of Crypto-Assets:

— intra-system (between wallets maintained by CityPay’s infrastructure) — without a CityPay fee and without a network fee;

— external (to addresses outside CityPay’s infrastructure) — with deduction of only the network fee of the respective network.

CityPay shall not charge a fee for the provision of the Services under this Appendix.

2. Terms and Conditions for Conducting Transactions (Receipt / Transfer)

2.1. Receipt (Deposit) of Crypto-Assets

(a) The User shall select the Supported Crypto-Asset and the corresponding supported blockchain network in the User Interface and use the up-to-date receipt details provided by CityPay — the address or QR code, and, where necessary, the memo, tag or other mandatory requisite. When sending a Crypto-Asset from an external wallet or service, the User shall be obliged to select, on the sender’s side, the same Crypto-Asset and the same blockchain network as indicated in CityPay’s User Interface.

(b) Crediting shall be effected after:

• receipt of the required number of confirmations of the respective blockchain network;

• technical identification by CityPay of the actually received Crypto-Asset, inter alia, on the basis of its Unique Technical Identifier, the blockchain network data and CityPay’s internal technical support parameters;

• the successful completion of checks provided for by legislation, CityPay’s internal AML/CFT/FP rules and sanctions control.

(c) The sending of a Crypto-Asset via an unsupported blockchain network, the use of an incorrect address, the absence or incorrect specification of a mandatory memo, tag or other requisite, as well as the sending of a different token instead of the Crypto-Asset selected in the User Interface, including a token with the same or similar name, ticker or logo, may result in non-crediting and the loss of the ability to dispose of the respective Crypto-Asset. CityPay shall not be obliged to restore such transactions.

(d) CityPay’s processing period — up to 24 hours from the moment the conditions of paragraph (b) are met, except for cases of additional checks, technical failures, scheduled maintenance or AML/CFT/FP measures, in which case the period may be extended for a reasonable time.

2.2. Intra-System Transfer

(a) It shall be initiated by the User through the partner’s interface by specifying the identifier/address of the recipient within CityPay’s infrastructure.

(b) No CityPay fee or network fee shall be charged.

(c) After the internal posting, the transaction shall be final and shall not be subject to cancellation, except for the correction of an obvious technical error of CityPay.

(d) Processing period — up to 24 hours.

(e) In the event of a technical failure or temporary unavailability, the execution period shall be suspended until such circumstances are remedied. In this case, the Crypto-Assets shall be preserved within CityPay’s custodial infrastructure.

2.3. External Transfer (to an external address)

(a) The User shall specify the asset, network and the recipient’s address (and, where necessary, the memo/tag).

(b) Before confirmation of the transaction, the estimated amount of the network fee and the total debit amount shall be displayed in the interface.

(c) The network fee shall be deducted by CityPay from the User and remitted to the respective network. The amount shall be determined by the network’s rules and may differ from the preliminary estimate due to network dynamics.

(d) After the transaction is transmitted to the network, the operation shall be irreversible. The speed and success of confirmation shall depend on the operation of the network and third-party infrastructure.

(e) CityPay’s processing period — up to 24 hours. Subsequent confirmation in the network shall not be dependent on CityPay.

(f) Minimum Sending Amount — the minimum permissible amount of an Order for the external sending of a Supported Crypto-Asset, which shall be:

- for TRX on the Tron network — the amount of TRX equivalent to 5 USDT;

- for other Supported Crypto-Assets — the amount of the respective Crypto-Asset equivalent to 10 USDT.

2.4. Cancellation, Refusal, Suspension

(a) Before the transaction is transmitted to the network, CityPay shall have the right to cancel or reject the transaction if there are grounds provided for by legislation and the Offer (including AML/CFT/FP, sanctions control, technical risks).

(b) After the transaction is transmitted to the network, cancellation shall be impossible. The deducted network fee shall not be subject to refund.

(c) CityPay shall have the right to request additional information or documents. The transaction may be suspended until they are provided.

(d) Information on the status of the transaction shall be displayed in the partner’s interface.

(e) In the event of a technical failure or the need to restore correct accounting, CityPay shall have the right to temporarily suspend transactions without incurring liability.

2.5. Execution Timeframes

(a) Transactions processed by CityPay shall, as a rule, be executed within up to 24 hours, unless otherwise determined by checks, technical circumstances or legal requirements.

(b) For external transfers, subsequent confirmations shall occur in accordance with the network’s rules and may take additional time.

2.6. Confirmation and Statuses

(a) Confirmation of the transaction shall be effected by the User through the partner’s user interface.

(b) The User shall have access to information on the transaction status, amounts, the deducted network fee, and for external transfers — the transaction identifier (TxID).

2.7. Additional Terms and Risks

(a) Only combinations of a Crypto-Asset and a blockchain network expressly specified in Appendix 2 and available for selection in CityPay’s User Interface shall be supported. Technical identification of the received token shall be carried out by CityPay, inter alia, on the basis of its Unique Technical Identifier.

Wrapped, bridge, derivative, synthetic and other third-party tokens shall not be supported, unless the respective token and blockchain network are expressly specified in Appendix 2 and CityPay’s User Interface.

(b) The User shall be obliged to independently verify the name of the selected Crypto-Asset, the blockchain network, the current address and the mandatory memo, tag or other requisite, and also ensure that the same Crypto-Asset and the same blockchain network as indicated in CityPay’s User Interface are selected on the sender’s side.

(c) If high-risk/prohibited sources are identified, the provisions of the Offer regarding suspension, return or freezing of assets shall apply.

(d) The procedure for dealing with technical failures shall be determined by the relevant provisions of the Offer.

2.8. Limits on Transactions (in USDT equivalent)

(a) single sending — up to 6,000 USDT;

(b) single receipt — up to 20,000 USDT;

(d) monthly aggregate volume — up to 100,000 USDT;

(e) maximum 30 transactions within 24 hours;

(f) The Minimum External Sending Amount shall be:

— for TRX on the Tron network — the amount of TRX equivalent to 5 USDT;

— for other Supported Crypto-Assets — the amount of the respective Crypto-Asset equivalent to 10 USDT.

If a transaction is executed in another asset, its volume for the purposes of the limits shall be recalculated into USDT at CityPay’s quotation at the time the transaction is registered.

Incoming transactions exceeding 20,000 USDT may be:

• returned to the sender (where technically possible) less the network fee,

• or suspended/frozen in the cases provided for by the Offer and legislation.

Control of limits shall be carried out according to Tashkent time (UTC+5).

**Appendix 2 to the Public Offer of JV LLC “City Pay Gate” dated August 7, 2026**

LIST OF SUPPORTED CRYPTO-ASSETS AND NETWORKS

1. List of Supported Crypto-Assets and Blockchain Networks

1.1. CityPay supports exclusively those combinations of Crypto-Assets and blockchain networks that are expressly specified in this Appendix and are available to the User in CityPay’s User Interface when generating receipt or sending details for a Crypto-Asset.

1.2. Support for a given Crypto-Asset on one blockchain network does not mean support for such Crypto-Asset on other blockchain networks, unless such networks are expressly specified in this Appendix and CityPay’s User Interface.

1.3. The coincidence of the name, ticker symbol, symbol, image or declared value of a digital unit with the name or designation of a supported Crypto-Asset shall not, in and of itself, mean that such digital unit is a supported Crypto-Asset.

1.4. Crypto-assets created by third parties, as well as wrapped, derivative, synthetic, bridge and other versions of Crypto-Assets, shall not be supported by CityPay, unless they are expressly included in this List and are available for selection in CityPay’s User Interface.

As of the date of publication, the following Crypto-Assets are supported:

1. BTC (Bitcoin) – BTC (Bitcoin) network

2. LTC (Litecoin) – LTC (Litecoin) network

3. ETH (Ethereum) – Ethereum (ETH) network

4. XRP (XRP Ledger) – XRP Ledger (XRP) network

5. SOL (Solana) – Solana (SOL) network

6. BNB (BNB Smart Chain / BSC) – BNB Smart Chain (BEP20) network

7.USDT (Tether USD) – Polygon (Polygon POS), Tron (TRC-20), Ton (TON), BNB Smart Chain (BEP20), Ethereum (ERC-20) networks

8. TON (Toncoin) – TON network

9. XAUT (Tether Gold) – Ethereum (ETH) network

10. TRX (Tron) – Tron (TRC-20) network

2. Fees and Internal Transfers

• For external transfers, only the network fee of the respective network shall be deducted (displayed before confirmation of the transaction). CityPay shall deduct the network fee from the User and remit it to the network.

• Transfers between CityPay wallets — no fee and no network fee.

3. Important Warnings for the User

• Always verify the asset, network and address before sending.

• Sending on a different network, to an incorrect address or without a mandatory memo/tag may result in irretrievable loss.

• Cross-chain bridges/swaps are not provided under the Offer.

• Technical requirements of the networks themselves (for example, minimum amount/“dust”, mandatory memo/tag) may apply.

• Processing of transactions by CityPay (receipt after network confirmations, intra-system and external transfers before broadcasting to the network) shall be performed within up to 24 hours; subsequent confirmations in the network shall depend on the rules of the respective network.

4. Minimum Receipt and Sending Amounts

Network Minimum Receipt Amount Crypto-Asset

BTC Bitcoin 0.0001 BTC

LTC Litecoin 0.001 LTC

ETH Ethereum 0.001 ETH

XRP XRP Ledger 1 XRP

SOL Solana 0.01 SOL

BNB BNB Smart Chain (BEP20) 0.01 BNB

TON TON 0.1 TON

USDT Ethereum (ERC-20) 1 USDT

USDT Tron (TRC-20) 1 USDT

USDT BNB Smart Chain (BEP20) 1 USDT

USDT Polygon (Polygon POS) 1 USDT

USDT TON 1 USDT

XAUT Ethereum (ERC-20) 0.0001 XAUT

TRX TRON (TRC-20) 1 TRX

Note:

Incoming transactions the amount of which is less than the established minimum receipt amount may not be subject to automatic crediting to the User’s Crypto-Wallet. CityPay does not guarantee the possibility of crediting, return or recovery of such transactions if this is technically impossible or economically inexpedient given the size of the network fee and the specifics of the respective blockchain network.

The minimum external sending amounts for Crypto-Assets shall be established as follows:

— for TRX on the Tron network — the amount of TRX equivalent to 5 USDT;

— for all other Supported Crypto-Assets — the amount of the respective Crypto-Asset equivalent to 10 USDT.

The equivalent in USDT shall be determined at the settlement rate displayed in CityPay’s User Interface at the moment the User confirms the sending Order. The applicable minimum amount shall be displayed to the User before confirmation of the transaction.

An Order for the external sending of a Crypto-Asset in an amount below the applicable minimum amount shall not be accepted by CityPay for execution.

5. Amendment of the List and Temporary Restriction of Transactions

5.1. CityPay shall have the right to amend the list of supported Crypto-Assets and blockchain networks, minimum amounts and other technical parameters in accordance with the procedure provided for by the Offer.

5.2. CityPay shall have the right to temporarily restrict the receipt or sending of a particular Crypto-Asset or the execution of transactions on a specific blockchain network in the event of a technical failure, scheduled maintenance, unstable operation or update of the blockchain network, the emergence of a security threat, termination of support by the technical service provider, as well as in cases provided for by legislation or the requirements of authorized state bodies.

5.3. Where it is necessary to take immediate measures to ensure security or comply with legislation, a temporary restriction may be imposed without prior notification to the User. Information on the restriction shall be posted in the User Interface or on CityPay’s Site within a reasonable period.

5.4. In the event of a planned termination of support for a Crypto-Asset or blockchain network, CityPay shall notify the Users and, where technically possible and permitted by legislation, shall provide a reasonable period for the disposal of the respective Crypto-Asset.

5.5. Amendments to minimum amounts and other technical parameters shall apply from the moment the updated version of this Appendix is posted, unless a different timeframe is expressly specified by CityPay.

5.6. The current version of this Appendix shall be posted on CityPay’s Site and shall form an integral part of the Public Offer.

The exclusive rights to the original content, structure and layout of this document belong to JV LLC “City Pay Gate”. Full or partial reproduction, copying, adaptation, distribution, publication or other use of this document without the prior written consent of JV LLC “City Pay Gate” is prohibited, except for cases expressly provided for by the legislation of the Republic of Uzbekistan. Infringement of exclusive rights shall entail liability in accordance with the legislation of the Republic of Uzbekistan.