Module relies on webhooks instead of API response

Just read through https://docs.recurly.com/push-notifications, which verifies what nDigitHQ is saying. Basically, we shouldn't rely on webhooks for mission critical updates and should do some combination of the following:

- Lookup an account's info in the API after receiving a webhook notification and broadcast that
- Use the token returned from a successfull signup via the Recurly.js form to update local information or create a local account. - https://docs.recurly.com/api/recurlyjs/integration#results-overview

Honestly, I think that these changes probably belong in the Recurly module itself. Since we'll we're doing in this module is implementing the main recurly module's hook.

Though, we could at least add in an extra check in the code here that pings the API and checks the account status before making changes to it locally at least.

This is definitely issue for the recurly module itself.

This is something that will be updated with the next version of the Recurly module, with Recurlyjs v3, and the use of tokens. Is there a specific place where you are having an issue or encountering errors? The module does rely primarily on the API.

Does the Recurly module currently require the use of webhooks to function properly? In testing, I noticed a setting for it in the module, but we haven't configured that in Recurly (just the API and Transparent Post keys).

@aburke626 what's the status of Recurlyjs v3, is this still being worked on? I'm having many issues with webhooks as well, finding them not reliable and very frustrating. Thank you.

Recurly js v3 has been implemented in 7.x-2.x-dev. There are still uses for push notifications, but I believe there are fewer now - please check it out but remember it's still a dev version!

We're looking at moving to the 2.x version soon because of the shutdown to TLS 1.0 on Recurly. I know that the 1.x version relied heavily on webhooks (as mentioned previously in this issue) and that Recurly even considered that a 'non-standard' practice (ie. not a good idea, but it'll mostly work).

With the 2.x version I'm wondering how 'standard' this reliance on webhooks is. You mention there's 'fewer' webhooks that are relied on...but according to Recurly is the module now using 'best practices'? Or are there webhooks it still relies on that are outside the recommended norm for how to use the API?

I'm just trying to understand, really, whether the 2.x version is a 'fix' to bring things up to the Recurly standard...or if it's a "partial fix" where 'some webhooks were removed but some remain" and it's not really relying on the API as much as Recurly recommends.

Any input on where things stand as of now?