Exchange Rules

Key terms for creating, funding, and processing exchange requests through the Bablos service.

Bablos Exchange Rules

These Rules govern the use of the Bablos service, the creation and processing of exchange requests, and the rights and responsibilities of both the user and the service.

By creating an exchange request, the user confirms that they have read and accepted these Rules.

1. General Provisions

Bablos provides users with the technical ability to create exchange requests for assets and payment methods available on the website.

The list of available exchange directions, exchange rate, reserve, minimum and maximum amount, and any additional terms applicable to a specific exchange are displayed on the website when the request is created.

The terms of each individual request are based on the information available to the user before confirmation.

2. Creating an Exchange Request

To perform an exchange, the user:

  • selects an exchange direction;

  • enters the amount;

  • provides the required payment or wallet details;

  • checks the entered information;

  • confirms the request;

  • makes payment according to the service instructions.

The user is responsible for the accuracy of the details provided.

Before confirming a request, the user should carefully verify the wallet address, account number, banking details, digital asset network, and any other relevant information.

3. Exchange Rate

The exchange rate is displayed on the website when the request is created.

Depending on the selected direction, the rate may be:

  • fixed for a specified period;

  • calculated when payment is received;

  • recalculated according to the terms of the selected exchange direction.

The applicable rate-fixing method is shown in the request interface or in the terms of the selected direction.

Changes in the market rate after an exchange has been completed do not in themselves constitute grounds for recalculating a completed request.

4. Payment of the Request

The user must make payment using the details and instructions provided in the exchange request.

Users are advised not to:

  • pay one request using several separate transfers without prior approval;

  • send an amount that materially differs from the amount stated in the request;

  • use an incorrect digital asset network;

  • make payment using outdated payment details;

  • reuse payment details from a previous request unless the service explicitly confirms that they remain valid.

If the actual payment amount or payment details differ from those stated in the request, additional verification may be required.

5. When Payment Is Considered Received

For bank and electronic payments, payment is considered received when the funds are actually credited to the payment details specified by the service.

For digital currencies, the required number of network confirmations may be necessary.

A receipt, screenshot, or transaction identifier provided by the user does not by itself confirm that the service has actually received the funds.

6. Processing the Request

After payment has been received and any required checks have been completed, the service sends the corresponding funds or assets to the details provided by the user.

Processing time may depend on:

  • the selected exchange direction;

  • the operation of banks and payment systems;

  • network congestion;

  • the time required to obtain blockchain confirmations;

  • whether additional verification is required;

  • other circumstances beyond the service’s control.

Bablos aims to process requests without unjustified delays.

7. Incorrect Payment Details

The user must ensure that all payment details are correct before confirming and paying the request.

If the service has sent funds to the details specified by the user in a confirmed request, the service’s obligation is considered fulfilled to the relevant extent.

If an error is discovered before the service sends the funds, the user should contact support as soon as possible.

Whether the details can be corrected depends on the request status, technical feasibility, and security requirements.

8. Incorrect Payment Amount

If the amount actually received differs from the amount stated in the request, the service may:

  • recalculate the request;

  • request an additional payment;

  • offer a refund;

  • agree with the user on another way to complete the transaction.

The decision depends on the exchange direction, the size of the discrepancy, and the technical possibility of processing the payment.

9. Reserve

Exchanges are processed within the available reserve.

The reserve amount may change during the operation of the service.

Creating a request does not mean that funds are reserved indefinitely. Specific reservation terms may depend on the exchange direction and the status of the request.

10. AML / KYC and Additional Verification

Bablos may review users and transactions where required by law, the service rules, or internal control procedures.

The service may request additional information or documents needed to confirm identity, ownership of payment details, source of funds, or to resolve an identified risk.

More information about these checks is available in the AML / KYC Policy.

The fact that additional verification is requested does not mean that the user is suspected of unlawful activity.

11. Suspension or Refusal

The service may suspend processing or refuse to carry out a transaction if:

  • there are indications of fraud or unlawful use of the service;

  • additional verification is required;

  • the information provided is inaccurate or inconsistent;

  • the origin of funds cannot be established where such verification is required;

  • the transaction does not comply with the terms of the selected exchange direction;

  • the transaction cannot be completed for technical or legal reasons;

  • completing the transaction would violate applicable law.

Any refund in such cases is handled taking into account the circumstances of the transaction, applicable legal requirements, and the technical possibility of returning the funds.

12. Refunds

If a request cannot be completed, the service may issue a refund where there are sufficient grounds and where technically possible.

Actual blockchain network fees, banking fees, or payment system fees may be deducted from the refund where such deductions are permitted by applicable terms and law.

Refunds are generally sent back to the original payment details or by another method after any required verification has been completed.

13. Prohibited Use

Bablos must not be used for:

  • fraud;

  • money laundering;

  • terrorist financing;

  • transactions involving stolen funds;

  • circumvention of restrictions imposed by law;

  • other unlawful activities.

Where required by law, information about a transaction may be provided to authorized public authorities.

14. User Responsibilities

The user is responsible for:

  • the accuracy of the information provided;

  • the correctness of payment details;

  • the lawful origin of the funds used;

  • compliance with laws applicable to the transaction;

  • access to their own payment methods, accounts, and digital wallets.

The user must also take reasonable measures to protect devices, passwords, confirmation codes, and other means of access.

15. Circumstances Beyond the Service’s Control

Bablos cannot guarantee the operation of third-party banks, payment systems, blockchain networks, internet providers, or other external services.

Delays or failures involving such systems may affect request processing times.

In such cases, the service will take reasonable steps to complete the transaction or offer the user available alternatives.

16. Support

If the user has questions about a request, they may contact support through the communication channels available on the website.

For faster handling, users are advised to provide the request number and briefly describe the issue.

Bablos support staff should never request a user’s private keys or wallet seed phrase.

17. Changes to These Rules

Bablos may update these Rules in response to changes in law, service functionality, supported exchange directions, or internal procedures.

The current version of the Rules is always published on the website.

A request is generally governed by the version of the Rules that was in effect when the request was created, unless otherwise required by applicable law.