Transfers

Transfers are the core payment processing component of Infinite, handling movement of funds across fiat and crypto rails with built-in compliance.

Overview

A transfer moves money from a source account to a destination account, optionally converting between currencies. Transfers support:

Fiat to crypto — Deposit fiat, receive stablecoins
Crypto to fiat — Deposit stablecoins, receive fiat via SWIFT, SEPA, ACH, etc.
Crypto to crypto — Move between chains or stablecoins. Same-asset USDC/USDT across supported chains settles at par — see Same-asset bridging
Fiat to fiat — Cross-border fiat payments

Transfers are one-off: you specify the amount and destination per payment. For a standing deposit address that sweeps every incoming deposit automatically, see Fixed Routes.

Creating a Transfer

Every transfer requires a source, destination, amount, and payment reason:

import requests

response = requests.post(
    'https://api.infinite.dev/v1/transfers',
    headers={
        'Authorization': 'Bearer sk_live_...',
        'Content-Type': 'application/json',
    },
    json={
        'onBehalfOf': 'cus_abc123',
        'amount': {
            'currency': 'USDC',
            'rawValue': '100000000',
        },
        'source': {
            'currency': 'USDC',
            'paymentRail': 'ETHEREUM',
            'accountId': 'inw_source123',
        },
        'destination': {
            'currency': 'USD',
            'paymentRail': 'ACH',
            'accountId': 'eba_dest456',
        },
        'paymentReason': 'PAYMENT_FOR_GOODS_AND_SERVICES',
    },
)

const response = await fetch('https://api.infinite.dev/v1/transfers', {
  method: 'POST',
  headers: {
    Authorization: 'Bearer sk_live_...',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    onBehalfOf: 'cus_abc123',
    amount: {
      currency: 'USDC',
      rawValue: '100000000',
    },
    source: {
      currency: 'USDC',
      paymentRail: 'ETHEREUM',
      accountId: 'inw_source123',
    },
    destination: {
      currency: 'USD',
      paymentRail: 'ACH',
      accountId: 'eba_dest456',
    },
    paymentReason: 'PAYMENT_FOR_GOODS_AND_SERVICES',
  }),
});

export INFINITE_API_KEY=sk_live_...
infinite transfers create \
  --customer cus_abc123 \
  --amount 100000000 \
  --amount-currency USDC \
  --source-currency USDC \
  --source-rail ETHEREUM \
  --source-account inw_source123 \
  --dest-account eba_dest456 \
  --dest-currency USD \
  --dest-rail ACH \
  --reason PAYMENT_FOR_GOODS_AND_SERVICES

Send 100 USDC from inw_source123 on Ethereum to eba_dest456 as USD by ACH on behalf of cus_abc123, for goods and services.

# Via MCP this needs a write-capable session (agent key for payments, org key for onboarding — see /guides/mcp); otherwise run the CLI tab.

curl -X POST "https://api.infinite.dev/v1/transfers" \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "onBehalfOf": "cus_abc123",
    "amount": {
      "currency": "USDC",
      "rawValue": "100000000"
    },
    "source": {
      "currency": "USDC",
      "paymentRail": "ETHEREUM",
      "accountId": "inw_source123"
    },
    "destination": {
      "currency": "USD",
      "paymentRail": "ACH",
      "accountId": "eba_dest456"
    },
    "paymentReason": "PAYMENT_FOR_GOODS_AND_SERVICES"
  }'

Key Fields

Field	Description
`onBehalfOf`	Customer ID the transfer is for
`amount`	Amount as `MoneyInput` (`{ currency, rawValue }`) in minor units
`source`	Source account with `currency`, `paymentRail`, and optional `accountId`
`destination`	Destination account with `currency`, `paymentRail`, and `accountId`
`paymentReason`	Compliance reason code (e.g. `PAYMENT_FOR_GOODS_AND_SERVICES`, `TRADE_SETTLEMENT`) — see the create-transfer API reference for the full list
`quoteId`	Optional — reference a held quote to lock in an exchange rate
`confirm`	Optional — set `true` to submit immediately, otherwise creates as `DRAFT`

Response

{
  "id": "tfr_xyz789",
  "sourceCustomerId": "cus_abc123",
  "status": "PENDING",
  "source": {
    "currency": "USDC",
    "paymentRail": "ETHEREUM",
    "accountId": "inw_source123"
  },
  "destination": {
    "currency": "USD",
    "paymentRail": "ACH",
    "accountId": "eba_dest456"
  },
  "sourceAmount": {
    "currency": "USDC",
    "exponent": 6,
    "value": "100000000",
    "displayValue": "100.00"
  },
  "destinationAmount": null,
  "createdAt": "2026-01-15T10:30:00Z"
}

Transfer Status

Status	Description
`DRAFT`	Transfer created but not yet submitted
`IN_REVIEW`	Under compliance review
`PENDING`	Submitted, awaiting processing
`PROCESSING`	Actively being processed
`COMPLETED`	Successfully completed
`FAILED`	Transfer failed before funds were received
`CANCELLED`	Cancelled before completion
`REVERSED`	Funds were returned

