Skip to main content

Payments on Arbitrum

This page is the implementation entry point for teams building payments on Arbitrum. Payments settle as stablecoin transfers on Arbitrum One: fund in fiat or stablecoins, define your payout logic, execute transfers, and reconcile against an onchain audit trail. Arbitrum One supports USD-denominated stablecoins (USDC, USDT, PYUSD) and non-USD options with onchain volume (EURe, MXNB, MYRC), with sub-cent transaction costs and 24/7 settlement, which reduces the need to pre-fund nostro accounts across weekends and holidays.

Overview

We will dive into the deployment paths, which route into the technical documentation needed to implement the solution, and list the stablecoins, service providers, and a pilot checklist commonly used in production payment stacks. It assumes the deployment decision is already made—this is an orientation, not a decision aid.

Start on Arbitrum One

For most payment pilots, start on Arbitrum One before launching a dedicated Arbitrum chain. You get access to existing stablecoin liquidity with less infrastructure overhead.

Choose your deployment path

Three paths cover most payment builds:

  1. Settle on Arbitrum One — send stablecoin transfers with no custom contracts.
  2. Build a payments application on Arbitrum One — enforce payout logic onchain.
  3. Launch a dedicated Arbitrum chain — operate payments with chain-level control.

Each path routes into existing documentation. Where a path needs material that does not yet exist, that is marked explicitly below.

Use Arbitrum One as your settlement rail. Your product submits stablecoin transfers (e.g., USDC) over standard RPC. No custom smart contracts are required on day one. This path is mostly a matter of pointing existing tools at the right network.

Choose this when

  • You want a fast path to production
  • Compliance screening lives offchain with vendors such as Chainalysis—see Compliance and analytics in the payments ecosystem below
  • You need access to existing stablecoin liquidity and off-ramps
Wallet UX for pilots — ZeroDev

If payers or payees hold funds onchain, ZeroDev smart accounts (built by Offchain) provide passkey or social login, sponsored gas (or gas paid in your settlement ERC-20), and batched transfers on Arbitrum One without building wallet infrastructure from scratch. It works with whichever stablecoin you settle in, not USDC alone. See ZeroDev on Arbitrum.

Core documentation

If you want to confirm the full flow end to end before integrating, follow the testnet settlement walkthrough, which strings the steps above into a single payment-shaped recipe.

Build a payments application on Arbitrum One

Deploy Solidity smart contracts for treasury logic, routing, FX policy, or payout automation directly on Arbitrum One. Combine onchain execution with offchain compliance and fiat rails. If you later need chain-level control (custom gas, compliance engine, private execution), you can launch a dedicated Arbitrum chain and deploy the same style of contracts there.

Choose this when

  • Payout rules, limits, or multi-party approvals must be enforced onchain
  • You want composability with DeFi liquidity and existing Arbitrum integrations
  • You are building a proprietary orchestration layer (e.g., Rise programmable payroll)

Core documentation

Private payments

Confidential amounts and counterparties can be implemented at the smart contract layer on Arbitrum One or at chain level on a dedicated Arbitrum chain. On Arbitrum One, see Fhenix CoFHE (encrypted contract logic on Arbitrum Sepolia today) and Railgun (private transfers). Chain-level private execution is on the dedicated chain roadmap. For architecture scoping, contact Offchain Enterprise Services.

Sample payment contracts

Arbitrum docs do not yet include reference contracts for treasury, batch payout, or remittance flows. A reviewed batch-payout and treasury reference contract is in progress. Until it ships, use the USDC quick start guide to validate settlement and build payout logic on the application-layer references above, or contact Offchain Enterprise Services to design contract architecture. This page will link the reference contract here once it is published and audited.

Launch a dedicated Arbitrum chain

Deploy your own Arbitrum chain when you need control over network economics, fee denomination, permissions, and data visibility. This path fits teams scaling proprietary payment infrastructure. You can deploy your own payment smart contracts on the chain (the same programmability as a payments application on Arbitrum One) while adding chain-level controls that Arbitrum One alone cannot offer.

Many pilots settle in existing stablecoins. Teams can also issue a custom settlement token—for tokenized deposits, bank-branded assets, or a custom gas token on your chain. See Issuing your own stablecoin or contact Offchain Enterprise Services for issuance design.

Choose this when

  • You require stablecoin-denominated network fees (e.g., USDC, USDT as gas)
  • You need protocol-level compliance controls or restricted participation beyond application-layer screening on Arbitrum One
  • Proprietary routing, FX, or counterparty data must not appear on a public ledger

Ethereum L1 anchors security and finality; your chain settles stablecoins and payment contracts; offchain service providers handle fiat. A dedicated chain adds chain-level control—it does not replace third-party service providers.

Core documentation

Some features unavailable

Chain-level compliance tooling and private chain configurations are not yet available. This page does not document them.

Choose stablecoins by corridor

Map settlement assets to destination market, liquidity, and issuer requirements. Verify token addresses on Arbiscan before production.

USD-denominated (Arbitrum One)

