Rhino.fi logo

BLOG

/

Rhino.fi vs Relay: who funds the payout on a cross-chain stablecoin deposit

By Tara Annison

/


Last fact check: 18 November 2026. We review this page again by 10 January 2027.


Rhino.fi vs Relay comes down to whose money pays the customer on the destination chain. Relay (relay.link), the cross-chain payments and bridging platform, hands each cross-chain order to a solver: a company that pays out on the destination chain from its own funds and is repaid from the customer’s deposit afterwards. Rhino.fi, which provides stablecoin payments infrastructure to businesses, settles each payout from reserves it keeps itself on every chain it supports.


Both are fast, and both give a business deposit addresses, screening and stablecoin conversion. For anyone weighing a relay.link alternative for stablecoin deposits, the choice therefore turns on three questions: what limits a single payment, who carries a fixed 1:1 rate (one USDT always converted to one USDC), and what the business must fund itself. This page answers them, and the answers can be useful to a product or payments lead at a payment service provider, neobank or remittance business. And, of course, to anyone who wants to dig deeper into the topic.


Rhino.fi wrote this comparison, so every Relay fact below comes from Relay’s own documentation, read on 16 November 2026, or its public API, read on 18 November 2026, and is listed under Sources. Where Relay’s pages are silent, the page says so rather than guessing. Readers who spot something out of date can let us know, and we will fix it.


On 1 September 2026, the Rhino.fi retail app was retired. Rhino.fi operates today as a B2B provider of stablecoin payments infrastructure, the Stablecoin Activation Stack, which businesses use to accept stablecoin deposits on many chains and settle them in the token and on the chain they choose.

How Relay pays out a cross-chain deposit


When a customer pays through Relay, Relay first quotes the order, the customer sends the funds, and a solver then fills the order, which means it delivers the requested token to the recipient on the destination chain. In Relay’s words, “a solver uses its own capital to complete the requested action on the destination chain”. Rhino.fi’s guide to choosing the right cross-chain bridge model sets this kind of design beside the other ways value moves between chains.


The solver gets its money back afterwards, from the customer’s deposit. On orders that use Relay Protocol (Relay’s own settlement system), that deposit waits in a Relay contract on the origin chain until Relay’s own settlement chain records the fill, and the solver then claims it. Relay’s docs describe solvers as “participants, not a single protocol-wide operator”.


The design favours speed, because solvers fill “before origin chain finality”, the point after which the origin chain’s record of the deposit can no longer be reversed. Since there is “no orderflow auction or solver competition window”, an order is filled as soon as a solver receives it. Relay’s payments pages give a median fill time under 3 seconds across all routes and “99.9%+ fill success” on supported routes.


Since each payout is paid from solver funds, what a route can carry depends on what solvers hold there at that moment. Relay publishes those holdings through a public endpoint (an address in its API that software can query), which reports solver balances per token on each chain, and Relay’s error list includes the case where “the solver’s available capacity for this route has been exceeded”.

How Rhino.fi pays out the same deposit


Where Relay relies on solvers, Rhino.fi pays the same deposit out of its own reserves, which changes where the money comes from, what the quote fixes and how fast the payout lands.

Where the payout money comes from


Rhino.fi pays out of money it owns and keeps on the chains it supports:

  • Each payout is drawn from reserves Rhino.fi owns on the chain where it lands.

  • The homepage puts it in one line: “We’re a native liquidity provider, not an aggregator.”

  • Because Rhino.fi holds reserves across 30+ chains, “every transaction settles from Rhino-owned liquidity, never routed through third-party bridges or public DEXs” (Bridge and Convert), where a DEX is a decentralised exchange run by smart contracts (programs that run on a blockchain).

  • Rebalancing, the work of moving reserves between chains so each one stays stocked, runs 24/7 and separately from the customer’s payment, as Rhino.fi’s post on liquidity orchestration explains.

What the quote fixes


