0xProcessing integration options
Explore practical 0xProcessing use cases to address business-specific crypto payment needs, optimizing transactions and expanding possibilities.
The 0xProcessing API supports several payment integration models for websites, platforms, chatbots, and other services.
The main use cases are listed below:
The Merchant needs to process fixed-amount payments (for example, e-commerce or subscriptions)
The deposit is made by invoice with a fixed amount.
A payment is marked as successful only when the exact amount specified in the payment form is received. If the Client underpays, the Merchant receives a webhook with the Insufficient status.
The Merchant can confirm an underpayment manually in the dashboard or enable automatic processing. Underpayments are accepted only after the 30–50-minute payment window closes.
If the Client overpays, the transaction is marked as successful and the Merchant receives a webhook for the full amount paid. Contact support for a working integration example.
Example: evavpn.com
The Merchant needs to process variable-amount payments (for example, gaming services or platforms with Client balances)
A variable-amount payment method is suitable when the Merchant maintains Client balances on the platform, because it helps manage cryptocurrency underpayments and overpayments.
In response to a deposit request, 0xProcessing returns payment details that the Merchant can display in a pop-up, window, or page within the platform.
0xProcessing returns the wallet address, minimum payment amount, and QR code. The Merchant can customize the layout and add explanatory text or a recommended payment amount.
A successful deposit is any amount greater than the minimum amount and sufficient to cover network fees.
Funds received from the Client are transferred to the Merchant's balance in 0xProcessing.
After the Client's deposit, the Merchant receives a webhook containing the amount sent. The Merchant can then credit that amount to the Client's balance.
Ask support for a working example of Merchant integration.
Payments to static wallets (gambling, platforms with user balances)
The Merchant generates a static wallet for each user through the API during user registration and embeds it in the user's personal account.
A deposit to this wallet of any amount greater than the minimum is considered successful.
The advantage of this integration type is that it makes repeated deposits easier for users: they can top up the same wallet address each time. It also reduces the number of cases where Clients accidentally pay to the wrong wallet.
Ask the support team for a working example of Merchant integration.
Example: megapari.com
Payment link for a specific amount, used for a Merchant deposit button (e-commerce, tickets, subscriptions with a fixed cost)
This option opens a payment form where the Client can enter payment details if they are not specified in the link. Because the Client can still choose how much to transfer, the Merchant should control and confirm deposits as needed.
Example: Add your merchant account ID (required), payment currency, amount, SuccessUrl, and CancelUrl to redirect the Client after payment:
If the payment details are not specified in the link, the Client can enter them independently in a special form.
Web3 wallet payments (gambling, lottery, investment projects, charity)
Web3 processing
This option allows users to track transactions transparently and see how much money is in the project's bank.
Example: dexsport.io
Recurring Web3 wallet payments (subscriptions, salary payments, etc.)
This method is used when the Merchant needs to deduct amounts from the user on a regular basis.
When a user registers on the Merchant platform, the Merchant can connect the user's Web3 wallet to a special contract. The contract allows the Merchant to charge a certain amount from the user's Web3 wallet monthly, weekly, daily, or at another agreed interval.
Last updated
Was this helpful?