#lamigne-checkout-prefill
1 messages ยท Page 1 of 1 (latest)
Hello @wide linden , thank you for your answer, however I needed the opposite : never prefill data even if customer already exists. Looks like your solution also create a new customer everytime... or maybe am i not seeing something ? ๐ฎ
Why don't you want to pre-fill? It makes their lives a lot easier and improves conversions drastically
yes sure !
however I am a bit worried about the following scenario :
Customer uses my website to fulfill his mission for a Company. As he needs to pay for my website services, I am scared that one day, one of them directly send the stripe checkout link to a company, and keeps paying for services using the same payment method saved by the company.
I don't know if I am too much worried !
Hello ๐ , stepping in here and catching up
hello there ๐
I am unsure how likely that scenario is but if you don't want their PaymentMethods to show up, I think you will have to detach them. https://stripe.com/docs/api/payment_methods/detach
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
okay thank you ๐ That was also a second idea I got, however, this might not be worth it if the customer also has an active subscription right ? as it would make a failed payment on renewal
Correct. If this is for subscriptions, you should definitely keep the payment method
I think I'll go for the normal process now, and if this scenario happens I will create a new customer everytime ๐
Thank you for the help @thick lagoon and @wide linden