Skip to main content
Transit runs on two testnets, so you can test your integration end to end before you use real funds. Testnet uses the same API, endpoints, and order flow as mainnet. Only the chains, the tokens, and the route filter are different.
Testnet tokens have no value. Testnet fees and minimum order sizes are different from mainnet, and testnet orders settle more slowly. Do not use testnet results to estimate mainnet costs or timing.

Chains

Tokens

To get test tokens, contact your Paxos Labs representative. You also need testnet ETH on the source chain for gas and the messaging fee.

Routes

Step 1: List Testnet Routes

Testnet routes are listed only when you request them. Add network=TESTNET to the filter parameter of GET /v1/transit/routes:
A filter without a network key returns mainnet routes only, even if it names a testnet chain ID. To list mainnet and testnet routes in one response, use network=MAINNET OR network=TESTNET. Each route’s minOrderSize is the smallest order it accepts, in offer-asset base units.

Step 2: Submit an Order

Follow Order Submission with testnet chain IDs and token addresses. The authorization check, the quote, and the transaction you broadcast work the same as on mainnet. Send the transaction on the source testnet.

Step 3: Track the Order

Use the Order Tracking endpoints with the order ID from the OrderSubmitted event. Testnet orders use the same statuses as mainnet orders. Testnet orders are processed about every 10 minutes, so they settle more slowly than mainnet orders. After an order reaches the destination chain, expect it to stay PROCESSING for several minutes before it is PROCESSED.