Smart Deposit Addresses

A Smart Deposit Address (SDA) is a deposit address you generate for each end customer. When the customer sends a supported token to it, on any of its enabled chains, Rhino.fi detects the deposit, routes it as needed (bridging, swapping and, where configured, running an onchain action on settlement), runs compliance screening, and settles the funds to the configured destination address. For examples of how clients use SDAs, see 5 ways to use Smart Deposit Addresses.

For initial testing, projects start with a limit of 500 SDAs in total and 50 new SDAs per hour. Subscription accounts have production limits that depend on their tier. See Limits and contact your account manager before launch.

How it works

Check where SDAs are available

Find the chains and tokens you can accept, and their deposit limits.

Create an address for each customer

Choose the deposit chains, the destination chain and address, and the token to settle in. One API call returns the address. On EVM chains, one address works on every EVM chain you list. Non-EVM chains, such as Solana or Tron, are also supported, each with its own address.

Show the address to your customer

You can also show the supported tokens and the minimum and maximum deposit amounts.

Your customer sends funds

Your customer, or your platform after consolidating customer funds, sends a supported token to the address.

Rhino.fi settles each deposit

Funds arrive at your destination in the token you configured. You receive webhooks at each stage. Afterwards, Rhino.fi periodically sweeps the address to consolidate balances. You don’t need to do anything.

All examples use the rhinoFetch helper from Authentication. All SDA endpoints require authentication.

1. Check where SDAs are available

See Supported chains and tokens for the full list. In code, the configs endpoint flags each chain that supports SDAs with enabledDepositAddress:

const configs = await rhinoFetch('/bridge/configs', { auth: false })
const sdaChains = Object.keys(configs).filter((chain) => configs[chain].enabledDepositAddress)

To see which tokens are accepted between a deposit chain and your destination, and their limits:

const tokens = await rhinoFetch(
  '/sda/deposit-addresses/ETHEREUM/BASE/supported-tokens?tokenOut=USDC', // tokenOut is optional
)

See Supported tokens for an SDA for the response format.

2. Create an address

Create addresses as you need them, for example when a customer first opens your deposit screen, rather than in bulk. See best practices for operating SDAs.

const addresses = await rhinoFetch('/sda/deposit-addresses', {
  method: 'POST',
  body: {
    depositChains: ['ETHEREUM', 'BASE', 'ARBITRUM', 'OPTIMISM'],
    destinationChain: 'BASE',
    destinationAddress: '0xYourTreasuryAddress',
    tokenOut: 'USDC',                 // optional: settle everything as USDC
    addressNote: 'customer_8f3a21',   // optional: your own reference, max 80 characters
    webhookUrl: 'https://api.example.com/rhino', // optional: overrides your project webhook
  },
})

The response is an array with one entry for each deposit chain:

[
  {
    "depositChain": "ETHEREUM",
    "depositAddress": "0x4567…",
    "destinationChain": "BASE",
    "destinationAddress": "0xYourTreasuryAddress",
    "tokenOut": "USDC",
    "addressNote": "customer_8f3a21",
    "supportedTokens": [
      { "symbol": "USDT", "address": "0xdAC1…", "minDepositLimitUsd": 10, "maxDepositLimitUsd": 100000 }
    ],
    "isActive": true,
    "isPaused": false
  }
]

depositAddress is the address to show your customer. When you list several EVM chains, the address is the same on every one.

List every EVM chain that supports SDAs, even ones you do not advertise. If a customer sends funds on the wrong EVM network, Rhino.fi still detects and settles them, and no manual recovery is needed. See best practices for operating SDAs.

Request fields

