kabala_api

[tiny moss]

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

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

[rigid vigil]

I see this in the subscription when the charge is due

[tribal island]

hello! taking a look, gimme a few minutes!

have you tried with the card ending with 3155 instead? That should be what you're looking for. The card ending for 3184 will always require authentication

[rigid vigil]

ahh i can try

does the sequence of API calls look correct for this purpose?

[tribal island]

are you using a trial for your subscription? that's why you're collecting the payment method upfront using a SetupIntent?

[rigid vigil]

it's similar, this is for a donation to a charity, some organisations prefer to take the card from the donor then register them in their platforms before taking the first payment of a monthly giving plan

[tribal island]

generally, for Subscriptions, we recommend using the Subsciption's underlying PaymentIntent or SetupIntent to collect the payment method details. You can read through https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements to see how to go about it.

Alternatively, if you don't want to create the Subscription first, you can use the deferred intent flow to collect the payment method details first then create a Subscription : https://stripe.com/docs/payments/accept-a-payment-deferred?platform=web&type=subscription

In short, if a customer intends to make payment for a Subscription immediately, we don't recommend that you create a separate SetupIntent, then use the newly created PaymentMethod to create a Subscription. There are several reasons for this :

• Doing so results in additional (unnecessary) API calls which contributes to your rate limits as your business grows
• This can result in in customers needing to authenticate twice, once for the SetupIntent, and once for the Subscription payment.