Comment on page
0Xprocessing use cases
With 0Xprocessing via API integrations it's possible to receive payments in variety of ways: on websites, platforms, chats, etc.
Below are main use cases:
Merchant needs to process payments with fixed amount (e-commerce, subscription)
The deposit is made by invoice with a fixed amount.
Only the exact amount specified in the payment form will be credited as successful. In case of underpayment, the merchant is sent a callback with an appropriate status of Insufficiency.
The merchant can confirm an underpayment in the personal account manually or enable automatic execution of such transactions in the personal account, but they will be accepted only after closing the account payment window (30 min).
In case of overpayment, the transaction passes as successful, and the merchant receives a callback for the full amount of payment. Ask support for a working example of merchant integration.
Merchant needs to process payments with non-fixed amount (gambling, platforms with user balance)
If the merchant has a user balance on the platform side (recommended, as this is the best option to avoid the problem of underpayment or overpayment in cryptocurrency) a payment method without a fixed amount is appropriate.
In response to a deposit request, 0Xprocessing sends payment data, which the merchant can embed in a pop-up, window or page in its platform design.
0Xprocessing sends the wallet address, minimum payment amount and QR. The window design, additional text and recommended payment amount can be added by the merchant at his discretion.
A successful deposit is any amount greater than the minimum (covering network fees).
Funds received from the client are transferred to the merchant's balance in 0Xprocessing.
After the customer's deposit, the merchant receives the callback for the amount sent by the user, and after reading it the merchant can display the amount from the callback as a top-up of the user's balance.
Ask support for a working example of merchant integration.
Payments on static wallet (gambling, platforms with user balance)
Merchant generates a static wallet for each user through API at user registration and embeds them in the user's personal account.
A deposit to it of any amount greater than the minimum is considered successful.
The advantage of this type is that it is easier for a user to make repeated deposit, just to top up the purse. There will be fewer calls to the merchant that the client has paid in the wrong wallet.
Ask the support team for a working example of merchant integration
Link for payment of specific amount for integration of Merchant's deposit button (e-commerce, tickets, subscriptions with specific cost)
It doesn't guarantee full payment because it opens a form for fixed payment, how much the user will transfer at his discretion.
It requires additional control and confirmation of deposits by the merchant.
Example: In the link you need to put your merchant account ID (required), currency of payment, amount, SuccessUrl and CancelUrl to redirect client after payment:
Web3 wallets payments (gambling, lottery, investment projects, charity)
It allows you to transparently track transactions for other users. It allows all users to track how much money is in the "bank" of the project.
Recurrent Web3 wallets payments (subscription to service, salary, etc)
This method is used if the merchant needs to deduct amounts from the user on a regular basis.
When you register a user on the merchant platform, it is possible to sign up a Web3 wallet user on a special contract that allows merchant to write off every month, weekly, daily or at any other time a certain amount of money from the Web3 wallet user.