Matt11

[pallid fulcrum]

Unfortunately no. I would recommend specifying new API version on each API call in order to test, before you upgrade the API version of the whole account

We have a guide here https://stripe.com/docs/upgrades#how-can-i-upgrade-my-api

[turbid heath]

Thanks, so basically in testing mode I can use the api version I want and later, in production, I can upgrade it, right?

Another question please.
Right now, depending if the Plan has 7 trial days or not, I'm creating a Setup Intent or a Payment Intent with createToken function.

I see here that https://stripe.com/docs/payments/payment-intents/migration?web-migration=elements#web
I need to create a Payment Intent before landing on client side checkout.

How can I manage the simple collection of card infos without creating a PI?

[pallid fulcrum]

"Simple collection of card infos without creating a PI" is exactly SetupIntent

So you always can create a SetupIntent to collect payment method, and create PaymentIntent or Subscription later on

[turbid heath]

yes, but right now I create a SI or PI when the customer clicks on "PAY" button.
I don't know in advance if he wants to use the trial period (SI) or not (PI).

The documentation always talk about PI

[pallid fulcrum]

How about just go ahead with a SI. After you know if he want trial or not you can create the Subscription according to

[turbid heath]

i don't need to create a subscription, only a payment intent.
And what about 3DS popup during checkout? Setup Intent shows it even if I'm not charging anything?

[pallid fulcrum]

Yes

It will say "Setup" instead of "Pay"

[turbid heath]

Ok thanks, I will try this solution

and 'confirmCardPayment' is working also with setup intent?

[pallid fulcrum]

it gonna be confirmCardSetup iirc

Those are old methods btw. The newer one is confirmPayment or confirmSetup using PaymentElement