-
Notifications
You must be signed in to change notification settings - Fork 772
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
Wrong "StripeInvalidRequestError, Must provide source or customer" error? #307
Comments
The
|
Thanks for the clarification @remi-stripe! And apologies for confusion, this issue should actually be about the misleading error, not the actual call - it should probably say something along 'unexpected account_id field' rather than 'must provide source or customer'. |
@bebbi I can't find that specific request but my guess is that something is not sent properly in your code so we default to the common error indicating that to charge a customer you need to pass a token or a customer id. |
@bebbi There's an issue in the way requests get created if you don't separate out |
I'm getting this error when I just try to package it up for the very first time with grunt run/grunt package, per the README instructions. What am I missing? There shouldn't be any stripe requests triggered in setup, should there? |
@staringispolite This library is only for server-side use. On the client side, you'll want to use Checkout or Elements. |
StripeInvalidRequestError: Funds can't be sent to accounts located in IN because it's restricted outside of your platform's region |
@Hasnain-110 this is a github issue from 5 years and you provided zero information and it's irrelevant to the question at hand. Please work with our support team for help instead https://support.stripe.com/contact |
If I add
to my call to stripe.charges.create(), it consistently fails with the error in the title. If I leave these out, it consistently succeeds.
Reading the API docs I realize that coming from python I'm probably posting the "stripe_account" info in the wrong way, but the error still looks invalid.
Two examples of the full payload (some anon with dots by me):
Success:
Failure:
The text was updated successfully, but these errors were encountered: