Accounts

Accounts are the financial infrastructure layer in Infinite. They represent where funds are held and how they move — whether through traditional banking rails or blockchain networks.

Overview

Infinite uses a typed account system where each account serves a specific purpose. Accounts are always linked to a customer and have distinct creation endpoints. Think in roles, not just type names. The same INFINITE_WALLET (inw_) type is used for a deposit mailbox and for a treasury vault.

Role	Type	Prefix	What it is
Fiat mailbox	`VIRTUAL_BANK`	`vba_`	Bank details we issue so a customer can send ACH, wire, or SWIFT
Crypto mailbox	`INFINITE_WALLET` (`walletType: VIRTUAL`)	`inw_`	Dedicated deposit address from `POST /v1/fixed-routes/virtual-wallets`
Vault (custodial)	`INFINITE_WALLET` (treasury)	`inw_`	Where Infinite holds crypto. Auto-provisioned. Source of withdrawals
Their bank	`EXTERNAL_BANK`	`eba_`	Customer’s own bank account. Payout destination
Their wallet	`EXTERNAL_WALLET`	`ewa_`	Customer’s own address. Payout, sweep target, or a co-signer / guard they control
USD / stablecoin balance	`VIRTUAL_BANK` / `PROVIDER_BALANCE`	`vba_` / `pba_`	Held balance, not a sweep

Infinite Wallets (`INFINITE_WALLET`, `inw_`)

Blockchain wallets managed by Infinite on behalf of your customers. There is no public create endpoint for treasury wallets — they are provisioned automatically when a customer is approved. List them with GET /v1/accounts?type=INFINITE_WALLET. Three jobs share this type:

Treasury (vault) — holds balances; source for withdrawals and payouts
Transaction — system-controlled address used while a one-off transfer is in flight
Deposit mailbox (walletType: VIRTUAL) — created by crypto fixed routes. Unique receive address that auto-sweeps to a bank or wallet

Do not treat a treasury inw_ as something you can sandbox-fund. Account fund-in only accepts funding-method ids (vba_, vwa_, pba_). To credit a vault in sandbox, pick a fixed route whose sweep target is that vault, then simulate a deposit with the route’s source account id (vba_… or mailbox inw_…). Funds land on the destination, not the source mailbox. Then create a transfer from the vault. You cannot attach a third-party key as a co-signer on an Infinite wallet. If you need a customer-controlled address (a guard, guardian, or self-custodial destination), create an external wallet. Supported address types: EVM, SOLANA, TRON, BITCOIN

External Bank Accounts

Bank accounts owned by your customers at external institutions. Used as payout destinations for fiat transfers.

import requests

response = requests.post(
    'https://api.infinite.dev/v1/external-bank-accounts',
    headers={
        'Authorization': 'Bearer sk_live_...',
        'Content-Type': 'application/json',
    },
    json={
        'customerId': 'cus_abc123',
        'beneficiaryName': 'Acme Corp',
        'paymentRails': ['swift'],
        'swiftBic': 'CHASUS33',
        'accountNumber': '1234567890',
        'beneficiaryAddress': {
            'addressLine1': '123 Main St',
            'city': 'New York',
            'state': 'NY',
            'postalCode': '10001',
            'country': 'US',
        },
    },
)

const response = await fetch('https://api.infinite.dev/v1/external-bank-accounts', {
  method: 'POST',
  headers: {
    Authorization: 'Bearer sk_live_...',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    customerId: 'cus_abc123',
    beneficiaryName: 'Acme Corp',
    paymentRails: ['swift'],
    swiftBic: 'CHASUS33',
    accountNumber: '1234567890',
    beneficiaryAddress: {
      addressLine1: '123 Main St',
      city: 'New York',
      state: 'NY',
      postalCode: '10001',
      country: 'US',
    },
  }),
});

export INFINITE_API_KEY=sk_live_...
infinite api POST /v1/external-bank-accounts --body '{
  "customerId": "cus_abc123",
  "beneficiaryName": "Acme Corp",
  "paymentRails": ["swift"],
  "swiftBic": "CHASUS33",
  "accountNumber": "1234567890",
  "beneficiaryAddress": {
    "addressLine1": "123 Main St",
    "city": "New York",
    "state": "NY",
    "postalCode": "10001",
    "country": "US"
  }
}'

Add a SWIFT bank account for cus_abc123: beneficiary Acme Corp, BIC CHASUS33, account number 1234567890, address 123 Main St, New York, NY 10001, US.

# Infinite MCP is read-only today — run the CLI tab to execute.

curl -X POST "https://api.infinite.dev/v1/external-bank-accounts" \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "customerId": "cus_abc123",
    "beneficiaryName": "Acme Corp",
    "paymentRails": ["swift"],
    "swiftBic": "CHASUS33",
    "accountNumber": "1234567890",
    "beneficiaryAddress": {
      "addressLine1": "123 Main St",
      "city": "New York",
      "state": "NY",
      "postalCode": "10001",
      "country": "US"
    }
  }'

Required fields vary by payment rail. See the API reference for full details.

External Wallets

Third-party blockchain wallets owned by your customers. Infinite does not hold the keys. Use them as payout destinations, fixed-route sweep targets, or a customer-controlled guard address.

import requests

response = requests.post(
    'https://api.infinite.dev/v1/external-wallets',
    headers={
        'Authorization': 'Bearer sk_live_...',
        'Content-Type': 'application/json',
    },
    json={
        'customerId': 'cus_abc123',
        'walletAddress': '0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb7',
        'chains': ['ETHEREUM', 'BASE'],
    },
)