StablecoinIssuerDescriptionDocumentation
Native USDCCircleDefault for most dollar pilots; native issuance on Arbitrum One with CEX support and direct redemptionUSDC on Arbitrum One · USDC quick start
Bridged USDC (USDC.e)Circle (via Arbitrum bridge)Legacy bridged USDC from Ethereum; prefer native USDC for new production flowsUSDC on Arbitrum One
USDTTetherWidely used in LATAM, Africa, and parts of APACTether documentation (external)
PYUSDPaxosPayPal USD on Arbitrum One; suited to PayPal ecosystem payoutsPaxos blockchains (external)
USDLPaxos InternationalYield-bearing USD stablecoin on Arbitrum One for treasury yield use casesUSDL on Arbitrum (external)

More USD-denominated tokens are listed on the Arbitrum Portal.

Non-USD-denominated (Arbitrum One)

Non-USD stablecoins with meaningful volume on Arbitrum today for corridor-specific pilots. Verify contract addresses on Arbiscan before production.

StablecoinIssuerDescriptionDocumentation
EUReMoneriumEuro e-money token, 1:1 with EUR; available on Arbitrum for SEPA-corridor and euro-native settlementEURe (external)
MXNBJunoMexican peso stablecoin, 1:1 with MXN; fiat-backed for LATAM corridor access on ArbitrumMXNB (external)
MYRCBLOXMalaysian ringgit stablecoin, 1:1 with MYR; issued on Arbitrum for APAC fiat and crypto railsBLOX / MYRC (external)

More non-USD-denominated tokens are listed on the Arbitrum Portal.

Issuing your own stablecoin

Deploy a custom ERC-20 on Arbitrum One with the Create a token quickstart. For bank-branded or corridor-specific settlement assets, work with issuance providers in the payments ecosystem below (for example, Circle bridged USDC on dedicated chains, or fiat-backed issuers such as Monerium, Paxos, and BLOX). Contact Offchain Enterprise Services for issuance architecture.

References and sources

The following service providers are commonly used in production payment stacks on Arbitrum. Links point to Arbitrum docs where available; external links go to provider documentation. Listing a provider does not imply an official commercial partnership with Offchain.

Fiat on- and off-ramps

ProviderDescriptionDocumentation
Yellow CardAfrica-focused fiat ↔ cryptoYellow Card (external)
MoonPayGlobal fiat on-rampMoonPay documentation (external)
BanxaFiat gatewayBanxa documentation (external)
TransakFiat on- and off-ramp APITransak documentation (external)

Custody

ProviderDescriptionDocumentation
FireblocksWallet and treasury infrastructure for institutional teamsFireblocks documentation (external)
BitGoQualified custody and wallet APIBitGo documentation (external)
Coinbase InstitutionalCustody and trading (Coinbase product)Coinbase Institutional (external)

Compliance and analytics

ProviderDescriptionDocumentation
TRM LabsBlockchain intelligence and AMLTRM Labs (external)
ChainalysisCompliance and investigation toolsChainalysis (external)
EllipticCrypto compliance and screeningElliptic (external)

Oracles and market data

ProviderDescriptionDocumentation
ChainlinkPrice feeds and automationChainlink on Arbitrum
Pyth NetworkReal-time financial market dataPyth documentation (external)
ProviderDescriptionDocumentation
ZeroDevOffchain smart account stack: gasless or ERC-20 gas, passkey/social login, batching, session keys for payouts on ArbitrumZeroDev on Arbitrum · ZeroDev docs

Payment orchestration

ProviderDescriptionDocumentation
Stripe (Bridge)Fiat and stablecoin payment infrastructureBridge documentation (external)
LayerZeroOmnichain messaging and tokensLayerZero on Arbitrum

Data and reconciliation

ProviderDescriptionDocumentation
AlliumArbitrum transfers, balances, and SQL/API analytics for treasury reconciliationAllium on Arbitrum (external)
The GraphIndexing and querying onchain payment dataThe Graph
CovalentUnified API for historical balances and transfersCovalent

Explore more projects on the Arbitrum Portal.

A minimal path from zero to a verified settlement on Arbitrum One. Skip steps that do not apply to your deployment path.

  1. Pick a deployment path. Most pilots start by settling on Arbitrum One without custom contracts. Add onchain treasury contracts if you need them; launch a dedicated chain only if you need chain-level control.
  2. Pick a stablecoin for your corridor. Dollar pilots: native USDC on Arbitrum One. See Choose stablecoins by corridor for USDT, PYUSD, or non-USD-denominated options (EURe, MXNB, MYRC).
  3. Prove settlement on testnet. Configure RPC via Chain info (chain ID 421614), fund Sepolia ETH and USDC (Circle faucet), and complete a transfer with the USDC quick start guide. Confirm on Arbitrum Sepolia Arbiscan. For a guided version, follow the testnet settlement walkthrough.
  4. Add ZeroDev if end users touch funds onchain. Integrate ZeroDev on Arbitrum for passkey login and gasless payouts. Skip this step if only your treasury wallet sends transfers.
  5. Wire production service providers before mainnet volume. Choose on-ramps, custody, and compliance screening from the payments ecosystem. Track payouts with Allium on Arbitrum when you need reconciliation at scale.

Get help