User Agreement

1. General provisions

This User Agreement (the Agreement) sets the terms on which you may access and use the CryBit crypto-acquiring service published at CryBit.net, including the merchant dashboard, payment pages, API, widgets, documentation and related materials (the Service).

The parties are the person or legal entity that registers a dashboard or otherwise uses the Service (the Merchant, you) and the operator of CryBit.net (the Operator, we).

By creating an account, submitting a merchant for review, issuing an invoice, calling the API or otherwise using the Service you accept this Agreement. If you do not agree, do not use the Service. If you act for a company, you confirm that you are authorised to bind that company.

2. Definitions

Invoice — a payment request with an amount, a currency and a lifetime. After the Buyer picks a network, CryBit issues a unique on-chain address for that invoice.

Buyer — a person who pays an invoice from their own wallet. The Buyer does not need a CryBit account. Dashboard — the merchant cabinet. Sandbox — simulated payments that do not credit the live balance. Live mode — real on-chain transfers after the merchant is approved.

USDT — Tether USD in which the merchant balance is kept and payouts are sent. Gateway fee — the Service fee on a successful payment, as shown in the public table and on the merchant card.

3. Subject

The Operator provides the Merchant with access to the Service so the Merchant can accept cryptocurrency from Buyers and receive settlement in USDT on the terms of this Agreement.

The Operator is not a bank, not a card acquirer, not an exchange for traders and does not give investment, legal or tax advice. CryBit is not a party to the contract between the Merchant and the Buyer for goods or services.

4. Account and merchant

Registration requires a valid email and a password of at least eight characters. You are responsible for credentials, two-factor devices, recovery codes and API keys. Tell us at once if you suspect unauthorised access.

A merchant (website or app) must be submitted for review. Sandbox is available at once. Live accepting, API keys and payouts open after approval. The Operator may ask for information about the business, the site, traffic and beneficiaries, and may refuse or suspend a merchant that does not fit this Agreement or AML rules.

Keep profile and merchant data accurate. Three wrong passwords may lock the account until review.

5. Payments

For each invoice CryBit creates a unique address, or a standing address where the product allows it. The Buyer sends the amount shown in the chosen asset and network. After the required on-chain confirmation the invoice is marked paid. Incoming assets convert to USDT and credit the merchant balance, minus the gateway fee if the merchant pays it.

Who pays the gateway fee — merchant or Buyer — is set on the merchant card. Already issued invoices keep the rule they were created with. An unpaid or expired invoice costs no gateway fee. A new invoice uses a new address so payments do not mix.

Underpayments, overpayments, transfers in the wrong network and transfers after expiry may not credit automatically. Contact support; recovery is not guaranteed, and network gas may be deducted if a return is possible. Blockchain transfers are irreversible: the Operator cannot cancel a Buyer payment.

6. Fees

There is no setup fee and no monthly plan. The gateway fee is charged only on a successful payment, according to the public table and the network the Buyer used. The current table is on the website and in the dashboard.

Blockchain network fees are paid by the party that broadcasts the transfer. On an AML refund, the party who sent high-risk funds pays the gas of the return. The Operator may change fees; new invoices use the rules in force when they are issued.

7. AML and compliance

Incoming payments are screened. A high-risk result may reject the transfer: funds are returned to the sender minus network gas. The public AML checker is an address screen, not a legal opinion.

You must not use the Service to launder funds, evade sanctions, finance crime or accept mixer, darknet or other prohibited proceeds. The Operator may freeze, return or withhold credits, request documents, block a merchant and notify competent authorities where required. The Operator may refuse jurisdictions, assets or counterparties.

8. Merchant duties

You accept payment only for lawful goods and services you are entitled to sell, show the Buyer clear prices and terms, and handle claims about the underlying purchase yourself. You keep API keys secret, use HTTPS webhooks, pay applicable taxes on your revenue and do not present yourself as CryBit.

9. Prohibited use

Without limitation: weapons and dual-use items in breach of law; drugs; child sexual abuse material; trafficking; unlicensed gambling where it is prohibited; pyramids and unlicensed securities; malware; sanctions evasion; mixing as a business; spoofing CryBit or its payment pages.

Breach of this section is ground for immediate suspension of the merchant, invoices and payouts.

10. Balance and payouts

The merchant balance is denominated in USDT. Payouts go to the address you submit on the supported payout network (currently USDT TRC-20), from the stated minimum, after two-factor confirmation. Test merchants do not credit the live balance. Payouts send real USDT from live settlements only.

A payout may be delayed or refused while AML, review or a dispute is pending. The Operator is not liable for a payout sent to an address you entered incorrectly.

11. Intellectual property

CryBit, the logo, the dashboard, the API, widgets and documentation belong to the Operator or its licensors. You receive only the rights needed to use the Service under this Agreement. You may not copy, scrape, reverse engineer except where mandatory law allows, resell CryBit as your own gateway, or remove marks.

12. Availability

The Service is provided as available. Blockchains, nodes, AML providers and counterparties can fail. The Operator does not guarantee uninterrupted uptime. Coins and networks may be added or removed; where possible this does not change your integration. Material feature changes are announced in the dashboard or on the website.

13. Liability

To the maximum extent permitted by law the Operator is not liable for disputes between you and the Buyer; for congestion, reorgs, forks or keys lost on your side or the Buyer side; for indirect loss, lost profit or lost data; or for third-party wallets, browsers and plugins.

The Operator aggregate liability under this Agreement for a calendar month is limited to the gateway fees you actually paid that month, except where a cap is not allowed (including willful misconduct). You indemnify the Operator against claims that arise from your goods, content, taxes or unlawful use of the Service.

14. Term and termination

The Agreement starts when you accept it and continues until the account is closed or the Operator ends access. You may stop using the Service and ask to close the account. Outstanding invoices, AML holds and payouts are wound down first.

The Operator may suspend or terminate immediately for breach, AML risk, false data or a legal requirement. Provisions on intellectual property, liability, AML, fees already earned and disputes survive termination.

15. Changes

The Operator may update this Agreement. The current text is published at CryBit.net. Material changes are announced in the dashboard or by email. Continued use after the effective date is acceptance. If you disagree, stop using the Service and close the account.

16. Final provisions

If a provision is held invalid, the rest of the Agreement stays in force. Failure to enforce a right is not a waiver. English and Russian texts are both official. If they conflict, the Russian text prevails when you accepted the Agreement in the Russian interface; otherwise the English text prevails.

Disputes are first negotiated for thirty days through the contact form on CryBit.net or the email of the account. If unresolved, they are heard by the competent court at the Operator place of business, unless mandatory law says otherwise.

Notices to the Merchant go to the account email and, where relevant, the dashboard. Notices to the Operator go through the contact form on CryBit.net or the dashboard.