#harshittyagi_api
boreal ravineBOT
đź‘‹ 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/1450495299415048242
đź“ť Have more to share? Add more details, code, screenshots, videos, etc. below.
wooden zenith
hey there! this kind of functionality is not currently supported by payment intents directly. You would need to record line items in your own system associated with a payment or within payment intent metadata and then generate your own receipts with the format/content you want.
twin bear
Thank you for confirming.
I have one more question.
We have Link enabled so customers can save their card details for future payments. Since switching to PaymentSheet, Link usage by existing customers has dropped noticeably. We compared the flows between Checkout Sessions and PaymentSheet and found one key difference.
With PaymentSheet, even when an existing customer who already has Link enabled selects Pay with Link, they are redirected to checkout.link.com and asked to enter their email address again. We believe this extra step causes confusion and leads customers to abandon Link payments.
Since we already have the customer’s email in our app and it’s associated with their Stripe customer profile, is there a way to pass the Stripe customer ID or email to Link via PaymentSheet so existing customers aren’t prompted to re-enter their email?
@wooden zenith ^^
wooden zenith
Yep! You can prefill all the details you have as described here: https://docs.stripe.com/payments/link/mobile-payment-element-link#pass-email
twin bear
Okay, I'll try this.
I tried passing the customerId in PaymentSheet configuration, but that didn't work.