#bungee_docs
half narwhalBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1253726542773751849
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
zinc runeBOT
manic jay
Hi 👋 yes, that is expected behavior. Payment Links tend to create Customers because they aren't provided with the ID of an existing Customer object to use, that's something better handled by Checkout Sessions. I'm double checking whether we have a way to pass the ID of an existing Customer when adding the Payment Link to your page.
Are you using the Payment Link's URL directly, or are you embedding that on your page as a Buy Button?
pine rune
the URL directly
manic jay
Hm, I don't think you can then.
With the Buy Button approach, you can create a Customer Session and pass that in when adding the Buy Button script to your page:
https://docs.stripe.com/payment-links/buy-button#pass-an-existing-customer
But it doesn't look like you can add that as a query param on the URL if you're using the URL directly:
https://docs.stripe.com/payment-links/customize#customize-checkout-with-url-parameters
pine rune
Oh ok, thank you Toby!