Aesesdocs

Environments

Aeses provides two completely isolated environments: test mode and live mode. They share nothing — separate keys, separate ledgers, separate webhook endpoints, and separate blockchain networks.

Supported chains

Aeses currently supports three chain families. Each family is selected via the chain parameter on the create endpoints and accepts the assets listed below.

| chain value | Family | Live networks | Test networks | Supported assets | | ------------- | ------- | ---------------- | --------------- | ---------------- | | ethereum | EVM | Ethereum mainnet | Sepolia | ETH, USDT | | bitcoin | Bitcoin | Bitcoin mainnet | Bitcoin testnet | BTC | | tron | Tron | Tron mainnet | Tron Nile | TRX, USDT |

To get the live, machine-readable list, call GET /v1/assets.

When to use each mode

| Environment | API base URL | Funds | | ----------- | ------------- | --------------------------- | | Test mode | https://api.aeses.io | Worthless testnet tokens | | Live mode | https://api.aeses.io | Real value, real settlement |

The base URL is identical — Aeses routes the request based on the key prefix (sk_test_… vs. sk_live_…). There is no api.test.aeses.io host.

What is isolated

  • Keys. A test key cannot read live data and vice versa. Requests across boundaries return 401 key_environment_mismatch.
  • Resources. Test and live each have their own deposits, withdrawals, balances, webhook deliveries, and webhook endpoints.
  • Webhooks. Test webhook endpoints receive test events only.
  • Rate limits. Test and live have independent rate-limit buckets.

Getting testnet funds

Use the faucets recommended in your network's documentation:

Testnet funds have no market value. They exist only to verify integrations.

Going live

When you are ready to accept real payments:

  1. Complete the business profile in the dashboard.
  2. Create a sk_live_ API key.
  3. Update the secret in your production environment.
  4. Configure your live webhook endpoint and test it from Developers → Webhooks → Send test event.
  5. Run a small end-to-end transaction to validate the full flow.