Use manual crypto top-up addresses

Check the destination before sending

The manual top-up panel displays real mainnet receiving addresses supplied by the operator. These fixed destinations are shared; they are not generated for your account or assigned to a particular order. Viewing, selecting or copying an address does not create a deposit record, reserve a server or change the account balance. The local test-credit control is separate and never represents cryptocurrency received.

An asset symbol alone does not identify a transfer route. Select both the cryptocurrency and its blockchain, then read the destination label before copying. USDT on TRON and USDT on Ethereum are different routes. An Ethereum address does not authorize sending on every network that uses the same address format. Use only the exact asset and mainnet shown, and verify the entire destination in your sending wallet.

Legacy settlement-adapter reference

The active manual destinations and their enabled networks are listed in Billing and the checkout funding step. Those choices come from the manual-address configuration, not from the legacy settlement catalogue below. USDC on TRON is a disabled legacy choice because Circle discontinued support; the selectable USDC destination uses Ethereum. Never substitute a different chain when your preferred route is unavailable.

The following table documents the existing provider adapter's catalogue and confirmation settings. It is retained as an integration reference, not as the current manual top-up policy or a promise of automatic processing. That adapter is not connected to the manual address directory. Its thresholds do not mean this preview is monitoring transfers or will credit them after a stated number of confirmations.

Select and copy a manual destination

This is a read-only address directory. It does not provide a crypto amount quote, per-order payment reference, transaction submission form or payment confirmation. Copying the address makes no account mutation. A transaction hash by itself is not proof that the person presenting it is entitled to a credit; your developer must implement a verified association before enabling settlement.

1. Open Billing or the checkout funding step and find Manual crypto top-up.
2. Select the cryptocurrency, then choose its explicitly listed network. Disabled routes cannot be used.
3. Read the asset, network, full address and any warning together. Changing the network changes the destination shown.
4. Use Copy address, or select the full address manually if clipboard access is unavailable. Verify the pasted destination before doing anything in your wallet.
5. Confirm with the operator how a transfer will be handled and associated with your account or order before sending real funds.
6. If a transfer is agreed and made, retain its asset, network, destination, amount, time and receipt privately. Never include a seed phrase or private key.

Understand the balance and ledger

Orders spend a USD-denominated account balance, not a wallet balance. The manual panel does not calculate a crypto-to-USD conversion or promise an amount of future credit. A sending wallet's market conversion is not an accepted invoice quote. Exchange-rate rules, accepted amounts and settlement handling still need to be defined by the operator and implemented by the developer.

Billing history and the ledger show records already stored for the account; they are not blockchain monitoring. Refreshing the page cannot discover a transfer or credit it. The local testing control adds non-withdrawable TEST_CREDIT only, and that entry must never be presented as proof of a real deposit. A real transfer remains outside this preview's reconciliation flow.

If an address or credit is missing

• Address loading failed: the panel clears the previous destination and disables copying. Check that you are signed in and retry. Do not replace a missing destination with one found in a search result.
• Network unavailable: choose only an enabled route whose asset and network your wallet supports. USDC on TRON remains disabled by default; do not treat its legacy label as an active payment option.
• Transfer already sent: keep the wallet receipt and verify its asset, network and destination. Contact the operator through an established real channel; support tickets in this local preview are private test records, not delivered messages.
• No balance increase: manual payment matching is not implemented. Do not send a second transfer or add local test credit to make an unverified transfer appear paid.
• Wrong asset or network: preserve the transfer details and seek operator assistance. This interface has no self-service recovery, and recovery is not guaranteed. Never share a wallet seed, private key, account password or recovery code.

Continue once the balance is available

Only an available ledger balance can pay an order or renewal. A copied address, wallet receipt or unconfirmed claim cannot bypass the server-side balance check. For local checkout testing, use the clearly separate test-credit control; it does not withdraw or represent real funds.

Your developer will connect authenticated payment intents or another verified account association to transaction validation and exactly-once ledger crediting. That later integration must distinguish the correct blockchain and token, prevent reuse of a transfer, and record the approved USD value. Until then, manual receiving destinations and the test account remain separate from live settlement.