Rhino.fi logo

BLOG

/

Multi-chain stablecoin deposit infrastructure: build vs buy

By Jader Manno

/

Most businesses that accept stablecoins on several blockchains should buy the parts of multi-chain stablecoin deposit infrastructure that cost more with each new network they add. Each network needs its own liquidity, upgrades and nodes, and brings new ways for a deposit to go wrong, so these costs rise every time the business adds one. They should keep in-house the parts that make the product theirs, which are the customer ledger, the experience around each deposit and the fees they charge. Building the whole stack in-house is the better answer in only a few cases, which are set out below.

 

At launch, deposit infrastructure usually looks simple: the product goes live on one chain, with one deposit address per customer (a blockchain address assigned to that customer, so every payment sent to it can be credited to the right account), and each deposit arrives in the token the business already runs on. Then customers start sending USDT on the TRON blockchain to a product that settles in USDC on Base. At that point the team needs a second address format, liquidity on the chain it settles on, a way to convert between tokens and a process for deposits that arrive on the wrong network.

 

This guide is for the CTO, head of product or payments lead making that call at a payment service provider (PSP), a neobank, a card issuer, a Banking-as-a-Service (BaaS) provider or a cross-border payments provider. It splits a deposit stack into seven jobs, shows which of them keep costing after launch, sets out when building wins and ends with the questions to put to any vendor. Rhino.fi sells stablecoin deposit and settlement infrastructure, so its own model gets one section near the end, and the vendor questions apply to it as well.

 

Quick Answer

For multi-chain stablecoin deposits, a business should build what differentiates its product and buy the parts whose cost rises with each new chain it supports. Liquidity on every destination chain, per-chain upgrades, nodes, screening and the handling of wrong-chain deposits are permanent operations, while a first integration is a one-off project. Building in-house fits a business that runs one or two chains, settles on the same chain deposits arrive on and already holds float (working capital kept in advance) there.

The seven jobs between a deposit and a usable balance

 

Multi-chain stablecoin deposit infrastructure turns a stablecoin payment sent on any supported chain into a usable balance for the right customer, in the token and on the chain the business operates on. The work behind it splits into seven jobs, so a build vs buy decision is really seven smaller decisions. For each of them, the useful question is what it costs every time support for a new chain is added.

 

Addresses are where chains first differ. EVM chains (the blockchains that run the Ethereum Virtual Machine, such as Ethereum, Base and Arbitrum) share one address format, while TRON, Solana, Bitcoin and Stellar are non-EVM chains, each with a format of its own. Detection then runs through RPC nodes, which are the servers an application queries to read a blockchain and send transactions to it, so every chain adds nodes to run.

 

Screening, in turn, comes in two layers. Know Your Transaction (KYT) screening checks where the incoming funds came from, while anti-money laundering (AML) screening applies the wider rules a regulated business follows, sanctions lists included.

 

Before crediting, the business also has to know that a deposit is final: finality is the point after which a transaction cannot be reversed. Until then, a reorganisation (the chain replacing its most recent blocks) can remove a deposit that briefly looked confirmed. Every chain reaches finality by its own rules: Ethereum, for example, finalises blocks in checkpoints rather than one block at a time. Rhino.fi’s guide to stablecoin settlement compares finality chain by chain.

Job

What it involves

What each new chain adds

Address issuance

Creating an address per customer or per invoice, and keeping its keys safe

A new address format on each non-EVM chain

Detection

Watching every address for incoming transfers through RPC nodes

Another set of nodes to run, monitor and pay for

Finality

Deciding when a deposit is safe to credit

A different finality rule to encode and test

Screening

Checking each deposit with KYT and AML tools before it reaches a balance

Another chain the screening provider has to cover

Routing and liquidity

Moving value to the chain the business settles on, or paying out from float already held there

More float to fund and rebalance

Conversion

Turning USDT into USDC, or one version of a token into another, at a rate known in advance

New token contracts (the onchain programs that define each token) and versions to recognise

Exceptions and reconciliation

Handling wrong-chain, wrong-token and out-of-limit deposits and refunds, and matching every deposit to a ledger entry

New ways for a deposit to go wrong

 

