> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rns.id/llms.txt
> Use this file to discover all available pages before exploring further.

# Pay with Crypto on RNS.ID

> Pay with crypto on RNS.ID, review supported networks, tokens, and wallets, and troubleshoot an unmatched blockchain transaction.

A crypto payment must be completed through the payment flow opened for the current RNS.ID order. That flow supplies order-specific payment data that RNS.ID uses to match the blockchain transaction to the order.

This page covers crypto payments attached to an order in the RNS.ID dashboard. The manually coordinated [Hilton Grand Vacations offer](/programs/hilton-grand-vacations-offer) uses separate, request-specific instructions provided through the official Live Chat.

<Warning>
  Do not manually transfer cryptocurrency to a contract address or reuse payment details outside the active RNS.ID checkout. Start and complete the transaction through the crypto payment flow opened for the current order. A successful on-chain transfer by itself does not mean the RNS.ID order has been paid.
</Warning>

## Supported networks, tokens, and wallets

The current RNS.ID crypto checkout supports the combinations below. The options displayed in the active payment flow for a particular order control that payment and can change over time. Use only a network, token, and wallet offered there.

| Network | Supported payment tokens |
| - | - |
| Ethereum | ETH, USDT, USDC |
| BNB Smart Chain (`bsc` in checkout) | BNB, USDT, USDC |
| Polygon | POL, USDT, USDC |
| Base | ETH, USDT, USDC |
| Optimism | ETH, USDT, USDC |
| Avalanche | AVAX, USDT, USDC |
| Arbitrum | ETH, USDT, USDC |
| Solana | SOL, USDT, USDC |
| TON (The Open Network) | TON, USDT |
| Tron | USDT |

Do not assume that the same token symbol is supported on another network or that an asset visible in your wallet is accepted. Confirm the network and token together in the active payment flow.

### EVM-compatible chains

Supported chains:

* Ethereum
* BNB Smart Chain
* Polygon
* Base
* Arbitrum
* Optimism
* Avalanche

Supported wallet options:

* MetaMask
* WalletConnect
* OKX Wallet
* Coinbase Wallet
* Phantom
* Rainbow
* Uniswap Wallet
* Rabby Wallet
* Magic Eden
* Backpack
* Trust Wallet
* OneKey
* Bitget Wallet
* Keplr

### Solana

Supported wallet options:

* Phantom
* Backpack
* OKX Wallet
* Solflare
* Glow
* Magic Eden
* OneKey
* Bitget Wallet
* Wallet Mobile Adapter

### Tron

Supported wallet options:

* TronLink
* OKX Wallet
* Gate.io
* Ledger

### TON (The Open Network)

Supported wallet options:

* Tonkeeper
* OKX Wallet
* MyTonWallet
* Bitget Wallet
* HOT Wallet
* Tonhub Wallet

## Complete a crypto payment

1. Start or resume the intended order in RNS.ID.
2. Select **Pay with Crypto** when it is offered.
3. Continue through the crypto payment window opened for that order.
4. Select only a token and network offered inside that active flow.
5. Review the network, token, amount, destination, and wallet transaction before confirming.
6. Keep the payment flow open while it submits and validates the transaction.
7. Open **Orders** and confirm that the RNS.ID order reaches **Paid**.

Do not reuse a destination, payment request, QR code, or transaction details from another order or an earlier checkout. Do not construct a separate transfer to a contract address in your wallet.

## Blockchain status and order status are different

A wallet or block explorer can show a transaction as successful before the RNS.ID order is paid. The blockchain result confirms that a transaction was included on-chain; it does not by itself confirm that the transaction contains the payment-provider data required for the current RNS.ID order.

Check **Orders** for the current RNS.ID payment record. If it remains **Unpaid**, **Processing**, or **Payment Failed**, do not assume the order is paid. If the order and the provider or blockchain record conflict, preserve both and [contact support](/support/contact-us) before submitting another payment. Even **Paid** does not by itself mean approval, ID issuance, or service activation.

## If you sent crypto manually

1. Preserve the public transaction hash and do not delete the wallet record.
2. Open **Orders** and record the affected order number and current status.
3. Do not submit another payment until you have checked whether a separate attempt is already processing.
4. [Contact RNS.ID Support](/support/contact-us) with:
   * account email and order number;
   * blockchain network and token;
   * amount and timestamp;
   * sender address;
   * destination or contract address; and
   * public transaction hash.

RNS.ID does not guarantee that a manual transfer can be matched to an order or recovered.

## Protect wallet and payment information

Support may need public blockchain information, but it does not need a seed phrase, private key, password, email verification code, authenticator code, or complete card details. Reject any person who asks for those secrets or asks you to send another transfer to “verify” the first one.

For other payment options, see [Payment methods](/account/payment-methods). For status definitions and retry guidance, see [Orders and payment status](/account/orders-and-payment-status).