#Jens-Checkout
1 messages ยท Page 1 of 1 (latest)
yeah I don't have a great grasp of how this works in Checkout either unfortunately.
I think pre-filling of the payment method is tied to using our "Link" product โ https://stripe.com/docs/payments/checkout/customization#link-with-stripe so that has to be turned on, and only methods saved with it(when entering the details there should be a checkbox to "save payment information for future <your name> payments") get prefilled rather than any other methods on the Customer object. But I'm really not sure unfortunately.
Somehow even when I don't enable "Save payment information" when going through Checkout, it's still auto-filled next time I make a payment with the same customer ID. The customer ID seems to be the culprit here, existing customer ID's don't work with auto-fill, new ones do
I do have Link enabled, but for me it seems tied to whether the customer ID is new or not. The only things that differ between new accounts and old account is that old accounts have default_source and invoice_settings.default_payment_method set on the Customer object. Could this be disabling Stripe auto-fill?
unfortunately I know very little about this feature(I should, but I don't unfortunately) so I don't know how to answer this
going to tag my colleague @thorn niche who will be online in a little bit and they might be able to help!
Thank you ๐
๐ hello! just give me a few min to catch up on everything
@plain hatch what you've described doesn't sound expected to me, with the new/existing customer objects making a difference.
As @magic lynx mentioned, this is all driven by Link, which should work the same way for old and new customers
Can you explain whether Link is dependent on a customer ID?
I can't find much about how Link works. I think if I knew a bit more about how it works I could pinpoint the issue better. I understand my issue is vague.
As far as I know it doesnt, but your examples seem to conflict with that.
Can you reproduce this with a new "old" customer configured the same way?
I can pass in a "old" customer ID into stripe.checkout.sessions.create, and it will not prefill, and when I pass in a new ID it will prefill.
hey @plain hatch just bumping this to let you know we're poking at it to understand whats going on
Cool. Let me know if you need anything
With an "old" customer ID I mean one that has default_source and invoice_settings.default_payment_method set. New accounts don't because Checkout doesn't set those on customer objects even after a transaction.
I'm not sure what issues you're having with existing customers, but i was able to supply an old test customer (from Dec 2020) and go through Link set up and create antoher session to pay with the saved card
Is this a customer with credit card info saved through the Sources API? That's where i was having trouble.
I've recreated the test specifically with a customer with a pre-existing source set as the default_source and it works as expected so you'll need to provide more detail here or some screenshots showing what is/is not working for you
My colleague @rancid ridge can help inspect specific checkout session create requests for that customer if you can share that
Hello! What would really help us figure out what's going on is if you could provide request IDs for Checkout Session creation requests. Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
Will do this tomorrow
I can share a video of what's going on tomorrow
Sounds good, although you may want to write in to Support for longer running issues. This thread will be archived by tomorrow (although you're welcome to ask again in #dev-help so we can revive this thread or start a new one!).
You can write in to support here: https://support.stripe.com/contact