#bachir_error
slender cometBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1219660400199729304
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
thorny badgerBOT
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- bachir_unexpected, 5 days ago, 23 messages
zinc galleon
Hi there 👋 it looks like you're seeing that because you're trying to directly attach an ACH Payment Method to a Customer, rather than using an intent to set it up. Can you tell me more about your flow? I see you're creating Payment Methods from the Payment Element, is that because you're following our server-side confirmation or two-step confirmation guide?
misty heart
Hi, we indeed use the server-side confirmation.
I haven't tried since a while but I think that Stripe required us to attach the payment method to the customer before creating the subscription. Do you think that's the issue ?
zinc galleon
Yup, that's a pattern that isn't suggested anymore (and can actually lead to more problems than it avoids).
misty heart
It might also be linked to the fact that we provide Pre-authorized debits (PAD) in Canada, and that it might have blocked us
zinc galleon
Are you handling Subscriptions with free trials, or are they all requiring payment for the first Invoice?
misty heart
We always require payments. There can be a small free trial period, but there is always a payment.
(for example when they buy an annual membership 2 months before the expiration, we give them the 2 months for free + 1 year that has been paid)
sounds weird but let's say that this is one of our use cases aha
zinc galleon
Gotcha, if there's always a payment for the start of the Subscription, then it sounds like our guide likely covers your scenario. I'd recommend not attaching the payment method to the customer, and use this guide as a reference of how to create the Subscription using the new Payment Method ID and confirm the first Payment Intent for the Subscription:
https://docs.stripe.com/payments/finalize-payments-on-the-server?platform=web&type=subscription#create-and-submit-payment
If you're interested in trying out our new version of that server-side confirmation flow, we're actively looking for people to help test out that new flow and I'd suggest taking a look at this announcement:
#🔊announcements message
misty heart
I'd recommend not attaching the payment method to the customer, and use this guide as a reference of how to create the Subscription using the new Payment Method ID and confirm the first Payment Intent for the Subscription:
Will try that then, thanks.
If you're interested in trying out our new version of that server-side confirmation flow, we're actively looking for people to help test out that new flow and I'd suggest taking a look at this announcement:
I saw this doc when implementing the PaymentElement, will look into it.
Thanks for your help!