const response = await fetch('https://api.infinite.dev/v1/external-wallets', {
  method: 'POST',
  headers: {
    Authorization: 'Bearer sk_live_...',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    customerId: 'cus_abc123',
    walletAddress: '0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb7',
    chains: ['ETHEREUM', 'BASE'],
  }),
});

export INFINITE_API_KEY=sk_live_...
infinite api POST /v1/external-wallets --body '{
  "customerId": "cus_abc123",
  "walletAddress": "0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb7",
  "chains": ["ETHEREUM", "BASE"]
}'

Add external wallet 0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb7 for cus_abc123 on Ethereum and Base.

# Infinite MCP is read-only today — run the CLI tab to execute.

curl -X POST "https://api.infinite.dev/v1/external-wallets" \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "customerId": "cus_abc123",
    "walletAddress": "0x742d35Cc6634C0532925a3b844Bc9e7595f0bEb7",
    "chains": ["ETHEREUM", "BASE"]
  }'

The response id is ewa_…. Status starts IN_REVIEW and becomes ACTIVE after screening. See Create an external wallet.

Virtual Bank Accounts

Fiat bank accounts provisioned within Infinite’s banking partners. Used for receiving fiat deposits via ACH, wire, SEPA, SWIFT, and similar rails. These are typically created as part of a fixed route (POST /v1/fixed-routes/virtual-bank-accounts) rather than standalone. Each route gets its own account number, so the deposit identifies itself — no memo required. A USD balance account is also a vba_ that holds funds instead of sweeping. A separate fixed route can use that balance account as its sweep target, so deposits to a dedicated account number credit the balance with no conversion.

Virtual wallets (`vwa_`) vs crypto deposit wallets

The vwa_ prefix is a funding-method virtual wallet used in some products (for example card funding). It is not what POST /v1/fixed-routes/virtual-wallets returns. That endpoint creates an INFINITE_WALLET (inw_) with walletType: VIRTUAL — a dedicated crypto mailbox. Sandbox fund-in on vwa_ will not credit that mailbox. To test the route, simulate-deposit with the mailbox (source) account id; the sweep credits the route destination.

ID Prefixes

Each account type has a distinct ID prefix:

Type	Prefix	Example
Infinite Wallet	`inw_`	`inw_abc123`
External Bank Account	`eba_`	`eba_abc123`
External Wallet	`ewa_`	`ewa_abc123`
Virtual Bank Account	`vba_`	`vba_abc123`
Virtual Wallet	`vwa_`	`vwa_abc123`
Provider / stablecoin balance	`pba_`	`pba_abc123`

Account Status

Status	Description
`IN_REVIEW`	Account created, awaiting approval
`ACTIVE`	Account operational
`CLOSED`	Account permanently closed

Account status is read-only. Once an external bank or proxy account is ACTIVE, you can permanently close it with POST /v1/external-bank-accounts/{id}/close. Accounts still IN_REVIEW cannot be closed. Closed accounts cannot be used as transfer or FX destinations, and fixed routes that sweep to them are disabled.

Retrieving Accounts

List accounts for a customer

import requests

response = requests.get(
    'https://api.infinite.dev/v1/accounts',
    headers={
        'Authorization': 'Bearer sk_live_...',
        'Content-Type': 'application/json',
    },
    params={'customerId': 'cus_abc123'},
)

const response = await fetch(
  'https://api.infinite.dev/v1/accounts?customerId=cus_abc123',
  {
    headers: {
      Authorization: 'Bearer sk_live_...',
      'Content-Type': 'application/json',
    },
  },
);

export INFINITE_API_KEY=sk_live_...
infinite accounts list --limit 10
# Or filter via escape hatch:
infinite api GET /v1/accounts --query customerId=cus_abc123

List all accounts for customer cus_abc123.

curl -X GET "https://api.infinite.dev/v1/accounts?customerId=cus_abc123" \
  -H "Authorization: Bearer sk_live_..."

Get an account by ID

import requests

response = requests.get(
    'https://api.infinite.dev/v1/accounts/inw_abc123',
    headers={
        'Authorization': 'Bearer sk_live_...',
        'Content-Type': 'application/json',
    },
)

const response = await fetch(
  'https://api.infinite.dev/v1/accounts/inw_abc123',
  {
    headers: {
      Authorization: 'Bearer sk_live_...',
      'Content-Type': 'application/json',
    },
  },
);

export INFINITE_API_KEY=sk_live_...
infinite accounts get inw_abc123

Show me account inw_abc123.

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

Next Steps

Once accounts are set up, you can create transfers to move funds between them.

Transfers

Move funds between accounts across fiat and crypto rails

API Reference

Full API reference for account endpoints

Get started

Core Concepts

Guides

Overview

Infinite Wallets (`INFINITE_WALLET`, `inw_`)

External Bank Accounts

External Wallets

Virtual Bank Accounts

Virtual wallets (`vwa_`) vs crypto deposit wallets

ID Prefixes

Account Status

Retrieving Accounts

List accounts for a customer

Get an account by ID

Next Steps

Transfers

API Reference

​Overview

​Infinite Wallets (INFINITE_WALLET, inw_)

​External Bank Accounts

​External Wallets

​Virtual Bank Accounts

​Virtual wallets (vwa_) vs crypto deposit wallets

​ID Prefixes

​Account Status

​Retrieving Accounts

​List accounts for a customer

​Get an account by ID

​Next Steps

Transfers

API Reference

Overview

Infinite Wallets (`INFINITE_WALLET`, `inw_`)

External Bank Accounts

External Wallets

Virtual Bank Accounts

Virtual wallets (`vwa_`) vs crypto deposit wallets

ID Prefixes

Account Status

Retrieving Accounts

List accounts for a customer

Get an account by ID

Next Steps