Terms of Service
Version of test-2026-10-05
These Terms of Service (the "Terms") are an agreement between PayMeSafe Test Operator (the "Operator") and the person who uses the PayMeSafe service (the "User"). The Terms explain what the service does, how a deal works, what the service costs, how disputes are reviewed and who is responsible for what.
1. General provisions
-
The PayMeSafe service (the "service") is a website and a dashboard where Users make and carry out deals with payment locked in cryptocurrency. The service is provided by the Operator.
-
The Terms are a public offer by the Operator. The User accepts them in full and without reservations as described in section 6. The service cannot be used on any other terms.
-
The Dispute Resolution Rules, the Prohibited Use document, the Risk Notice and the service fee rates on the Fees page form part of the Terms.
-
How the Operator processes personal data is described in the Privacy Policy and the Cookie Policy. Consent to data transfer for AI review and consent to processing of an identity document copy are given separately, before the corresponding action.
-
All documents of the service share one version; its date is shown at the beginning of each document.
2. Definitions
-
Account — the User's account in the service.
-
Dashboard — the part of the website available after signing in: deals, wallet, settings.
-
Deal — an agreement between two Users made in the service: the buyer locks the payment, the seller fulfils the deal terms, and after acceptance the locked funds are released to the seller.
-
Parties — the buyer and the seller. Initiator — the party that created the deal. Partner — the other party of the deal from the User's point of view.
-
Deal terms — the text and parameters of the deal agreed by the parties: subject, amount and payment asset, deadlines, service fee payer, documents. Deal terms should not be confused with the Terms of Service.
-
Wallet — the User's assets in the service: balances by currency and network, deposit addresses.
-
Locking funds — moving the buyer's funds from the available wallet balance into the locked funds of a deal. Locked funds — funds that the Operator holds for a specific deal until they are distributed.
-
Distribution of locked funds — release of the locked funds to the seller, a refund to the buyer or a split between the parties.
-
Service fee — the Operator's charge for locking funds and settling the deal.
-
Network fee — the charge of a blockchain network for processing an operation. It does not belong to the Operator.
-
Dispute — a contractual procedure for settling disagreements between the parties of a deal with locked funds.
-
Arbiter — an employee of the Operator who reviews a dispute and decides how the locked funds are distributed. The arbiter is not an arbitrator of an arbitral tribunal, and the review of a dispute is not arbitration proceedings.
-
Appeal — a party's request to reconsider the arbiter's decision. An appeal is reviewed by a reviewer — an employee of the Operator.
-
Identity verification — a check by an employee of the Operator of a document proving the User's identity.
-
AI assistant — a feature of the service that, at the User's request, checks the text of the deal terms using a language model and offers findings: edits, additions and notes.
-
AI credits — the User's quota for terms checks by the AI assistant. AI credits are neither money nor an asset.
3. What the service does and the Operator's role
-
The service gives Users tools for a deal: agreeing the terms, inviting a partner, locking the payment, messaging and sharing files in the deal feed, acceptance, disputes and distribution of locked funds.
-
The Operator is not a party to the deal. It does not sell or buy the subject of the deal, does not represent the parties, does not check the subject of the deal, rights to it, its quality or legality, and does not guarantee that the parties will perform the deal.
-
The parties write the deal terms themselves. The service does not provide a standard contract: a deal template only sets the fields, deadlines and documents.
-
The custodian of funds in wallets and locked funds is the Operator itself. The Operator creates and keeps the deposit addresses and their keys and keeps records of each User's funds.
-
Funds in the wallet belong to the User. The Operator disposes of them only following the User's actions in the service, to perform a deal, under an agreement of the parties in a dispute or a decision in a dispute, and in other cases expressly provided for by the Terms or by law.
-
The service is not a bank: the Operator does not accept deposits and does not pay interest; funds in the service are not a bank deposit and are not covered by deposit insurance. The service does not exchange digital currencies for money or for other digital currencies.
-
The Operator does not give legal, tax or investment advice. Findings of the AI assistant and texts of the service are not advice.
-
The parties determine and pay the taxes and charges related to their deals themselves.
4. Who may use the service
-
A User may be an individual with full legal capacity who has reached the age of 18 years.
-
An account is registered to an individual for their own use. If the User acts in a deal on behalf of an organisation or another person, the User is responsible for having the authority to do so.
-
One person — one account. The account or access to it may not be transferred to others.
-
The User provides accurate information and registers only with their own email address.
-
The User checks for themselves that the law of their country of residence and citizenship allows them to use the service and to make deals with digital currency. A person whom the law prohibits from doing so may not use the service.
5. Registration and account security
-
To register, the User provides a name, an email address and a password, confirms their age and accepts the Terms (section 6). The email address is confirmed by a link in an email.
-
Until the email address is confirmed, the User cannot invite a partner, accept deal terms or lock funds.
-
Without an account, a deal draft can be put together. The draft is kept for a limited time; to continue, the User needs to sign up or sign in.
-
The User keeps their password, authenticator codes and backup codes secret and does not share them with anyone, including employees of the Operator. The Operator does not ask for the password or codes by email or through support.
-
The Operator recommends enabling multifactor authentication. When it is enabled, signing in, accepting delivery under a deal and withdrawing funds require a verification code.
-
If the User suspects that someone else has gained access to the account, the User changes the password, revokes access for unknown devices in the settings and reports it to support.
-
The User changes their name in the profile settings. To change other account details, the User writes to support.
6. Acceptance of the Terms and new versions
-
The User accepts the Terms when registering by ticking a box that confirms the User has reached the age of 18 years and accepts the Terms. The box is not ticked in advance; without it the account is not created.
-
The Operator records the acceptance: the account, the document, the version, the date and time, the IP address and browser details. The boxes the User ticks before identity verification, an AI review, the first wallet deposit and opening a dispute are recorded in the same way.
-
The Operator issues a new version when the text of any document of the service changes. The new version is published on the website with a new date.
-
A new version applies to the User once the User has accepted it. On signing in, the User sees a screen with a link to the new version and an accept button. Until the new version is accepted, actions in the dashboard are unavailable: the User can read the documents, accept them or sign out.
-
Until the new version is accepted, the relationship between the User and the Operator, including unfinished deals, is governed by the version accepted earlier.
-
A User who does not agree with a new version does not accept it and writes to support at test@example.invalid.
7. Simple electronic signature
-
The Operator and the User agree that the User's actions in the account are performed electronically and signed with a simple electronic signature.
-
The key of the simple electronic signature is the account's email address together with the password and, for actions that require confirmation, also an authenticator verification code or a backup code.
-
An action performed in the account after signing in with this key is deemed performed and signed by the account holder.
-
By creating a deal or proposing a revision of the terms, the author signs the deal terms as proposed. By accepting the terms or a revision, the other party signs them. Deal terms accepted by both parties are an electronic document signed by both parties; after acceptance it does not change.
-
Locking funds, confirming an order, reporting delivery, accepting delivery, returning for rework, a claim, offers in a dispute and their acceptance, an appeal, consent boxes and acceptance of the service documents are signed in the same way.
-
Electronic documents signed with a simple electronic signature are recognised as equivalent to paper documents signed by hand in the cases permitted by the applicable law.
-
The User must keep the key secret (section 5). If another person has learned the key, the User changes the password at once and reports it to support.
-
The fact and time of actions are confirmed by the service's records: the deal feed, the wallet transaction history and the records of document acceptance.
8. How a deal works
-
The initiator creates a deal: chooses a template and their role — buyer or seller — and specifies the subject, amount and payment asset, the service fee payer, deadlines and deal terms, attaching documents if the template requires them.
-
The initiator invites a partner with an invitation link: shares it personally or asks the service to email it to a given address. The User enters only the address of the person with whom they are negotiating the deal. The recipient of the email can opt out of invitations via the link in the email.
-
Until the terms are accepted, the parties agree on them through revisions of the terms. Only one revision can be under review at a time; the other party accepts or declines it. A revision can only be accepted from the comparison view showing its changes.
-
Once the other party accepts the terms, the deal awaits locking of funds. Accepted deal terms no longer change.
-
The buyer locks funds: moves the deal amount and their share of the service fee (section 9) from the available balance of their wallet into the locked funds. Locked funds cannot be withdrawn or used for other deals until they are distributed.
-
The seller confirms the order, fulfils the deal terms and reports delivery, attaching evidence.
-
The buyer checks the delivery and then:
- accepts it — the locked funds are released to the seller; this action is irreversible;
- returns the deal for rework;
- opens a dispute (section 13).
-
The release is credited to the seller's wallet in the service. The seller can withdraw funds from the service as described in section 10.
-
Deal deadlines are an arrangement between the parties and a hint in the interface. An expired deadline alone does not release or refund funds, cancel the deal or open a dispute: if a party does not act, the other party opens a dispute.
-
A deal can be cancelled only before funds are locked: the initiator deletes the draft, the partner declines the terms, and after the terms are accepted either party cancels the deal while the funds are not yet locked. After funds are locked the deal cannot be cancelled: funds can be returned to the buyer only under an agreement of the parties in a dispute or a decision in a dispute.
-
Locked funds are distributed in one of three ways: released to the seller after acceptance, under an agreement of the parties in a dispute or under a final decision in a dispute, except where the law requires the Operator to act otherwise.
-
The parties are responsible to each other for performing the deal under the deal terms and the law. Messages and files in the deal feed are visible to both parties and, in a dispute, also to the arbiter and the reviewer.
9. Service fee
-
The service fee is the Operator's charge for locking funds and settling the deal: holding the locked funds and distributing them.
-
The rate depends on the deal amount and applies to the whole amount. The current rates are published on the Fees page. The fee is charged in the payment asset of the deal.
-
The rate and amount of the fee are shown to the buyer when locking funds and are fixed at that moment. A change of rates after funds are locked does not affect the deal.
-
The initiator specifies the fee payer when creating the deal: the buyer, the seller or both parties equally. The fee payer is part of the deal terms accepted by the other party.
-
The fee is withheld when funds are locked. If the buyer pays it, the buyer locks the deal amount together with the fee. If the seller pays it, the fee is withheld from the locked funds and the seller receives the deal amount less the fee. If the parties pay equally, each bears half of the fee.
-
A deal cancelled before funds are locked pays no fee.
-
The service is deemed rendered once the locked funds are distributed, whatever the outcome: release to the seller, refund to the buyer or a split. The fee stays with the Operator in each of these outcomes. An agreement of the parties in a dispute and a decision in a dispute distribute the locked funds net of the fee and do not change its amount.
-
On a refund, the buyer receives the locked funds less the service fee, whoever the fee payer is: even if under the deal terms the seller pays the fee, on a refund it is withheld from the buyer's locked funds.
-
Network fees, the withdrawal fee and the parties' expenses outside the service are not included in the service fee.
10. Wallet, deposits and withdrawals
-
The wallet is created together with the account. The assets and networks supported by the service are shown in the wallet.
-
Before the first deposit, the User confirms having read the Risk Notice. Without this, no deposit address is issued.
-
For a deposit, the service issues an address. Only the asset and only the network shown next to the address may be sent to it; if a memo is shown, it must be included in the transfer. Funds are credited after the network confirms the transfer.
-
An asset sent over another network, to a wrong address or without a required memo may not be credited and may be lost irreversibly. The network fee for a deposit is paid by the sender.
-
Only the available part of the balance, which is not locked, can be withdrawn. A withdrawal requires completed identity verification (section 11) and, if multifactor authentication is enabled, a verification code.
-
The User enters the recipient address and network and is responsible for their correctness. A transfer on the network is irreversible: the Operator cannot cancel or return funds that have been sent.
-
A withdrawal fee is charged, and its amount is shown in the withdrawal form before confirmation. The network fee for a withdrawal is paid by whoever withdraws the funds. If a withdrawal fails, the funds, including the fee, are returned to the balance.
-
Wallet operations are shown in the transaction history.
-
The Operator may suspend individual wallet operations in case of network or service failures, if a breach of the Terms is suspected, and where the law requires it.
11. Identity verification
-
Identity verification is required to withdraw funds and to run an AI review of the terms.
-
The User uploads in the settings an image or scan of a document proving their identity: a passport, a national ID card, a driver's license or another document. Before each upload the User separately gives consent to processing of the document copy.
-
An employee of the Operator checks the document manually. The result is shown in the settings. The Operator may reject a document, for example if it is unreadable or does not allow the person to be identified; the User can then upload another one.
-
Once verification is completed, the document does not need to be uploaded again.
-
The Operator may refuse identity verification or a withdrawal where the law requires it.
12. AI assistant
-
The AI assistant is an auxiliary tool. At the User's request, it checks the text of the deal terms and offers findings: edits, additions and notes. Only what the User has accepted or written personally goes into the text of the terms.
-
The AI assistant's answer is not legal advice and not the Operator's assessment of the deal. A language model can make mistakes, miss important points and suggest unsuitable wording. The parties are responsible for the text of the deal terms.
-
The check is performed by an external AI model provider. The text of the terms and the deal fields are transferred to it only with the User's separate consent to data transfer, given before each check.
-
Before each check, the User also confirms understanding the nature of the AI assistant's answer and being responsible for the data included in the text. Other people's personal data may be included in the text only on a lawful basis.
-
An AI review is available after identity verification and uses AI credits. The number of credits granted and the cost of a check are shown in the interface. AI credits cannot be withdrawn, exchanged or transferred to other Users. Credits charged for a check are not returned, except where the check did not take place because of a failure.
-
The AI assistant does not make decisions on disputes and does not take part in reviewing them.
13. Disputes
-
If the parties disagree about the performance of a deal with locked funds, either of them can open a dispute. Until the dispute ends, the locked funds are not distributed.
-
A dispute is a contractual procedure that the parties accept together with the Terms. First, the parties try to agree themselves: they offer a refund amount to the buyer and accept or decline offers. If they cannot agree, the dispute is reviewed by an arbiter — an employee of the Operator — who decides how the locked funds are distributed.
-
The arbiter is not an arbitrator of an arbitral tribunal, and the review of a dispute is not arbitration proceedings. The arbiter's decision is a decision of the Operator as the custodian of the funds on how to distribute the locked funds under the Terms.
-
The arbiter's decision can be appealed once. An appeal is reviewed by a reviewer — an employee of the Operator — who upholds the decision or replaces it.
-
By accepting the Terms, the parties instruct the Operator to distribute the locked funds under an agreement of the parties in a dispute or under a final decision in a dispute.
-
The dispute procedure does not deprive the parties of the right to go to court — before, during or after it — and is not a mandatory pre-trial procedure.
-
How a dispute is opened, its deadlines, appeals and the execution of decisions are described in the Dispute Resolution Rules. By opening a dispute, a party confirms having read them.
14. Prohibited use
-
What may not be done in the service is listed in the Prohibited Use document.
-
In case of a breach, the Operator may refuse to carry out a deal or an operation, restrict or block the account (section 16) and pass information to government authorities where the law requires it.
15. Liability
-
The Operator is responsible for keeping and recording Users' funds and for distributing locked funds in accordance with the parties' actions, an agreement of the parties in a dispute or a decision in a dispute.
-
The service is provided as is. The Operator strives to keep the service running without interruptions or errors but does not promise this: maintenance and failures are possible.
-
The Operator is not liable:
- for the parties' performance of a deal, for the subject of the deal, its quality and legality, for the content of deal terms, messages and files posted by Users;
- for the operation of blockchain networks: delays, failures, changes in network fees and rules;
- for the consequences of the User's mistakes in the address, network or memo;
- for actions of persons who gained access to the account because the User did not keep the password or codes secret;
- for changes in the market value of assets;
- for the consequences of using the AI assistant's findings.
-
The Operator is not liable for failure to perform its obligations due to force majeure or decisions of government authorities that it could not prevent.
-
The User is responsible for the accuracy of their information, for complying with the Terms and the law and for the content they post in the service.
-
The limitations of liability in this section apply to the extent permitted by the applicable law and do not reduce the rights of a User who is a consumer established by law.
16. Restriction and blocking of the account
-
The Operator may restrict access to certain features or block the account if:
- the User breaches the Terms or the Prohibited Use rules;
- the User provided inaccurate information or registered more than one account;
- there are signs that the account is used by someone other than its holder;
- the law or a decision of a competent authority requires it.
-
A blocked account cannot be used to sign in; active sessions are ended.
-
Blocking does not cancel the parties' obligations under unfinished deals. The Operator decides how to handle the locked funds and wallet funds of a blocked account taking into account the law, the deal terms and the interests of the other party. The User may contact support about this.
-
The User may ask support for the reason for blocking and contest it. The Operator gives the reason unless the law prohibits disclosing it.
17. Closing the account
-
The User may stop using the service and close the account at any time. To do so, the User writes to support at test@example.invalid from the account's email address.
-
The account is closed if the User has no unfinished deals, open disputes, withdrawals in progress, locked funds or wallet balance. The balance must be withdrawn in advance. While any of these remain, the account is not closed.
-
When the account is closed:
- it is no longer possible to sign in;
- the email address, name, password, sessions, devices, multifactor authentication settings and identity document copies are deleted or anonymised;
- in deals and the feed, the User's role in the deal is shown instead of the User's name.
-
The history of deals and wallet operations is kept without personal data for as long as the law requires. Deal terms, messages and files that the User posted in deals remain there: the other party needs them, and they are needed for accounting.
-
After the account is closed, the Terms cease to apply, except for provisions that by their nature continue to apply: on settlements, liability and dispute resolution.
18. Notifications and correspondence
-
The Operator sends the User service emails to the account's email address: address confirmation, password recovery, invitations, emails about deal events and unread messages. Deal events are also visible in the deal feed in the dashboard.
-
The Operator decides which service emails are sent. An email may be delayed or not delivered; this does not change any deadlines and does not relieve the parties of the need to follow the deal in the dashboard.
-
The User contacts the Operator by email at test@example.invalid. Support is available by email only.
-
The User sends legally significant notices to the support address, and the Operator sends them to the account's email address.
19. Rights to the service and Users' materials
-
The rights to the service, its software, design and name belong to the Operator or its licensors. The User may use the service for its intended purpose within the Terms.
-
The rights to texts, messages and files that the User posts in the service remain with the User. By posting them, the User allows the Operator to store them, show them to the other party of the deal, the arbiter and the reviewer and use them to run the service and review disputes.
-
The User posts only what they have the rights to and does not infringe the rights of third parties.
20. Governing law and disputes with the Operator
-
These Terms and the relationship between the User and the Operator are governed by TEST DATA — governing law is not specified.
-
The User may send a claim to the Operator by email to support. The Operator responds within the period set by law.
-
Disputes between the User and the Operator that could not be settled by negotiation are heard in court.
Venue: TEST DATA — dispute venue is not specified.
-
This clause does not limit the right of a User who is a consumer to go to court under the jurisdiction rules that the law establishes to protect consumers.
-
Disputes between the parties of a deal are resolved as described in section 13 and the Dispute Resolution Rules.
21. Final provisions
-
The Terms are drawn up in Russian and English. In case of discrepancies between the language versions, the Russian text prevails.
-
If any provision of the Terms proves invalid, the remaining provisions continue to apply.
22. Operator details
- Name: PayMeSafe Test Operator
- Address: Test address, not a legal address
- Registration details: TEST DATA ONLY — not legal information
- Email for enquiries and legally significant notices: test@example.invalid