Why did you receive the DEPOSIT_ADDRESS_BRIDGE_REJECTED webhook event?

The DEPOSIT_ADDRESS_BRIDGE_REJECTED event is sent when a deposit cannot be processed through the Smart Deposit Address (SDA). The reason field in the webhook payload indicates the cause.

Possible reasons include:

UNDER_MIN — Deposit amount is below the minimum deposit limit
The deposited amount is below the minimum amount required for processing.

You can find the minimum deposit limit in the response of our status endpoint:
https://docs.rhino.fi/api-reference/sda/depositaddresses/get-deposit-address-status

ransfers below this are considered UNDER_MIN. We also ignore very small deposit to filter spam, address poisoning or dusting attacks.

Please contact our customer support team to initiate a refund.

OVER_MAX — Deposit amount exceeds the maximum deposit limit
The deposited amount is above the maximum amount supported for processing.

You can find the maximum deposit limit in the response of our status endpoint:
https://docs.rhino.fi/api-reference/sda/depositaddresses/get-deposit-address-status

Please contact our customer support team to initiate a refund.

OPERATION_UNAVAILABLE — Transaction blocked due to compliance screening
The transaction could not be processed due to compliance controls.

For compliance reasons, we cannot disclose whether a transaction was blocked due to AML checks. In such cases, we return OPERATION_UNAVAILABLE.

If you receive this reason code, please contact our customer support team.

UNSUPPORTED_TOKEN — Deposited token is not supported for SDA deposits
The token sent to the deposit address is currently not supported. We monitoring a small set of common tokens per chain for this webhook event. The list varies by chain and targets tokens users often deposit by mistake, mainly unsupported variants of USDC, USDT, or BTC. Detecting all tokens is not possible as we whitelist token contracts for monitoring, but we add tokens if we see frequent unsupported deposits in production.

Please contact our customer support team to initiate a refund.

TERMINAL_PROCESSING_ISSUE — Internal processing issue
The transaction could not be completed due to an internal processing issue.

If you receive this reason code, please contact our customer support team.

NO_ROUTE_FOUND — No valid processing route available
The transaction could not be processed because no valid bridge or swap route was available at the time of processing.

If you receive this reason code, please contact our customer support team.