You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Copy file name to clipboardExpand all lines: content/en-us/production/monetization/developer-products.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,13 +46,6 @@ To use scripting, you need a developer product ID. To get the product ID:
46
46
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.
47
47
</Alert>
48
48
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
-
56
49
You can sell developer products in two ways:
57
50
58
51
-[Inside your experience](#inside-your-experience)
@@ -158,7 +151,14 @@ end)
158
151
159
152
### Outside your experience
160
153
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.
162
162
163
163
<Alertseverity="warning">
164
164
Do **not** use the `Class.MarketplaceService:PromptProductPurchaseFinished|PromptProductPurchaseFinished` event to process purchases. You must use the `ProcessReceipt` callback instead.
0 commit comments