Token versions are the job most easily underestimated, because the same ticker (the short symbol, such as USDT) can be a different contract on each chain. Rhino.fi’s supported chains table, for example, lists USDT as USDT0 on Arbitrum and Polygon and as USDT.e on Base and Avalanche. A deposit stack therefore has to know exactly which contracts it accepts, or it credits a token it cannot settle. Rhino.fi’s article on why USDT is not always worth the same as USDC covers the conversion side, and the Smart Deposit Addresses page shows how a single programmable deposit address handles these jobs.

Which costs rise with every chain added?

 

Once the first integration is live, three costs keep growing with the number of chains:

  1. liquidity

  2. chain maintenance

  3. node infrastructure.

 

Address formats and the first integration are built once for each chain; these three costs, by contrast, keep running for as long as the product exists.

 

Liquidity is the largest of the three. To settle a deposit from one chain onto another in seconds, a business pays out from float that already sits on the destination chain, and it then moves that float back to where it’s needed as flows shift between chains. Rhino.fi’s pricing page estimates that a team running this internally “would hold seven figures of idle float to support $30M a month”.

 

Maintenance comes next, because every chain ships upgrades on its own timetable and some carry hard deadlines after which an outdated integration stops working. Rhino.fi, for example, counted roughly 12 to 15 mandatory or significant updates a year across Solana, TRON, Arbitrum and Base alone.

 

Watching deposit addresses also means constant node traffic, which Rhino.fi’s analysis puts at thousands of dollars a month at scale. Rhino.fi’s article on the cost of DIY stablecoin infrastructure goes through all three costs, chain by chain.

 

The TRON example from the opening shows how these costs compound. Besides the address format and the conversion, TRON brings its own nodes and its own finality rule, and enough USDC has to sit on Base to cover deposits from TRON. Every further chain brings the same set of requirements. Rhino.fi’s guide to USDT on TRON covers that network in more detail.

What stays with the business whether it builds or buys

 

Buying deposit infrastructure means handing a vendor one specific layer of the technology stack, one that is particularly complex and costly to maintain, while the product itself stays with the business. Whatever a vendor runs, the following remains the business’s own work:

  • The business keeps the ledger that records each customer’s balance, and reconciles it against the vendor’s settlement records.

  • Identity checks on its own customers stay with the business, unless a contract says otherwise in writing.

  • The deposit experience is the business’s to design, meaning which chains and tokens it shows, how the address is displayed and what customers see while a deposit settles.

  • The fees charged to customers are set by the business, which also decides whether to absorb network costs or pass them on, through the fee settings the provider offers.

  • Its regulatory position stays its own, meaning the licences it holds and the obligations that sit with it on each flow.

  • The business also decides where settled funds land, whether that is its own wallet, a custody provider’s wallet or an account inside an onchain application. In that last case, Rhino.fi’s Automated Onchain Actions extension, for example, deposits the funds directly into the destination protocol.

When does building deposit infrastructure in-house make sense?

 

Building multi-chain deposit infrastructure in-house makes sense when the deposit flow is simple and likely to stay that way, or when deposit infrastructure is the product the business sells. Buying, on the other hand, makes sense once customers choose their own chain and token and the business has to settle all of them into one balance.

Question

Points to building

Points to buying

How many chains do customers pay from?

One or two, and the list is stable

Several, and customers ask for more

Do deposits settle on the chain they arrive on?

Yes, same chain and same token

No, deposits need moving or converting

Does the business already hold float on each chain?

Yes, through an existing treasury operation

No, and capital tied up per chain has a cost

Are non-EVM chains such as TRON or Solana in scope?

No

Yes, each needs its own addresses, nodes and finality rule

How large are single deposits?

Small enough for any route

Large enough that route capacity matters

Who handles a deposit sent on the wrong network?

The business’s own support team, at low volume

A process that has to keep up with growing volume

Are deposits the product?

Yes, the business sells deposit infrastructure to others

No, deposits feed the business’s own product

 

Two cases settle the question on their own. A business that operates on one chain with no plans to expand does not need a cross-chain deposit layer, as Rhino.fi’s comparison of stablecoin infrastructure companies points out. By contrast, a business whose licence requires it to hold the keys to customer funds itself cannot use a vendor with custodial deposit addresses (where the vendor holds the keys), so its choice narrows to building, or to a custody platform (a provider that holds and secures the keys to digital assets for a business) with routing added on top.

