#shtelya_ach-testing
hollow crystalBOT
👋 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/1231959091035901993
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
jovial frigate
Additionally, the UI on the customer page breaks (this can be seen from the bolder border; the more such payment methods, the bolder it is)
fringe relicBOT
jovial frigate
When selected as a payment method for a subscription, it is not available
swift spire
Hi there 👋 can you tell me a bit more about how this payment method was created? It looks like it came from the Payment Element and is a testmode US Debit payment method. Did you manually enter the account and routing numbers when creating this?
jovial frigate
Hi, Yes it was created using Payment Element and using the react library.
swift spire
And you did manually enter the routing/account numbers?
hollow crystalBOT
shtelya_ach-testing
jovial frigate
I did not enter the data manually, but used the test bank and test account selection
After receiving the PM I will attack it to the catomer
swift spire
Alright, and you created a Payment Method directly, so it seems you're building a deferred intents flow. I would not recommend attaching the PM to the Customer, you should let the first intent handle that for you.
After creating the PM as part of your flow, what do you then plan to use it for? To immediately process a payment, if so one-time or Subscription, or to set it up for future payments?
jovial frigate
For subscription and future payments
swift spire
Gotcha, so this guide outlines the general flow that you're following:
https://docs.stripe.com/payments/build-a-two-step-confirmation
I'd recommend removing the step of attaching the Payment Method directly to the Customer. Using the above guide as a template, you'll want to do things a bit differently for steps 6 and 7 since it sounds like you won't need a payment intent.
(One minor note, this guide has been updated to use our newest flow, so you'll see it leveraging Confirmation Tokens now)
For Subscriptions:
In Step 6 you'll want to create a Subscription instead. When doing so, use expand to expand latest_invoice.payment_intent and pending_setup_intent.
If the Subscription requires a payment for the first Invoice, you'll use the client secret from latest_invoice.payment_intent to make the clientside confirmation. If it starts with a free trial you'll use the client secret from pending_setup_intent instead.
For Future Payments:
You'll use a Setup Intent instead of a Payment Intent, but otherwise the flow is very similar.
jovial frigate
Okey, thank you!