How are transactions checked for AML?

Last updated: February 18, 2026


AML Check Tools and Providers:

  • Rhino.fi uses a third party service provider to scan addresses for AML compliance, called TRM.

  • For some clients, Rhino can integrate external AML checks where the client provides an API that returns yes/no decisions.

  • The bridge only proceeds if both Rhino's check and the client's check return positive results.

AML Check Timing by Transaction Type:

1. Deposit via SDA (Smart Deposit Address):

  • AML checks are done in parallel with client KYA checks to ensure fastest experience.

  • The AML check happens when funds are already sitting in the SDA (since the transfer to SDA cannot be rejected).

2. Deposit directly using SDK:

  • AML check is performed at the quoting stage.

3. Withdrawal flow:

  • Usually performed before the transfer, but also performed after if the deposit to funding contract is delayed.

  • Check occurs when the commit endpoint is called to commit the quote.

  • Uses parameters such as depositor and

AML Blocking and Alerts:

  • Transactions can be manually blocked by compliance team members.

  • For rejected bridges, webhooks are sent with status "OPERATION_UNAVAILABLE" as a reliable indicator that an AML check failed.

  • Detailed information about why transactions were blocked cannot be shared via webhooks for compliance reasons.

  • In cases where funds are frozen by regulators, end users must not be informed of the specific reasons.