Middle paths between building and buying

 

Between building everything and buying everything sit three common middle paths, and each leaves a different set of jobs in-house. They differ in who holds the keys and who moves the value. A bridge moves tokens from one blockchain to another, while a swap aggregator compares bridges and exchanges to pick a route for each transfer. Rhino.fi’s guide to choosing a cross-chain bridge model sets out how the models differ. A route may also run through a solver, which is a party that fills a transfer from its own funds on the destination chain and is repaid on the source chain.

Path

What the vendor runs

What the business still builds and runs

A custody platform, plus the business’s own routing

Key management, approval policies and screening rules

Cross-chain conversion through third parties, liquidity and exceptions

A bridge or swap aggregator, plus the business’s own operations

A route for each transfer across third-party bridges, exchanges and solvers

Addresses, detection, screening, reconciliation and exceptions; settlement depends on the venue the route picks

A deposit and settlement provider

Addresses through to the settled balance, from liquidity it runs at least partly itself

The ledger and the customer experience

 

The comparison of stablecoin infrastructure companies names the providers in each category and compares them on security, compliance, speed and coverage. Rhino.fi, for example, is a deposit and settlement provider in this sense, as the next section describes.

How Rhino.fi’s Activation Stack fits

 

Rhino.fi’s Stablecoin Activation Stack runs the jobs from the deposit address to the settled balance through one integration, by API or with Rhino.fi’s software development kit (SDK), while the business keeps its ledger and its customer experience. The payment service providers page shows how that works for merchant payments.

Deposit addresses and detection

 

Each end customer gets a Smart Deposit Address (SDA), and the address covers the chain families described earlier:

  • One SDA works on every EVM chain listed for it (docs).

  • Non-EVM chains such as TRON or Solana each get a separate address.

  • Rhino.fi still detects and settles a deposit sent on the wrong EVM network, provided every SDA-enabled EVM chain is listed for the address.

Screening, liquidity and settlement

 

Every deposit passes the same steps before it reaches the business’s balance:

  • Rhino.fi screens every deposit and every outgoing transfer for AML risk before anything is credited.

  • Rhino.fi runs KYT screening through TRM Labs, a blockchain analytics provider.

  • Rhino.fi settles each deposit from its own liquidity on the destination chain and rebalances that liquidity across chains around the clock, so a deposit does not wait for a third-party route to settle.

  • Rebalancing runs in the background, outside the path of the customer’s funds, so it does not hold up settlement (Rhino.fi).

Chains, upgrades and pricing

 

The jobs whose cost rises with every new chain, as described earlier, are covered by the subscription:

  • Refunds, chain upgrades and new token support are included in the subscription, so Rhino.fi runs them rather than the business’s own team (pricing).

  • The platform covers 30+ chains, and the supported chains table in the docs lists the ones where SDAs can be created.

  • A new EVM chain typically takes 1 to 2 days to evaluate and onboard from agreement (docs).

  • Pricing is a subscription matched to expected activity, rather than a fee in basis points (hundredths of a percent) on each transaction.

What stays with the business

 

The business keeps the parts of the product described earlier:

  • Its ledger and customer balances are fed by webhooks, which are status messages Rhino.fi sends to the business’s system at each stage of a deposit.

  • Funds land where the business chooses, which can be its own wallet or a wallet at a custody provider.

  • The business sets the fees it charges customers, by customer or by route, with the Advanced Fee & Limit Management extension.

  • The business chooses the chains and tokens it shows its customers.

What the published figures show

 

Rhino.fi’s published figures cover volume, reliability and speed:

  • Rhino.fi has settled more than $15 billion in stablecoin volume across 30+ chains (rhino.fi).

  • Its largest single transaction settled was $10 million, an amount Rhino.fi can take in one payment because the liquidity that settles it is its own.

  • Its deposit success rate is 99.99% across the flow from deposit to activation, which is the point where funds are usable in the product (pricing); Rhino.fi’s article on time to usable balance explains why that point matters.

  • Between 1 July and 30 September 2026, Rhino.fi completed 376,488 payments to Base in its fast mode (the settlement speed Rhino.fi applies automatically to transfers of up to $50,000 from EVM chains, starting processing after a single confirmation) from six origin chains, and on five of the six routes the median payment settled in 3 seconds or less (deterministic settlement).

  • The median was 1 second from BNB Chain and 48 seconds from Ethereum, and settlement times vary by route and transaction size.

