Web Purchase Link - webCheckoutUrl property is empty

Hi ​@ian_404,

In order to have the webCheckoutUrl populated, you need to create a Web Purchase Link for the offering. Here are the docs that explain how to do that. Let me know if that’s not the issue so we can investigate further.

Best,

Antonio

Hi Antonio,
Thank you for your prompt response! We’ve configured the Web Purchase Link according to the documentation and confirmed that it’s accessible via the web. However, it still isn’t appearing in the property as expected.
Do you have any suggestions on what else we might check or additional troubleshooting steps we could try?
Thanks again for your assistance!

Hi ​@ian_404,

Could you try again? There’s a bug and the cached offerings response is not cleared after creating the Web Paywall Link. I’ve just cleared the cached for the two projects you are a collaborator of. The team is already aware of the issue and we’ll fix it soon, but for now I think you should already get the Web Purchase Link in the response. Let us know if that’s not the case.

Best, 
Antonio
 

Hi Antonio,
I just tried your suggestion, but unfortunately the field is still empty. I also completely uninstalled and reinstalled the app to ensure there was no cached data remaining, but the issue persists.
Do you have any other ideas on what might be causing this?
Thanks for your help!

Hi ​@ian_404,

Looking further into this, it seems that you don’t have a Paywall configured and perhaps are looking to get a webCheckoutUrl to build a web button on your own, is that correct?

As of right now, we are only returning these URLs in the packages as long as there’s a Paywall configured. This might not have been intentional, and I am currently checking with the team, but on the meantime, I’d like some clarification as how is it that you plan to use this URL? Is it in a pre-existing Paywall you already have in your app?

Cheers

Circling back again ​@ian_404,

After discussing with the team, it wasn’t really needed that we’d require our own Paywalls to attach the `web_checkout_url` to a Package.

We just shipped a fix and just verified that the URLs are indeed being returned!
Please let us know should you have any more questions,

Thanks

Hi Fon,
Yes, we’re using an existing paywall and wanted to integrate the link into it. I can confirm that the `webcheckoutURL` is now set and everything is working as expected.
Thank you so much, ​@fon  and ​@antonio , for resolving the issue so quickly!

Hello,
Following up on the `webcheckoutURL` issue: I’m seeing that the `webcheckoutURL` is populated for the annual package, but not for the monthly package. Could this be a configuration issue on my end?
Any guidance would be appreciated-thanks!

Hello,
I’ve just configured additional offerings to support web billing, but I’m noticing that the checkout URL is missing for these new offerings as well. ​@antonio , could this be related to the caching issue you mentioned earlier, or is there something else I should look into?
Thanks for your help!

This might be because there was no RC Web Billing product attached to the monthly package. 

It could be related. I’m going to take a look.

In order to move faster, it might be better to open a support ticket so you can provide more information about your project, apps, and offerings privately. 

Hi ​@ian_404,

We shipped some fixes and caching shouldn’t be a problem any more. Does everything look good on your side now? 

Best,

Antonio