Relay — Crosschain Payments Infrastructure
Relay is a lightning-fast crosschain protocol — swap, bridge, and transact across 85+ chains instantly in seconds wtih no friction, no waiting on any chain.
For Web3 builders, developers, financial product teams, and enterprises integrating cross-chain payment infrastructure, Relay replaces the slow finality, fragmented liquidity, and unpredictable fees that have long made cross-chain payments hard to scale.
This guide explains how Relay works as a universal onchain payment rail: its architecture, how relay bridges and relay links move funds from a source chain to a destination chain in seconds, the security and trust assumptions behind that flow, the developer APIs and operational reliability teams depend on, where it fits against traditional bridges and banking rails, and what comes next for relay systems.
Relay Overview: From Walkie-Talkies to Universal Onchain Payment Rail
In electrical engineering, a relay is an electrically operated switch that uses a low-power signal to open or close a high-power circuit. Relays provide electrical isolation between low-power control circuits and high-power loads, and they show up everywhere: electromechanical relays use a magnetic coil to mechanically operate a set of contacts, while solid-state relays use semiconductor devices to switch power without moving parts. Reed relays contain contacts sealed inside a glass tube and switch quickly. Latching relays remain in their last state after the coil is de-energized. Normally Open (NO) contacts remain disconnected until the relay is energized, and Normally Closed (NC) contacts remain connected until the relay is energized. Amplification allows a weak signal to switch a larger current effectively. Safety isolation is a primary purpose of using relays in electrical systems, and relays are extensively used in industrial automation, vehicles, and electronic devices.
The crypto-native Relay borrows that metaphor. Instead of switching electrical circuits, this relay system routes onchain payments and cross-chain messages across networks, acting as infrastructure that can accept a payment on one chain and deliver it on another. Relay supports over 85 chains for cross-chain payments, enables sub-3-second settlement for cross-chain transactions, and has completed 1.6M+ transactions across those chains as of mid-2026.
Key takeaways for Web3 builders:
- Relay is a payment-focused relay system, not a speculative token bridge or hardware device.
- It processes real volume across 85+ chains with median settlement under three seconds.
- The platform combines smart contracts, relayer nodes, and routing logic to move funds deterministically.
- Features like fee sponsorship, fixed quotes, and smart wallet support (ERC-4337) position it as infrastructure for customers building financial products.
What Is a Relay System in Onchain Payments?
A relay system in crypto is a layered architecture combining onchain smart contracts and offchain relayer or solver networks. Its job is to monitor an event on a source chain - for example a deposit or lock event - and trigger corresponding actions on a destination chain, such as releasing funds to a payee. Think of it as connecting two mechanisms: the observation layer and the execution layer.
This is conceptually similar to how automatic control systems often utilize relays to manage power distribution in industrial settings, or how differential relays measure differences in incoming and outgoing current to signal faults. Protective relays monitor electrical quantities and command breakers to disconnect faults. Thermal relays operate based on the thermal expansion of a bimetallic strip, and time delay relays do not switch contacts immediately when energized or de-energized. In all cases, the relay acts as a control mechanism that responds to a signal and triggers an action - the same logic underpins onchain relay infrastructure.
In the payments context, a universal onchain payment rail uses relayers to help chains communicate while abstracting away chain differences such as fees, finality thresholds, and gas tokens. A user sends a payment request, and the relay system handles routing logic, gas costs, and currency conversion so the payment arrives on the destination network without the user managing chain-specific issues. Unlike many bridges built for DeFi speculation, a payment-focused relay system optimizes for reliability, deterministic reconciliation, and real time data observability for operations teams detecting failures before they reach customers.
Relay Bridge Fundamentals: Source Chain to Destination Chain
A relay bridge is Relay's optimized crosschain payment bridge. Where many bridges exist to move tokens for trading or yield farming, a relay bridge is designed specifically for payments - fast, reliable, and capital-efficient.
Here's a simple example. Suppose a USDC payment originates on Ethereum mainnet (the source chain) and needs to arrive on Base or Solana (the destination chain). With a well-funded route, the relay bridge completes this in roughly two seconds. Relay's cross-chain payments minimize gas costs and execution latency by using pre-funded liquidity rather than waiting for slow crosschain proof verification.
Relay bridges connect multiple blockchains using validator nodes, and relay bridges can mint wrapped tokens on destination chains when a lock-and-mint model is used. But there are typically two mechanisms at play in modern bridge design:
- Lock-and-mint / burn-and-mint: The asset is locked or burned on the source chain; a wrapped or canonical version is minted on the destination chain. This requires trust in a validator set or token issuer.
- Liquidity-based design: Pre-positioned liquidity on the destination side - or a unified balance deployed on-the-fly - allows instant release without waiting for lock verification. Relay largely favors this path for stablecoin payments, reducing idle capital.
Through its integration with Circle Gateway, Relay holds a single unified USDC balance and deploys liquidity across chains in under 500 milliseconds. This means the bridge contract on the destination chain can release funds almost instantly.
Where does trust live? In the relay set of relayers or solvers, in Circle for USDC issuance and attestation, in the escrow or treasury contracts holding locked funds, and in the bridge contract deployment itself. When two dollar pegged assets like USDC and USDT are involved, the trust assumptions also extend to the stablecoin issuer maintaining reserves.
How a Relay Link Works: From Payment Request to Final Settlement
A relay link is the logical path connecting a payer, the relay system, and a payee across one or more chains. It encapsulates routing, fees, currency, deadlines, and metadata so developers don't rebuild this logic themselves.
Here's the step-by-step process:
- An application (wallet, merchant, SaaS platform) submits a payment request via Relay's Requests API. The request specifies source_chain, destination_chain, amount, currency (e.g., USDC), and optional parameters like sponsor_fees, deadline, and destination gas sponsorship.
- Relay computes a quote, returning the expected fee, settlement time, and routing path (whether via Gateway unified USDC or per-chain reserves).
- Once the user agrees and the payer signs, Relay creates a payment intent and an order ID. On the source chain, the payer's funds are transferred to an escrow or burn contract to lock the asset.
- Relayer nodes observe this source chain event, validate it, then initiate execution on the destination chain. Using their liquidity or the unified balance, the relayer submits a transaction to move funds to the payee's destination address.
- Gas on the source chain is provided by the payer or sponsor; gas and fees on the destination chain are handled by relayer infrastructure.
- Settlement is confirmed back to the merchant or dApp via callbacks or webhooks, with status updates (pending, succeeded, failed).
The relay link encapsulates metadata - currency, amount, chain IDs, deadline, fee sponsorship rules, tracking identifiers, and refund paths - so the developer doesn't have to re-implement routing or error-handling logic. Each relay link is traceable end to end, making it simple to track progress and audit every payment.
Relay as a Universal Onchain Payment Rail
Zoom out from bridge mechanics and Relay looks less like a protocol and more like a universal onchain payment rail - a foundational layer beneath wallets, exchanges, and SaaS platforms.
One integration into Relay lets a team pay across 85+ chains, with sub-3-second median settlement and exactly 1:1 stablecoin payments with no hidden FX. Dollar pegged assets arrive at the payee in the same denomination and amount they left the payer, closing the gap that many bridges introduce through wrapper fragmentation or slippage.
Key proof points as of mid-2026:
- Relay processed $40B+ in cross-chain payment volume, proving rail-level scale with real volume.
- From March through June 2026, approximately $410M of user volume settled via Circle Gateway.
- Relay bridges enable liquidity across 85+ supported chains.
- Fee sponsorship and fixed-rate quotes let platforms present predictable pricing to end users even when gas markets are volatile.
This form of infrastructure lets teams focus on their product - payroll, invoicing, disbursements - while Relay handles the bridging underneath.
Bridge Relay Architecture: Relayers, Gateways, and Smart Contracts
A modern bridge relay architecture has several interacting components: onchain contracts deployed per chain (escrow, locks, withdrawals), offchain relayer or solver nodes, liquidity pools or a unified treasury such as Circle Gateway, and external services like token issuers or attestation mechanisms.
Relay nodes run full nodes on both connected blockchains, giving them direct visibility into on-chain state. Relay nodes monitor smart contracts for bridge transactions, watching for lock or burn events. When an event is detected, relay nodes produce cryptographic proofs for transaction authorization and submit execution transactions on the destination chain. Consensus typically requires a quorum of 2/3 or more nodes to confirm that a source chain event is valid before funds are released.
Where Relay diverges from classical validator-set bridges is capital management. Historically, bridge operators held per-chain reserves, leading to significant idle capital. Relay uses a centralized treasury on a primary chain plus programmatic replenishment of destination-chain liquidity in under 500 milliseconds via Circle Gateway. This means less money sitting idle on chain b waiting for a transaction that may not come for hours, and more capital available where it's needed.
End-to-End Flow: Relaying, Verification, and Execution
Consider a canonical example: Company A on Solana wants to pay a contractor on Arbitrum in USDC. The process breaks into three phases.
Phase 1 - Relaying. The payer's application calls Relay's Requests API, specifying source_chain = Solana, destination_chain = Arbitrum, amount, and currency. Relay returns a quote. The payer accepts, and funds are sent to Relay's escrow contract on Solana. Relay nodes confirm transactions by generating cryptographic proofs, and a quorum of 2/3 relay nodes typically confirms transaction locks before proceeding.
Phase 2 - Verification. The relayer verifying the source chain event constructs a proof or uses attestation, confirming the lock is valid and final. This phase accounts for source chain finality - waiting for sufficient block confirmations within a defined time window before treating the event as irreversible.
Phase 3 - Execution. The relayer executes on Arbitrum, using either pre-funded liquidity or drawing from the unified Gateway USDC balance. Funds arrive at the contractor's address. Relay enforces exactly-once semantics: payments either succeed or revert cleanly, avoiding duplicates and stuck funds. The application receives a webhook confirming settlement.
This service runs with strong observability - every phase is logged, and automated systems surface failures early so operations teams can act.
Trust, Finality, and Security in Relay Bridges
Every relay bridge carries trust assumptions that operators and users should understand. The core questions are: who controls the keys, what happens if something goes wrong, and how final is "final"?
Some relay bridges use fixed validator sets for node selection, meaning a predefined group of operators validates crosschain messages. Relay bridge security relies on the validator set - if compromised validators gain control, they can mint unlimited wrapped tokens on a destination chain. Wrapped tokens depend on the underlying reserves' security; if reserves are drained or broken, the tokens become worthless.
Mitigations include:
- Multi-signature schemes mitigate relay security risks by requiring multiple independent signers.
- Regular audits are essential for relay security, covering smart contracts, relayer logic, and treasury management.
- Segregated treasuries and withdrawal limits constrain worst-case losses.
- Relay systems can fail if relayers go offline or collude, so redundancy in the relayer network is critical for safety.
Finality varies by chain. Ethereum mainnet typically requires 12+ confirmations before a payment is treated as irreversible. Solana has faster block times but different revocation risk profiles. L2 chains have their own latency and finality properties. Relay accounts for these differences, only treating a source chain event as final after sufficient confirmations - detecting reorgs and triggering clean reverts or refunds if a payment cannot be fulfilled.
Failure scenarios - source chain reorgs, destination chain congestion, or relayer downtime - are handled via fallback paths (Gateway pool), automatic refunds, and real-time alerting. The key principle: a payment should never fail silently.
Relay Link for Developers: APIs, Dashboards, and Integration Patterns
For builders, the relay link is the primary abstraction. You create and manage relay links programmatically via Relay's Requests API, specifying parameters like source_chain, destination_chain, amount, currency, sponsor_fees, and deadline. The API returns quotes, creates payment intents, and delivers status updates via webhooks.
The relay dashboard serves as the visual control plane. Built-in views - Recent, Failed, Refunds - let teams filter by chain, currency, and status. Saved filters and real-time monitoring make it straightforward to monitor every relay bridge payment across all supported chains. You can export logs for reconciliation or compliance, and the dashboard surfaces real time data on settlement latency and failure rates.
Common integration patterns include:
- Single-treasury multi-chain payouts: Hold reserves on one chain, let Relay route payments to any destination network.
- Marketplace disbursements: Split payments to creators across chains, each split forming its own relay link.
- Subscription billing: Recurring crosschain payments with fee sponsorship so customers don't pay gas.
- B2B bulk payments: High-volume, low-touch pipelines where automation replaces manual intervention.
If you're evaluating Relay, start with a small test transfer on a testnet to validate the flow before committing to production volume. You can contact the Relay team for SLA details and enterprise onboarding.
Operational Reliability: Monitoring, Fees, and Treasury Management
Relay's relay system is built for teams operating at scale - millions of monthly transactions with predictable costs and strong monitoring.
Fee management includes sponsorship caps per transaction, accrual and withdrawal of protocol fees, and the ability for teams to optimize spend by choosing cheaper destination chains for payouts. Fixed-rate quotes mean that even when gas markets spike, the platform presenting payments to end users doesn't have to pass through volatile costs.
Treasury management workflows typically involve holding reserves on a primary chain, letting Relay route payouts to user-preferred destination chains, and reconciling via dashboard exports or API queries. The deposit and withdrawal cycle stays clean because every relay link carries full metadata for audit.
Consider the Splits collaboration example: 1,137 payouts moving $3.72 million with approximately two-second completion and zero manual intervention. This demonstrates that Relay can enable fully automated pipelines. No broken transactions, no manual reconciliation - just a pipeline that communicates results back to the application in real time.
Use Cases for Relay as a Universal Onchain Payment Rail
Global payroll and contractors. A company holds a USDC treasury on one chain and pays contractors across Base, Arbitrum, and Solana. Each payout is a managed relay link. The contractor receives funds on their preferred destination chain without the employer managing per-chain liquidity.
NFT royalties distributed crosschain. A marketplace owes royalties to creators who prefer payouts on different chains. Relay handles exact USDC transfers - no exchange rate surprises, no wrapper tokens. Each royalty payment is auditable and traceable.
SaaS invoicing. An enterprise SaaS platform invoices customers in USDC. The buyer selects which chain to pay from; the seller receives on their preferred chain. Relay's onchain payments process abstracts chain complexity.
Financial apps and exchange settlement. Trading platforms and financial apps use Relay as invisible infrastructure to settle cross-chain movements for their users. Relay often operates behind another brand, similar to how card processors sit behind consumer banking apps.
Comparing Relay Bridges to Traditional Bridges and Bank Rails
Traditional token bridges often serve DeFi-focused use cases. They tend to use lock-and-mint models, create wrapped asset fragmentation, and carry validator-set risk. Many bridges have suffered exploits precisely because of weak trust assumptions in their relay set or multisig configurations.
A payment-optimized relay bridge differs in several ways:
- Settlement guarantees: Deterministic settlement with exactly-once semantics, not probabilistic outcomes that can fail or leave funds stuck.
- Operational tooling: Dashboards, webhooks, fee sponsorship, and SLAs - not just a swap interface.
- Capital efficiency: Unified balances and sub-500ms liquidity deployment, rather than idle per-chain reserves.
Compared to traditional banking rails (ACH, SWIFT, card networks), Relay's universal onchain payment rail offers clear advantages in latency (sub-3 seconds versus hours or days), availability (24/7/365 versus business-hours-only operating windows), and transparency (every transaction is verifiable onchain). The gap between traditional finance and crypto payment infrastructure is narrowing, and Relay is accelerating that progress.
Future of Relay Systems and Universal Onchain Payment Rails
Looking ahead from 2026 to 2030, relay systems will evolve as more L2s, appchains, and enterprise chains launch. Relay has signaled intent to support new chains like Circle's Arc chain from day one, making new ecosystems immediately reachable via relay links.
Potential expansions include programmable compliance - embedded KYC/AML within relay links - and automated tax handling across jurisdictions. Support for additional stablecoins beyond USDC could broaden Relay's reach while retaining 1:1 semantics and minimizing risk. More modular solver networks, greater decentralization of relayer nodes, and formal trust models will strengthen the reliability and security profile of the entire system.
The trajectory is clear. Relay is moving from a crosschain bridge into foundational payment infrastructure for the multi-chain era - a universal onchain payment rail powered by secure relay bridges and developer-friendly relay links. If you're building payments in Web3, understanding this layer isn't optional. It's the infrastructure your product will eventually run on.