User Agreement

1. General Provisions

This User Agreement governs the use of the PayHot technology platform, which is operated by HOT GATE TECHNOLOGY LTDA, CNPJ 67.633.679/0001-27, NIRE 33.2.1494553-4.

The Agreement applies to website visitors, registered users, Merchants, their representatives, Payers, payout recipients, and other persons who use PayHot interfaces.

By using the website, creating an account, submitting a Project for review, connecting to the API, creating a payment, making a payment through a payment form, or continuing to use the service after an updated version has been published, the User confirms that they have read and accept this Agreement.

PayHot provides software and technology infrastructure and is not a bank, credit institution, card issuer, payment system operator, or direct acquirer. All financial settlements are performed by independent Partner Providers.

2. Definitions

• PayHot / Platform — the website, Account, API, payment forms, applications, Telegram interfaces, and other software tools provided by the Operator.
• Operator — HOT GATE TECHNOLOGY LTDA.
• User — any person using the Platform, including a Merchant, Payer, and payout recipient.
• Merchant — a person or organization that connects a Project to the Platform to access payment methods and technology functions.
• Payer — a person who pays for a Merchant's goods, work, or services.
• Partner Provider — an independent bank, acquirer, payment institution, transfer operator, crypto-processing provider, payout provider, or another participant that performs a financial transaction.
• Payment Transaction — acceptance of a payment, transfer, refund, bulk payout, conversion, or another financial transaction performed by a Partner Provider through technical interaction with the Platform.
• Project — a website, application, Telegram bot, service, store, or another Merchant product submitted for review.
• Account — the protected part of the Platform containing settings, Projects, statuses, reports, and available functions.

3. Subject of the Agreement

The Operator provides access to technology functions that may include:

• account registration and management;
• adding and reviewing Projects;
• APIs, payment forms, links, and status notifications;
• routing requests to Partner Providers;
• displaying transactions, reports, limits, and technical errors;
• tools for accepting payments via the Faster Payments System, cards issued by Russian banks, international e-commerce payments, the ERIP system of the Republic of Belarus, cryptocurrency payments, recurring transactions, and bulk payouts, subject to the availability of a relevant partner and approval of the Project;
• anti-fraud tools, AML analysis, monitoring, and other risk-management functions;
• technical and operational support.

The specific set of functions is determined by the Project category, geography, review results, technical readiness, and the rules of Partner Providers.

4. Roles of PayHot and Partner Providers

PayHot enables technical interaction, transmission of requests, receipt of statuses, management interfaces, monitoring, and integration support. PayHot does not accept funds into its own bank balance for subsequent transfer to the User unless this is expressly provided for in a separate agreement and permitted by law.

Payment acceptance and processing, authorization, clearing, transfers, refunds, conversion, custody, and remittance of funds are performed by the relevant Partner Providers. The User's relationship with such a partner may be governed by separate terms that the User must comply with.

Availability of a method, fees, exchange rates, limits, reserves, holds, settlement periods, grounds for refusal, and required documents may be determined by the Partner Provider and may change in accordance with its rules and payment-system requirements.

5. Registration and User Requirements

To register, the User must have the necessary legal capacity and authority. A representative of an organization confirms their authority to act on its behalf.

The User must provide accurate and up-to-date information. It is prohibited to create an account using another person's information, conceal a beneficial owner, provide forged documents, or use an account for a third party's activities without approval.

PayHot may request additional information and verify identity, authority, the Project, traffic sources, source of funds, and business model either independently or through partners.

6. Project Review

Each Project is reviewed before connection and may be reviewed again during operation. The review considers the product content, website or bot, geography, traffic sources, average transaction value, turnover, refunds, complaints, and other risks.

The outcome may be approval, approval subject to restrictions, a request for changes, refusal, temporary suspension, or a change to the available methods. Approval of one Project does not automatically extend to the User's other Projects.

The User must notify PayHot in advance of any material change in activities, domain, product range, owner, legal structure, traffic sources, geography, or payment scenario.

