jimmy3DS

[severe wave]

Can you share the ID (req_xxx) of the failing API request? https://support.stripe.com/questions/finding-the-id-for-an-api-request

[warm narwhal]

just trying to get it!

[severe wave]

This is default behaviour, FYI. Explained here: https://stripe.com/docs/api/invoices/object#invoice_object-billing_reason

If you're passing a cus_xxx without a default PM/Source attached and are instead capturing payment details in a checkout flow you'll want to pass payment_behavior: 'default_incomplete

[warm narwhal]

req_kCEa0uJE8LzFrX

I'm migrating away from the Source API

That's what I'm currently using however it's stopped working as sources don't work with 3D secure v2 right?

So I'm now trying to create a customer and subscription without a source

[severe wave]

You need to pass payment_behavior: 'default_incomplete' on subscription create then

[severe wave]

Correct

[warm narwhal]

ahhh

thank you, I'll try that

@severe wave that worked(ish) but my original question re: stripe api compatibility stands. see this request: req_DhFx6AvKGuc3S5 the invoice is a string not an object. if I retrieve the invoice then the payment_intent will be a string not an object. I'm just not convinced this API will let me do 3D secure v2?

[silent citrus]

if I retrieve the invoice then the payment_intent will be a string not an object
yep, but you can retrieve the PaymentIntent object by ID as well

but really, you would use the expand feature of the API here to 'expand' =>["latest_invoice.payment_intent"] when creating the subscription, and then you can use the PaymentIntent on the frontend to perform 3D Secure.

it's explained in detail in this guide https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=elements

[warm narwhal]

ah thank you

@silent citrus I'm getting requires_source now rather than the expected payment_method_required. req_DVZUdl5xlBIdJa -I'm convinced it's because of the API version?

[silent citrus]

requires_source is the old name for requires_payment_method on old API versions yes

[warm narwhal]

Are you confident that I can go all the way to getting 3d secure v2 working with this api version?

[silent citrus]

so if using an old version you have to bear that in mind when adapting the example code

[silent citrus]

you can, it works fine. But the docs assume you are using the latest version of everything so it can make them hard to follow, but there are not technical blockers

[warm narwhal]

okay thanks