Find your payment network.

A new address identifies each invoice. Keep the complete wallet backup: a wallet app may need to scan further than its initial address gap. Bitcoin Lightning is a separate payment method, explained below.

Use Ethereum mainnet. Verified ERC-20 tokens such as USDC and USDT need ETH at each sending address when you move them later. Importing the recovery phrase into MetaMask may show only the first account.

Use Base, not Ethereum mainnet, even though both use ETH and similar addresses. Select the exact token contract; bridged and native versions are different assets.

Native SOL and verified classic SPL tokens are supported, including matching USDC/USDT mints. Token-2022 and its extensions are not accepted. Keep SOL for fees and token-account creation; use the address and payment request shown by checkout.

Use BNB Smart Chain and verified EVM token contracts, often called BEP-20. This is not the former Beacon Chain. Fees use BNB, not ETH.

Native TRX only. TRC-20 tokens, including USDT on TRON, are not invoice payment methods. A healthy basic node does not prove that indexed or solidified transaction history is available.

Invoices share a funded account and use a unique destination tag. The customer must include the exact tag; an X-address can encode it. XRP account reserves apply. Issued tokens are not accepted.

This integration is HyperEVM, not HyperCore or an exchange spot-deposit account. Use HYPE for fees and only verified contracts on HyperEVM.

Only transparent ZEC payments are scanned. Do not use shielded transfers or assume a shielded balance will appear. Each invoice has its own transparent receiving address.

Connect an external, project-specific view-only wallet RPC as well as a daemon. Each invoice gets a subaddress. A public daemon alone cannot see your payments. Keep the spending wallet elsewhere; Wholly Crypto cannot sweep XMR.

Native ADA only, with transaction history from a compatible source such as Koios. Cardano native tokens are not invoice assets. Account for minimum output requirements when moving funds.

A funded shared account uses a numeric MEMO_ID for each invoice. Copy the memo exactly, with the correct memo type. Account reserves apply. Stellar-issued assets, including USDC, are not accepted.

Use Bitcoin Cash, not Bitcoin. Native BCH payments get new invoice addresses. SLP and CashTokens are not accepted invoice assets. Confirm that the payer supports the displayed address format.

Use ordinary transparent LTC transfers to the new invoice address. MWEB private transfers are not covered by the invoice scanner. Allow for network fees when sending.

Native DOGE uses a new address for each invoice. Many small outputs can cost more to consolidate than one larger payment. Check fees and minimum send amounts before sweeping.

Use Avalanche C-Chain. X-Chain and P-Chain are different networks and are not this checkout method. C-Chain token transfers need AVAX for fees.

Use Polygon PoS and POL for fees. Ethereum and Polygon zkEVM are not interchangeable with this network. Check the exact token contract rather than just its ticker.

Use Arbitrum One. ETH on Ethereum mainnet or another Arbitrum network does not fund an Arbitrum One invoice. Keep ETH on this chain for token sweeps.

Use OP Mainnet and its verified contracts. The same token ticker on a different network is not the same payment method. Token sending needs ETH on OP Mainnet.

Invoices use a shared wallet and an exact invoice comment. Use a wallet that preserves the comment when paying. Native TON only: Jettons, including USDT on TON, are not accepted.

Native APT is tracked through compatible Aptos REST transaction APIs. Other Move tokens are not invoice methods. Check the exact network and account address when paying.

Native SUI requires a compatible history API, including supported GraphQL access. A working basic RPC health check is not enough. Other Sui coins/tokens are not invoice assets.

This means native ATOM on Cosmos Hub, not every Cosmos SDK chain or IBC token. The scanner needs indexed transaction events. Use the invoice address, not an exchange deposit address.

Use DOT on Polkadot Asset Hub, not the relay chain. A compatible Asset Hub transaction API or supported raw-block scanner is required. Other Asset Hub tokens are not invoice methods.

Native NEAR only. Detection checks successful receipts, not merely a submitted transaction. Preserve the account and derivation details in your wallet backup. NEP tokens are not accepted.

Native ALGO uses compatible Indexer or algod transaction history. Account minimum balances apply. Algorand Standard Assets, including USDC ASAs, are not accepted invoice assets.

Native HBAR invoices use an EVM alias that resolves to its Hedera account after funding. Receive history comes from a Mirror REST API; an EVM relay alone is not enough. HTS tokens are not accepted.

Native KAS requires a compatible REST transaction source and accepted-chain evidence. DAG progress is not the same as a confirmed payment. KRC-20 tokens are not invoice assets.

Native XTZ needs applied operations from TzKT or a compatible Octez source. Failed operations do not pay an invoice. FA1.2 and FA2 tokens are not accepted invoice assets.

Native DASH uses a new address for each invoice. Let the scanner apply your confirmation policy; do not assume an InstantSend label alone settles the Wholly Crypto invoice.