Support API version 2023-08-16

https://stripe.com/docs/upgrades#2023-08-16

Looks like we'll need to specify return_url when creating paymentIntents/setupIntents.

Hi @mattwire , thanks for reporting. I've run into this as well now.

What do you think would be easier as a "hotfix":

1. Somehow adding a "return_url" , or
2. adding "stripe_version": "2022-11-15" to the call?

I ran into this issue and am looking for a hotfix as well. I have a client that just opened up a Stripe account so the API version is set to 2023-08-16 and can't be downgraded.

While troubleshooting I found that in CRM/Core/Payment/Stripe.php -- setAPIParams() -- we are setting the API version to 2022-11-15. However, that doesn't seem to be working (or perhaps it needs to be explicitly set elsewhere). In my tests I can see in the Stripe interface that the failing API calls have the default API version set instead of the version set with that function.

Yes, I came across the same thing. I seemingly cannot find the right place to set the stripe_version / Stripe-Version API parameter/header anywhere, it always gets ignored or filtered out. Maybe @mattwire knows better, otherwise I'd have to do some more profound debugging.

Also, the composer.json pegs the library version as 9.x:

    "stripe/stripe-php": "^9"

The current major version is 12. Maybe our problem was fixed in the recent version...Has anyone tested that?

The current major version is 12. Maybe our problem was fixed in the recent version...Has anyone tested that?

I have tested that, and it doesn't help. It looks like this issue is not related to the Stripe API version.

I have instead now "hot-patched" the library and added the following line HERE:

$defaultHeaders['Stripe-Version'] = '2022-11-15';

With that, it seems to work again for me.

Obviously, that is a hack and not a proper fix, and we need to find out why the requested API version from the extension (e.g. HERE) isn't passed on to the API call, but I'm running out of resources to follow up on this.

From what I remember you can't always specify the Stripe API version.

We really need to set the return_url parameters which will be backward-compatible.

We really need to set the return_url parameters which will be backward-compatible.

No doubt. I just wanted to document my patch in case somebody else is in trouble right now.

Thanks. Also need a hotfix for Stripe API version 2023-08-16

If you try master branch it fixes this issue. Will release soon as extension version 6.10.

Hi! Do you have any idea when version 6.10 will be released?

When it's been tested by enough people and no critical issues are found

@JonGold @jitendra see discussion at c4b40b55 should be fixed via 3d66892c

changed milestone to %6.10

I'm running master branch and this now works with the 2023-08-16 API version.

I'm running the master branch and it is working for me with the 2023-08-16 API version. Thanks.

I'm having this issue with 6.10 and the former API version (2023-08-16). I received a message from Stripe saying that we encountered many errors because we don't specify a value for the attribute return_url in the Paymentintent. Should we upgrade to the last one?

Hello All, I'm running in the same thing with CiviCRM 5.63.3 and Stripe Ext. 6.9.4. The only solution that worked for me was the hint from mattwire:

"here should be fixed via 3d66892c"

added: $intentParams['payment_method_types'] = ['card'];

Regards, Heiko

Fixed in 6.10

closed