Closed lorenalexm closed 1 year ago
StripeKit currently only supports API version 2020-08-27
you're likely using an API version higher than that. A future version with full async await support will be updated to support the latest version of 2022-11-15
https://github.com/vapor-community/stripe-kit/pull/152
I appreciate your timely reply! Looking over the Stripe Dashboard, I am only seeing the ability to use the 2016-07-06 or 2022-11-15 API versions, nothing in between.
My current use only makes use of signature verification and models to extract customer information from the intent. I would assume this would rule out the usage of the Stripe-Version: XXXX-XX-XX
header. Is there a known way to specify an exact version for webhooks?
@lorenalexm I don't think so, what I can recommend for now is forking the current branch and add the new enum type of requires_source
to the status
property of the StripePaymentIntent
type until the new version is ready to go.
Thanks for the suggestion. I will run with that and keep plugging away for now. Quite grateful for your time, thanks!
@Andrewangeta I just wanted to say thank you again. I was able to get webhook processing taken care of by adding the requires_source
to the StripePaymentIntentStatus
and also by changing public var request: StripeEventRequest?
within the StripeEvent
struct to a optional String
type.
Environment: Xcode 14.2 Swift 5.7.2 vapor 4.69.2 stripe-kit 17.0.0
When responding to a webhook from Stripe, currently coming from the CLI for testing, I find an issue when attempting to decode to a
StripeEvent
. The Vapor console outputs the following warnings:When wrapping the decoding in a
do catch
block it outputs the following fromerror.localizedDescription
The data received from the Stripe web hook is below:
The code in my project is hardly anything but the basic Vapor template; just trying to hack together a better understanding of how everything comes together between the code and Stripe. The controller used to respond to webhooks can be found below:
Is there something blatant that I am overlooking in my code, or has Stripe recently changed something on their end? I greatly appreciate any insight on this issue of mine, thank you!