A Rhino.fi quote sets what the business receives before the payment moves:

  • The homepage states the commitment as “The amount you quote is the amount that settles”.

  • The docs say Rhino.fi honours the quoted fee until the quote expires.

  • Webhooks (automatic messages sent to the business’s backend) report each stage of a deposit.

How long settlement takes


Rhino.fi measures speed as time to usable balance (how long it takes until the business can actually use the funds), and publishes both a typical time and its own route data:

  • The published figure is “Under 10 seconds from deposit to usable balance” (pricing), a typical time that varies with route and size.

  • Between 1 July and 30 September 2026, Rhino.fi ran 376,488 fast-mode payments (payments on its fastest speed setting) to Base, with a median of 1 second from BNB Chain and 48 seconds from Ethereum, where a deposit takes longer to become irreversible (article on deterministic settlement).

  • By size, settlement typically takes under 10 seconds below $500,000 and typically under 60 seconds from $500,000 to $5 million.

The size limit on a single payment


On Relay, the ceiling for a single payment follows a maximum per token pair and the solver balances on that route. On Rhino.fi, the Smart Deposit Addresses page states it can take “up to $10M in a single SDA deposit”, with limits set per project and higher ones on request.


To see Relay’s side in practice, we read its public API at 13:46 UTC on 18 November 2026, for payments that end as USDC on Base:

  • The liquidity endpoint reported about $4.5 million of USDC held by solvers on Base, the chain where these payments end.

  • Deposit-address quotes for USDC from Ethereum came back at $1 million, $3 million, $4 million, $5 million and $6 million, each with a 24-second time estimate.

  • Requests for $7 million, $8 million and $10 million were refused with the message “Amount is higher than the available liquidity.”

  • USDT from TRON was quoted at up to $2 million with a 1-second estimate, and requests for $3 million and $5 million were refused because the amount “exceeds the maximum for this pair”.


These figures describe one route at one moment. Because solver balances move all day, the ceiling on Relay can be higher or lower tomorrow, and Relay’s docs suggest splitting an amount above the per-pair maximum into smaller quotes. Rhino.fi’s $10 million, by contrast, is the amount it states it can take in one deposit rather than a live quote, and it matches the largest single transaction Rhino.fi has settled. Rhino.fi can take this amount because it settles it from its own liquidity, and its limits are “a configuration choice matched to your profile, not a fixed ceiling”.

Rhino.fi vs Relay side by side


Every cell below quotes or summarises what the company itself publishes, as read on 16 and 18 November 2026. Where a cell says “Not published”, our search of that company’s pages came up empty, which does not necessarily mean the thing is missing.


Relay

Rhino.fi

What it is

“A developer platform” to “swap, pay, and transact across every blockchain” through “enterprise-grade APIs”

One integration covering stablecoin deposit addresses, screening, settlement and onchain actions

Who pays out

A solver, from its own capital, repaid through Relay Protocol

Rhino.fi, out of reserves it holds on the destination chain

Chains

“85+ Chains” on its payments page; its public chain list returned 58

“30+ chains”; Smart Deposit Addresses on most of them

Tokens

Varies by chain; same-chain and cross-chain swaps

“All major stablecoins”

TRON

Deposit addresses enabled; USDT and TRX (TRON’s own coin) accepted

USDT, through Smart Deposit Addresses and transfers

Fixed 1:1 USDT/USDC

Fixed rates set per quote; the gap to the market rate is settled from a balance the business funds

1:1 Stablecoin Settlement from Rhino.fi’s reserves, inside a 3 basis point (0.03%) band around 1:1, which can be widened up to 20 basis points

Fees

Per transaction: $0.02 plus gas (the network fee), swap costs, and a platform fee from 0% on bridges to 0.15% on minor swaps

Monthly subscription by tier, with overages; no fee in basis points; prices not published

Published speed

Median fill under 3 seconds across all routes

“Under 10 seconds from deposit to usable balance”, typical

Largest single payment

Not published; capped by a maximum per token pair and by solver balances on the route

“Up to $10M in a single SDA deposit”

Deposit addresses on Relay and Rhino.fi


