Partner Dashboard Configurations

🕙

Saving Configurations

All configurations will take around 15 minutes to take effect on the live Banxa Checkout.

Disable WalletConnect and MetaMask Connection

This configuration will allows your users to connect their wallet's directly on Banxa Checkout using a MetaMask or Wallet Connect button.

Display User's Wallet Address and Memo

This configuration will make the user's wallet address and memo/tag (if passed in the API or link) be displayed when the user is redirected to Banxa. If this configuration is set to false, then the user's wallet address and memo/tag will be hidden.

Set the Default Cryptocurrency

This is the default cryptocurrency for all your users when they are redirected to Banxa Checkout.

Coins and Blockchains

This configuration will allow you to set what cryptocurrencies and blockchains are available for your users to select from. By default, all options will be available until they are de-selected. Please note that native tokens for a blockchain cannot be de-selected.

Upload Logo

This is the logo that will be displayed on the Banxa Checkout screens on all pages of the checkout flow. This image must be uploaded with a maximum of 70 pixels height.

Primary Colour

This will be your brand colour that will be used for the buttons, highlighted texts and checkboxes.

Theme

This configuration will allow selection between Dark and Light mode. Please note that if the user changes the theme from their browser, then this will override the default selected by you.

Webhook URL

If you would like to receive webhooks for all status changes on your orders, you may put your webhook URL here and we will send your webhooks to that URL. You can put in different webhook URL's for your sandbox and production environments.

For more information on how to implement webhooks, please find the documentation here: https://docs.banxa.com/docs/webhooks

Enable HMAC Encrypted Webhook

If you enable this configuration, then Banxa will encrypt all webhooks that we send to you using HMAC authentication. This will provide extra security from bad actors who might send webhooks to your address.

For more information on how to implement HMAC encrypted webhooks, please find the documentation here: https://docs.banxa.com/docs/webhooks

Send Webhook

After you have saved a Webhook URL, you may test the webhook by clicking on the Send button. We will send a webhook to the URL that you have set and the results will be displayed on the screen.

IFrame Hosts

If you are implementing Banxa Checkout as an iFrame, then please set your hosting URL here. We will whitelist these URLs so that the iFrame can successfully be displayed on your application.

Return URL

This is the callback URL that will be used to return your user back to your application after they have completed the Banxa Checkout flow. If you are already passing this parameter in the API i.e. return_url_on_success then that will take precedence.

Enable Account Reference parameter

As part of the Create Order API, an account_reference parameter that identifies the user is mandatory. If you do not have an account_reference i.e. a customer ID, you can turn this configuration off, making the account_reference parameter optional in your Create Order request and Banxa will create a customer ID on your behalf.

Dynamic callback URL variables

If you have set a Return URL, then this configuration will allow you to indicate if you want any order related parameters that can be appended to that Return URL. e.g. https://yourCompanyName/?orderId={509427}&fiat={AUD}&fiatAmount={0}&coin={BTC}&coinAmount={0}&orderRef={12a320b36117089a9e94b3e8acd4cf5d}&orderStatus={Expired}&fulfillmentStatus={Pending}&paymentStatus={Expired}&identityStatus={Complete}

This configurations provides the opportunity for you to know order details after the user has submitted their order, and to deep link your customer to specific pages on your application.