· AvaGuru · tutorials · Updated · 9 min read

How to Sell License Keys on Telegram: Software and Game Codes

Set up Telegram Stars checkout for software or game keys, import key inventory, attach installers, and test delivery without confusing it with activation.

Set up Telegram Stars checkout for software or game keys, import key inventory, attach installers, and test delivery without confusing it with activation.

To sell license keys on Telegram with AvaGuru, create a digital product, choose License Key Only or License Key + Files, import unused keys into its License Pool, and test a Telegram Stars purchase. AvaGuru assigns keys from your inventory and makes the buyer’s assigned key available through the order after fulfillment.

Key delivery and software activation are separate jobs. AvaGuru delivers the key strings you supply. Your software’s licensing system or the game publisher’s platform must recognize them. For your own software, AvaGuru also offers activation, validation and deactivation endpoints that your application must integrate. Importing a string does not make it valid on an external publisher’s platform.

This guide uses illustrative software and game-key examples, not customer results. For bot creation and store connection, start with the Telegram digital-download shop setup guide. You can inspect the demo storefront before configuring your own catalog.

Choose the correct product and delivery model

Example offer AvaGuru delivery mode Where activation happens
A desktop utility you develop, with an installer and a key License Key + Files In your application’s existing licensing system
An authorized game activation code, with download handled by its publisher License Key Only On the publisher’s specified platform
A downloadable script with no activation requirement Downloadable Files Only No key is needed; the purchase includes files and your usage terms

For the desktop utility, you might sell Desktop Utility — Windows, single-user license. Upload the installer and a short setup guide, then import keys that your own licensing system already accepts. Explain supported operating systems, the number of permitted users or devices, and whether future major versions are included.

For a game, the product name and description should identify the title, edition, activation platform, region restrictions, and any prerequisite base game. “Global” is a claim to verify with your supplier, not a default label. Sell only keys you have the right to distribute and comply with the publisher’s resale conditions.

Use separate products and pools for different regions, editions, or operating-system licenses. A pool should contain keys that all match the same offer. Mixing editions creates a fulfillment problem even when every key is technically valid.

Prepare valid inventory before importing

Get keys from your own licensing system or an authorized source. Keep a private inventory record linking each batch to its product, source, restrictions, and purchase or issuance date.

The Import License Keys interface takes a CSV with one key per line. A simple file has no header:

EXAMPLE-ONLY-NOT-A-REAL-KEY-001
EXAMPLE-ONLY-NOT-A-REAL-KEY-002

These are deliberately nonworking examples. Replace them with actual unused inventory; never upload sample strings to a live product.

The current import endpoint accepts CSV files up to 1 MB. For a larger inventory, split the file into smaller batches and review each import result. Keep key files private and avoid putting real keys in screenshots, support posts, or analytics documents.

An import can detect duplicate inventory entries; it cannot check whether a publisher has already redeemed a key, whether a supplier has revoked it, or whether its stated region is correct. Those checks belong in your sourcing and activation process.

Create the product and load the pool

  1. In the AvaGuru Admin Portal, open Products and add a product.
  2. Set Product Type to Digital.
  3. Select License Key Only for a code, or License Key + Files if the purchase also includes your installer or documentation.
  4. Enter a precise title, description, price, and cover image URL. Keep Status as Draft while preparing inventory.
  5. Click Create Product.
  6. Return to Products, open the product’s actions, and choose Licenses.
  7. On License Pool, select Import License Keys and upload your CSV.
  8. Review the result and check Total Keys, Available, and Assigned. Investigate a smaller imported count before assuming the entire file was accepted.

The pool page shows health and low-stock information. Monitor Available inventory and replenish it before running a promotion. Key products use key inventory; uploading an installer does not create any keys.

For the complete storefront overview, see Telegram store builder.

Attach installers only when they belong to the offer

For License Key + Files, reopen the saved product for editing. Use Upload Files to attach the installer, archive, or setup document. Add a version and platform label so buyers can distinguish releases. Confirm the files appear in Downloadable Files.

Test the actual installer on every operating system you claim to support. For your own software, use your normal release checks, signing process, and malware scanning before distributing it. AvaGuru file delivery does not establish publisher trust or make an unsigned application trusted by an operating system.

For a publisher-issued game code, buyers will usually download through the named activation platform. Explain that process; do not upload a game installer you are not permitted to redistribute.

