Release Date: 08/10/2026

1. Summary

This version delivers two main fronts:

• Self-Custody Declaration across the three points where a crypto withdrawal destination is registered — Whitelist and counterparty Connections on the Platform, and end-user withdrawal addresses (Withdraw Addresses) registered in the CaaS Manager — to support clients in meeting national (IN 2291 - DeCripto) and international (Travel Rule) compliance requirements.
• Support for asynchronous AML provider responses, with the new Provider Response Timeout field in Compliance > AML on the Platform.

2. What's New

2.1 Self-Custody Declaration in Whitelist, Counterparty Connections, and end-user Withdraw Addresses

• Every new registration of a crypto destination now requires the Is self-custody? field, with possible values yes and no.
• Addresses and connections already registered can be complemented with this declaration, without a full re-registration.
• Once defined, the declaration cannot be changed: to modify it, the destination must be recreated (re-registration or reconnection).
• Addresses and connections without the complete declaration become unavailable for selection as a destination for withdrawals and transfers. Clients with whitelists or counterparty connections already registered must complete this information to keep using those destinations.

Feature Documentation: Self-Custody Declaration

2.2 New “Self Custody” column in the RFQ Funding report

• The RFQ Funding report now includes the Self Custody column, added at the end of the layout and populated from each withdrawal's destination declaration. The column is empty for withdrawals prior to this version.
• This information supports building the distinction between the 0450 and 0650 records required by DeCripto (IN 2291).

2.3 Provider Response Timeout — configurable wait time for the AML provider

• New Provider Response Timeout field in the AML Screening block, under Compliance > AML. It is a global instance setting and is independent of the selected provider.
• With it, the Platform now supports AML providers with asynchronous responses: it waits for the response up to the configured limit and, if the time expires without a conclusive response, records the assessment with the TIME_OUT result (the same handling already applied to ERROR).

Feature Documentation: AML Module

3. Integration Impact

3.1 Self-Custody Declaration (Whitelist and Counterparty Connections)

Does not impact integrations

Capturing the “Is self-custody?” declaration is available only through the Platform interface — no API impact.

3.2 New “Self Custody” column in the RFQ Funding report

Does not impact integrations

The new “Self Custody” column is available only in the report/export (CSV), not in an endpoint or webhook. The existing layout is preserved; no current column changes name or position, and the new column is simply appended at the end without altering the existing columns. Integrations that consume the RFQ Funding report do not need any change to keep working, and may start reading the new column if they want to incorporate the self-custody distinction.