#SaileshKumar - Customers
tall loom
- If you use our Stripe hosted Checkout page, then yes, we generate a Customer object each time. Otherwise, we likely do not create Customer objects for you.
- Nothing immediately comes to mind. It is up to you whether you want every user to have a Customer or if you only want to create them for your users once they get a coupon like this
ripe jolt
Got it - is there duplicate checking on Stripe's side in case we accidentally make an account for the same email address twice
tall loom
There is not, you can enforce it yourself by looking up existing accounts and filtering by email though https://stripe.com/docs/api/customers/list#list_customers-email
Or by storing email -> customer ID mappings on your side so that you don't have to query that API endpoint so much
tall loom
The Search API? Either should work
ripe jolt
When I filter by email, is that being applied after the limit or before?
For example if I have 100,000 accounts, and pass in the email, do I need to pass a limit as well to handle pagination, or will that filter happen on Stripe's backend
tall loom
The limit is on the number of objects after the filter is applied. So if you have 100,000 accounts and five of them have the same email, filtering based on email would give you a response with five Customer objects and there wouldn't be a next page.
Does that help? I can try rephrasing again, I get how the interaction between these two can be confusing