Order help
Your purchased key will not activate: what to check
This guide starts after delivery: you already have a key, but the product will not accept it. Keep the original order open and note the exact error before trying anything else. A rejected key needs different checks from a payment that has not completed or a key you cannot find.
Avoid placing another order just to see whether a new code works. First establish which product is rejecting the key and whether you are following that product's redemption instructions. The order reference and error message give support a much better starting point than a second purchase.
Match the key to the product and variant
Compare the product name on your order with the screen where you entered the key. An executor license should not be treated as a script key, and one script's key should not be entered into another hub. If the names differ, return to the delivered instructions before repeating registration.
Check the selected variant, too. A Maru Mobile purchase is not evidence that you bought the PC version. A timed plan also should not be assumed to have the access terms of a lifetime key. Read the original option label so you can explain any mismatch accurately when contacting support.
Follow the intended redemption flow
Some listings say redemption happens through Discord. Others have their own account registration steps. Use the instructions supplied for the purchased product rather than applying a tutorial from a different provider. If the delivered steps name a bot or support server, verify that destination before sharing the key privately.
For Potassium, the supplied process is to register with the psm bot using your chosen username, password, and key, then request the download using that account. That is a product-specific process. It should not be assumed to describe GLua, Axon, or another script that also mentions Discord redemption.
If you copied the key, check for extra spaces or a missing character without posting the code publicly. Record whether the error occurs during registration, after login, or inside the product. For example, a successful registration followed by a download error gives support a different starting point from a key rejected at registration.
Send a focused support request
Include the order reference, product and variant, device, and exact error message. Explain which step failed and which checks you already made. A screenshot can help if it shows the error while hiding passwords, paid keys, and unnecessary payment details. Use a private ticket for sensitive order information.
If you are unsure whether a timed key has expired or was already redeemed, describe what the product shows instead of assuming either explanation. Support can investigate the existing order with those details. Keep the order reference until the issue is resolved, and read the refund policy before requesting a replacement or refund.