jt_docs

[shadow elk]

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

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

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.

• jt_docs, 1 day ago, 6 messages

[craggy vale]

The way to save and verify a user's card is to use a setupintent

That doc you linked is correct

[winter canopy]

But that appears to reply in webhooks? Or will it immediately authenticate the card as well and respond to API call with indication authentication failed?

[craggy vale]

Both

We just always recommend relying on webhooks

Customer can have network/browser issues and may not finish the checkout experience

Webhooks are always the most robust way to handle things

[winter canopy]

I see, we are consuming webhooks, but we are not relying on webhooks for real-time feedback to the User.

Just to be clear, We are selling a subscription with a 7-day free trial, we create a setupintent when the user enters this trial and we collect card information. At that time, Stripe will authenticate the card (for how much? full amount or?)

[craggy vale]

We don't always do a real authorization. Sometimes we do and sometimes we don't. it's an internal optimization. But when we do a card auth it's either for $0 or $1

[winter canopy]

Is there a way to do a real-time authorization 100% of the time? Would that require using the Create Charge API for just the authorization? Then if it succeeds, we create a SetupIntent for future off-session payments?

[craggy vale]

There's not. You'd have to create the charge yourself

But I don't recommend doing that

[winter canopy]

We are trying to prevent the scenario of having the user come back later to update their payment information

[craggy vale]

i recommend only relying on setupintents

Sure, but you'll be charged a bunch on auth fees otherwise

Setupintents were built for this purpose

And we optimize when a real auth is needed or not

[winter canopy]

Ok thank you! this was very helpful information. Appreciate your time