Fiat ramps and key management

 

Two points complete the picture:

  • Fiat on- and off-ramps (services that turn bank money into stablecoins and back) are due in Q4 2026, so their launch is imminent.

  • Rhino.fi manages the keys to SDAs and holds deposits until they are swept, meaning moved from customer addresses into a central wallet (help centre).

Questions to ask before you choose a deposit infrastructure vendor

 

The build vs buy question for multi-chain stablecoin deposit infrastructure comes down to which of the seven jobs the business wants its own team running in three years’ time, when customers will likely pay from more chains than they do today. The questions below test an internal build plan as well as every vendor on the shortlist, Rhino.fi included.

  1. Which of the seven jobs does the vendor run, and which stay with the business?

  2. Whose liquidity settles a cross-chain deposit, and what happens when a route runs short of liquidity?

  3. What are the limits per transaction, and can they be set for the business’s flows?

  4. Can the business request support for a token or chain that isn’t supported yet? If so, what’s the process, how long does it take and how much work does it need from the business?

  5. What happens to a deposit on the wrong network, in an unsupported token or outside the limits, and who pays to return it?

  6. Who holds the keys to the deposit addresses, and who holds the funds until they are swept?

  7. What status updates does the business receive for each deposit, and are they enough to reconcile its ledger without reading the chains directly?

  8. Can the business test on mainnet (the live network) with small amounts before it signs?

  9. How is the service priced, and what does the price include: refunds, address monitoring, rebalancing, network fees?

  10. If the business leaves, what happens to the addresses its customers have saved?

 

If you are weighing these against an in-house plan, bring your chain mix, typical deposit size and volume to a call with the Rhino.fi team, who will walk through how each job would work for your flows.

Sources

 

Frequently asked questions

What is a deposit address in stablecoin payments?

A deposit address is a blockchain address that a business assigns to one customer or one invoice, so every stablecoin payment sent to it can be matched to that customer without a payment reference. The business watches the address for incoming transfers and credits the customer once the deposit is final and has passed screening. Rhino.fi’s Smart Deposit Addresses also convert each deposit and settle it on the chain and in the token the business operates on.

Can one deposit address receive stablecoins on every chain?

One address can receive stablecoins on every EVM chain, because EVM chains such as Ethereum, Base and Arbitrum share the same address format. A deposit is credited, however, only if the business watches that address on the chain it arrives on. Non-EVM chains such as TRON and Solana use address formats of their own, so each of them needs a separate address.

How long does it take to add a new chain to stablecoin deposit infrastructure?

For an in-house team, each new chain brings its own nodes, finality rule, screening coverage and token contracts, and a non-EVM chain adds a new address format as well, so every chain is a project of its own. With a deposit and settlement provider, the time depends on how the provider onboards chains. Rhino.fi, for example, typically evaluates and onboards a new EVM chain in 1 to 2 days from agreement.

Launch with an API.
Scale with a partner.

Built for complex global payments and onchain finance

Rhino.fi’s services are offered on a B2B basis to enterprise clients and are not directed at, and shall not be construed as an offer to, persons or entities in any jurisdiction where such offer would be unlawful.

© 2026 rhino.fi. All rights reserved.

Built for complex global payments and onchain finance

Rhino.fi’s services are offered on a B2B basis to enterprise clients and are not directed at, and shall not be construed as an offer to, persons or entities in any jurisdiction where such offer would be unlawful.

© 2026 rhino.fi. All rights reserved.

Built for complex global payments and onchain finance

Rhino.fi’s services are offered on a B2B basis to enterprise clients and are not directed at, and shall not be construed as an offer to, persons or entities in any jurisdiction where such offer would be unlawful.

© 2026 rhino.fi. All rights reserved.