Short, late or wrong-network payments: what happens next

Write to support@vanepeptides.com before doing anything else, and before sending a second transfer. Include:

• the order number;
• the transaction hash (TXID) of every transfer made for it;
• the asset and the network you sent on;
• the amount sent and the address you sent from.

With those, a transfer can be looked up on-chain and compared with the order. Without the hash there is nothing to match.

Finding the hash

Wallets show it in the transaction history, under the details of the transfer. Exchange accounts usually show it on the withdrawal record, sometimes labelled TXID or transaction ID. If a withdrawal record has no hash yet, the transfer may not have been broadcast; wait for one before writing.

A payment is short when less than the amount due arrives. The usual causes: an exchange that takes its withdrawal fee out of the amount, a figure typed from memory, or a BTC amount converted at a different moment than expected. Any public block explorer for the network will show, from the hash, the exact amount that reached the address.

A short order is not packed, and its 72-hour window keeps running. Email support with the hash and wait for a reply on how the difference is to be handled; a second, unannounced transfer is harder to match to the order.

The deadline printed on the order page falls 72 hours after the order was placed. Once that deadline passes without payment, the order is cancelled.

A transfer that lands after cancellation does not attach itself to the order. Email support with the hash; support will look at it and reply. Whether a lapsed order can be picked up again, or what else is possible, cannot be said in advance. A fresh order is priced at the listing price on the day it is placed.

Running out of time

If the deadline is near and the transfer is not ready, write before it passes. Letting an unpaid order lapse is allowed; a new one can be placed later from the shop.

Every address on the order page is tied to one network and to the assets named on its row. A transfer outside that pairing is not a payment to the order: USDT sent on a network other than the one printed on the row, USDC sent to a row that lists only USDT, or any token sent to the Bitcoin address.

Whether such a transfer can be traced or returned depends on the networks and addresses involved, and often it cannot. Email support with the hash, the asset and the network you used; support will check and tell you what they find. No recovery is promised here, because none can be promised before that check.

Wrong address

A transfer to an address that is not on your order page never reached the store, and support can neither see it nor reverse it. Check the address against the order page before every send.

1. CHK 01Read the network label on the order page row before copying its address.
2. CHK 02Paste the address, never type it, and compare the first and last six characters.
3. CHK 03Choose the same network in the wallet as the row states.
4. CHK 04Check the amount that will arrive, after any exchange withdrawal fee.
5. CHK 05Send well before the deadline printed on the order page.
6. CHK 06Keep the transaction hash and email it with the order number.

Step by step: USDT on Tron. Asset differences: USDT, USDC or BTC. Standing rules: payment and contact.