7. Account and Security

The User must:

• use a unique password and available additional verification methods;
• not disclose login credentials, passwords, API keys, or verification codes to third parties;
• restrict employee permissions according to the need-to-know principle;
• keep keys out of public repositories, publicly accessible documents, and shared chats;
• immediately report any suspected compromise or unauthorized action;
• verify payment details and wallet addresses before confirming a withdrawal.

Actions performed using valid credentials and confirmations may be deemed actions of the User until PayHot is notified of a compromise, unless otherwise provided by law.

8. Integration and Use of the API

The Merchant is responsible for correct integration, the security of its own system, safekeeping of keys, verification of notification signatures, and processing of statuses. Goods or services must not be released solely because the customer has returned to a success page or presented a screenshot; a confirmed status must be obtained through the designated interface.

It is prohibited to create excessive load, circumvent restrictions, test for vulnerabilities without written permission, interfere with the Platform, tamper with requests, or use the API for purposes not approved by PayHot.

9. Payment Methods

Depending on the Project, available methods may include the Faster Payments System, Mir, Visa, Mastercard, and Maestro cards issued by Russian banks, international e-commerce, the ERIP system of the Republic of Belarus, cryptocurrencies, recurring payments, and bulk payouts. This list is not guaranteed and depends on partner infrastructure.

A partner may temporarily suspend a method, change routing, or decline a transaction for reasons related to security, law, limits, sanctions restrictions, technical failure, suspected fraud, or a breach of rules.

10. Fees, Exchange Rates, Limits, and Settlements

Fees and other commercial terms are provided in the Account, in a message from a manager, in an annex to an agreement, or in a separate offer. Terms may vary by Project, method, currency, geography, and risk category.

For conversion, the rate determined by the relevant partner or an agreed source is applied. The payout amount may reflect fees, network costs, refunds, reserves, chargebacks, and other agreed deductions.

Settlements are performed by Partner Providers. The time required to credit funds depends on banks, payment systems, the blockchain network, reviews, and other participants. Displaying an amount in the Account does not always mean that the funds are finally and irrevocably available.

11. Refunds, Disputes, and Chargebacks

The Merchant independently determines and performs the terms of sale, delivery, provision of services, and refunds in its relationship with the Payer. PayHot is not the seller and is not responsible for the quality of goods or services.

A refund is processed through the available interface and a Partner Provider. Availability, timing, and cost of a refund depend on the original method. In the event of a dispute or chargeback, the Merchant must promptly provide documents confirming the order, the customer's consent, and performance of the obligations.

Amounts relating to disputes, refunds, penalties, and partner expenses may be deducted from available settlements where this is provided for by the agreed terms and applicable law.

12. Recurring Payments

The Merchant may use recurring charges only with the Payer's explicit consent and after disclosing the amount, frequency, cancellation procedure, and renewal terms before the first payment. The Merchant must provide an easy way to cancel the subscription and comply with the requirements of the payment partner and applicable law.

13. Bulk Payouts

The bulk-payout function is available after separate approval. The Merchant is responsible for the lawful basis of a payout, accuracy of the payment details, the recipient's consent to data processing, and compliance with tax and other obligations.

PayHot and the partner may request the purpose and source of funds and information about the recipient, set limits, and suspend suspicious payouts.

14. Cryptocurrency Transactions

Supported assets and networks are determined separately. The User must select a compatible network and verify the address. Blockchain transactions are generally irreversible, and an erroneous transfer may result in loss of funds.

Transactions and wallets may be subject to AML analysis. Where there is elevated risk, additional information may be requested, and a transaction may be delayed, declined, or returned if a return is technically and legally possible.

The User independently considers the legal, tax, market, technology, and custody risks of digital assets in the User's jurisdiction.

15. Prohibited Use

The Platform must not be used for activities that violate the law, third-party rights, the rules of Partner Providers, or payment-system requirements, including:

