Shop Pay Path B OAuth — access_denied on Catalog client (pay:wallet:read) and invalid_request on App client (identity link)

Hi we’re integrating Shop Pay Path B (identity-linked / buyer-linked) for our AI shopping agent and have hit two different failures depending on which client credentials we use. Looking for confirmation on which client + scopes are correct for customer identity linking.

What we’re building

  • Backend mints an authorize URL via discovered Shop AS (https://accounts.shop.app/oauth/authorize)
  • Scopes we send for identity link (per UCP / buyer-linked docs):
    openid dev.ucp.shopping.catalog.search:read dev.ucp.shopping.checkout:manage
  • Registered redirect URI (exact match in Dev Dashboard):
    http://localhost:8765/ai/shopping/shop/oauth/redirect

Attempt 1 — Catalog API client

  • Used our Catalog client credentials ( client_id : 723505eba7f967590f74234688e2105c)
  • When we included pay:wallet:read, Shop returned access_denied
  • Without wallet scope, create_checkout / get_checkout with the buyer-linked token returns payment.instruments=[], so we can’t complete Shop Pay even though the merchant advertises dev.shopify.shop_pay

Attempt 2 — Dev Dashboard App client

  • Client ID: e54e3f8f326dc6c8a934f5f919ead180
  • App has shop_app:oauth and the localhost redirect URI above registered
  • Our API POST /oauth/start succeeds (200) and returns an authorization_url
  • Opening that URL on Shop shows:
    “An error has occurred — Missing a required parameter or the parameter has an invalid value (invalid_request)”
  • So we never get past the linking / authorize step (no code redirect back to us)

Questions

  1. For customer identity linking (Path B), should we use the Catalog client, the Dev Dashboard App client, or a separate Shop Pay / identity client?
  2. Which scopes are required / entitled for that client? Specifically:
    • Are dev.ucp.shopping.catalog.search:read and dev.ucp.shopping.checkout:manage correct?
    • How do we get pay:wallet:read entitlement (Catalog currently access_denied)?
  3. For App client e54e3f8f…, what typically causes invalid_request on accounts.shop.app/oauth/authorize when redirect_uri is already registered exactly as sent?

Happy to share the full authorize URL query params or a screen recording. Thanks!

Hey @ykxmalai - thanks for reaching out!

On the app client, the invalid_request comes from the redirect URI. This client only accepts HTTPS redirect URIs that are included in a released version of the app, so http://localhost:8765/ai/shopping/shop/oauth/redirect fails validation and the authorize page shows the error instead of redirecting back. To get past it, add an HTTPS redirect URI, such as a tunnel URL, to the app’s allowed redirect URLs and release a new app version.

For Shop Pay through Shop MCP, the sign-in guide has your app request openid personal_agent with resource=https://mcp.shop.com from a registered private OAuth client. The Catalog client can’t grant pay:wallet:read, so this needs to go through the app client.

personal_agent isn’t self-serve for apps yet. Shopify has to enable it for your organization before you can add it to your app, and there’s no public application process for that right now. Until it’s enabled, requests that include it return access_denied. I’m checking internally on how apps can request access and will follow up here.

hi @Wes-Dev-Shopify i resolved the access denied issue with https , that is no longer an issue but for the wallet read access on the app client ( which i used ) how do i get the access who can provide me the access ?

hi @Wes-Dev-Shopify do we have some updates in here ?

Hey @ykxmalai - sorry about the delay here, and glad the HTTPS redirect sorted out the app client.

Wallet access for apps still isn’t available, and Shopify isn’t granting personal_agent or wallet scopes to individual apps by request right now. So there isn’t anyone who can enable it for your app at the moment.

We’re looking into a self-serve way for apps to get this access. I don’t have a timeline to share yet, but I’ll post an update here if anything changes on that front.