Skip to content

Commit 5fdeed3

Browse files
authored
Relocate ProcessReceipt API notes
Update document for readability and improved organization. Moved the ProcessReceipt API comments from below the header of "Sell your developer product" to it's appropriate location, "Outside your experience." This is to avoid misleading developers into believing that ProcessReceipt is required for all transactions, when it is actually only required for transactions outside of the experience. Also improved some verbiage for better readability.
1 parent 3ab4c98 commit 5fdeed3

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

content/en-us/production/monetization/developer-products.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -46,13 +46,6 @@ To use scripting, you need a developer product ID. To get the product ID:
4646
If you're using [price optimization](./price-optimization.md), make sure to place the script inside a `Class.LocalScript` so that users see personalized product prices.
4747
</Alert>
4848

49-
Before selling developer products, make sure you are properly processing sales receipts and granting users their purchased products. To do so, you must:
50-
51-
- Use the `Class.MarketplaceService.ProcessReceipt|ProcessReceipt` API to check purchase receipts. `ProcessReceipt` automatically reads and acknowledges that a user has purchased a product outside of the experience.
52-
- Validate each receipt for `User ID`, `Developer Product ID`, and the receipt status.
53-
- If the receipt has a status of **Open**, grant the user the developer items they have purchased.
54-
- Respond to the `ProcessReceipt` API with a message acknowledging the receipt and validating that the purchased items were granted.
55-
5649
You can sell developer products in two ways:
5750

5851
- [Inside your experience](#inside-your-experience)
@@ -158,7 +151,14 @@ end)
158151

159152
### Outside your experience
160153

161-
To enable developer product purchases outside your experience, you must work with the `Class.MarketplaceService.ProcessReceipt|ProcessReceipt` API. After a user makes a purchase in the **Store** tab of your experience details page, you must use `ProcessReceipt` to confirm their purchase and grant them their items once they enter your experience.
154+
To enable developer product purchases outside of your experience, you must work with the `Class.MarketplaceService.ProcessReceipt|ProcessReceipt` API.
155+
156+
After a user purchases a developer item in the **Store** tab of your experience page, you must:
157+
158+
- Use the `Class.MarketplaceService.ProcessReceipt|ProcessReceipt` API to check purchase receipts. `ProcessReceipt` automatically reads and acknowledges that a user has purchased a product outside of the experience.
159+
- Validate each receipt for `User ID`, `Developer Product ID`, and the receipt status.
160+
- If the receipt has a status of **Open**, grant the user the developer items they have purchased.
161+
- Respond to the `ProcessReceipt` API with a message acknowledging the receipt and validating that the purchased items were granted.
162162

163163
<Alert severity="warning">
164164
Do **not** use the `Class.MarketplaceService:PromptProductPurchaseFinished|PromptProductPurchaseFinished` event to process purchases. You must use the `ProcessReceipt` callback instead.

0 commit comments

Comments
 (0)