Credentials

Before You Start

Read the following guides before proceeding:

Guide	Why
Platform Overview	Platform overview

API Credentials

Wirex provides the following credentials per environment:

Credential	Format	Purpose
`client_id`	UUID	Identifies your company for API requests
`client_secret`	String	Secret key for S2S token exchange

On-Chain Identifier

Credential	Format	Purpose
`partner_id`	16-byte hex	On-chain identifier for Account Abstraction operations

The partner_id is used as the parentEntity parameter when registering user wallets in the Accounts smart contract.

Blockchain Infrastructure

When deploying Smart Wallets directly (not using Wirex SDK), you receive the following endpoints per environment:

Credential	Purpose
Bundler RPC URL	ZeroDev bundler for UserOperation submission
Paymaster RPC URL	ZeroDev paymaster for gas sponsorship
RPC Provider URL	Blockchain RPC endpoint

Rhino.fi Integration

For multi-chain deposits via global addresses:

Credential	Purpose
Rhino.fi API Key	Creating smart deposit addresses for cross-chain bridging

See Global Addresses for integration details.

Smart Contract Addresses

Wirex provides a ContractRegistry address per chain and environment. All other contract addresses are resolved dynamically from the registry using contractByName(name).

ContractRegistry Addresses

Environment	Chain	Chain ID	ContractRegistry Address
Sandbox	Base Sepolia	`84532`	`0xC801a0f38E20500B5840c4927553b3409890bc3c`
Sandbox	Stellar Testnet	`9223372036854775806`	`CBI44PUQEKP2IAD77ZPCTN2QX2IOWOSY5VYHI3SPBN4CAZY6BHR7KIVE`
Production	Base	`8453`	`0xAFa697ebC7919998AF5CdE325Fbe990dC926aae4`
Production	Stellar	`9223372036854775806`	`CC34TW4W4NUAS54WYPSAUK7RR4LMF4RSAJV555J6ZMTPGEVPAB3A563E`

Contracts Resolved from Registry

Contract Name	Purpose
`Accounts`	User registration (`createUserAccountWithWallet`)
`FundsManagement`	Executor module for oracle transactions
`ExecutionDelayPolicy`	Time-lock policy for wallets
`TokensRegistry`	Supported token list

See ABI Reference for contract ABIs and interface definitions.

Credential Storage

API Credentials

Store client_secret in a secrets manager (AWS Secrets Manager, HashiCorp Vault, GCP Secret Manager)
Never commit credentials to source control
Never expose credentials in client-side code or logs
Rotate credentials immediately if compromised

Partner ID

The partner_id can be stored in application configuration
It is not secret but should be validated against your expected value

Token Addresses

Production (Base - Chain ID 8453)

Token	Address	Decimals
USDC	`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`	6
USDT	`0xfde4C96c8593536E31F229EA8f37b2ADa2699bb2`	6
EURC	`0x60a3E35Cc302bFA44Cb288Bc5a4F316Fdb1adb42`	6
WUSD	`0xb4bB2032A73A53C0Aa7Dc9ee2d9658a978fA7bC2`	18
WEUR	`0x379e120C1921bFD8f5E0A1a3C699e7e800b66606`	18

Sandbox (Base Sepolia - Chain ID 84532)

Token	Address	Decimals
USDC	`0x7Af7cDbd557eD302F7538Db1e3d094C8BBcA665c`	6
USDT	`0x2C6c7c00ACa9B9D8446d107367485079b0471706`	18
EURC	`0xF70461ffb413981852683657A310892227e3989e`	6
WUSD	`0x0774164DC20524Bb239b39D1DC42573C3E4C6976`	18
WEUR	`0x5c55F314624718019A326F16a62A05D6C6d8C8A2`	18