Skip to content

Solana and Tron

Solana and Tron networks are listed in GET /api/v1/networks next to EVM networks, with family set to solana or tron. Read their tokens, decimals and minimum_payment from the API; do not keep your own list. Addresses on these networks use their own base58 format in requests, responses and webhooks.

EVM Solana Tron
Payment address A contract address. The recipient is fixed on chain when the address is created. A key per payment, held by the Invoise signer. A key per payment, held by the Invoise signer.
Custody Funds can go only to the recipient fixed on chain, minus the fee. Invoise holds a payment only until it forwards it to your recipient. Invoise holds a payment until it forwards it. There is no payment contract.
Recipient The shop’s recipient PUT /shops/{shop_id}/solana-recipient PUT /shops/{shop_id}/tron-recipient
Delegate Optional None None
Sandbox shop Yes No: 400 solana_sandbox_unavailable Yes

By default a merchant can keep 100 Solana deposit addresses active at once; Invoise staff can set a different limit for a merchant. Disable idle ones to free a place: see Limits.

A shop needs a Solana or Tron recipient before it can issue on that network. Without one, creating an invoice or deposit returns 400 solana_setup_required or 400 tron_setup_required.

Terminal window
curl -X PUT 'https://platform.invoise.me/api/v1/shops/{shop_id}/solana-recipient' \
-H 'Authorization: Bearer <session-token>' \
-H 'Idempotency-Key: <saved-unique-key>' \
-H 'Content-Type: application/json' \
-d '{"address":"<your-solana-wallet>"}'

Use /tron-recipient for Tron. Setting it needs an owner session; a shop API key can only read it. GET on the same path returns {"address":"..."}, with an empty address until one is set.

The recipient is set once. Sending the same address again succeeds; another address returns 400 shop_addresses_immutable. Check the address before you save it.

Network Rules
Solana Use an ordinary wallet, not a program-derived address and not an Invoise address: invalid_solana_address. The wallet must already hold an account for the token; otherwise creating an invoice or deposit returns solana_recipient_token_account_required. Receive that token there once first.
Tron A malformed address, including one with a wrong checksum, returns invalid_tron_address; an Invoise address returns invalid_tron_recipient. If Invoise has switched Tron off for the merchant, setting it returns merchant_network_disabled.

The Invoise wallet lives on EVM networks. A shop whose Solana or Tron payouts go to the wallet still gets a Solana or Tron payment address, and Invoise bridges each payment into the wallet on Arbitrum. GET /merchants/{merchant_id}/networks shows wallet_bridge: true on a Solana or Tron network that can bridge.

When bridging is not possible, issuing on that network returns 400 solana_bridge_unavailable or 400 tron_bridge_unavailable, and choosing the wallet for Tron is refused with tron_bridge_unavailable. A shop that pays Solana or Tron to its own address is not affected.

Choose per network family with PATCH /shops/{shop_id}: solana_payout_target and tron_payout_target take address or wallet. See the API reference.