Understand the asset
SOL payments require an invoice that explicitly supports the Solana network and native SOL. Token symbols and network names should never be treated as interchangeable.
Before you send
Use the named network and confirm that the wallet is sending the correct asset. Exchange withdrawal delays and minimums may differ from direct wallet transfers.
What privacy means here
Low transaction fees do not imply anonymity. Public account activity can still connect payments and services.
After payment
Payment should be confirmed only after the invoice has been reconciled under its confirmation policy. If a payment is delayed, provide the transaction identifier and invoice number through a verified support channel. Never provide a wallet recovery phrase or private key.
Native SOL on Solana mainnet
The configured Solana route receives native SOL on Solana mainnet. It does not represent every token whose name mentions Solana or SOL. Read the quote amount at full precision and leave the sending wallet enough for its fee. A fast block does not replace the order backend’s confirmation and matching rules.
Keep the payment record useful
Retain the order reference, quoted asset and network, expiry and transaction identifier. Contact support through a verified channel if reconciliation is needed. A support enquiry should never include a wallet seed, private key or signing credential.
A little more clarity.
Can I send a Solana stablecoin instead of SOL?
No. The configured Solana route is native SOL. USDC is configured separately on Ethereum, not as a Solana token.