> For the complete documentation index, see [llms.txt](https://docs.0xprocessing.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.0xprocessing.com/basic/general/terms-and-definitions.md).

# Terms and definitions

Understand crypto payment terms and definitions to integrate seamlessly, ensuring efficient transactions and smooth operations with our payment gateway.

* **Merchant** — a party that integrates 0xProcessing to accept cryptocurrency payments for its services and/or goods.
* **Client** — a customer of the Merchant who makes a payment through 0xProcessing on the Merchant's side.
* **Network fee** — a fee paid to network validators or miners to process a cryptocurrency transaction.

The network fee varies by network. In 0xProcessing, the network fee can be paid by the Client or covered by the Merchant. By default, the Client pays the network fee.

Here is an example of how network fees can vary:

{% hint style="info" %}
If a Client makes a payment of 1,000 USDT on the Tron network (TRC20), they will be charged 1,000.81 USDT because the network fee is approximately 10 TRX (\~$0.80) for any transaction amount.

If a Client makes a payment of 1,000 USDT on the Ethereum network (ERC20), they will be charged 1,005.43 USDT. The network fee changes continuously and averages approximately 0.00310555 ETH (\~$5).
{% endhint %}

* **Processing fee** — the 0xProcessing fee for each deposit credited to the Merchant's balance. The final fee amount depends on the Merchant's monthly turnover. There is no processing fee for withdrawals.
* **Webhook** — a JSON notification sent to a specified webhook URL when an event occurs during payment processing. It provides merchants with real-time updates on the statuses of their clients' payments.
* **VRCS** — Volatility Risk Control System.

To help manage cryptocurrency volatility, 0xProcessing provides automatic conversion to stablecoins. When VRCS is enabled, eligible funds received from a Client are automatically converted into a stablecoin supported by 0xProcessing.

* **Stablecoin** — a token designed to maintain a stable value relative to another asset. Stablecoins may be backed by fiat currencies or other reserve assets. Common examples include USDT, DAI, USDC, and TUSD.
* **0xProcessing vault** — a system of secure hot wallets used to store Merchants' balances.
* **KYC/KYB** — Know Your Customer / Know Your Business, an identification process for merchants and their customers.
* **Destination tag** — an optional or required identifier used by certain networks and custodial wallets. For XRP, it helps associate a payment with the correct Client. Payments without a required destination tag cannot be matched automatically and may be marked as unpaid.
* **Transaction hash** — a unique identifier for a blockchain transaction that can be used to check the transaction status. A transaction hash usually looks like a random set of letters and/or numbers.
* **Static wallet** — a permanently assigned deposit address that can be reused.
* **Web3 wallet** — a non-custodial wallet for storing cryptocurrency, NFTs, and other digital assets. It provides a user-friendly way to interact with decentralized applications (dApps) across supported blockchains. Popular Web3 wallets include MetaMask and Trust Wallet.
* **Fiat money** — government-issued currency, such as USD, EUR, CNY, or JPY.
* **Wallet address** — a unique blockchain address used to send or receive cryptocurrency. Address format and length depend on the blockchain network.
* **System wallet** — a unique 0xProcessing wallet used to receive deposits from Merchant's clients and determine payment validity. After the payment is validated, the amount is sent to the 0xProcessing vault and credited to the Merchant's balance.
* **Native network currency** — the main asset of a blockchain used to pay network fees, such as BNB on BNB Chain or ETH on Ethereum.
* **Token** — a crypto asset created by a smart contract on a particular blockchain. Each token follows a standard supported by the network on which it was created.