Should I create another order when the first one looks stuck?
Check order history first. If a draft exists, keep its reference and investigate that draft. A second order can make it harder to distinguish a retry from a separate purchase.
Saving an order, confirming payment and receiving codes are different events. Know which stage you are at before you retry or ask for help.
Payment confirmation starts the fulfilment process after the required checks. Delivery is complete when the codes are available to the purchasing account. A payment screenshot, saved selection or supplier acknowledgement is not the same as delivered codes.
Last updated
Use the recorded order state, not a payment screenshot alone. Keep all stages tied to the same order reference.
Product, quantity and price are recorded for review. A selection alone does not collect funds or reserve codes.
The order must record the correct asset, network, amount and confirmation. Sending funds is not itself a delivery event.
The supplier request and receipt belong to the same order. A retry must not create a second charge or duplicate fulfilment.
Codes become visible only to the purchasing account after they have been saved to the order.
Check the order reference and the last visible state before taking another action. Do not send a second payment because a page is slow.
| Situation | Useful evidence | Next safe action |
|---|---|---|
| No order after saving | Time, selected product and visible error | Check order history before creating another draft. |
| Payment still confirming | Order reference and transaction reference | Follow that order’s instructions; do not reuse an address from an old order. |
| Only part of a batch received | Ordered and received quantities, without revealing codes | Ask for review of the missing lines, not a repeat of the whole batch. |
| Code cannot be redeemed | Exact error text and the product/account markets | Use the redemption guide; keep the full code out of screenshots. |
This catalogue covers digital codes, not printed cards or parcels. Keep account access controlled and decide who in your business may distribute a code. Sharing a screenshot of an entire batch can expose every code in it.
Blockchain confirmation, supplier response and customer-visible delivery are separate steps. An order may need review if the amount or network does not match, supply is delayed or a security check fails.
Automated delivery is not a fixed-time guarantee. Check the last recorded state and the order-specific terms before planning onward distribution. Prepare an order-support request ↗
Check order history first. If a draft exists, keep its reference and investigate that draft. A second order can make it harder to distinguish a retry from a separate purchase.
Hide gift-card codes, passwords, two-factor codes, wallet recovery phrases and unnecessary personal details. Keep the order reference, state and error text visible.
No. Payment confirmations, supplier availability and exception review can affect timing. Rely on a specific written delivery commitment only where one forms part of your order terms.
Review the product market, denomination and quantity in your business account. Keep the recipient balance separate from the seller amount.