-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Webhook support? #98
Comments
@jbaugh I missed this question somehow, sorry for the delay. There isn't any webhook support built into the library currently. I've never made use of their webhooks and never had cause to implement them. A PR would certainly be welcome, even if only for a subset of the potential events: https://developers.braintreepayments.com/guides/webhooks/overview |
@sorentwo I think I'll work on that. I got it working for my use case, so I think I might be able to at least get something put together than can help :) |
- Ensure compatiblity with pre-OTP-22 version as well as OTP-22 and beyond - Right now, Braintree.Webhook#parse/2 returns the signature and decoded payload (an xml document embedded in a string) from Braintree for later post-processing - Future work envision handling the webhook notification payload parsing in a more standardized way - Related to sorentwo#98
- Ensure compatiblity with pre-OTP-22 version as well as OTP-22 and beyond - Right now, Braintree.Webhook#parse/2 returns the signature and decoded payload (an xml document embedded in a string) from Braintree for later post-processing - Future work envision handling the webhook notification payload parsing in a more standardized way - Related to sorentwo#98
- Ensure compatiblity with pre-OTP-22 version as well as OTP-22 and beyond - Right now, Braintree.Webhook#parse/2 returns the signature and decoded payload (an xml document embedded in a string) from Braintree for later post-processing - Future work envision handling the webhook notification payload parsing in a more standardized way - Related to sorentwo#98
- Ensure compatiblity with pre-OTP-22 version as well as OTP-22+ - Right now, Braintree.Webhook#parse/2 returns the signature and decoded payload (an xml document embedded in a string) from Braintree for later post-processing - Future work envision handling the webhook notification payload parsing in a more standardized way - Related to sorentwo#98
- Ensure compatiblity with pre-OTP-22 version as well as OTP-22+ - Right now, Braintree.Webhook#parse/2 returns the signature and decoded payload (an xml document embedded in a string) from Braintree for later post-processing - Future work envision handling the webhook notification payload parsing in a more standardized way - Related to sorentwo#98
- Ensure compatiblity with pre-OTP-22 version as well as OTP-22+ - Right now, Braintree.Webhook#parse/2 returns the signature and decoded payload (an xml document embedded in a string) from Braintree for later post-processing - Future work envision handling the webhook notification payload parsing in a more standardized way - Related to sorentwo#98
…113) * Add module for parsing and validating webhook events from Braintree - Ensure compatiblity with pre-OTP-22 version as well as OTP-22+ - Right now, Braintree.Webhook#parse/2 returns the signature and decoded payload (an xml document embedded in a string) from Braintree for later post-processing - Future work envision handling the webhook notification payload parsing in a more standardized way - Related to #98 * Refactor tests to use sample fixture(s)
I might be missing something obvious, so I apologize if so, but I can't see where webhook support is implemented (if it is). If there is, can you point me in the right direction, and if not, do we have plans to add it? Thanks in advanced.
The text was updated successfully, but these errors were encountered: