Set up and sell DLCs
Introduction
The In-app Purchase integrations in AccelByte Gaming Services (AGS) enables you to sync player purchases from third-party platforms (e.g., PlayStation, Xbox, etc.). To achieve this, items sold on a third-party platform need to be correctly mapped to items created in AGS.
This article walks you through how to:
- Add DLCs in AGS
- Map items from third-party platforms to DLCs in AGS
We recommend checking out the DLC Management Guidelines section first for best practices in managing DLCs in AGS.
Prerequisites
The items you intend to add to DLCs must be:
- Properly configured in your third-party platform.
- Already existing in your AGS Store. To create store items, refer to the Create store items article.
Add DLCs
After configuring the items you want to include in DLCs in your third-party platform and creating them in your AGS Store, you can proceed to adding DLCs in the AGS Admin Portal. You can add DLCs in the AGS Admin Portal in two ways: manually or by using a JSON file.
Manually add a DLC
Go to your game namespace.
On the Admin Portal sidebar, select Commerce > In-App Purchase > DLC Settings.
On the DLC Settings page, open the DLC Configuration tab and click on the +Add DLC button. The Add DLC form appears.
On the form, fill in the required information:
- Fill in the DLC ID.
- Choose Item or Currency as the Reward Type.
- Choose SKU or ID as the Item Identity. You can search for an item using its name.
- Choose COINS, INGAMEITEM, BUNDLE, CODE, SEASON, or MEDIA as the Item Type.
- Fill in an amount for the Quantity.
- Click on the Add button to save the DLC.
Add DLCs using a JSON file
Go to your game namespace.
On the sidebar, select Commerce > In-App Purchase > DLC Settings.
On the DLC Settings page, open the DLC Configuration tab and click on the + Add JSON button. A JSON template appears.
noteIf there is an existing DLC configured already, click on the JSON Options button. Then, click Edit to modify the existing DLC JSON file or Delete to replace it with a new one.
Follow the template to configure your JSON file.
Map DLCs in AGS to third-party platforms
After completing the DLC configuration, you can proceed to the DLC Mapping tab to map the DLC you created to the corresponding items in your third-party platform. You can map DLCs in AGS in two ways: manually or by using a JSON file.
Manually add DLC Mapping
Go to your game namespace.
On the sidebar, select Commerce > In-App Purchase > DLC Settings.
In the DLC Mapping tab, click on the platform with the DLC that you want to map. Then, click on the Add Mapping button. The Add DLC Mapping form appears.
Fill in the required information on the form:
- Fill in the 3rd Party Platform Item ID.
- Fill in the DLC ID.
Add DLC Mapping using JSON file
Go to your game namespace.
On the sidebar, select Commerce > In-App Purchase > DLC Settings.
In the DLC Mapping tab, click on the platform with the DLC that you want to map. Then, click on the + Add JSON button. A JSON template appears.
noteIf there is an existing DLC mapping already in the platform, click on the JSON Options button. Then, click Edit to modify the existing DLC JSON file or Delete to replace it with a new one.
Follow the template to configure your JSON file.
DLC management guidelines
It is recommended to avoid including virtual currencies and other consumable items in DLCs for several reasons, including but not limited to the following:
Complicated refund handling: Including virtual currencies or consumable items in DLC rewards may complicate the refund process as these items are often immediately consumed, partially consumed, or traded within the game. This creates difficulties in tracking and revoking the benefits gained from these items upon a refund request.
Potential fraudulent activities: Players might exploit the refund policy by purchasing DLCs containing virtual currencies or consumable items, using these items, and then requesting a refund, thus obtaining without cost.
If you still want to use virtual currency in DLCs, your revocation strategy must allow negative balances. This prevents exploitation by ensuring that if a player spends all their currency and then gets a refund, their balance can go negative. For example, if a player buys 100 VC, spends it all, and then receives a refund, their balance might go to -100. This approach helps manage refunds and maintain the game's economic balance. For more information, see Configure revocation rules.