Answers.Body: <p>I have this problem also.
  It's a known issue with version 1.9.1 <a href="https://github.com/drastik/com.drastikbydesign.stripe/issues/76" rel="nofollow">You can view the Github thread here.</a>
  The developer says his latest commit may have <a href="https://github.com/drastik/com.drastikbydesign.stripe/pull/105" rel="nofollow"> fixed the issue.</a></p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-19T06:25:15.363Z
Answers.Text: Hi John, Thanks for the reply....  I  already checked the link you mentioned in your answer. But the patch is not working mentioned in  https://github.com/drastik/com.drastikbydesign.stripe/pull/105.
  
  I have done some debugging. While submitting the form the $params['stripe_token'] is getting empty.
Answers.UserDisplayName: 1990rk4
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-16T15:22:52.847Z
Answers.LastActivityDate: 2015-10-16T15:22:52.847Z
Answers.UserDisplayName: John F
Answers.Body: <p>This should have been solved back in November 2015 (worked on CiviCRM 4.6.9).</p>
  
  <p>I am trying to bring order to the issue reports scattered across here &amp; GitHub and get appropriate issues closed.</p>
  
  <p>(Note: It was not the PR on 105 that fixed, but a different commit afterwards).  Use the 4.6-dev branch from GitHub.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-01-18T19:02:02.010Z
Answers.LastActivityDate: 2016-01-18T19:02:02.010Z
Answers.UserDisplayName: drastik
Body: <p>I have following configuration: CiviCRM version - 4.6.2 Stripe version: 1.9.1</p>
  
  <p>I have configured stripe on site and using it on contribution page and trying to use with "PayPal payment processor" and "Pay-later option".</p>
  
  <p>After submitting the contribution I have getting the error as follows:</p>
  
  <p>"Error: Stripe.js token was not passed! Report this message to the site administrator"</p>
  
  <p>Is above error getting due to compatibility issue? Because on <a href="https://civicrm.org/extensions/stripe-payment-processor/" rel="nofollow">https://civicrm.org/extensions/stripe-payment-processor/</a> in this page compatibility for stripe with CiviCRM version for 4.4 and 4.5 is mentioned</p>
  
  <p>Please guide!!!</p>
  
Tags: <payment-processor><stripe>
Title: Error: Stripe.js token was not passed! Report this message to the site administrator" for Stripe extension
ThreadText: # Error: Stripe.js token was not passed! Report this message to the site administrator" for Stripe extension
  
  (Asked by: username_0 on 2015-10-16)
  
  I have following configuration: CiviCRM version - 4.6.2 Stripe version: 1.9.1
  
  I have configured stripe on site and using it on contribution page and trying to use with "PayPal payment processor" and "Pay-later option".
  
  After submitting the contribution I have getting the error as follows:
  
  "Error: Stripe.js token was not passed! Report this message to the site administrator"
  
  Is above error getting due to compatibility issue? Because on <https://civicrm.org/extensions/stripe-payment-processor/> in this page compatibility for stripe with CiviCRM version for 4.4 and 4.5 is mentioned
  
  Please guide!!!
  
  **Tags:** payment-processor, stripe
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2015-10-16. Score: 1
  
  I have this problem also.
  It's a known issue with version 1.9.1 [You can view the Github thread here.](https://github.com/username_2/com.drastikbydesign.stripe/issues/76)
  The developer says his latest commit may have  [fixed the issue.](https://github.com/username_2/com.drastikbydesign.stripe/pull/105)
  
  > **Comments:**
  > **username_0**: Hi username_1, Thanks for the reply....  I  already checked the link you mentioned in your answer. But the patch is not working mentioned in  https://github.com/username_2/com.drastikbydesign.stripe/pull/105.  I have done some debugging. While submitting the form the $params['stripe_token'] is getting empty.  
  
  ---
  
  ### Answer by username_2 on 2016-01-18. Score: 0
  
  This should have been solved back in November 2015 (worked on CiviCRM 4.6.9).
  
  I am trying to bring order to the issue reports scattered across here & GitHub and get appropriate issues closed.
  
  (Note: It was not the PR on 105 that fixed, but a different commit afterwards). Use the 4.6-dev branch from GitHub.
  
  
  ---
  
  