Activation code not delivered: self-check and support flow

A successful payment with no delivered content is one of the most stressful situations in the digital-goods world. This guide gives you a clean order of operations: rule out normal delays first, then decide whether something is actually wrong, and only then contact support.

1. Check the order page first, do not re-order

There is a normal 1 to 10 minute window between a successful payment and the order page showing the delivered content. The typical flow looks like this:

1. You complete payment.
2. The payment processor (for example Tariapay) sends a webhook to the store.
3. The store confirms the order status as paid.
4. The auto-delivery module writes the activation code or account details.
5. The order page refreshes and displays the delivered content.

While the order state is still updating, do not place the order again. Most "not received" reports are actually this pipeline still running.

2. Three things to try in the first ten minutes

• Refresh the order page: the page itself pulls the latest state, and sometimes one refresh is all it takes.
• Check your email: some products also send a notification. Check spam, too.
• Verify payment: open your bank or wallet app to confirm the charge cleared rather than sitting in an authorization-pending state.

3. Still nothing after 30 minutes

This is when it is reasonable to worry. Work through the checklist in this order:

• Is the order "paid" or "pending"? If it is still pending, the webhook likely did not arrive. Contact support with the order number.
• Paid but no delivered content? Auto-delivery may have failed or stock may be empty. The activation codes page shows stock status for comparable items.
• Cancelled or refunded? The platform has decided the order cannot be fulfilled and triggered a refund. Money usually returns to the original payment method within 1 to 5 business days.

4. When the platform issues a refund automatically

• Auto-delivery fulfillment failed beyond the retry budget.
• The promised delivery window on the product page has passed.
• The product was removed while the order was in flight.

In these cases the platform refunds on its own, without you needing to file a dispute. Only if the wait clearly exceeds the promised window and the platform has not acted is manual escalation appropriate.

5. Prepare before opening a ticket

• Order number: starts with ord_ and is part of the order link.
• Payment method and charge time: needed for reconciliation.
• Screenshots: one of the order page, one of the charge.

Tickets with complete information often resolve on the first reply. Back-and-forth clarification slows everything down.

6. Three things not to do

• Do not open a payment dispute immediately: once the bank steps in, automated handling is usually frozen and things get slower, not faster.
• Do not trust "add my personal account for priority handling." A legitimate platform resolves tickets inside its own system.
• Do not submit the same ticket multiple times: it does not speed anything up. It forces support to reload context each time.

If you want to understand how delivery actually works end to end, read the buying help page. If your concern is payment safety more broadly, the payment safety guide covers that. For your next purchase, if you want something with a cleaner delivery path, consider Claude API credit top-up: the credit appears in your console right after delivery, with none of the "code arrived but won't redeem" ambiguity.