#franois_unexpected

1 messages · Page 1 of 1 (latest)

tame abyssBOT
#

👋 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/1310620755771396106

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

hollow orchidBOT
ionic elbow
#

Hi there 👋 we don't have prebuilt behavior to deduplicate Customer objects based on their provided email address.

The only prebuilt feature we have that does something similar, is the one described here where you can limit Customers to having only one Subscription:
https://docs.stripe.com/payments/checkout/limit-subscriptions

Can you share the ID of a Customer that was created even though you provided a Customer ID when creating a Checkout Session? So I can take a closer look at what happened there.

rapid ridge
#

Of course, give me a sec

ionic elbow
#

Removing that as this is a public forum and customer information should not be shared. Please share the ID of the Customer object, it should be an alphanumeric string starting with a cus_ prefix.

rapid ridge
#

On our end, the stripeId we use is cus_RFjqOz64SaNRZN

rapid ridge
ionic elbow
rapid ridge
#

This one is the one that we created before doing the session checkouts

#

We create the customer to get an id, then create the sessions

#

But it seems to be ignored, unless we did something wrong on our end

ionic elbow
rapid ridge
#

Sure

#

Here are the 3 customers created on stripe side:
cus_RFjqOz64SaNRZN
cus_RGBrr3C3qwHtGe
cus_RFmtpdOyU8YFn8

#

Hum... Wait a second

#

I'm might understand what happened

#

Apparently, it has not been created using the checkout api, but the paymentIntent

ionic elbow
#

I'm not sure what that means, since Payment Intents can't create Customers, but that doesn't seem to be the case for any of the Customer's you shared there.

  • cus_RFjqOz64SaNRZN - created via a request to create a Customer: https://dashboard.stripe.com/logs/req_GqY9UBU196435t
  • cus_RGBrr3C3qwHtGe - created by a Checkout Session that was created from a Payment Link
  • cus_RFmtpdOyU8YFn8 - created by a Checkout Session that was created from a Payment Link
Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

#

I'm double checking whether you are able to provide existing Customer IDs when using Payment Links.

#

I don't think that's possible for Payment Link integrations, typically you'd just create the Checkout Session for the Customer directly instead of providing them with a Payment Link.

If you want to keep using Payment Links, I'd suggest reviewing the setting in the first doc I linked to earlier, which does work for Payment Links as mentioned here:
https://docs.stripe.com/payment-links/customize#limit-subscriptions

Customize checkout for Payment Links

Collect additional information, taxes, or update your branding.

rapid ridge
#

cus_RGBrr3C3qwHtGe - created by a Checkout Session that was created from a Payment Link
cus_RFmtpdOyU8YFn8 - created by a Checkout Session that was created from a Payment Link
This is the issue

#

The payment link has been generated through the dashboard by someone new here. She probably didn't do it correctly. I'll investigate that part

#

Thanks a lot for the help. Really appreciated