Terms of Use

These terms describe how you may use CryptoLike: the website cryptolike.net, the cabinet, the API and SDKs, the CMS plugins, the payment page, the widget and the Telegram bot. By creating an account or using the service, you accept these terms and the Privacy Policy. They describe the rules of the service and are not legal advice for your business; if you need advice on how they apply to you, consult your own lawyer.

#The service

CryptoLike is a platform for accepting crypto payments and paying out from your balance. It runs the wallets for you: payments arrive on addresses the platform manages, the private keys stay inside a separate signing service, and your money is recorded as a balance per asset in the CryptoLike ledger. You do not hold the private keys of these addresses, and you move money out of your balance with payouts.

• Accepting payments: invoices, static addresses, payment links, CMS plugins, the payment widget and the REST API.
• Payouts: one at a time from the cabinet, the Telegram bot or the API, or a CSV batch from the cabinet.
• Assets: the current list of assets and networks is on the supported coins page.

Balances and payouts are held and made in crypto assets. An invoice may be priced in a fiat currency: the amount to pay is then calculated in the chosen asset, and fiat amounts are kept for your reports. CryptoLike does not decide how you account for revenue or pay taxes.

#Your account

To open an account, you provide an e-mail address, a password and a project name, then confirm the e-mail address. Businesses and private individuals can open an account. Keep the details in your account up to date and accurate.

You are responsible for what happens under your account: the actions of the team members you invite, the roles you give them (owner, admin, finance, developer, viewer), and the API keys you create.

• Two-factor authentication (2FA). Every payout from the cabinet or the Telegram bot needs a fresh code from an authenticator app; without 2FA set up, such payouts are refused. We recommend turning 2FA on for sign-in as well.
• API keys. A payout through the API is authorised by a key with the withdraw permission and asks for no 2FA code. Give that permission only to keys that need it, limit such keys to your servers' IP addresses and use the payout whitelist. The API secret is shown once: store it outside your code.
• If you suspect unauthorised access, freeze the account from the cabinet: new payouts and API requests stop, while incoming payments continue to be credited. Then write to support to unfreeze it.
• Test mode. Test keys work only with test networks; test coins have no value.

The controls behind these rules are described on the security page.

#Acceptable use

You may use CryptoLike only for lawful activity. You may not use it:

• to sell goods or services that are illegal where you or your customers are, or that infringe someone else's rights;
• for fraud, scams, or schemes that deceive payers or recipients;
• to launder money, finance terrorism or evade sanctions, including payments to or from sanctioned persons or addresses;
• to receive funds from, or send funds to, darknet markets or mixing services;
• to get around screening, verification, limits or a block, for example by splitting one payment into several or by opening a new account after a block;
• to act on behalf of another person without their permission or to use someone else's account, documents or data;
• to interfere with the platform: attacks, attempts to access other accounts or internal systems, or load beyond the documented API limits.

Businesses in regulated or higher-risk categories are reviewed individually during verification. If your business needs a licence or permit to operate, holding it is your responsibility.

#Verification (KYB)

Accepting payments does not require verification. Payouts start after your account is verified (KYB). For verification, we ask for documents about you or your business; we review them and either verify the account or reject the request with a comment. We may refuse verification, and in that case payouts stay unavailable. More on the process: KYB.

#Screening, holds and returns

CryptoLike screens incoming transfers after their confirmations, before the money becomes available on your balance. Which transfers are screened, and against which sources, depends on the screening settings the platform applies to your account. Payout destinations are screened when a payout is created and again before it is signed.

• Incoming funds that screening links to a sanctioned source or rates above the risk threshold are held, and your server gets a deposit.on_hold webhook. After a compliance review, we decide on each case: the held funds are credited to your balance, stay frozen, or are to be returned to the sender. A return is not automatic: after the decision, our finance team sends the funds back to the sending address by hand, and returned funds never reach your balance. Until held funds are credited, they are not part of your available balance.
• If a transfer needs screening and the screening service cannot answer, the credit waits until screening succeeds.
• Payouts to a sanctioned address are refused, and payouts to a high-risk address go to a manual review. A payout also goes to review when it exceeds a limit set for your account or looks unusual, for example a large payout to a new address. Review usually finishes within 24 hours; the payout then continues, or it is rejected and the full amount returns to your available balance.

