Already paid? Check these three steps first.
Transfer purchases do not create website order references. Keep the original hash and check the payment and resources before paying again.
Check the original payment
Check that the transaction is solidified and executed successfully. No result does not prove failure. Keep the original hash and check again if uncertain.
Check payment transactionCheck address, currency and amount
Verify the payment address, a normal TRX transfer and the exact amount listed. Energy goes to the paying wallet; another receiver cannot be specified in a memo.
View current purchase rulesCheck the paying wallet resources
Check available Energy at the paying wallet. Usage, rental expiry and concurrent transactions affect availability. Successful payment does not confirm Energy delivery.
Check address resourcesQuestions after payment
Payment succeeded but Energy is missing?
Verify the paying wallet and tier amount, then check available Energy. If it is still missing, prepare the information below and contact the original purchase channel. Do not send another payment to chase delivery.
How long does delivery take?
Verify the actual on-chain delegation and wallet resources. No fixed delivery time is promised. An unavailable lookup does not prove failed delivery.
Wrong amount, currency or duplicate payment?
Keep each original transaction hash, currency and amount, and explain each payment separately. This page does not automatically create replacement orders or refunds; original payments and delivery records must be reviewed.
Paid from an exchange or another wallet?
Energy is delivered to the paying address. Keep the original transaction and contact the original channel. Do not assume it will reach another wallet or keep paying again.
Energy arrived but a USDT transfer failed?
Check the rental period, available Energy, Bandwidth, TRX balance and original receipt. Buying Energy cannot guarantee every contract call succeeds.
Do I need to provide a private key or seed phrase?
No. Provide only public addresses, hashes, amounts and a description. Do not include private keys, seed phrases, verification codes or API credentials.