Have your say in Community Polls: What was/is your greatest motivation to start your own business?
Our Partner & Developer boards on the community are moving to a brand new home: the .dev community forums! While you can still access past discussions here, for all your future app and storefront building questions, head over to the new forums.

RecurringApplicationCharge - charge_id not in url

RecurringApplicationCharge - charge_id not in url

jozo
Shopify Partner
1 0 0

Our app uses RecurringApplicationCharge. When our customer confirms a charge in Shopify, he/she is redirected back to our app. In most cases the url contains charge_id. So the url is decorated_return_url. However in some cases it doesn't contain charge_id even though the charge was confirmed in Shopify and is active. Why is that?

 

I can provide more info if needed.

Reply 1 (1)

ShopifyDevSup
Shopify Staff
1453 238 522

Hey @jozo,

Thanks for sharing all of those details, example docs and outlining a functionality you feel isn't working as expected. There are known cases where it is expected for a charge_id not to carry over in a return_url, however there have been a few similar reports that our teams are tracking at the moment. For next steps, our suggestion would be to connect with Shopify Partner Support to share a few examples. 

Generally an investigation requires some specific details such as an x-request-id and date response header, request body, full endpoint, and response body showing the behavior. In the case of data that was returned via the Admin directly, we instead suggest requesting collaborator permissions on an affected store, and documenting a url/timeframe. 

Please feel free to share a link to this post should whomever you work with need to review as context - Best!
 

Developer Support @ Shopify
- Was this reply helpful? Click Like to let us know!
- Was your question answered? Mark it as an Accepted Solution
- To learn more visit Shopify.dev or the Shopify Web Design and Development Blog