Frequently Asked Questions
Everything you need to know about Flash USDT.
Getting started
The Starter Claim costs $2 and includes 200 Flash. Open the plan details and place an order to continue.
No. The previous free claim has been retired. The Starter Claim is the entry-level paid option.
OxaPay sends a signed webhook when an invoice changes state. For paid invoices, our server also checks the payment directly with OxaPay and verifies the order reference and amount before updating the claim.
Wallets and networks
The $2 Starter Claim accepts BEP20 or SOL only. Other plans support TRC20, ERC20, BEP20, and SOL. The available networks are shown on each plan’s order page.
Trust Wallet is recommended for compatible tokens. Your wallet must support the network you select. We do not claim support for any exchange or platform unless it has been independently verified.
Open your compatible wallet, select the receiving network, choose Add token or Manage crypto, and enter the contract or mint address, symbol, and decimals shown on the claim page.
Never. Checkout only asks for a public receiving wallet address. Never share private keys, seed phrases, or recovery codes with anyone.
Orders and payment
Select Buy now, choose a receiving network, enter your public receiving address, and select Place order. Every plan is in stock.
After you place the order you continue to accepted payment checkout. Complete payment there to activate the order.
Pending invoices remain visible in your dashboard while OxaPay confirms them. Expired, cancelled, or failed invoices do not release a claim. You can start a new checkout with a fresh invoice.
No. The old manual payment flow has been removed. Payment status comes only from OxaPay's signed webhook and server-side verification.
Tracking and support
Open the customer dashboard and go to Order history. Each record includes the plan, amount, network, wallet, payment status, and transaction reference. Pending orders include a Pay now button.
Payment confirmation and token distribution are separate states. A claim is not marked completed until a corresponding on-chain distribution transaction has been verified.
Contact support through the website support channel and include your unique claim order ID. Never send your private key or seed phrase.
Security and policies
The merchant key is kept as a server-side environment secret or encrypted admin configuration. It is never included in browser JavaScript, customer responses, or dashboard data.
Each checkout has a unique order and invoice. Signed webhook payloads are hashed and recorded, and paid state transitions are idempotent so repeated callbacks cannot create additional claims.
Review the Refund Policy page for the current terms and contact support with your order ID if you need assistance.