Field	Required	Description
`depositChains`	Yes	Chains on which to accept deposits. Several chains in one request must all be EVM chains.
`destinationChain`	Yes	Chain to settle funds on
`destinationAddress`	Yes	Address that receives settled funds, in the destination chain’s format
`tokenOut`	No	Token to settle in. Any token supported on the destination chain. If not set, each deposit settles in the token that was deposited.
`addressNote`	No	Your own reference, up to 80 characters. It is returned by every status endpoint and can be searched.
`reusePolicy`	No	`reuse-existing` (default) or `create-new`. See Reuse addresses.
`webhookUrl`	No	Webhook URL for this address only. If omitted, your project webhook from the Rhino.fi Console is used.
`refundAddress`	No	Address to suggest when a deposit to this address needs a refund. It is not used automatically. See Refunds.
`postBridgeData`	No	A predefined contract call to run on settlement. Requires the Automated Onchain Actions extension.
`bridgeIfNotSwappable`	No	When `true`, a deposit that cannot be swapped to `tokenOut` is settled in the deposited token instead of being rejected

The full schema and error list are in the API reference.

Deposits that are not processed

Rhino.fi only processes deposits that meet all of these conditions:

The token is in supportedTokens for that chain.
The amount is between minDepositLimitUsd and maxDepositLimitUsd.
The deposit passes AML screening. For custom screening rules and real-time AML alerts, see Enhanced Compliance & Risk Management.
For native tokens such as ETH, the deposit is sent as a direct transfer. Internal transfers, where a smart contract sends the funds (for example a smart wallet, or an exchange that batches withdrawals), are only supported on Ethereum, Base and Optimism. On other chains, such as Arbitrum, Rhino.fi does not detect them, so no webhook is sent.

You can show these conditions to your customer next to the address, so they know which deposits will be processed. Deposits slightly outside the limits may still be processed, to allow for price movement, but do not rely on this. If liquidity on a route is temporarily insufficient, the deposit is retried until it settles or is refunded. Deposits that are not processed trigger a DEPOSIT_ADDRESS_BRIDGE_REJECTED webhook. Contact your Rhino.fi account manager to arrange a refund.

Settle in a different token

With tokenOut set, every deposit is settled in that token, swapped where needed. It can be any token supported on the destination chain. For example, USDT deposits can be settled as USDC. If you don’t set tokenOut, each deposit settles in the token that was deposited. Bitcoin is the exception: BTC deposits settle as WBTC by default. See Interacting with Bitcoin. With the 1:1 Stablecoin Settlement extension, USDC and USDT conversions run at a guaranteed 1:1 rate, with no slippage or market exposure.

Reuse addresses

SDAs are reusable. Rhino.fi monitors each address for seven years, and it can receive any number of deposits in that time. After seven years the address is no longer monitored, unless the period is extended. Contact your account manager if you need longer. With the default reusePolicy: "reuse-existing", a create request returns your existing address when all of the following fields match a previous request: depositChain, destinationChain, destinationAddress, addressNote, tokenOut, postBridgeData, webhookUrl and refundAddress. Only addresses created by your project are considered. This makes the create call safe to retry. If several customers settle to the same destination address, put each customer’s ID in addressNote. Otherwise, with reuse-existing, they would all receive the same address. Use reusePolicy: "create-new" only when you need a fresh address every time.

Refunds

Deposits that can’t be processed, such as an unsupported token or a deposit on an unsupported chain, are refunded by your account manager, who returns the funds to a verified address. You can set a refundAddress when you create an address. It doesn’t trigger a refund on its own. If set, it is offered as the default destination when a refund for that address is processed, instead of the sending address. Only set it if the depositor controls that address. Many customers deposit from exchanges and other pooled wallets, where funds sent back may never reach them.

3. Monitor an address

Check its status

const status = await rhinoFetch(`/sda/deposit-addresses/${depositAddress}/ETHEREUM`)

The response has the same shape as the create response. destinationAddress is included only when the JWT comes from a secret key.

List its deposits

Requires a secret key.

const query = new URLSearchParams({
  from: String(Date.parse('2026-09-01')), // optional, milliseconds; default is the last 7 days
  to: String(Date.now()),
})
const history = await rhinoFetch(`/sda/deposit-addresses/${depositAddress}/ETHEREUM/history?${query}`)