If funds have already been received and the transfer needs manual review before it can be settled or returned, the transfer remains IN_REVIEW externally until it reaches COMPLETED or REVERSED.

Transfer Legs

Transfers are broken into legs (steps) that represent each segment of the payment flow. For example, a crypto-to-fiat transfer might have:

Crypto deposit leg — Customer deposits stablecoins
Conversion leg — Stablecoins converted to fiat
Fiat payout leg — Fiat sent to bank account

Each leg has its own status (PENDING, IN_PROGRESS, COMPLETED, FAILED, SKIPPED) and is visible in the transfer response under the legs array.

Deposit Instructions

When a transfer requires the customer to deposit funds (e.g. crypto or fiat), the response includes depositInstructions. One-off POST /v1/transfers onramps often reuse the same bank coordinates for a customer. There is no unique memo or transaction reference on those fiat instructions, so concurrent deposits cannot be told apart by bank details — matching is by amount. Parallel onramps at the same amount will collide. For concurrent or recurring USD→crypto, create a unique virtual bank account per destination with POST /v1/fixed-routes/virtual-bank-accounts and sweepTargetAccountId set to that wallet. Each route gets its own account number, so the deposit identifies itself. Listen for transfer.* webhooks on the auto-created sweep — no per-deposit create-transfer needed. The same pattern applies to crypto offramps via POST /v1/fixed-routes/virtual-wallets (unique deposit address per destination).

Crypto Deposit

{
  "depositInstructions": {
    "type": "crypto",
    "paymentRail": "ETHEREUM",
    "toAddress": "0x1234567890abcdef1234567890abcdef12345678",
    "amount": {
      "currency": "USDC",
      "exponent": 6,
      "value": "100000000",
      "displayValue": "100.00"
    }
  }
}

Fiat Deposit

{
  "depositInstructions": {
    "type": "fiat",
    "paymentRail": "ACH",
    "bankName": "JPMorgan Chase",
    "accountNumber": "1234567890",
    "routingNumber": "021000021",
    "beneficiaryName": "Infinite Inc",
    "amount": {
      "currency": "USD",
      "exponent": 2,
      "value": "10000",
      "displayValue": "100.00"
    }
  }
}

Amounts

All amounts in the API use the MoneyOutput format:

{
  "currency": "USD",
  "exponent": 2,
  "value": "10000",
  "displayValue": "100.00"
}

value is the amount in the smallest unit (cents, base units)
exponent is the number of decimal places
displayValue is the human-readable decimal

When creating transfers, use MoneyInput:

{
  "currency": "USD",
  "rawValue": "10000"
}

Tracking Transfers

import requests

response = requests.get(
    'https://api.infinite.dev/v1/transfers/tfr_xyz789',
    headers={'Authorization': 'Bearer sk_live_...'},
)

const response = await fetch(
  'https://api.infinite.dev/v1/transfers/tfr_xyz789',
  {
    headers: {
      Authorization: 'Bearer sk_live_...',
    },
  },
);

export INFINITE_API_KEY=sk_live_...
infinite transfers get tfr_xyz789

Show me transfer tfr_xyz789.

curl -X GET "https://api.infinite.dev/v1/transfers/tfr_xyz789" \
  -H "Authorization: Bearer sk_live_..."

Webhooks

Subscribe to transfer events for real-time updates:

transfer.created — Transfer created
transfer.processing — Transfer is being processed
transfer.completed — Transfer completed successfully
transfer.failed — Transfer failed before funds were received
transfer.cancelled — Transfer was cancelled
transfer.refund_initiated — Refund was initiated
transfer.refund_completed — Refund completed

See the Webhooks guide for setup instructions.

Next Steps

Quotes and Transfers

Learn about quoting and rate locking

SWIFT Payouts

Crypto-to-fiat via SWIFT wire transfers

Same-asset bridging

USDC or USDT from one chain to another at par

Get started

Core Concepts

Guides

Overview

Creating a Transfer

Key Fields

Response

Transfer Status

Transfer Legs

Deposit Instructions

Crypto Deposit

Fiat Deposit

Amounts

Tracking Transfers

Webhooks

Next Steps

Quotes and Transfers

SWIFT Payouts

Same-asset bridging

​Overview

​Creating a Transfer

​Key Fields

​Response

​Transfer Status

​Transfer Legs

​Deposit Instructions

​Crypto Deposit

​Fiat Deposit

​Amounts

​Tracking Transfers

​Webhooks

​Next Steps

Quotes and Transfers

SWIFT Payouts

Same-asset bridging

Overview

Creating a Transfer

Key Fields

Response

Transfer Status

Transfer Legs

Deposit Instructions

Crypto Deposit

Fiat Deposit

Amounts

Tracking Transfers

Webhooks

Next Steps