#ykmb_best-practices
1 messages ¡ Page 1 of 1 (latest)
đ 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/1283847288665669632
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello! Setting up the card with a Setup Intent is our recommended approach. It won't be able to tell you if a later charge will succeed or not (nothing can predict the future) but it will attempt to set up the card for future use. On Subscriptions, there's a pending_setup_intent property containing a Setup Intent you can use for this purpose: https://docs.stripe.com/api/subscriptions/object#subscription_object-pending_setup_intent
I see, thanks for the quick response. I have a few follow up questions
- If a customer needs 3DS auth (e.g. card from India), then should we make them go through the 3DS pop up flow when they sign up for the trial? (when the setup intent is created)
- Using set up intent only sets up the payment, but does not do any fraudulent checks on the card. Is this understanding correct?
- From what I understand, the Radar fraud prevention rules are more like "charge-time" rules, but they don't do anything until there is an attempt to charge. Is this understanding correct? Trying to see if we can use some rule / model that stripe provides to do an early diagnosis of if the card is legitimate (does not need to be bullet proof)
- To confirm, stripe does not offer the ability to create a test charge on a subscription?
#1: Yep, the Setup Intent will walk them through whatever setup is required, including 3D Secure. Note that India transactions have special rules and requirements as outlined here: https://docs.stripe.com/india-recurring-payments
#2: That depends on what you mean by "fraudulent checks". Can you provide more details?
#2: That depends on what you mean by "fraudulent checks". Can you provide more details?
E.g. stolen credit cards, credit card testing
#3: By default, yes, that's correct. However, you can enable Radar rules for Setup Intents in your Dashboard here: https://dashboard.stripe.com/settings/radar
#4: What exactly do you mean by "test charge" here?
#4: What exactly do you mean by "test charge" here?
E.g. try to charge $1 to the card, then do a refund.
The Setup Intent will perform some level of validation, including checking to see if the card number itself is valid, but it doesn't confirm things like if there's any available balance or things like that. The specific validation steps performed also depend on the specific payment method and set up in each particular case.
Setup Intents will often perform a $0 validation with the card issuer, but in some cases they may also perform a $1 validation. We control that on our end, it's not something you can force to happen. You can, however, take a $1 payment yourself, but it's not recommended to do so just to validate the card.
The Setup Intent will perform some level of validation, including checking to see if the card number itself is valid, but it doesn't confirm things like if there's any available balance or things like that. The specific validation steps performed also depend on the specific payment method and set up in each particular case.
I see, balance checks are not necessary.
Setup Intents will often perform a $0 validation with the card issuer, but in some cases they may also perform a $1 validation. We control that on our end, it's not something you can force to happen. You can, however, take a $1 payment yourself, but it's not recommended to do so just to validate the card.
I see, good to learn this