#swe_api

1 messages ¡ Page 1 of 1 (latest)

idle sequoiaBOT
#

👋 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/1240407943564759131

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

pallid sparrow
ocean seal
#

Why do you suggest using payment intents instead of setup intent? I usually use payment intent - only when amount is involved, in other cases - we use setup intent only.

pallid sparrow
#

I suggested the opposite

#

Setup Intents for setting up a Payment Method for future payments

ocean seal
#

If I have a use case of setting up a payment method for future payments along with making the first payment?
For example - a subscription usecase to start a recurring transaction as well as first installment collection?

#

In that case, should we be using setup intents - to create a payment method and again a payment intent - to make an actual payment?

pallid sparrow
#

Why not use a one-off Invoice Item instead of a wholly separate charge unrelated to the Subscription?

ocean seal
#

We are not using Stripe's subscription API yet. So, building a custom solution

pallid sparrow
#

Ah, got it. Yeah, I mean, in that case you would still use Setup Intents, then just immediately create a payment once it's setup.

ocean seal
#

Does this rule apply only for single use payment methods like ideal, bancontact or all payment methods like SEPA, ACH as well ?