Environments

Before You Start

Read the following guides before proceeding:

Guide	Why
Platform Overview	Overview of Wirex BaaS

API Endpoints

BaaS API

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

Use Sandbox for development and testing. Credentials are environment-specific.

PCI Secure Environment

Card tokenization for push to card transfers requires calls to Wirex's PCI-compliant secure environment.

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: PCI environment endpoints handle sensitive card data and are subject to additional security requirements.

Sandbox Helper API

The Sandbox Helper API provides methods for simulating external events that cannot be triggered through the standard API (bank deposits, transfer completions, card transactions).

Environment	Base URL	Purpose
Sandbox	`https://ramc.wirexapp.tech`	Test event simulation

Important: This API is available in Sandbox only. It does not exist in Production. See Sandbox Testing for usage.

Supported Chains

Production

Chain	Chain ID
Base	`8453`
Stellar	`9223372036854775806`
Tempo	`4217`

Sandbox

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

Token Catalogue

GET /api/v1/config/tokens

Returns the tokens available to your company. Use it to resolve the token_address values the fee,
transfer, card and withdrawal endpoints accept, and to read each token's decimals — the exponent
behind every precise_amount. See Amounts.

Response:

{
  "data": [
    {
      "address": "0x0774164DC20524Bb239b39D1DC42573C3E4C6976",
      "symbol": "WUSD",
      "default_symbol": "WUSD",
      "base_token_address": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "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`
`symbol`	Token symbol
`default_symbol`	Symbol used to group equivalent tokens
`base_token_address`	Underlying ERC-20 a unified token is backed by. Absent on regular 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

Read token addresses from this endpoint rather than hardcoding them. The tables in
Credentials are a convenience for reading the docs, not a contract — the
catalogue is per company and per chain.

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.

Client Application Configuration

GET /api/v1/config?company_name={name}

Returns the client-side bootstrap configuration for a company — auth provider settings, chain list and
support integration.

Parameter	In	Required	Description
`company_name`	query	Yes	Your company's name. An unrecognised name returns `400` with `Company with the specified name does not exist`

This endpoint exists for front-end initialisation. A server-side integration takes its chain and
contract configuration from Credentials instead.

Sandbox Test Credentials

The following shared credentials are available for quick testing:

Credential	Value
`client_id`	`3fCeoWq6FOtKJBZiyorXnxE41Dqp2zKB`
`client_secret`	`6FIY2GEQvdlgUEFHw4Dbii22_wCAqZ37lWV3TEMfTlkxrn8F5IbdgX9TiAvQUEsC`
`partner_id`	`0x00000000000000000000000000000044`

These are shared credentials for initial integration testing. Contact Wirex to obtain dedicated credentials for your company.