Skip to main content

Payments on Arbitrum

This page is the implementation entry point for teams building payments on Arbitrum. During evaluation you chose a deployment path, a settlement currency, and a set of provider categories. This page restates the three deployment paths in the same order you saw them, then routes each one into the technical documentation you need to implement it. It assumes the decision is already made — this is orientation, not a decision aid.

The three deployment paths, in order:

  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.

Settle on Arbitrum One​

For teams sending stablecoin transfers with no custom contracts. This path is mostly a matter of pointing existing tools at the right network.

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​

For teams enforcing payout logic onchain. This path routes into the application-layer documentation.

Info
A reviewed batch-payout and treasury reference contract is in progress and not yet available. Until it ships, build payout logic on the application-layer references above. This page will link the reference contract here once it is published and audited.

Launch a dedicated Arbitrum chain​

For teams that need chain-level control. This path has the deepest existing coverage; route directly into it.

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

Shared reference​

Relevant to all three paths: