#danielvvv
1 messages · Page 1 of 1 (latest)
Hello! No, you can't pre-fill those specific things (beyond email) when using Stripe Checkout.
What you could do instead is not collect those details yourself up front, but instead get them from the Customer object after the Checkout Session completes.
I don't know if that changed, when we created this way sometime ago, we did because we had to calculate taxes, and Stripe checkout would not allow Canadian taxes (we pass as an item to Stripe as a "hack), we were also using our own invoice and we have discount codes, it becomes quite complex to test these. There is a very specific reason we use our own invoices which I'm not going to get into details, but it's complex (we generate some authorization code for a hardware USB Dongle)
Another way I believe would be processing everything on our end (collecting the C/C with stripe elements), but are we liable for PCI compliance or Stripe takes the hit? for ex. if someone exploits a vulnerability , my company would have to pay 500K to visa (or another credit card company) and also being blocked from new transactions?
The company is very small, we have 2 devs in this project, no security team
we don't have bad code, but can't afford hiring a security team, and doing PCI compliance audits, we don't generate that much money
There are details about PCI compliance here: https://stripe.com/docs/security/guide#validating-pci-compliance
If you use Stripe Elements it would be the same Pre-filled SAQ A as Checkout.
Gotcha. Thank you @mighty prawn
I'm a little confused, support said I could use this: https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=checkout#prefill-customer-data
Yep, that's what you would use to pre-fill the email.
Sorry about that!
no worries
any chance implementing this as a feature? it is still quite risky and time consuming to redo this whole flow, we have cypress tests , unit tests
to pass billing address
doesn't need to be non editable, just prefill would be amazing
or ability to turn off the country and region/postal code (not sure if this is a requirement for security)