Test Networks and Mainnet
Manatee groups credentials by environment. One Test API key covers BTC Testnet4, BCH Testnet4, and XMR Stagenet; one Mainnet key covers the mainnet assets enabled for that deployment. Asset-specific API responses still report their actual network, so XMR returns stagenet while BTC and BCH return testnet.
Network differences
| Asset and network | API value | Coin value | Typical use |
|---|---|---|---|
| BTC Testnet4 | testnet | No real market value | Integration tests, webhook tests, checkout QA |
| BCH Testnet4 | testnet | No real market value | BCH wallet and checkout tests |
| XMR Stagenet | stagenet | No real market value | Monero wallet, subaddress, and checkout tests |
| Mainnet | mainnet | Real BTC, BCH, or XMR | Production payments |
Test and mainnet addresses are not interchangeable. Always verify the asset and network shown by both Manatee and the sending wallet before transferring funds.
Testing checklist
- Create a shared Test API key.
- Use a wallet configured for BTC/BCH Testnet4 or XMR Stagenet.
- Send valueless test coins from a faucet or separate test wallet.
- Verify
payment.detectedandpayment.confirmedwebhooks. - Confirm your webhook signature verification uses the raw request body.
- Store payment IDs and event IDs idempotently.
Going to production
Before switching to mainnet, change the API key, asset-specific wallet configuration, confirmation threshold, and webhook endpoint. Keep test and mainnet data separate in your own system so test orders cannot be confused with real payments. A working XMR Stagenet wallet does not configure Mainnet; create and verify an independent Mainnet view-only wallet.