Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get customer by email / Check if email is already used #1156

Closed
aboulinguez opened this issue Apr 16, 2018 · 10 comments
Closed

Get customer by email / Check if email is already used #1156

aboulinguez opened this issue Apr 16, 2018 · 10 comments
Assignees

Comments

@aboulinguez
Copy link

Hi,

Is there a way to check if an email address is already used by an existing user, or maybe get a customer by just passing its email address ?

Thanks for your help.

Best regards,

Antoine Boulinguez.

@remi-stripe
Copy link
Contributor

@aboulinguez You can use the List Customers API and filter with the email parameter.

At the moment, the library does not support this filter but I'll add this now!

@aboulinguez
Copy link
Author

Hi @remi-stripe

Thanks for your answser. I was already using the "List" method and I will now wait for your update to use the email parameter.

Any idea of the delay before seeing the parameter to be available?

Thanks again!

Antoine.

@remi-stripe
Copy link
Contributor

@aboulinguez The code is ready and needs to be reviewed and deployed so I'd say a few days!

@aboulinguez
Copy link
Author

@remi-stripe It sounds great. Thanks!

@remi-stripe
Copy link
Contributor

@bronthulke
Copy link

bronthulke commented May 31, 2018

@remi-stripe I'm very thankful for your fix for this as I need the ability to do this now... however I can see that the fix went into 15.5.0, but I have 16.3.0 and the fix isn't in that version. Is there some way I can get the fix?

Thanks!

(sorry if it's considered bad practice to comment on a closed bug, but I thought this may be preferrable to opening another ticket on the same topic)

@remi-stripe
Copy link
Contributor

@bronthulke That is really strange, it's like that PR was never merged in the end. We'll investigate and likely release a new version tomorrow or early next week.

cc @ob-stripe this was merged in #1157 do you know what's going on and why it never made it to master after all? Master has no email field: https://github.com/stripe/stripe-dotnet/blob/master/src/Stripe.net/Services/Customers/StripeCustomerListOptions.cs

@remi-stripe remi-stripe reopened this May 31, 2018
@ob-stripe
Copy link
Contributor

@remi-stripe The PR's target branch was remi-add-sepa-ideal instead of master. Should be easy enough to fix.

@ob-stripe
Copy link
Contributor

Released in 16.4.0, which should appear on NuGet soon.

@bronthulke
Copy link

Thanks so much for resolving this so quickly, guys!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants