In order for RevenueCat's servers to communicate with Google on your behalf you need to provide a set of service credentials. The process for configuring these credentials is a bit complex, but the added level of control improves security by only providing RevenueCat with the access we need.
Your Play Developer account needs to be linked to a Google Developer Project.
Next we need to create a service account. This is done from the Google API Console.
When you hit create, a JSON file will be downloaded. These are the credentials that RevenueCat will need to communicate with Google.
Add two Roles:
- Pub/Sub Admin (to enable Platform Server Notifications)
- Monitoring Viewer (to allow monitoring of the notification queue)
You can skip the optional third step, "Grant users access to this service account" by clicking Done.
In the Google Cloud Console, click on Actions > Manage keys.
Click ADD KEY > Create new key.
Make sure JSON is selected and click Create to create and download the JSON key.
You are all done with the Google Cloud Console. Switch back to the Google Play Console and click Grant access for the newly created service account. If you do not see the service account you created, try refreshing the page.
- View app information and download bulk reports (read-only)
- View financial data, orders, and cancellation survey responses
- Manage orders and subscriptions
You will be redirected to Users and Permissions where you should see your newly created service account as Active.
In the Users and Permissions section, click on the service account and add your apps to the account. Click Apply on the sheet that appears.
Copy and paste the credentials JSON that were downloaded in step 2 to your RevenueCat account and we'll be ready to handle Google Play purchases!
It can take up to 36 hours for your Play Service Credentials to work properly with the Android Developer API. You may see "Invalid Play Store credentials" errors and be unable to make purchases with RevenueCat until this happens.
Updated 4 days ago