Stix

[sand jetty]

Hi there, yes you can use customer email to associate a customer in your own record

If the payment link is for subscription, stripe will also create a customer object upon checkout session completion. You can use the customer.id which is an unique identifier

[opal flax]

Ok, thanks

[sand jetty]

https://stripe.com/docs/billing/subscriptions/webhooks

Theses are the events for subscriptions

[opal flax]

okay thank you, i was looking at payment intents! this makes more sense

[sand jetty]

If you want to avoid duplicate customer (email is not unique after all), you can consider using Checkout Sessions API directly. Here's how it works
2. Create a customer before hand, and save the customer.Id to your DB
3. Pass the customer ID to the CheckoutSession creation API
4. Upon Checkout completion, the subscription will be associated to the customer.

[opal flax]

Is the payment from a subscript a paymentintent.succeeded or an invoice.paid?

[sand jetty]

You'll get both payment_intent.succeeded and invoice.paid.

[opal flax]

ahhhh okay

[opal flax]

more worried about someone using email_one for my service and email_two for stripe - i suppose i make people enter their stripe email if they use different ones?

[sand jetty]

What do you mean by email for stripe ?

[opal flax]

whatever email exists in the customer.email if they checkout via a https://buy.stripe.com/...

can i make a customized link?

[sand jetty]

If that's the concern, you should really use CheckoutSession API so that you can prefill the email address field and make it non-editable.

https://stripe.com/docs/payments/checkout/custom-domains Yes you can use your own domain.

[opal flax]

okay thanks ill look into this