Testnet and mainnet
Brale has two environments, testnet and mainnet. There is no separate sandbox. The environment is set by the API application you create in Dashboard → Settings → API. Testnet credentials work only with testnets. Mainnet credentials move real value. Both environments use the same hosts:auth.brale.xyz for tokens and api.brale.xyz for API calls.
On testnet, use testnet transfer_type values such as base_sepolia or solana_devnet. No real fiat moves. To test inbound fiat, use Simulate an Automation deposit.
Store your client_id and client_secret in environment variables or a secrets manager. Never put them in code.
Testnet
Brale provides a testnet environment for non-production requests. Only testnets (Sepolia, Solana Devnet, Base Sepolia, etc.) are supported. Blockchain mainnets (Ethereum, Solana, etc.) are not supported in testnet. Real fiat movement is not supported in testnet. Brale does not contact a bank or move real funds. You can still test fiat-funded flows: testnet mints and burns skip the fiat leg, and you can simulate inbound ACH and wire deposits into testnet Automations. See the full set of supported blockchain networks.1. Create API Credentials scoped to Testnet
Create an application on the Settings page in the Dashboard.
Testnet as Network and enable all resources.

2. Mint Tokens on Testnets
When you submit a mint on testnet, we skip the fiat leg and immediately mint on-chain. This simulates an onramp transaction and acts as a faucet to mint tokens for other flows (payouts, etc.). POSThttps://api.brale.xyz/accounts/account_id/transfers
Request
3. Burn Tokens on Testnets
When you submit a redemption on testnet, we immediately burn on-chain and skip the fiat payout. This simulates an offramp transaction. No real wire, ACH, or FedNow payment is sent from testnet. POSThttps://api.brale.xyz/accounts/account_id/transfers
Request
4. Simulate a deposit into a testnet Automation
Testnet Automations return placeholder banking coordinates that cannot receive real deposits. To test the full Automation flow, simulate an inbound ACH, wire, or FedNow deposit. Brale runs the normal Automation, Transfer, and testnet mint flow and emits the normalpayment.completed webhook event.
Your testnet API credentials need the automations:write and network:testnet scopes.
Create an Automation with a testnet destination
"status": "active".
Simulate the deposit
202 Accepted with the resulting Transfer, including automation_id. transfer_type accepts ach, wire, or fednow. A fednow simulation produces a Transfer with source.transfer_type: "fednow_credit". See Receive FedNow deposits.
Fetch the Transfer
status is complete, destination.transaction_id holds the testnet mint transaction. See Simulate an Automation deposit for validation errors and idempotency behavior.
Testnet limitations
Testnet behaves like mainnet for most flows. The differences below are expected and do not indicate a problem with your integration.USDC transfers are capped at $0.01
Brale caps testnet transfers that involve USDC at $0.01 per transfer because of testnet faucet limits. The cap applies to any testnet transfer where USDC is the source or destinationvalue_type, including SBC↔USDC swaps.
- Brale rejects larger amounts with
400andredemption_limit_exceeded. - The cap applies per transfer, not to a running total. You can send repeated $0.01 transfers.
- Open testnet USDC transfers created before the cap took effect may show
status: "canceled". - Testnet transfers that do not involve USDC, such as SBC mints, burns, and payouts, are not affected.
Simulated deposits do not include payment_details
Simulated Automation deposits carry no sender or bank data. Brale does not populate source.payment_details on the resulting Transfer for ach, wire, or fednow simulations, whatever the destination token or chain. Fields such as sender_name, imad, and trace_number are absent.
Brale does not add these fields later. They do not appear in Get a transfer responses or in webhook events for the simulated Transfer. On mainnet, Brale fills them in from the real bank payment when that data is available.
Treat payment_details as optional and possibly null in your integration and reconciliation logic.