Changelog

Changelog

Improved

Create Identities endpoint now supports Base64

When sending us customer documents, we now accept Base64 encoded images. Previously we only support links to images in a secure location, however we now support both. See detailed guide here, see API reference here.

Added

Automated Webhook Re-Tries

The new webhook retry mechanism ensures reliable delivery of event notifications. If Banxa does not receive a 200 OK response from your server after sending a webhook, the system will automatically re-send the same webhook multiple times. The payload of the webhook remains unchanged across all retry attempts.

Added

Introduce contract_id to Get Coins and Get Order(s)

In order to support additional reporting that you may wish to do, we have introduced the cryptocurrency/blockchain smart contract value to each cryptocurrency and blockchain pair returned in the Get Coins and Get Order(s) Single and Bulk API responses.

Improved

Webhooks Version 2

Today, if you have subscribed to Banxa webhooks, they are sent for only a subset of order status transitions (inProgress, completed, expired and waitingPayment). Additionally, the webhook payload only contains the order ID and requires you to make a Get Order call to retrieve the status.

Improved

New URL parameters available for theme changes

Using the URL Parametization method of integration, you will now be able to pass parameters that will change the look and feel of the customer's checkout experience. These new parameters include: theme, primaryColor, secondaryColor, backgroundColor and textColor.

Added

Introduce X-Request-Id to response payloads

There will be a new header parameter you will receive on all Banxa API responses called X-REQUEST-ID. This value can be used for any integrations troubleshooting with us, and will help us identify all Request and Response pairs.