Skip to main content
See some live use cases here: 5 ways to use SDAs
Premium Extension: 1:1 Stablecoin SwapsWhen the 1:1 Stablecoin Swaps extension is enabled on your account, cross-stable conversions (USDT→USDC and USDC→USDT) are executed at a guaranteed 1:1 rate with no slippage and no market exposure. This removes the guesswork from mixed-stablecoin deposit flows.Learn more →

​
The Flow

At a high level, the process works as follows:
  1. Generate an SDA: Call the API to create a new deposit address, linked to a destination chain and address or a target action (coming soon).
    We strongly recommend generating an SDA on all available EVM chains immediately to ensure that funds accidentally sent by customers to the wrong chain are automatically detected.
  2. User deposits: Any wallet, CEX, or payment service can send supported tokens to the SDA. The user only performs a normal token transfer.
  3. Monitoring & orchestration: The system continuously watches for incoming transfers. If a valid deposit arrives (correct token, within limits), it triggers the bridge process.
  4. Cross-chain execution: Funds are credited on the destination chain, or the requested Automated Onchain Action (e.g. swap, pool deposit) is performed.
  5. Reconciliation & sweeping: After crediting is complete, addresses are swept periodically to consolidate balances and keep monitoring efficient.
From the client/user perspective: user sends → destination credited → job done.

​
The Features

Key properties that make SDAs flexible:
  • Many-to-one: Multiple SDAs can funnel to the same destination address.
  • Multi-chain source support: SDAs can currently be generated on the top EVM chains like Ethereum, Arbitrum, Base, BSC, Polygon, Optimism, Kaia, Tron, and Solana. Full list available under Supported Chains → Smart Deposit Address.
    Generating a Tron (and Solana) SDA requires a separate call. I.e. you can specify all EVMs to generate SDAs across all EVMs. Then generate a Tron and Solana SDA with separate calls.
  • Webhooks – Real-time push updates on deposit results.
  • Any-chain destination: Funds can settle on any of the 35+ Rhino-supported chains, including non-EVMs (Starknet, Ton, Solana, etc.).
  • Stablecoin primitives:
    • Same-to-same (e.g. USDC → USDC)
    • Cross-stable swap (e.g. USDC → USDT) — with the 1:1 Stablecoin Swaps extension, cross-stable conversions execute at a guaranteed 1:1 rate with no slippage
  • Programmable actions: Trigger Automated Onchain Actions like swaps, pool deposits, or contract interactions.
  • Metadata support: Attach arbitrary data (e.g. UUID) to track users, payments, or invoices.
  • Flexible fees: End users pay standard fees by default. With the Advanced Fee & Limit Management extension, clients can sponsor fees on behalf of end users, or add a configurable markup that Rhino collects and remits via end-of-month invoicing.
  • Validity: unlimited
  • Deposit size: Typically 5-digit USD+ supported, 7-digit on request.
  • 100% KYT screening: Every deposit is screened for KYT/AML before crediting. Clients never receive funds that fail compliance checks. Enhanced screening options and real-time AML notifications are available via the Enhanced Compliance & Risk Management extension.
  • Privacy benefit: SDAs are naturally decoupled from destination addresses.
Coming soon:
  • Refund address – Users/clients can specify fallback if a credit fails (< 1% of cases).

​
The Constraints

There are some limitations to be aware of:
  • Native tokens (ETH, BNB, SOL, etc.): Native token support is currently in beta rollout, including both direct SDA bridging and native → stablecoin swaps. Contact us if you’re interested in using native token deposits.
  • Wrong tokens will not be credited and require a manual refund.
  • Deposits below $5 USD equivalent or above set limits will not process and require a manual refund.
  • If liquidity is insufficient, deposits will retry until successful or refunded.
  • Fees can be fetched in real time through the API or fixed by agreement.

​
Core Technologies

Several technologies come together to make Smart Deposit Addresses (SDAs) work in practice:
  • API / SDK (SDA generation): Developers generate deposit addresses via Rhino’s API or SDK with zero blockchain complexity. No private key management or contract deployment is required.
  • Wallet & App Transfers (funding SDA): Any wallet, CEX, or app that supports token transfers can send funds to an SDA. This keeps the user interaction primitive and universal.
  • Rhino Solver & Liquidity Layer (orchestration & crediting): Our solver system monitors deposits in real time and uses Rhino’s liquidity to credit the specified destination chain/address.
  • Reconciliation (sweeping): On EVM chains we use EIP-7702; for non-EVMs we maintain custom implementations. This ensures SDA balances are reconciled safely after crediting.

​
Before You Start

Default limits apply to Smart Deposit Addresses for initial testing purposes:
  • 500 total SDAs
  • 50 SDAs generated per hour
Please contact us to lift your limits.
  • You’ll need an account in the Rhino Console.
  • The API docs are the source of truth for supported chains, tokens, and endpoints.