We may ask you for information about a payment, a payer or a recipient as part of a review. How screening shows up in the cabinet and the API: AML screening of incoming payments.

#Fees

The platform fee is set per asset and per direction (incoming payments and payouts) and is published on the pricing page with its effective date; an individual rate may be agreed for your account. The fee is charged only when a payment is confirmed: creating a payment costs nothing, and an expired or cancelled payment is not charged.

• The fee on an incoming payment is deducted from the credited amount, unless the payment is set up so that the payer covers it.
• The fee on a payout is added on top of the payout amount, together with the network fee of the transfer, which you pay. The payout shows these amounts before you confirm.
• When an invoice is priced in a fiat currency, the amount in the asset is calculated at the market exchange rate, plus a conversion spread only if one is published on the pricing page (the current rates have none), and the rate is locked until the payment expires.

Fees may change. A change applies to payments and payouts created after it takes effect; the current rates and the date from which they apply are always on the pricing page.

#Blockchain risks

Payments and payouts are blockchain transfers, and blockchains work by their own rules, which CryptoLike does not control.

• Transfers cannot be reversed. A payout sent to a wrong address cannot be recalled. Check the address, the asset and the network before you confirm.
• The asset and network must match. Funds sent on a network other than the one shown, or in an asset the payment does not accept, are not detected or credited and may be impossible to recover.
• Amounts must match. A payment that falls short of the requested amount by more than the underpayment tolerance of your account (0.5 % of the amount by default) stays underpaid until the payer sends the rest or the payment expires; a smaller shortfall counts as paid. An overpayment is credited in full, and settling the difference with the payer is up to you. A payment that arrives after the payment expired is still credited and marked as late. Refunds to your customers are payouts you make from your balance.
• Confirmations take time. A payment is credited after the confirmations set for its asset. If a block reorganisation removes a confirmed transfer, the credit is reversed and your server gets a webhook.
• Network fees are set by the network and change with its load.
• Prices move. Asset prices can change sharply; amounts in fiat currency in the cabinet and in reports are for information.
• Networks can stop. Congestion, upgrades or failures of a network can delay payments and payouts, and we may pause accepting or sending an asset for maintenance.

#Availability and changes to the service

We work to keep CryptoLike available, but we do not promise uninterrupted operation: maintenance, network events and failures can make the service or part of it unavailable for a time. We may add, change or stop features, assets and integrations. SDKs marked as pre-release may change before their first stable version.

#Limitation of liability

CryptoLike is provided as it is offered at the time you use it. To the extent the law applicable to you allows, CryptoLike is not liable for indirect losses or lost profits, or for losses caused by blockchain networks, by wrong details entered by you, your team or your customers, by the actions of third parties, or by events beyond our reasonable control. Nothing in these terms limits liability that cannot be limited by law.

#Suspension and closure

We may restrict, suspend or block your account, pause payouts or refuse a payout when these terms are breached, when verification or a review requires it, after screening results, when the law requires it, or when we see a risk to your account, your customers or the platform. A blocked account cannot use the cabinet or the API; incoming payments to its addresses continue to be credited.

You can stop using CryptoLike at any time. To close your account, withdraw your balances and write to support from the account owner's e-mail address. Some records are kept after closure for the periods described in the Privacy Policy.

#Changes to these terms

We may update these terms. The current version is always on this page with the date of the last update. We tell you about significant changes by e-mail or in the cabinet before they apply. If you continue to use CryptoLike after a change applies, the updated terms apply to you.

#Contact

Questions about these terms: support@cryptolike.net.

Last updated: October 9, 2026.