Offer every customer a persistent, multi-chain stablecoin deposit address

​

Resources

​

Prerequisites

• An active Rhino.fi account with API credentials provisioned in Rhino.fi Console.
• The Rhino.fi SDK integrated into your backend services.
• One or more treasury wallets under your control on your settlement network, pooled or segregated per client to match your fund management model. This recipe settles USDT received on Tron as USDC on Base.
• A publicly accessible HTTPS endpoint to receive Rhino.fi webhook events.

​

How it works

1. Persistent deposit address: each customer is assigned one dedicated SDA that does not change.
2. Customer deposit: the customer transfers a supported stablecoin from any supported network (in this example, USDT on Tron).
3. Rhino.fi processing: Rhino.fi detects the inbound transfer, performs KYT/AML screening, and executes bridging and conversion.
4. Treasury settlement: funds settle into your treasury wallets as USDC on Base, or your chosen asset and network.
5. Ledger reconciliation: your backend receives a webhook, identifies the customer from the SDA’s addressNote, and credits their account.

​

Interactive demo

​

Step 1: Provision a dedicated SDA for each customer at onboarding

// Create a persistent deposit address for a new customer
const sda = await sdk.api.depositAddresses.create({
  depositChains: ['TRON'],                 // customers send USDT on Tron; add more chains here
  destinationChain: 'BASE',                // where you settle
  destinationAddress: TREASURY_WALLET,     // your treasury on Base
  addressNote: customer.id,                // your customer ID, returned on webhook events
});

// Save sda.depositAddress on the customer record to display it in-app.
// No separate SDA-to-customer mapping is needed: addressNote identifies the customer.

​

Step 2: Surface the deposit address in the customer’s account details

​

Step 3: Process settlement webhooks and credit the customer’s account

app.post('/webhooks/rhino', async (req, res) => {
  // Verify the event was signed by Rhino.fi
  const isValid = await sdk.api.webhook.verifySignature(req.body, req.headers['x-rhino-signature']);
  if (!isValid) return res.sendStatus(401);

  const { event } = req.body;
  if (event._tag === 'BRIDGE_EXECUTED') {
    // addressNote carries the customer ID set when the SDA was created
    await ledger.credit(event.addressNote, event.amountOut, 'USDC');
  }
  res.sendStatus(200);
});

​

Step 4 (optional): Configure fee sponsorship

​

Monitor transaction status

GET https://api.rhino.fi/sda/deposit-addresses/{depositAddress}/TRON/history?from={ms}&to={ms}

​

Operational considerations

• Misdirected deposits, handled for you: customers will occasionally send an unsupported token on a supported chain, or send to their address on a network it wasn’t set up for, such as the wrong EVM chain. Rhino.fi absorbs this complexity so your team doesn’t have to. Our support team refunds these deposits in full, with no fees deducted and refund gas covered by Rhino.fi, typically within 24 hours on business days once a refund address is confirmed. See how refunds on SDAs work for thresholds and refund destinations.
• Paused addresses: you can pause, unpause or update an SDA through the API, for example when closing a customer account (see pause, unpause or update deposit addresses). Deposits sent to a paused SDA are not processed, so avoid pausing addresses that customers may continue to use.
• Compliance holds: deposits that fail KYT/AML screening are not settled. Show these to the customer as pending review.

​

Reference architecture

​

In the wild: Wirex

​

How a Wirex Business customer funds their account with stablecoins

1

Open Account Details → Crypto

Alongside their bank transfer details, the customer sees a crypto deposit address and the tokens supported on the selected network (EURC, USDC and USDT on Base). The screen tells them deposits typically arrive within a few minutes and are automatically converted to their base currency.Rhino.fi: this is the customer’s dedicated Smart Deposit Address, created when the account was opened.

2

Choose the network they're sending from

Base, Arbitrum One, BNB Smart Chain, Ethereum, OP Mainnet, Polygon, Kaia, Tron, Solana or Stellar.Rhino.fi: one persistent address per chain family, monitored across every supported chain; deposits are bridged and converted before settlement.

3

Deposit received and credited

The customer sends stablecoins to their address, and the funds appear in their Wirex Business account converted to their base currency, usually within a few minutes.Rhino.fi: detects the deposit, screens it for KYT/AML, settles it to Wirex’s treasury and confirms by webhook, which is when Wirex credits the customer’s balance.

​

Outcome

“Wirex’s mission is to make stablecoin complexity invisible. Users should see a bank account, not a bridge or a chain.” — Daniel Rowlands, General Manager, Wirex