Reconcile Voided Purchases
A 2-step recipe with Android. We can help you get access.
Recipe · 2 steps
Reconcile Voided Purchases
with Android · Entitlement Enforcement
List voided purchases for a window and re-verify a voided token before clawing back its entitlement.
- Read the voided purchases feed for the requested window. This is the authoritative source for refunds and chargebacks that your app never saw.
- Re-read the first voided purchase token against the product purchase endpoint to confirm Google Play's current view of it before revoking the user's entitlement in your own system.
What you'll need to have ready
- packageName: The package name of the application (e.g. com.example.myapp).
- startTime: Milliseconds since the Epoch of the oldest voided purchase to return. Defaults to 30 days before now when omitted.
- endTime: Milliseconds since the Epoch of the newest voided purchase to return.
- maxResults: Maximum number of voided purchases to return. Maximum is 1000.
- type: Which voided purchases to return: 0 for voided in-app product purchases, 1 for voided subscription purchases.
- productId: The in-app product SKU used to re-verify a voided token in the second step.
For your developer
Arazzo workflow android:reconcile-voided-purchases, 2 operations: listVoidedPurchases → getPurchaseProduct. Specs on APIs.io.