This endpoint retrieves wallet control information by making an HTTP GET request to the specified URL. The request includes the wallet address and a callback URL. The response returns a status code of 200, along with the encrypted receiving wallet address and callback URL in the JSON format.

Request Parameters

• address: The wallet address to receive instant payouts after customer payment. Wallet must be a valid USDC (Polygon).

• callback: urlencoded callback URL where the payment confirmation will be sent using GET request. You must have at least one unique GET parameter with each request. If you use the same parameter value again the same temporary receiving address will be provided in the response. In production use your own unique callback NOT example.com

Response

The response returns a newly generated encrypted receiving temporary wallet address and the same provided callback URL for confirmation in the JSON format. You may need to json_decode(); the response address_in to pass it in the next step.

• address_in : This is the encrypted wallet address that need to be passed to the payment link generator (Process Payment) in the second step.

• polygon_address_in : This is the generated receiving address decrypted for easy payment tracking. You can't pass this address directly to the second step, you need to pass the encrypted address_in.

• callback_url : This is the same callback URL you passed containing all your parameters returned in a decoded format for confirmation. Our bot will send a GET request to this URL when the customer complete the payment containing all your parameters with an additional parameter value_coin representing the actual USDC value sent by the payment provider which can be useful for your system in case you want to verify the sent amount.

• ipn_token: This token is useful when provided to our support team we will be able to track your payment and investigate failed callback events.

This endpoint will redirect the customer to the payment page. You should treat this as the payment URL. Your CMS should pass all the following parameters.

• address: you need to pass the encrypted address_in generated from GET wallet.php | Passing your payout wallet address directly without the first step will result in a 400 bad request.

• amount: Amount you need the customer to pay. For example 105.78 this should be the order total in your system. You can add more fees by passing bigger amounts to cover the payment processing fees.

• provider: Possible values can be fetched from provider id at provider status endpoint. Other providers can be available exclusively through the Multi-provider mode only.

• email: urlencoded customer email address

• currency: Currency code, for example: USD or EUR or CAD
  stripe, transfi, robinhood and bitnovo providers values need to be in USD only!
  upi is INR currency only! | interac is CAD currency only!

Please note that you are not allowed to use the payment link within embedded iframe, user must be redirected to the licensed payment provider page directly. Your system will be notified after customer payment using the predefined callback URL.

By default when the end customer is redirected through this endpoint our servers would detect the customer location country automatically. However in some cases you may want to hide our domain completely and fetch the end provider payment URL that this endpoint is redirecting to. In this case you may need to note that payment links are usually built based on end customer location country and you should always make sure to pass the end user geo country ISO code by passing HTTP request header PGTO-IPCountry with its value as the country ISO code of end user for example ES for Spain.

This endpoint is similar to process-payment.php but it will redirect the customer to a hosted page with multi-provider selection list. Options displayed on the hosted payment page are based on several factors including but not limited to customer location, payment amount and currency. GET parameters can be as follows:

Required Parameters

• address: you need to pass the ecnrypted address_in generated from GET https://api.anexpay.net/control/wallet.php | Passing your payout wallet address directly without the first step will result in a 400 bad request.

• amount: Amount you need the customer to pay. For example 105.78 this should be the order total in your system. You can add more fees by passing bigger amounts to cover the payment processing fees.

• email: urlencoded customer email address

• currency: Currency code, for example: USD or EUR or CAD

Optional Parameters

• domain: This is an optional parameter to white-label (rebrand) the hosted checkout page with your own custom domain name. You can set your own rebranded subdomain that will replace any instance of checkout.anexpay.net in the hosted payment page code. The format of this optional parameter value should be like checkout.example.com and it can be set to be hidden within your cloudflare worker code to prevent manipulation.

• logo: urlencoded image URL to be used as the brand logo displayed on the multi-coin crypto checkout page. This is an optional value and it can be for example your own website/brand logo.

• background: urlencoded HEX color code to optionally change the background color of the checkout page. Instead of HEX code you may pass direct CSS color naming like green, blue, orange, etc.

• theme: urlencoded HEX color code to optionally change the theme color of the checkout page. Instead of HEX code you may pass direct CSS color naming like green, blue, orange, etc.

• button: urlencoded HEX color code to optionally change the checkout page button color. Instead of HEX code you may pass direct CSS color naming like green, blue, orange, etc.

This endpoint will return full list of possible providers you can use within the credit card system and their minimum order value. No extra GET parameters needed with this endpoint.

Response

• id: This is the API provider id to be used as &provider= parameter value for process payment link.

• provider_name: User friendly (human readable) provider name.

• status: Up to date status of the provider. If it is not active then you should avoid using this provider in your system.

• minimum_currency: The currency of the minimum allowed order amount for this provider. Note that the provider may still support other currencies.

• minimum_amount: The minimum order amount for this provider.

Optionally if you want to white-label (rebrand) our payment gateway then you can use this endpoint as the first step and pass your affiliate wallet as an extra affiliate parameter to earn commission on every sale. Merchant wallet and affiliate wallet must be different or the request will fail.

This optional endpoint is for advanced rebranding usage. If you want to rebrand (white-label) and set a custom redistribution of the payout or set a custom commssion fee to yourself as an affiliate then you can optionally use this endpoint to create wallets. This endpoint is similar to the Affiliate endpoint with two extra parameters affiliate_fee and merchant_fee. Those two parameters can be used to distribute percentage of the instant payout to address and affiliate wallets.

affiliate_fee is used to set percentage to the affiliate wallet, if it is set to 0.01 this wallet would receive 1% of the total final payout. merchant_fee is used to set percentage to the address wallet, if it is set to 0.98 then this wallet would receive 98% of the total final payout.

The sum of affiliate_fee and merchant_fee must always be 0.99 as our service fee is 1% of the total payout. If the total is not 0.99 the request would fail.

This optional endpoint is for advanced rebranding usage. If you want to rebrand (white-label) and set a custom redistribution of the payout or set a custom commssion fee for both yourself as an affiliate and your sub-affiliate then you can optionally use this endpoint to create wallets. This endpoint is similar to the Affiliate endpoint with extra parameters affiliate_fee , sub_affiliate_fee and merchant_fee. Those parameters can be used to distribute percentage of the instant payout to address, sub-affiliate and affiliate wallets.

affiliate_fee is used to set percentage to the affiliate wallet, if it is set to 0.01 this wallet would receive 1% of the total final payout. merchant_fee is used to set percentage to the address wallet, if it is set to 0.97 then this wallet would receive 97% of the total final payout. sub_affiliate_fee is used to set percentage to the sub_affiliate wallet, if it is set to 0.01 the sub_affiliate would receive 1% of the final payout.

The sum of affiliate_fee, sub_affiliate_fee and merchant_fee must always be 0.99 as our service fee is 1% of the total payout. If the total is not 0.99 the request would fail.