Cannot add scope read_shopify_payments

Retired Boards Appdev Authentication

Topic summary

Developers are encountering an error when attempting to query Shopify Payments data via GraphQL. The API returns an “ACCESS_DENIED” error requiring the read_shopify_payments scope, which is no longer available for apps to request.

Core Issue:

  • Certain fields within ShopifyPaymentsAccount (such as payoutSchedule and chargeStatementDescriptors) still reference the deprecated read_shopify_payments scope in their documentation and error messages
  • The replacement scope read_shopify_payments_accounts doesn’t provide access to these nested objects
  • Developers report having all available scopes enabled, yet still receive access denied errors

Shopify Support Response:
A support representative acknowledged the confusing error messaging and recommended using read_shopify_payments_accounts instead. However, this doesn’t resolve access to all child objects.

Current Status:
The issue remains unresolved. Developers are advised to contact Shopify support directly with affected store details if problems persist after adding proper scopes. This appears to be a documentation/API inconsistency requiring platform-level fixes.

Summarized with AI on November 4. AI used: claude-sonnet-4-5-20250929.
4

Hi Kyle,

I’m having the same issue.

I am able to summon the ShopifyPaymentsAccount object because my app has the read_shopify_payments_accounts access scope enabled (as well as every other access scope).

However, some objects within the ShopifyPaymentsAccount still require the read_shopify_payments access scope, which is not available anymore.

In my query, for instance, I queried chargeStatementDescriptors, but I got the same error, that I need the read_shopify_payments access scope, even though it is unavailable.

In @supermamka 's request, the ShopifyPaymentsPayoutSchedule object requires the read_shopify_payments access scope.

In the docs, we see that both of these objects require the read_shopify_payments access scope.

So I suppose this is something that’ll have to be fixed?

I’m on API version 2024-10 if that matters.

Access denied for balanceTransactions field