Before either provider can pay out, the customer needs somewhere to send the funds. A deposit address lets a customer pay the ordinary way, from their own wallet or as an exchange withdrawal, with no wallet connected to the business’s app. Relay and Rhino.fi both offer one, and they are built for different jobs.

Relay’s open and strict addresses


Relay offers two kinds of deposit address, and the same processing rules apply to both:

  • An open address can be reused for the same route (the same token and chain in, and the same token and chain out), and each new deposit is filled with the fee settings of the original quote.

  • A strict address accepts one deposit, and Relay recommends it for single-use payment instructions, such as one address per invoice.

  • Relay processes only the tokens it lists for solvers on that chain, and a deposit too small to cover the fees is refunded, or stays at the deposit address if it cannot cover the gas for the refund.

  • A deposit address works only on chains that share its address format. If a customer sends funds to it on another supported chain of the same type, Relay processes the deposit automatically when the quote fixed the amount sent, and needs its support team to step in when the quote fixed the amount received.


Refunds go back on the origin chain to a refund address the business sets, less the gas for the refund. Relay requires a refund address on every deposit-address quote, open or strict. For senders paying from exchanges, Relay suggests a refund address the business controls, because a refund to the sending address would reach the exchange’s wallet instead of the customer.

Rhino.fi’s Smart Deposit Addresses


Rhino.fi gives each end customer one reusable Smart Deposit Address (SDA), which covers several chains at once:

  • One address covers every EVM chain the business lists, EVM chains being those that run the Ethereum Virtual Machine and share one address format, such as Ethereum, Base and Arbitrum.

  • Solana, TRON, Bitcoin and Stellar each get their own address.

  • A deposit sent on the wrong EVM network is still detected and settled, as long as that network is listed on the address.


A deposit is processed when the token is supported, the amount is within limits and it passes anti-money laundering (AML) screening. Anything else is returned by Rhino.fi to a verified address, because funds sent back to a pooled exchange wallet (one address an exchange uses for many customers’ withdrawals) “may never reach” the customer who paid from it. A deposit that meets a temporary liquidity gap on its route “is retried until it settles or is refunded”.

Holding a fixed 1:1 rate between USDT and USDC


Once a deposit arrives in one stablecoin and has to settle in another, someone has to carry the rate between them, because USDT and USDC trade at a market rate against each other, since their values differ. Both providers can deliver USDT and USDC at 1:1, and they put the cost of holding that rate, and of the float behind it, in different places. Float is money a business keeps parked on a chain so payouts can leave before incoming funds arrive.


Relay offers two optional features for this, and both draw on an app balance the business funds, held in USDC on Base:

  • Price Stabilization lets a business “lock in a specific exchange rate (e.g. 1:1) and absorb the volatility yourself”, and after each fill the difference to the market rate is posted to the balance as a credit or a debit.

  • Fast Fill pays the destination before the origin deposit lands, and if that deposit never lands, “the sponsoring app bears the loss”.


Without either feature, the solver’s capital carries the payout and the business holds nothing on Relay.


Rhino.fi’s 1:1 Stablecoin Settlement converts USDT and USDC at 1:1 thanks to its own reserves, in both directions, as long as USDT/USDC trades within 3 basis points (hundredths of a percent) of 1:1. With the Advanced Fee & Limit Management extension, a business can widen that band up to 20 basis points. Beyond that band, or above a volume limit, conversion falls back to the market rate, and for a single conversion above $1 million Rhino.fi’s account manager first confirms the liquidity available. This feature is available on every plan, and the pricing page lists “No liquidity requirement or infrastructure build on your balance sheet”.

Screening before money moves


Both providers screen before money moves, and the difference lies in control: Relay documents the screening vendors it relies on; Rhino.fi does the same, but also lets the business bring its own screening providers.


Relay screens every address in a transaction: the sender, the recipient, and any refund, recovery or fee address. It does so on every flow, once when the quote is requested and again before the fill, with four sources running in parallel: TRM Labs, Chainalysis, ZeroShadow and Relay’s own blocklist. Relay also publishes a list of exchanges it does not accept deposits from, and keeps screening records that partners can ask for.