Track deposits from a browser or app

Your frontend should not use a secret key, so it cannot call the history endpoint. Use the public status endpoint with a JWT from a public key instead. It requires the address’s destinationAddress, which your frontend already has from the create response. The request is rejected if the value does not match.

const query = new URLSearchParams({ destinationAddress })
const res = await fetch(
  `https://api.rhino.fi/sda/deposit-addresses/${depositAddress}/ETHEREUM/public-status?${query}`,
  { headers: { Authorization: jwtFromPublicKey } },
)
const { lastBridges } = await res.json()

lastBridges contains the most recent deposit, whether accepted or rejected. An empty array means no deposit has been detected yet.

Find your addresses

Search your project’s addresses. All filters are optional. destinationAddress also requires destinationChain.

From 9 November 2026, this endpoint requires a JWT created from a secret key. Call it from your backend.

const query = new URLSearchParams({
  addressNote: 'customer_8f3a21',
  depositChain: 'ETHEREUM',
  destinationChain: 'BASE',
  pageSize: '20', // default 20, maximum 50
})
// To fetch the next page, add pageToken=<nextPageToken from the previous response>
const results = await rhinoFetch(`/sda/deposit-addresses/search?${query}`)

Pause or update an address

You can pause, resume or update an address with the pause, unpause or update endpoint. Pausing is useful when you offboard a customer or want to stop accepting deposits on an address. A paused address is not monitored, so any funds sent to it get stuck and are not processed.

Fees

For subscription clients, most SDA fees are covered by the subscription. Many of the fields in the quote response’s fees object relate to the legacy pricing structure, so read them with that in mind. Tron, Solana and Bitcoin have additional onchain costs (see Tron, Solana and Bitcoin Access). On a subscription, you choose who pays them:

Paid by you. The cost appears in the sponsored section of the response and is invoiced in your month-end accounting.
Paid by your end customer. The cost appears in the non-sponsored section and is deducted from the amount settled on the destination chain.

Price a deposit

To show the fees for a deposit before your customer sends it, request a quote with isSda: "true". Use the SDA as the depositor and your destination address as the recipient:

const quote = await rhinoFetch('/bridge/quote/bridge-swap/user', {
  method: 'POST',
  body: {
    chainIn: 'ETHEREUM',
    chainOut: 'BASE',
    tokenIn: 'USDT',
    tokenOut: 'USDC',
    amount: '250',
    mode: 'pay',
    depositor: depositAddress,
    recipient: '0xYourTreasuryAddress',
    isSda: 'true',
  },
})
console.log(quote.receiveAmount, quote.fees)

This quote is for display only. Don’t commit it: Rhino.fi creates the transfer automatically when the deposit arrives. See the quote API reference for the full response. To set more granular fee rules or change an existing fee configuration, see Advanced Fee & Limit Management.

Get Started

SDK

Migration guides

Webhook

API Integration

Smart Contracts

Widgets

General information

How it works

1. Check where SDAs are available

2. Create an address

Request fields

Deposits that are not processed

Settle in a different token

Reuse addresses

Refunds

3. Monitor an address

Check its status

List its deposits

Track deposits from a browser or app

Find your addresses

Pause or update an address

Fees

Price a deposit

Next steps

Track transactions

SDA Widget

​How it works

​1. Check where SDAs are available

​2. Create an address

​Request fields

​Deposits that are not processed

​Settle in a different token

​Reuse addresses

​Refunds

​3. Monitor an address

​Check its status

​List its deposits

​Track deposits from a browser or app

​Find your addresses

​Pause or update an address

​Fees

​Price a deposit

​Next steps

Track transactions

SDA Widget

How it works

1. Check where SDAs are available

2. Create an address

Request fields

Deposits that are not processed

Settle in a different token

Reuse addresses

Refunds

3. Monitor an address

Check its status

List its deposits

Track deposits from a browser or app

Find your addresses

Pause or update an address

Fees

Price a deposit

Next steps