Configure revocation rules

Last updated on October 9, 2026

Overview

The AccelByte Gaming Services (AGS) Revocation service enables you to configure and customize your revocation strategy logic for durable entitlements, consumable entitlements, and virtual currencies.

This article walks you through how to configure revocation rules correctly based on your preferences and business needs as well as the implications of each rule. You can configure them in the Admin Portal or with the AGS CLI.

Prerequisites

• Store, wallets, and in-app purchase services are configured properly.
• If the user intends to use customized revocation rules, the custom service address must be configured properly.
• To follow the AGS CLI steps, you have installed the AGS CLI and signed in. See Install and sign in.

Configure revocation strategies

Revoke virtual currency

Admin Portal

1. In the AGS Admin Portal, go to your namespace.

2. On the sidebar, go to Commerce> Revocations > Configurations.

3. If you would like to enable virtual currency revocation, turn on the Allow Revocation toggle, then select your preferred revocation strategy.

   

   • Fail Revocation if Wallet Balance would drop below 0: Select this when the amount to be revoked is greater than a player's wallet balance, the revocation will be failed.

   • Allow negative wallet balance: Select this when the amount to be revoked is greater than a player's wallet balance, the player's wallet balance will be deducted accordingly and become negative.

   • Customization: Select this to use your own custom revocation strategy by using gRPC Custom Service.

     

   note

   1. Virtual currencies can only be deducted from their corresponding wallets.
   2. Custom Service gRPC Server Address needs to be configured if you would like to use customization.

AGS CLI

1. Save the current revocation configuration to a file. Any file name works. This example uses revocation-config.json:

   ags platform revocations get-config --namespace <YourNamespace> --format json > revocation-config.json

2. In the file, change the wallet section. Set enabled to true to turn on Allow Revocation, and set strategy to one of the values in the table:

   {
     "wallet": {
       "enabled": true,
       "strategy": "REVOKE_OR_REPORT"
     }
   }

   Admin Portal strategy	strategy value
   Fail Revocation if Wallet Balance would drop below 0	REVOKE_OR_REPORT
   Allow negative wallet balance	ALWAYS_REVOKE
   Customization	CUSTOM

3. Send the whole file back. This resends the other settings as they are, the same way the Admin Portal does:

   ags platform revocations update-config --namespace <YourNamespace> --json @revocation-config.json

   note

   If you use CUSTOM, configure the custom service gRPC server address first. Otherwise, the update fails.

Durable entitlements revocation

To configure your preferred strategy for durable entitlements, follow these steps:

Admin Portal

1. In the AGS Admin Portal, go to your namespace.

2. On the sidebar, go to Commerce> Revocations > Configurations.

3. On the Revocation Configurations page, select Entitlement (Durable).

   

4. Select your preferred strategy for durable entitlements.

   • Default: Entitlement will be revoked from the player's account.
   • Customization: Use your own custom revocation strategy by using gRPC Custom Service.

AGS CLI

1. Save the current revocation configuration to a file. Any file name works. This example uses revocation-config.json:

   ags platform revocations get-config --namespace <YourNamespace> --format json > revocation-config.json

2. In the file, change the entitlement.durable section. Set strategy to REVOKE_OR_REPORT for Default or CUSTOM for Customization:

   {
     "entitlement": {
       "durable": {
         "enabled": true,
         "strategy": "REVOKE_OR_REPORT"
       }
     }
   }

3. Send the whole file back. This resends the other settings as they are, the same way the Admin Portal does:

   ags platform revocations update-config --namespace <YourNamespace> --json @revocation-config.json

   note

   If you use CUSTOM, configure the custom service gRPC server address first. Otherwise, the update fails.

Consumable entitlements revocation

Admin Portal

1. In the AGS Admin Portal, go to your namespace.

2. On the sidebar, go to Commerce> Revocations > Configurations.

3. On the Revocation Configurations page, select Entitlement (Consumable).

   

4. Select your preferred strategy for consumable entitlements.

   • Default: Only consumable entitlements that are unused or with enough use count will be revoked from players.
   • Customization: Use your own custom revocation strategy by using gRPC Custom Service.

AGS CLI

1. Save the current revocation configuration to a file. Any file name works. This example uses revocation-config.json:

   ags platform revocations get-config --namespace <YourNamespace> --format json > revocation-config.json

2. In the file, change the entitlement.consumable section. Set strategy to REVOKE_OR_REPORT for Default or CUSTOM for Customization:

   {
     "entitlement": {
       "consumable": {
         "enabled": true,
         "strategy": "REVOKE_OR_REPORT"
       }
     }
   }

3. Send the whole file back. This resends the other settings as they are, the same way the Admin Portal does:

   ags platform revocations update-config --namespace <YourNamespace> --json @revocation-config.json

   note

   If you use CUSTOM, configure the custom service gRPC server address first. Otherwise, the update fails.

View revocation history

Admin Portal

1. In the AGS Admin Portal, go to your namespace.

2. On the sidebar, go to Commerce> Revocations > Revocation History. The Revocation History page appears, showing a table of all historical revocation records is displayed.

   

3. On the Revocation History page, you can narrow down your search by using the All Source and All Status filters, or search for individual user records by using the Search by User ID search box.

   • All Source: This includes Order, downloaded content (DLC), and Other, which indicates where these revocations came from.
   • All Status: This includes "Success" and "Failed".

4. To open a specific revocation record, click its View button to view its details.

   

AGS CLI

1. List the revocation history of a player:

   ags platform revocations get-history --namespace <YourNamespace> --user-id <UserId>

2. To narrow down the results, add a source or a status filter. The source is ORDER, DLC, IAP, or OTHER. The status is SUCCESS or FAIL:

   ags platform revocations get-history --namespace <YourNamespace> --source ORDER --status FAIL

   Each record in the output includes its details.

Refund and chargeback

1. Refund and chargeback events that occur on third-party platforms are hard to detect as AGS is not directly integrated with third-party platforms.

2. For PlayStation, AGS uses Sony's Commerce Management API to detect when there is a refund or a chargeback event and will revoke or reinstate player entitlements or ownership accordingly.

3. For other platforms, AGS cross-references durable entitlements a player has on the third-party platform with what the player has on AGS. Then, AGS will revoke or grant entitlements accordingly.

   note

   1. This is an automatic process but only happens when a player logs into the game.
   2. There is no automatic process to revoke consumable entitlements and virtual currencies. Currently, the process has to be manually performed by admins.