Rhino.fi screens every deposit to a Smart Deposit Address before crediting it, using Know Your Transaction (KYT) checks from TRM Labs, which trace where incoming funds have come from. Deposits from flagged addresses are blocked automatically (Enhanced Compliance docs). With the Enhanced Compliance & Risk Management extension, a business adds its own rules from “Chainalysis, Elliptic or your own in-house solution”.

Rhino.fi vs Relay: which fits which payment flow

When Relay fits


Relay is likely the closer fit in these cases:

  • The business needs chains or tokens beyond Rhino.fi’s list, since Relay names 85+ chains.

  • Most of its payments are small and frequent, so a per-transaction fee and a sub-3-second median fill matter most.

  • It wants deposit addresses on many chains with a strict mode for one-off orders.

When Rhino.fi fits


Rhino.fi is likely the closer fit in these cases:

  • Single payments run into the millions, and the business wants one provider paying them out of its own reserves.

  • Its customers pay in USDT while it holds USDC, and it wants the 1:1 rate held by its provider rather than by a balance it funds.

  • Each customer should keep one reusable address, as described earlier, and every deposit should pass KYT screening, with the option to add the business’s own screening provider.

  • The business wants each deposit put to work on arrival, which Automated Onchain Actions do by sending an instruction to a smart contract when the deposit settles, such as a deposit into a vault (a smart contract that holds pooled funds).

  • It needs payment infrastructure that keeps settling “through congestion, volatility and chain outages”, which Rhino.fi supports by rebalancing the liquidity it owns across internal and external routes 24/7, with 99.99% uptime.


Rhino.fi’s pages for payment service providers and remittance providers cover the payments case in more depth, and the post on how the main stablecoin infrastructure companies compare shows where both sit among other providers.

What should you send either provider before a call?


Both providers give a straighter answer when they see the flow first, so a business gets more from a first call when it prepares the following:

  1. The chains and tokens its customers pay in, and the token and chain it settles in.

  2. Its largest single payment, and how often a payment that size happens.

  3. The share of deposits that come from exchanges or other pooled wallets.

  4. Whether it needs USDT and USDC at a fixed 1:1, and who should hold the spread.

  5. Its monthly volume, and whether it wants fees per transaction or a fixed monthly cost.

  6. The screening it runs today, and which provider its compliance team already uses.


Rhino.fi works from the same list, so book a call with the team and we will map your corridors onto Smart Deposit Addresses.

Sources


Documentation and web pages read 16 November 2026; API reads on 18 November 2026.


Relay


Rhino.fi

Frequently asked questions

What is the difference between Rhino.fi and Relay?

The difference lies in whose money pays the customer on the destination chain. Relay hands each cross-chain order to a solver, a company that pays out from its own capital and is repaid from the customer’s deposit afterwards. Rhino.fi pays every payout from reserves it owns on each of the 30+ chains it supports, so the amount it quotes is the amount that settles.

What is a relay.link alternative for stablecoin deposits?

Rhino.fi is an alternative to Relay for businesses that accept stablecoin deposits and want every payout funded from the provider’s own reserves. Each end customer gets one reusable Smart Deposit Address across chains, every deposit is screened with Know Your Transaction (KYT) checks from TRM Labs, and settlement typically takes under 10 seconds from deposit to usable balance.

Who carries the 1:1 rate between USDT and USDC on Relay and on Rhino.fi?

On Relay, a business can fix a rate such as 1:1 on each quote, and the difference to the market rate is then posted as a credit or a debit to a balance the business funds. Rhino.fi’s 1:1 Stablecoin Settlement converts USDT and USDC at 1:1 from its own reserves while the market stays within 3 basis points (hundredths of a percent) of 1:1, a band that can be widened up to 20 basis points with the Advanced Fee & Limit Management extension. The feature is available on every plan.

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.