Download count and expiry options control file access. They do not define the activation period or device limit of the supplied key. If a product is a permanent license with a limited installer-download window, make both terms explicit before purchase.

Use Stars checkout and account for costs

Software and game keys are digital goods. Telegram requires Stars for digital goods sold inside bots and Mini Apps. A card gateway or cryptocurrency payment is not a substitute for this in-app checkout.

Set the catalog price in your store currency and verify the resulting Stars invoice. Read Telegram Stars payments and use the Stars calculator to explore price and payout assumptions.

AvaGuru earns revenue from SaaS subscriptions and takes no share of each sale. Payment costs still apply. Your margin must also account for the cost of acquired keys, support, refund exposure, taxes, and your plan. Avoid treating the face value of Stars or a calculator estimate as guaranteed proceeds.

If you are moving from another platform, compare fees and responsibilities on Gumroad alternative for Telegram, and check the licensing dependency described below before turning off the old service.

Test delivery and activation separately

Set the product to Active when the pool and files are ready. Make a purchase through your own store bot; a live test may spend real Stars and consume a real key.

First verify delivery:

  • The product describes the correct region, platform, and edition.
  • The invoice shows the intended Stars price.
  • Payment and fulfillment complete before the key is available.
  • The buyer can reveal the assigned key from the order.
  • The pool shows the expected assignment, and any included files download correctly.

Then verify activation using a key reserved for testing:

  • Your software or the publisher’s platform accepts it.
  • It unlocks the promised edition and duration.
  • The instructions explain where to paste it and any account or platform prerequisites.

Do not return a redeemed test key to the sale inventory. Opening the demo shop verifies neither your imported keys nor your activation backend.

Prepare for invalid-key and refund requests

Ask buyers to contact you privately with their order reference and the exact activation error. Do not ask them to publish a full key in a group. Distinguish an unfulfilled order from a delivered key that fails activation; these need different investigation.

Check the product edition, buyer’s region, activation platform, and supplier record before issuing a replacement. A “wrong region” message is different from “already redeemed,” and a working key pasted into the wrong application is another problem again.

The License Pool page lets you revoke an assigned license record. For your own software integrated with AvaGuru validation, a revoked key is rejected on validation; your client’s caching and offline policy still determine local behavior. Revocation does not reverse redemption on an external game platform. Do not assume a refunded or revoked key becomes safe to resell.

Publish a support contact and refund policy. Telegram’s digital payment documentation makes the seller responsible for legitimate disputes and explains Stars refunds. Explain region and activation restrictions before purchase so buyers can choose correctly.

Keep existing license verification working during a migration

If your application calls a previous seller platform to verify keys, moving checkout to Telegram does not change that code. Keep the existing verification service available until you have implemented and tested an alternative.

AvaGuru’s Restore Buyers can restore eligible past purchases and original key strings, but restoring a key is not migrating the activation backend. The Gumroad migration guide explains this distinction for software using Gumroad’s license verification endpoint.

For creators building an offer around their own software and audience, Telegram creator monetization covers the wider commercial model. For a recurring software offer, use the separate Renewing license product and review recurring software licenses on Telegram. Its first confirmed Stars payment assigns a key, and subsequent confirmed renewals extend that same key.

Frequently asked questions

Does AvaGuru generate software licenses for me?

The workflow in this guide imports keys you supply. Generate them in your licensing system or obtain authorized publisher inventory first. An imported key must already be meaningful to the system where it will be redeemed.

Can my app call AvaGuru to verify a key?

Yes, for your own software you can integrate AvaGuru’s public activation, validation and deactivation API, including activation limits. Test the client integration, device identifiers and entitlement handling before changing an existing backend. Key delivery alone does not provide DRM or offline license validation. External publisher keys remain controlled by their publisher.

Can I sell game keys without uploading files?

Yes. Choose License Key Only, import valid authorized keys, and explain the platform and activation instructions in the product description. The publisher’s platform handles the game download when that is how the code works.

Is revoking an assigned key the same as disabling the software?

It changes the AvaGuru license record. Your integrated software must act on validation results; a dashboard action does not instantly disable every installed or offline copy. Reversing redemption on an external publisher’s platform requires that publisher’s support.

Can I use the same pool for multiple regions?

Use separate products and pools when the keys have different restrictions. Each buyer should receive a key that matches the exact edition, platform, and region advertised on the product they bought.

Open the demo shop, then create your store and test one complete product with known, valid inventory.

Back to Blog

Related Posts

View All Posts »