Field note: verify the network and contract before every flash USDT order

Questions, answered plainly.

A practical reference for choosing a plan, preparing a wallet, understanding payment states, and knowing when to contact support.

01

Getting started

Flash USDT is presented as a utility token for testing, demonstration, and related wallet workflows. It is not Tether-issued USDT and should not be treated as a redeemable stablecoin. Review the contract, validity period, and network details on each flashusdt plan before ordering.

The Starter Claim is a $2 entry-level order for 200 Flash USDT. It supports BEP20 or Solana receiving addresses and follows the same account, payment, and order-tracking workflow as the larger plans — a low-risk way to buy flash USDT for the first time.

Yes. An account keeps your selected plan, receiving network, public wallet address, payment state, and distribution state together. If you start checkout signed out, you will be asked to create an account and then return to your selection.

02

Wallets and networks

The Starter Claim supports BEP20 and Solana. Other plans support BEP20, ERC20, TRC20, and Solana. The checkout only displays networks allowed for the selected flash USDT plan.

Only where the plan explicitly says exchange wallets are supported. Several lower-tier plans are wallet-to-wallet only. Read the wallet support note on the plan page and confirm with the receiving platform before you buy flash USDT online.

Choose the receiving network in your wallet, open its add-token or manage-crypto screen, and enter the contract or mint address, symbol, and decimals shown for your plan. Always verify those details before adding a token.

No. The service only needs your public receiving address. Never share a seed phrase, private key, recovery code, or wallet password with support or anyone else.

03

Orders and payment

Choose a plan, select an allowed receiving network, enter your public address, and place the order. The server creates a unique order and an OxaPay invoice. Complete the invoice to move the order into payment processing.

OxaPay sends a signed webhook when the invoice changes state. For paid invoices, the server also checks the payment directly with OxaPay and verifies the order reference and amount before updating the order.

That state means payment has been confirmed but the flash USDT distribution step is not complete. It is intentionally separate from the final completed state so you can see what still needs to happen.

Expired, cancelled, or failed invoices do not release an allocation. You can return to checkout and create a fresh order with a new invoice.

04

Security and policies

No. Payment status comes from OxaPay's signed webhook and server-side verification, not from a customer-entered hash. This prevents an unverified transaction reference from marking an order as paid.

Each checkout uses a unique order and invoice. Webhook payloads are hashed and recorded, and paid state transitions are idempotent so repeated callbacks cannot create additional allocations.

The Refund Policy explains eligible delivery failures, exclusions, evidence to include, and review timelines. Contact support with your order reference if you believe your order qualifies.