Deposit Addresses

Overview

Deposit addresses let users initiate crosschain transfers by sending tokens to a generated address. Call /swap/counterfactual with your route parameters and receive a unique depositAddress. The user sends the input token to that address on the origin chain. Across detects the transfer, sweeps the funds, and completes the crosschain transfer to the recipient on the destination chain.

This is ideal for:

• Onramps: user withdraws from a CEX or fiat onramp directly to a deposit address
• Bots and automation: no wallet signing flow needed
• Simplified UX: reduce the integration to a single token transfer

How It Works

const params = new URLSearchParams({
  useDepositAddress: "true",
  originChainId: "42161",
  destinationChainId: "1337",
  inputToken: "0xaf88d065e77c8cC2239327C5EDb3A432268e5831", // USDC on Arbitrum
  outputToken: "0x2000000000000000000000000000000000000168", // USDH on HyperCore
  amount: "1000000",
  recipient: "0xRecipientAddress",
  refundAddress: "0xUserOriginAddress",
});

const response = await fetch(
  `https://app.across.to/api/swap/counterfactual?${params}`,
  {
    headers: {
      Authorization: "Bearer YOUR_API_KEY",
    },
  }
);
const data = await response.json();

console.log("Deposit address:", data.depositAddress);
console.log("Send", data.inputToken.symbol, "to this address on origin chain");

import { erc20Abi } from "viem";

const hash = await walletClient.writeContract({
  address: data.inputToken.address,
  abi: erc20Abi,
  functionName: "transfer",
  args: [data.depositAddress, BigInt(data.inputAmount)],
});

console.log("Transfer tx:", hash);

const statusRes = await fetch(
  `https://app.across.to/api/deposit/status?depositAddress=${data.depositAddress}&index=0`
);
const status = await statusRes.json();

console.log("Status:", status.status);
console.log("Deposit tx ref:", status.depositTxnRef);

const depositRes = await fetch(
  `https://app.across.to/api/deposit?depositTxnRef=${status.depositTxnRef}`
);
const deposit = await depositRes.json();

console.log("Fill tx:", deposit.fillTxnRef);

API Parameters

Request

Response

Address Lifecycle

Each call to /swap/counterfactual returns a new, unique address. Deposit addresses are not intended to be reused.

Tracking Status

Track deposit status using the depositAddress and index parameters on /deposit/status:

GET /deposit/status?depositAddress=0x1234...abcd&index=0

The index is 0-based. Use 0 for the first (and typically only) deposit to that address.

The response uses the same status values as standard deposits: pending > filled / expired > refunded.

See Tracking Deposits for the full polling guide.

Fees

There is currently no deployment fee charged for generating deposit addresses. If a fee is introduced in the future, it will be:

• A fixed amount (not a percentage)
• Deducted from the user's input amount
• Included in the quote response

Bridge fees (relayer capital, destination gas, LP) are included in the response under fees.total and steps.bridge.fees.

Refund Behavior

If there's ever an issue with your bridge transaction while using /swap/counterfactual, please know your funds are not lost. Deposit addresses have built-in safeguards to ensure funds can always be recovered.

Below is a breakdown of each scenario, what happens automatically, and what steps you need to take to resolve it.

Need help recovering funds?

For any scenario that requires manual recovery, reach out to us with the following details:

1. depositAddress — the address returned by /swap/counterfactual
2. Token address — the contract address of the token you sent
3. Chain ID — the chain where the funds were actually sent

Contact us via Telegram, Discord, or Slack if your team has a shared channel with us.

This refund behavior is specific to /swap/counterfactual. For general refund timing and behavior applicable on all other APIs, see Refunds.