• fraud, money laundering, terrorist financing, sanctions evasion, or concealment of the source of funds;
• sale of prohibited goods or services, unlawful trafficking in personal data, malware, or unauthorized-access tools;
• fictitious transactions, cashing-out schemes, testing stolen payment data, or transactions with no genuine economic purpose;
• misleading a Payer about the seller, goods, price, subscription, or refund;
• use of a Project, domain, or business category that has not passed review;
• conduct that creates excessive levels of complaints, refunds, disputes, fraud, or regulatory risk.

PayHot may impose additional restrictions for particular categories and geographies.

16. Anti-Fraud, AML, and Reviews

PayHot and its partners may analyze every transaction using rules, AI models, and external sources. The analysis may examine payment-behavior anomalies, technical signals, links between transactions, wallet risk, sanctions indicators, and other factors.

The User must provide documents and explanations upon request. Certain functions or transactions may be restricted until a review is completed. Detailed criteria are not disclosed because disclosure would reduce the effectiveness of the protective measures.

17. Intellectual Property

Rights to PayHot software code, design, databases, documentation, trade designations, and other materials belong to the Operator or their respective right holders. The User is granted a limited, non-exclusive, and revocable right to use the functions under this Agreement.

It is prohibited to copy, sell, decompile, modify, create derivative solutions, or use PayHot designations without permission, except where expressly permitted by law.

18. Personal Data

Data processing is governed by the Privacy Policy and Cookie Policy. The Merchant is independently responsible for the lawfulness of transferring its customers' and payout recipients' data to PayHot and for providing the required notices and establishing the appropriate legal bases.

19. Service Availability and Changes

PayHot seeks to maintain stable operation but does not guarantee absolute continuity. Scheduled maintenance, incidents, and failures involving partners, banks, communications, blockchain networks, or external services may occur.

The Operator may change the interface, documentation, API, and available functions. A reasonable transition period may be provided for material incompatible changes where technically and legally possible.

20. Limitation of Liability

PayHot is responsible for its own actions within the limits of applicable law and agreed obligations, but is not liable for:

• the Merchant's actions, the quality of goods, performance of an order, or the relationship between the Merchant and the Payer;
• decisions or failures of an independent Partner Provider, bank, payment system, blockchain, or telecommunications network;
• incorrect payment details, wallet addresses, integration settings, or actions of the User's authorized persons;
• losses caused by force majeure, binding requirements of authorities, sanctions, or changes in law;
• indirect losses, loss of profit, or loss of data, except where such limitation is prohibited by law.

Nothing in this Agreement limits liability that cannot be excluded under mandatory law, including consumer rights where applicable.

21. Suspension and Termination

PayHot may restrict or terminate access in the event of a breach of this Agreement, suspected fraud, failure to provide documents, a requirement from a partner or authority, elevated risk, account compromise, or technical necessity.

The User may stop using the Platform and request account closure after all obligations have been completed. Termination does not cancel obligations relating to disputes, refunds, fees, confidentiality, data retention, or other provisions that by their nature continue to apply.

22. Changes to the Agreement

A new version is published on the website and enters into force on the stated date. Material changes may also be communicated through the Account, email, or Telegram. Continued use constitutes acceptance of the new version unless otherwise provided by law.

23. Governing Law and Dispute Resolution

This Agreement is governed by the laws of the Federative Republic of Brazil. The parties shall seek to resolve a dispute by a written claim. If the dispute is not resolved, it shall be heard by a competent court in the city of Rio de Janeiro, State of Rio de Janeiro, subject to mandatory rules on jurisdiction and consumer protection where applicable.

24. Contact and Company Details

HOT GATE TECHNOLOGY LTDA

CNPJ: 67.633.679/0001-27

NIRE: 33.2.1494553-4

Address: Avenida Marechal Câmara, 160, Sala 1107, Centro, Rio de Janeiro, RJ, CEP 20.020-907, Brazil

Email: team@pay.hot

Website: https://pay.hot