Release Date: 10/07/2026


1. Summary

Version 4.6.0 brings more transparency to failed on-chain transfers:

  • Failure reason for on-chain transfers — a standardized error code and a description of what happened, available in the API, webhooks, the platform, and the Crypto Transactions report.
  • Error catalog in the API documentation — new Transfer Errors section explaining what each code means and how to resolve it.


2. What's New

2.1 Failure reason for on-chain transfers

  • Every on-chain transfer that fails now reports its reason in a standardized way: a stable error code and a description of what happened.
  • The same reason is available across all interfaces:
    • API: the reason is returned in the error response of the transfer endpoints.
    • Webhooks: failure events now carry the failure reason.
    • Platform: the error toast and a new tooltip next to the failed status in Activity > Crypto Transfers display the message.
    • Crypto Transactions report: new columns with the error code, the error message, and the original provider error, populated when the status is a failure.

Important Note

  • The reason is recorded at the moment of failure. Transfers made before this version are not retroactively assigned a new reason.


2.2 Transfer error catalog in the API documentation

  • The API documentation adds a Transfer Errors section, with one row per error code: the code (Error), what happened (Description), and what to do (How to resolve).
  • The existing errors section is renamed General Errors, with no change to its content.
  • Some messages include variables in curly braces, such as {asset} and {network}, which are replaced with the actual value in the response.


3. Integration Impact

3.1 Failure reason in transfer error responses

May impact integrations.

  • The error response format of the transfer endpoints does not change: the fields remain the same. What changes is their content, which now carries the standardized failure reason:
    • error_code — new standardized error code.
    • message — what happened. May include values such as the asset and network involved.

⚠️ Integrations that make decisions based on the text of message or on specific error_code values returned before this version should review that logic, as the values of these fields now follow the Transfer Errors catalog.

Impacted Endpoints:

  • WMS Transactions
    • GET /v1/api/wms/transactions
  • Transactions
    • GET /v2/api/transaction
    • GET /v1/api/transaction/{transactionId}


3.2 Error fields in transaction webhooks

May impact integrations.

  • The TransactionCustody and WmsTransaction failure events now include a new error object, with the code and message fields.
  • Event names and existing fields do not change; the error object is added.

⚠️ Integrations that strictly validate the webhook schema must accept the new error object.


3.3 Platform and Crypto Transactions report

Does not impact integrations.

  • Three new columns in the Crypto Transactions report, next to the status: Error Code, Error Message, and Provider Error.
  • Toast and tooltip showing the error message.

Impacted Interfaces:

  • Activity > Crypto Transfers
  • Crypto Transactions report


4. References

API Documentation