Weelay

Terms of Use

Core Weelay usage rules, merchant responsibilities, service limitations, API, webhook, plans and liability.

Legal document Published: 2026-06-21 ~6 min read

General provisions

These terms describe the rules for using Weelay.

Weelay provides technical infrastructure for creating invoices, displaying a checkout page, checking USDT TRC20 payments, using the API and sending webhook notifications to the merchant.

By using Weelay, the user confirms that they have read, understood and accepted these terms.

Weelay is not a seller, bank, payment institution, cryptocurrency exchange or custodial wallet.

Terms

Weelay means the service that provides technical tools for creating and checking USDT TRC20 invoices.

Merchant means a Weelay user who creates a project, sets a wallet address and accepts payments from buyers.

Buyer means a person who pays an invoice created by the merchant through Weelay.

Invoice means a Weelay record containing the amount, status, expiration time, payment link and technical data for payment checking.

Project means a separate merchant configuration for accepting payments.

API key means an access key used by the merchant to work with the Merchant API.

Webhook means a server-to-server notification from Weelay to the merchant backend.

Role of Weelay

Weelay provides technical tools:

  • invoice creation;
  • checkout page display;
  • USDT TRC20 payment checking;
  • invoice status updates;
  • merchant API;
  • webhook notifications;
  • technical logs and trace_id for troubleshooting.

Weelay does not sell goods or services to the buyer, does not fulfill merchant orders and does not become a party to the transaction between the merchant and the buyer.

Non-custodial model

Weelay operates under a non-custodial model.

Buyer funds are sent directly to the merchant wallet address. Weelay does not receive funds on its own balance, does not hold them and does not control the merchant wallet.

This model is explained in more detail in the Non-Custodial Payment Notice.

Merchant account

The merchant is responsible for the security of the account.

The merchant should use an active email address, secure password and, where available, additional account protection methods.

The merchant must not transfer account access to third parties if this may lead to abuse, data loss or unauthorized use of the service.

Projects and wallet address

The merchant creates projects and sets the USDT TRC20 wallet address for receiving funds.

The merchant is responsible for the correctness of the wallet address.

If the merchant provides an incorrect address, loses wallet access, uses an unsupported network or gives the buyer incorrect payment data, Weelay cannot restore access to funds or cancel the transaction.

API keys

The secret API key must be stored only on the merchant backend.

The secret API key must not be placed:

  • in frontend code;
  • in public JavaScript;
  • in a mobile application without a protected backend;
  • in public repositories;
  • in screenshots, documents or messages;
  • in logs in full form.

If the secret API key is exposed, the merchant should revoke it and create a new key.

API usage

The merchant may use the Merchant API to create invoices, retrieve invoice data and integrate Weelay with the merchant order system.

The merchant must handle API errors correctly, avoid excessive load on the service and follow the limits.

Weelay may temporarily limit requests in case of limit abuse, suspicious activity or technical risk to the service.

Webhook notifications

Webhook helps the merchant receive invoice event notifications.

The merchant is responsible for the security of the webhook endpoint, signature verification, idempotent handling of repeated events and correct order updates on the merchant side.

Webhook should not be the only protection in disputed situations. The merchant may additionally verify invoice status through the API.

Plans and limits

Weelay may provide different plans, billing periods, limits for projects, invoices, active invoices, addresses and other features.

Plans and limits may differ depending on the selected plan.

Weelay may change plans, limits and available features. Material changes are published in the service interface or documentation.

Merchant responsibilities

The merchant is solely responsible for:

  • legality of the merchant activity;
  • accuracy of information about goods and services;
  • order fulfillment;
  • buyer support;
  • refunds;
  • complaint handling;
  • correctness of the wallet address;
  • account and API key security;
  • compliance with applicable laws and Weelay rules.

Buyer responsibility

The buyer is responsible for sending the payment correctly.

Before payment, the buyer should check the amount, network, recipient address and invoice expiration time.

Payment through the wrong network, to the wrong address, with insufficient amount or after invoice expiration may require manual review with the merchant.

Prohibited use

Weelay must not be used for illegal activity, fraud, phishing, malware, sale of prohibited goods or services, sanctions evasion, money laundering, buyer deception or other activity that violates law, third-party rights or the acceptable use rules.

Weelay may restrict, suspend or block access to the account, project, API key or specific features if the rules are violated.

Complaints and disputes

A buyer or third party may submit a complaint about a merchant.

Weelay may review technical data: invoice, status, amount, tx_hash, recipient address and related records.

Weelay is not a court, bank, payment arbitrator or enforcement authority. Weelay does not guarantee a refund from the merchant.

Refunds

Weelay does not issue refunds on behalf of the merchant.

If the merchant agrees to refund the buyer, the merchant sends the refund independently from the merchant wallet.

Blockchain transactions are usually irreversible. Weelay cannot cancel a sent transaction or return funds from blockchain.

Service availability

Weelay aims to maintain stable service operation, but does not guarantee the absence of all outages, errors, delays, maintenance, external provider issues or blockchain infrastructure problems.

Weelay may temporarily limit access to specific features for maintenance, security or abuse prevention.

Limitation of liability

Weelay is not responsible for goods, services, merchant actions, buyer actions, loss of merchant wallet access, incorrect wallet addresses, blockchain fees, network delays, transaction irreversibility or inability to return funds from blockchain.

Weelay responsibility is limited to the technical role of the service.

Changes to terms

Weelay may update these terms.

The current version is published on the Weelay website. Continued use of the service after an update means acceptance of the updated version.

Related documents

These terms should be read together with other Weelay documents:

  • Non-Custodial Payment Notice;
  • Privacy Policy;
  • Acceptable Use Policy;
  • Refund Policy;
  • Merchant Complaints;
  • Cookie Policy.

Support

Need help?

Contact Weelay support if this page does not answer your question.