Environments

Before You Start

Read the following guides before proceeding:

Guide	Why
Getting Started	Integration overview and prerequisites

API Endpoints

Environment	Base URL	Purpose
Sandbox	`https://api-business.wirexapp.tech`	Testing and integration
Production	`https://api-business.wirexapp.com`	Live environment

The Corporate API is served under /api/v1/, /api/v2/ and /api/v3/ on these hosts. Credentials are
environment-specific and are not interchangeable.

The Corporate API has its own hosts. api-baas.wirexapp.tech and api-baas.wirexapp.com serve
the retail API, documented under For Retail Developers; corporate endpoints are not
routed there.

PCI Secure Environment

Tokenizing a destination card for Card Transfer requires a call to
Wirex's PCI-compliant environment. It is a separate host with separate credentials — the corporation
token is not accepted there.

Environment	Base URL	Purpose
Sandbox	`https://wx-acquiring-card-manager-uat.wirexapp.com`	Card tokenization testing
Production	`https://wx-acquiring-card-manager.wirexapp.com`	Live card tokenization

Note: These endpoints handle card numbers and are subject to additional security requirements.
Request access from Wirex separately from your API credentials.

Supported Chains

Production

Chain	Chain ID
Base	`8453`
Stellar	`9223372036854775806`

Sandbox

Chain	Chain ID
Base Sepolia	`84532`
Stellar Testnet	`9223372036854775806`

The chain is fixed into the corporation token at login, from the X-Chain-Id header sent on
POST /api/v1/corporations/login. Requests made with that token are evaluated against the chain recorded
in its chain_id claim; sending a different X-Chain-Id on a later request does not change it. To switch
chains, log in again with the chain you want.

If X-Chain-Id is omitted at login, the environment's default chain is used.

Runtime Configuration

GET /api/v1/config

Returns the live chain and client configuration for the environment. This endpoint is anonymous — no
Authorization header is required — and is the authoritative source for RPC, bundler, paymaster and
ContractRegistry addresses in each environment.

Response

{
  "auth": { },
  "api": {
    "apiUrl": "https://api-business.wirexapp.com",
    "socketIo": "https://socket.wirexpaychain.com"
  },
  "support": { },
  "analytics": { },
  "defaultCompanyId": "550e8400-e29b-41d4-a716-446655440000",
  "defaultChain": {
    "id": 8453,
    "name": "Base",
    "contractRegistry": "0xAFa697ebC7919998AF5CdE325Fbe990dC926aae4",
    "blockExplorerUrl": "https://basescan.org",
    "bridgeUrl": "https://bridge.base.org",
    "rpcUrl": "https://mainnet.base.org",
    "rpcWsUrl": "wss://mainnet.base.org",
    "bundlerUrl": "https://rpc.zerodev.app/api/v2/bundler/...",
    "paymasterUrl": "https://rpc.zerodev.app/api/v2/paymaster/..."
  },
  "chains": {
    "8453": {
      "id": 8453,
      "name": "Base",
      "contractRegistry": "0xAFa697ebC7919998AF5CdE325Fbe990dC926aae4",
      "blockExplorerUrl": "https://basescan.org",
      "bridgeUrl": "https://bridge.base.org",
      "rpcUrl": "https://mainnet.base.org",
      "rpcWsUrl": "wss://mainnet.base.org",
      "bundlerUrl": "https://rpc.zerodev.app/api/v2/bundler/...",
      "paymasterUrl": "https://rpc.zerodev.app/api/v2/paymaster/..."
    }
  }
}

Field	Description
`api.apiUrl`	Base URL of the API for this environment
`api.socketIo`	Socket.IO endpoint for the environment
`defaultCompanyId`	Default corporate company id for this deployment
`defaultChain`	The chain used when a request carries no `X-Chain-Id`. Omitted when no configured chain matches the deployment's default chain id
`chains`	Map of supported chains, keyed by EIP-155 chain id
`chains.<id>.contractRegistry`	ContractRegistry address — resolve every other contract address from it
`chains.<id>.bundlerUrl`	Bundler endpoint for UserOperation submission
`chains.<id>.paymasterUrl`	Paymaster endpoint for gas sponsorship

Token Catalogue

GET /api/v1/config/tokens

Returns the tokens available to your company. Requires a partner token or a corporation token. Use it to
resolve the token_address values accepted by the fee, transfer and card endpoints.

Response

{
  "data": [
    {
      "address": "0x0774164DC20524Bb239b39D1DC42573C3E4C6976",
      "base_token_address": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "symbol": "WUSD",
      "default_symbol": "WUSD",
      "equivalent_symbols": ["USDC", "USDT"],
      "decimals": 18,
      "is_active": true,
      "supported_chain_ids": [8453],
      "token_type": "Synthetic"
    }
  ]
}

Field	Description
`address`	Token contract address — the value to pass as `token_address`
`base_token_address`	Underlying ERC-20 a unified token is backed by. Absent on regular tokens
`symbol`	Token symbol
`default_symbol`	Symbol used to group equivalent tokens
`equivalent_symbols`	Symbols this token can settle against
`decimals`	Token decimals — the exponent behind every `precise_amount`
`is_active`	`false` means the token is not currently usable
`supported_chain_ids`	Chains on which the token exists
`token_type`	Token classification — see Token Types below

Token Types

token_type tells you which of the two token families an entry belongs to.

`token_type`	What it is	Examples
`Synthetic`	A unified token — the platform's own balance-bearing asset, minted when a supported stablecoin is deposited and burned when value leaves	`WUSD`, `WEUR`
`Regular`	A plain ERC-20 stablecoin, held directly at its own contract	`USDC`, `USDT`, `EURC`

A unified token always carries base_token_address, pointing at the ERC-20 it is backed by; a
regular token does not. Balances are held in unified tokens, while on-chain movements in and out of
the platform happen in regular tokens.

Other token_type values exist for products that are not part of this integration surface. Treat any
value outside the two above as one you do not handle.

Both unified and regular tokens can be linked to a card at issuance.

Sandbox Credentials

Corporate sandbox credentials are issued per partner. There are no shared corporate test credentials —
the retail sandbox credentials published under For Retail Developers are registered
as a retail company and are rejected by the Corporate API. Request corporate sandbox credentials from your
Wirex account manager.