Purchases and licenses

When a license moves from one person to another, How they got it changes to Transferred. Its history still starts with how it began, then records each move.

A bundle hands over the products inside it as well. Someone who gets a bundle gets a license for each product in it that they don't already hold, and more days on any subscription in it that they do. See Bundles.

What buying again does

Each product's How buying works setting, on its Pricing page, decides what happens when someone gets it again. See Pricing and license types.

• One purchase: one license per person. Buying again while they hold an active license adds nothing, though the payment is still kept as a purchase.
• Buy more than once: every purchase is a license of its own, so one person can hold several licenses for the same product.
• Subscription: every purchase adds the product's days to their license, counted from its current end date if that hasn't passed yet.

Grants and codes follow the same rules. Granting a one-purchase product to someone who already has it is refused, and a code for it is used up without adding anything.

Changing How buying works doesn't touch licenses customers already hold.

License statuses

• Active: they own it. It's in their library, they can download its files, and games that check with Enviglo can see it.
• Revoked: your store took it back. It leaves their library, their downloads stop, games no longer see it, and the product's Discord role is removed if it has one. The license stays in your records with its history, and you can restore it.
• Ran out: a subscription whose end date has passed. It's still active in your records, but it no longer gives access: downloads stop, games don't see it and the product's Discord role is removed. Owners are told three days before it ends, and again when it does. The customer's page in your dashboard calls this Expired.

Revoke, restore and transfer

• Revoke takes the product back, as described above, and the owner is told. The purchases behind the license don't change.
• Restore brings the same license back, with its history. Their access comes back with it.
• Transfer moves the license to another Enviglo account, and tells both people. The old owner loses access, and the new owner gets it, along with its downloads and Discord role. The purchases behind it stay as they were, still showing who originally paid.

Your team does all three from the Licenses page. See Give, revoke, restore and transfer licenses.

Customers can hand their own licenses to someone else too, if you let them. Switch on Let customers transfer licenses under Settings → Selling (see Store settings), and turn on Block customer transfers for this product on a product's Pricing page to keep one product out of it. See Give a license to someone else for how it works for customers.

Buying again after a revoke or transfer

• Paying again in your game makes a new license. A revoked license stays revoked, as the record of what happened, and a transferred one stays with its new owner.
• Owning a game pass isn't a new payment. Registering it again in game doesn't bring back a license that was revoked or given away.
• A grant or a code after a revoke also makes a new license.
• A free product can't be claimed again once you've revoked it.
• A subscription that ran out isn't revoked, so buying it again extends the same license from the day they buy.

How games see licenses

Your game asks Enviglo about a player by their Roblox ID. Enviglo finds the Enviglo account that Roblox ID is linked to, and answers with that account's licenses that give access right now: active ones, and for subscriptions, ones that haven't run out.

That has a few consequences:

• A license only counts in game once its owner has linked the Roblox account they play on. If you give a product to someone by username and they haven't linked Roblox, they own it on Enviglo, but no game can see it until they link. See Link your Roblox account.
• For Buy more than once products, your game can ask how many copies a player holds.
• A player banned from your store is reported as banned, and as holding nothing from your store. See Customers and bans.

To set this up in your game, see Check licenses in your game.

Players who haven't joined Enviglo yet

When someone buys in your game with a Roblox account that isn't linked to anyone on Enviglo, the license waits for that Roblox ID. Granting or transferring a product to a Roblox ID that isn't linked to anyone does the same.

• Your game can check it by their Roblox ID straight away.
• In your dashboard, they show up under Customers like any other customer, by name and username, usually with their Roblox name and picture.
• When the player links that Roblox account to their Enviglo account, everything waiting for it moves over, licenses and purchases included, and Enviglo lets them know.
• If they already held a license for the same product on their own account, both are kept, side by side.

Licenses and purchases from myPod

Enviglo is myPod's successor, and myPod's licenses and purchases came with it.

• Imported licenses show From myPod as how the owner got them, and their history starts with Brought over from myPod.
• Imported purchases show as Roblox purchases with a myPod purchase reference. Each is linked to the buyer's license for that product when they still hold one. If a myPod license has no purchase linked to it, its page says it came over from myPod, which kept its purchases separately.
• myPod didn't record what each buyer paid, so a myPod purchase shows the product's Robux price when it was imported.
• They count as sales, like any other Roblox purchase.
• A myPod buyer who hasn't joined Enviglo yet has their licenses waiting in the same way, until they sign in with the Discord account or link the Roblox account they used on myPod.

See Coming from myPod for more on the move.

Keep reading

• Give, revoke, restore and transfer licenses
• View purchases
• Customers and bans