#Nitroxis
timid mountain
fallow wren
Hi! Let me help you with this.
We have Customer Billing Portal: https://stripe.com/docs/no-code/customer-portal
And invoices can be sent by email.
fallow wren
Happy to help. Let me know if you have any other questions.
fast citrus
Is it possible to restrict a payment link to a specific customer?
I just ran in to an issue, where I created two customer's with the same e-mail in stripe.
Reproduction steps:
- Create Customer A in Stripe manually using e-mail a@example.com
- Create payment link
- Visit payment link
- Pay with a@example.com
Customer database now has two different customers with the same e-mail.
ruby haven
👋 stepping in here as vanya needed to step away
We don't de-duplicate customers for you and Payment Links are meant for a one-to-many scenario. If you want to avoid this potential duplication of Customers then you want to use Checkout Sessions and not Payment Links so you can pass the Customer ID to the Checkout Session on creation
fast citrus
Alright, so if Customer A visits a payment link, and pays using their e-mail address, and I send them another payment link a few days after, and they pay with the same e-mail address again - they will be two different customers in the database?
ruby haven
Yes that's correct.
fast citrus
Okay, and if they then login using the Customer Billing Portal, will they see both their payments?
ruby haven
No don't believe they will
I think in this case we show the most recent active Subscription if you are using the no-code portal.
If you create the Portal Session yourself then you can dictate which Customer the login will provide
fast citrus
Okay, that seems kind of odd. Yes it does indeed only show the latest subscription with that e-mail.
Because then the first customer would never be able to log in through the customer portal and access their e-mail
ruby haven
Yeah this is a known gap right now with no-code Customer Portal + Payment Links. We are working on de-duplicating here for Customer creation with Payment Links so this isn't an issue going forward.
However I don't have a timeline for when that will be released
fast citrus
Okay. Thanks for clarifying everything to me. This has been really helpful. Seems like we can get a long way with just using the Payment Links + Customer Portal, and if you have a fix in the pipeline I think we can still use this solution, as it's only going to be used by a limited number of people right now
ruby haven
Glad to hear it!