#vilesa
dense pagoda
that's one way to do so. But it will create a 1€ payment by stripe (directly canceled after). Which can be confusing to the customer
is that the only way? thanks!
sage fjord
It shouldn't
But also how are you accepting payment method?
If you're just using the underlying payment intent on the subscription object to collect payment details then there shouldn't be any additional auths charged
dense pagoda
it definitely does:
I tested in prod:
x=stripe.Subscription.modify(
"sub_1O9rNQGTsLVnzqGE1G10qcuq",
default_payment_method="pm_1O9rNiGTsLVnzqGEWqNRDWZH"
)
and I directly on my Revolut this 1eur payment which was directly canceled
and that PM ID, I retrieved it looking at the underlying pi_ of the subscription I paid with my wallet
sage fjord
Oh idk then
That's how you set default payment method
So you're integrating correctly
dense pagoda
so there's no way to create the sub and have the wallet pm ID directly attached to it ?
sage fjord
No you need to make an additional call to set the payment method as default
I've never heard of a $1 auth being charged for that though
Let me ask a colleague if that's normal
mortal sinewBOT
sage fjord
Ok so apparently this is normal with the current state of things... Had no idea. So, another thing you can do is set default payment method at the customer level (under invoice_settings.default_payment_method: https://stripe.com/docs/api/customers/update#update_customer-invoice_settings-default_payment_method). This shouldn't trigger a validation from what my colleague understands. The only thing to note is if default payment method is ever also set at the subscription level, then that payment method set on the subscription will override the one set at customer level. This is explained here: https://stripe.com/docs/api/subscriptions/update#update_subscription-default_payment_method