#bernie-checkout
tepid viper
Hi! Thank you!
I'm trying to enable Stripe Checkout to save card details and prefill them when the customer makes a following purchase
I found this argument in the API but I tested in the dashboard with a payment link and although it did save the card to the customer account, it doesn't prefill the card in future payment attempts
And btw, I'm not trying to use Link
flat juniper
It depends. There are some conditions to display if setting up for future usage:
ID of an existing Customer, if one exists. In payment mode, the customer’s most recent card payment method will be used to prefill the email, name, card details, and billing address on the Checkout page. In subscription mode, the customer’s default payment method will be used if it’s a card, and otherwise the most recent card will be used. A valid billing address, billing name and billing email are required on the payment method for Checkout to prefill the customer’s card details.
Reference: https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-customer
tepid viper
Yes, that sounds exactly what I'm looking for
But in my tests it doesn't seem to be working
How can I authenticate the user in a payment link?
Maybe that's the problem
You see, my user's email address is johndoe@test.com. My ideal scenario would be to prefill the payment details with the payment method saved to this customer's account
For reference, I'm checking the save payment details box. I've confirmed that it sets the setup_future_usage argument to off_session
flat juniper
In this case, the process will be:
- Create a customer: https://stripe.com/docs/api/customers/create
- Create a checkout session for future usage with customer ID. Both
customerandpayment_intent_data.setup_future_usagefields should be filled: https://stripe.com/docs/api/checkout/sessions/create
Customer validation should be done by your side
tepid viper
Got it. Is there any way to test it with the dashboard?
fickle rover
Worth noting that Payment Links can't reuse an existing Customer object (cus_xxx) so prefilling that way is not possible
tepid viper
Ah ha
That explains it 🙂
Thanks a lot, guys!
Hey and a quick unrelated question: The docs say that Stripe Radar is pre-integrated with the whole ecosystem. Is there a free version of it, though or is it paid only? I'm trying to find out how to configure 3DS
fickle rover
Yep, all accounts have Radar (there's a paid upgrade with some further controls/insights)
What are you trying to 'configure'?
tepid viper
I'd like to configure triggering rules, say, for a specific country
tepid viper
Yep, all accounts have Radar (there's a paid upgrade with some further controls/...
And in this free version, 3DS is fully handled (and presented) by Stripe Checkout? Is there anything for me to do?
fickle rover
I'd like to configure triggering rules, say, for a specific country
Will be useful: https://stripe.com/docs/radar/rules/reference
fickle rover
And in this free version, 3DS is fully handled (and presented) by Stripe Checkou...
Yep, Checkout includes Radar by default: https://stripe.com/docs/radar/risk-evaluation#:~:text=CAN I USE RADAR WITH STRIPE CHECKOUT OR STRIPE BILLING%3F
tepid viper
That's great, thank you. I was confused by the pricing page in the Stripe Radar product site. To confirm, I can do this without extra cost, right?
fickle rover
Correct, the regular fees are waived for accounts on regular pricing. Radar for Teams is extra
fickle rover
np!