Static wallet

This method allows you to assign the merchant clients permanent deposit wallets instead of payment forms, when client deposit any amount greater than the minimum amount (~3 USD) which will be sent to the processing vault and then it will be credited to the merchant balance.

When integrating a static wallet VRCS is not available.

This type of deposit does not support the XRP currency

When requesting a deposit of TON, USDT (TON) currencies, the "destinationTag" parameter is also passed, which must be displayed in your payment form, since a client payment without Destination Tag will not be processed automatically.

The resulting value of the destinationTag parameter will be static for the client.

The payment form must necessarily contain a field with the value of the destinationTag/memo parameter.

Creating a wallet for a user

The request must contain an APIKEY header with your API key. The key can be generated in the menu Merchant\Classic processing\General settings

Import the user's ID into the 0x system (create a permanent individual wallet for your client using the user ID from the merchant platform):

Method: POST

Content Type: application/json

Endpoint:

https://app.0xprocessing.com/Api/CreateClientWallet

Parameters:

Name	Description	Type
Currency	Wallet currency. List of supported currencies: BTC, DAI (ERC20), AXS (ERC20), DASH, DOGE, BCH, ETH, TUSD (ERC20), LTC, USDC (ERC20), USDT (ERC20), WEVER (ERC20), TRX, USDT (TRC20), AXS (TRC20), ETH (TRC20), BNB, ETH (BEP20), DAI (BEP20), USDT (BEP20), DESU (BEP20), ADA (BEP20), USDC (BEP20), BTCB (BEP20), MDAO (BEP20), AVAX, USDT (AVAXC), TUSD (AVAXC), USDC (AVAXC), MATIC, USDT (POLYGON), USDC (POLYGON), DAI (POLYGON), WETH (POLYGON), ETH (ARB1), USDT (ARB1), DAI (ARB1), USDC (ARB1), WBTC (ARB1), TON, USDT (TON)	string
ClientId	Unique user ID in your system	string

Result:

Parameters:

Name	Description	Type
Currency	Wallet currency	string
Address	Wallet address	string
destinationTag	Unique identifier of the client, which needs to specify when sending funds in TON, USDT (TON)	string

                        {
                        "Currency": "string",
                        "Address": "string",
                        "destinationTag": "string"
                        }

To support different currencies from the same network, one constant wallet address will be created for each user.

For example: for TRX and USDT (TRC20) the client will have the same wallet address.

In order for the customer to deposit funds in a chosen currency, there must be a static wallet created in that currency. For example, if only TRX wallet has been created, but the customer sent USDT (TRC20), the payment will not be processed automatically by the system unless a static USDT (TRC20) wallet has been created. Do not forget to initialize the static wallet in each required currency for your customer.

If a static wallet was initialized by mistake after the customer sent funds in the wrong currency, don't worry, just contact 0xProcessing payment support, and we will assist you.

Getting the list of wallets by customer ID:

The request must contain an APIKEY header with your API key. The key can be generated in the menu Merchant\Classic processing\General settings

Method: GET

Endpoint:

https://app.0xprocessing.com/Api/GetClientWallets/{Id}

Parameters:

Name	Description	Type
Id	Unique user ID in your system	string

Result:

Parameters:

Name	Description	Type
Currency	Wallet currency	string
Address	Wallet address	string
destinationTag	Unique identifier of the client, which specifies when sending funds in TON, USDT (TON)	string
Balance	Wallet balance	decimal

                        [
                        {
                        "Currency": "string",
                        "Address": "string"
                        }
                        ]

After creating a wallet, the user can deposit it for any amount.

The deposits report can be implemented by means of webhooks

Webhooks

Deleting the list of wallets by customer ID:

This method should be used on the merchant side if the customer has been blocked or deleted from the system, in this case you should definitely use this method and delete the customer's static wallets.

By completing this request ALL static wallets of the specified customer will be deleted.

The request must contain an APIKEY header with your API key. The key can be generated in the menu Merchant\Classic processing\General settings

Method: POST

Content Type: application/json

Endpoint:

https://app.0xprocessing.com/Api/DisableClientWallets/{clientId}

Parameters:

Name	Description	Type
clientId	Unique user ID in your system	string

Response:

HTTP Code: 200 OK

Enabling the list of wallets by customer ID:

This method should be used on the merchant side if the customer has been unlocked or the customer has returned to your service, in which case you can use this method and all customer static wallets will be enabled.

By completing this request ALL static wallets of the specified customer will be enabled again.

The request must contain an APIKEY header with your API key. The key can be generated in the menu Merchant\Classic processing\General settings

Method: POST

Content Type: application/json

Endpoint:

https://app.0xprocessing.com/Api/EnableClientWallets/{clientId}

Parameters:

Name	Description	Type
clientId	Unique user ID in your system	string

Response:

HTTP Code: 200 OK