> 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/faq.md). # FAQ Find answers to frequently asked questions about our crypto payment gateway, ensuring clarity and support for your integration and operations. How do I connect to 0xProcessing? 1. Complete the form at . 2. One of our managers will contact you. After your account has been created, log in at . 3. Open the verification email and confirm your account. 4. Integrate 0xProcessing by following the documentation. 5. Set the withdrawal limit under Confirmations → Auto Confirm and configure the webhook URL under Settings → API. 6. After testing is complete, the processing fee for client deposits is set according to the merchant's expected turnover. Who can use 0xProcessing? Individuals and legal entities can apply to use the platform, subject to the applicable onboarding requirements. Submit your contact details through the feedback form to discuss the terms with a manager. ### Are there deposit and withdrawal limits for 0xProcessing? Through the API you can deposit or withdraw amounts equivalent to \~2 USD in all supported cryptocurrencies. Withdrawal from the merchant's personal account is possible if the withdrawal amount exceeds 10 USD. Withdrawal is possible in the merchant's balance currency only. If you have questions or experience a problem with a deposit or withdrawal, contact technical support at or your personal manager. What should I do if a required currency or feature is not supported? We continuously develop the platform and evaluate requests for additional currencies and features. Submit a request to technical support at or contact your manager. The team will review the requested currency or feature. ### How do I contact technical support? If you experience a transaction or integration problem, contact your manager or email . Include your merchant ID and the email address associated with your 0xProcessing account. If you made a transaction through 0xProcessing as a merchant's client, contact 0xProcessing support first so the issue can be investigated promptly. ### How can I add liquidity to my balance in 0xProcessing? Merchants can add liquidity to maintain sufficient cryptocurrency balances for client withdrawals. When adding liquidity, only the network fee is charged. A guide to adding liquidity: ### Are there deposit and withdrawal limits for 0xProcessing? You can deposit or withdraw an equivalent amount from \~3 USD in all supported cryptocurrencies. ### How quickly will the client's payment be credited to the merchant's account? What is the speed at which the merchant can withdraw funds from 0xProcessing? After a client submits a valid payment, 0xProcessing waits for the required blockchain confirmations. Confirmation can take from a few seconds to several minutes, depending on the blockchain network. The amount is then credited to the merchant's balance, and a payment status webhook is sent to the merchant's configured URL. Funds credited to the merchant's balance are available for withdrawal. You can withdraw funds manually under Dashboard → Withdraw or configure automatic withdrawals through the API. If VRCS is enabled, eligible funds are sent to VRCS and converted into the selected stablecoin. When the configured minimum is reached, the funds are transferred to the merchant's main 0xProcessing balance. Configure the minimum under Settings → Currency. What common transaction problems can occur? 1. The client sends funds to the address shown on the payment form after the 30–50-minute payment window has closed. The payment remains unpaid, and the merchant receives a webhook with the Canceled status. 2. The client does not send funds to the address shown on the payment form. The payment remains unpaid, and the merchant receives a webhook with the Canceled status. When a client contacts the merchant, first verify the deposit address using the transaction hash and destination address provided by the client. If funds reached the address but were not transferred to the 0xProcessing vault, contact 0xProcessing support. 3. The client underpays a fixed-amount payment: * If automatic underpayment confirmation is disabled, the payment remains underpaid and the merchant receives a webhook with the Insufficient status. The merchant can review and confirm Insufficient transactions under Confirmations. * 0xProcessing waits until the payment window is closed (30 min) and automatically deducts the amount received from the balance; the payment is considered successful and the payment status "Insufficient" is sent to the merchant; another callback with the **"Success"** status and **insufficient=true** flag is sent to the merchant; * If the deposit amount is less than the minimum, the payment is assigned the status **"Insufficient"**. You will not be able to confirm the payment data without an additional payment * If the merchant's client sends the remaining amount before the payment window closes, the payment is considered fully paid and is processed as successful when the payment window closes. {% hint style="warning" %} To avoid underpayment, inform clients that the platforms from which the client pays may charge an additional withdrawal percentage or deduct from the network fee. {% endhint %} 4. The client sent an asset over the wrong network or sent the wrong asset. {% hint style="info" %} **For example:** USDT (BEP20) instead of USDT (ERC20) BNB (BEP20) instead of USDT (BEP20) {% endhint %} In this situation, ask technical support to verify the transaction and determine whether the payment asset can be corrected. 5. If an asset is sent to an incompatible address or unsupported network, the funds may be permanently lost. 6. When a client sends an amount less than the minimum payment limit. The amount will remain in the system wallet until the client sends the additional amount required to reach the minimum deposit limit. 7. When a client sends an unsupported asset over a supported network, it may be possible to return the funds after deducting the network fee. If the amount does not cover the network fee, a refund may require an additional transfer of the network's native asset, such as ETH, BNB, or TRX. Funds sent over an unsupported network cannot be refunded. 8. If the merchant's client does not provide a required destination tag or payment ID when sending XRP, GRAM, USDT (TON), or NOT (TON), the funds may arrive but the system cannot match them automatically. To locate the transaction in the dashboard, provide the transaction hash, client ID, or client email address for a variable-amount deposit. 9. Some blockchain transactions can take several hours to confirm. For example, a Bitcoin transaction with a very low network fee may be delayed. 10. The payment was created in test mode. {% hint style="info" %} Set the **Test=true** parameter in the request to create a payment form. {% endhint %} Test payments are intended only to simulate payment statuses. Test payments must not be funded with real cryptocurrency and do not appear in the merchant dashboard. If real cryptocurrency is sent to a test payment address, contact technical support to determine whether the payment can be recovered and processed. 11. Duplicate top-up. The client sent a second payment to an address from an expired payment form. Technical support can help credit the received funds to the merchant's account balance, but the system cannot send a webhook for this transaction. The merchant must credit the client's balance manually. What information should I provide to 0xProcessing support if I have a deposit or withdrawal problem? #### Deposit: 1\. Txn Hash (required for XRP, GRAM, USDT (TON), NOT (TON) transactions) or Address (wallet the payment was made to); 2\. Payment ID, the payment identifier in 0xProcessing (required for XRP, GRAM, USDT (TON), NOT (TON) transactions); 3\. Billing ID (payment identifier in your system); 4\. Client ID (required for XRP, GRAM, USDT (TON), NOT (TON) transactions); 5. Client email address, if requested by 0xProcessing support. #### Withdrawal: 1\. Withdrawal ID from your side; 2. If the withdrawal ID is not available, send a screenshot of the withdrawal from the client's 0xProcessing profile or provide the withdrawal amount and date. {% hint style="danger" %} Send identifiers and addresses as text, not only as screenshots. {% endhint %} Where can I check the balance of the destination address used by the client? Use a blockchain explorer to check a transaction or cryptocurrency wallet balance. **Tron:** [**https://tronscan.org/**](https://tronscan.org/) TRX, USDT (TRC20), AXS (TRC20), ETH (TRC20) **Binance Smart Chain:** [**https://bscscan.com/**
](https://bscscan.com/)\ BNB, USDT (BEP20), USDCOIN (BEP20), DAI (BEP20), BTCB (BEP20), ETH (BEP20), ADA (BEP20), DESU (BEP20), MDAO (BEP20), DOGE (BEP20), ZEC (BEP20), ASTER (BEP20), DOT (BEP20), USD1 (BEP20), BONK (BEP20)\ \ **Ethereum:** [**https://etherscan.io/**
](https://etherscan.io/)\ ETH, USDT (ERC20), USDC (ERC20), TUSD (ERC20), DAI (ERC20), AXS (ERC20), WEVER (ERC20), TRX (ERC20), PEPE (ERC20), APE (ERC20), SHIB (ERC20), LINK (ERC20), PYUSD (ERC20), XAUT (ERC20), BGB (ERC20), UNI (ERC20)\ \ **Dogecoin:** [**https://dogechain.info/**](https://dogechain.info/) DOGE\ \ **Litecoin:** [**https://live.blockcypher.com/**](https://live.blockcypher.com/) LTC\ \ **XRP:** [**https://xrpscan.com/**](https://xrpscan.com/) XRP\ \ **Bitcoin:** [**https://blockchair.com/**](https://blockchair.com/) BTC\ \ **Bitcoin Cash:** [**https://blockchair.com/**](https://blockchair.com/) BCH **Dash:** [**https://explorer.dash.org/**](https://explorer.dash.org/) DASH\ \ **Polygon:** [**https://polygonscan.com/**](https://polygonscan.com/) POL *(prev. MATIC)*, USDT (POLYGON), USDCE (POLYGON) (PoS Bridge)*,* USDCOIN (POLYGON), WETH (POLYGON)\ \ **Arbitrum One:** [**https://arbiscan.io/**](https://arbiscan.io/) ETH (ARB1), ARB (ARB1), USDT (ARB1), DAI (ARB1), USDCE (ARB1) *(Bridged)*, USDCOIN (ARB1), PYUSD (ARB1), WBTC (ARB1)\ \ **Avalanche:** [**https://snowtrace.io/**](https://snowtrace.io/) AVAX, USDT (AVAXC), TUSD (AVAXC), USDC (AVAXC) **The Open Network:** [**https://tonviewer.com/**](https://tonviewer.com/) **,** [**https://tonscan.org/**](https://tonscan.org/) GRAM, USDT (TON), NOT (TON)\ \ **Base Chain:** [**https://basescan.org/**](https://basescan.org/) ETH (BASE), USDC (BASE) **Solana:** [**https://explorer.solana.com/**](https://explorer.solana.com/) SOL, USDT (SOL), USDC (SOL), USD1 (SOL), PYUSD (SOL), WBTC (SOL), SOETH (SOL), PUMP (SOL), TRUMP (SOL), JUP (SOL), BONK (SOL), PENGU (SOL), SPX (SOL), RAY (SOL), EURC (SOL), FARTCOIN (SOL), JTO (SOL), DBR (SOL) **OpBNB:** [**https://opbnb.bscscan.com/**](https://opbnb.bscscan.com/) BNB (OPBNB), USDT (OPBNB), ETH (OPBNB) **Optimism:** [**https://optimistic.etherscan.io/**](https://optimistic.etherscan.io/) USDT (OP), USDC (OP), USDCE (OP), OP (OP), ETH (OP), WLD (OP) **Monero:** [**https://blockchair.com/**](https://blockchair.com/) XMR **SUI network:** [**https://suiscan.xyz/**](https://suiscan.xyz/) SUI, ETH (SUI), WSOL (SUI), WBTC (SUI), USDT (SUI), USDC (SUI) **Robinhood chain:** [**https://robinscan.io/**](https://robinscan.io/) ETH (HOOD), USDG (HOOD), PONS (HOOD), CASHCAT (HOOD) **1. If you only know the Txn Hash, then copy it, go to an explorer such as the TRON network** [**https://tronscan.org/**](https://tronscan.org/)**, paste in the Txn Hash and hit \[Search].**\\
The transaction data opens. Click on the wallet on the right-hand side.
Your wallet opens where you can see if a payment has been credited to your wallet. In addition, you can see if your client has sent an amount less than the minimum payment limit. **Payment has been received on the wallet.**
**Payment has not been received on the wallet.**
**2. If you only know the wallet your client paid to, copy it, navigate to the explorer, e.g. Ethereum network** [**https://etherscan.io/**](https://etherscan.io/) **, paste the wallet and hit \[Search].**
Your wallet opens where you can see if a payment has been credited to your wallet. This is because you can see whether your client has sent an amount less than the minimum payment limit and whether the deposit has passed through. The wallet addresses used in the payment forms are always unique for each payment and contain a zero balance. **Payment has arrived in the wallet.**
**Wallet is empty, payment has not been received.**
**Payment has been made. The wallet has a withdrawal transaction in the vault.**
### Examples of how hash and wallet networks look
NetworkHashWallet address
Bitcoinf5c36d082cc958f0999cf0f7a5e5e9f465f18c346640626555f1129f02f4ce604LgYSPAtUFogixKgQzvaoXBERXZ16o2fKq
BNB chain / Ethereum0xb4bc263278d3f77a652a8d73a6bfd8ec0ba1a63924bbb5f38147fb8a943da26d0x4A084eF7EcFcf7af9E17d90C558Dc954DdB112eE
Tron3497e6d1b0a5ffb788c20a8a4fc822d6faae340ecde45e81a4cf80afc495117cTYhoLrdQej5mUEPcqYGeVxQCZyfowvq6hm
XRP (Ripple)33048FC64DBF3260AECBC48B71CC5710201ACD9EDFB3442B1024E7575E40AEA2rBYxNHGYggorQts4Z12rQDy8Ws61C10RtEb
Litecoin23eb9d4a3c47f9a6844ed276513d1e05040a9b8af90ac05d4b206b3024f5f35aMPGNSeMzD2zUy2Vh3wy5vN8Dcs42tTeyd9
Dogecoin6f5449cab534994d0c72555be6e552b173cb384030f4f97c50864cb7cf9561b7DDZkuCx1F4fUQAuJohkeyu3WDUbrz2m5oM

GRAM, USDT (TON),

NOT (TON)

a6068d69084f8ccb541e901d3a22197f0dce068749384e562b2732115e17660cEQAFF6Tf_jAATTaj-hs1ireZOvfdP7bL8x4fHWmM32wvP-G5