Answers.Body: <p>Problem turned out to be js conflicts with Themefy popup messing up the js files in civicrm. </p>
  
  <p>Disabling the plugin from /wp-admin/plugins.php?plugin_status=all&amp;paged=1&amp;s removes this problem and contributions go through to Stripe as intended</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-04-27T08:23:48.650Z
Answers.LastActivityDate: 2020-04-27T08:23:48.650Z
Answers.UserDisplayName: petednz - fuzion
Body: <p>CiviCRM 5.24.4/WP 5.4</p>
  
  <p>Some freakish behavior going on with CiviContribute and Stripe processing. Based on Stripe logs, it <em>looks</em> like its originating with CiviContribute. Everything worked for at least one test transaction before I upgraded to 5.24.4, but, despite several restores and reconfigurations, I haven't been able to charge the right amount.</p>
  
  <p>Here's the deal: if a user opts to make a $25 contribution, CiviContribute sends the charge to Stripe as $225. If they opt for $100, the charge is $300. Exactly $200 every time. Pretty weird.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-04-21T18:44:54.313Z
Comments.Text: are you using any extensions that affect contributions?
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-04-22T03:11:52.400Z
Comments.Text: Not that I'm aware of (TinyMCE, Stripe, Firewall, MJWShared, FlexMailer, and Mosaico).
Comments.UserDisplayName: mc_burger
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-04-22T04:10:58.943Z
Comments.Text: and is this pure civi, not eg a webform_civicrm (Drupal) or Caldera_civicrm (WP)
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-04-22T04:36:04.647Z
Comments.Text: Straight up civi, created and controlled through CiviContribute.
Comments.UserDisplayName: mc_burger
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-04-22T08:06:41.683Z
Comments.Text: really no idea what to suggest without doing some audit of the process. sorry
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-04-22T09:47:47.577Z
Comments.Text: appreciate it anyway!
  
  really drilling down now; if I manage to learn anything, I'll share it here.
Comments.UserDisplayName: mc_burger
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-04-23T08:22:30.053Z
Comments.Text: What amount is recorded for the Contribution?  What Line Items does it have? What happens if you use a different processor other than Stripe?  Is this via a Contribution Page?  If so, does it happen with all Contribution Pages?
Comments.UserDisplayName: Aidan
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-04-23T15:32:02.377Z
Comments.Text: We just have the one contribution page--and the one payment processor--at the moment; just getting Stripe going was a bit of a challenge. I can confirm that it did work correctly for one test charge.
  
  For the record of the test contribution, everything is correct. I'm still looking at Stripe logs and trying to keep a thread alive in reporting on extension bugs. I'll update this one if I learn anything there.
Comments.UserDisplayName: mc_burger
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-04-24T03:44:39.607Z
Comments.Text: Chatted with Stripe for a while about this, and they pointed to the error message I've been seeing (and reported in another thread here): "Credit Card This PaymentIntent's amount could not be updated because it has a status of requires_capture. You may only update the amount of a PaymentIntent with one of the following statuses: requires_payment_method, requires_confirmation, requires_action."
  
  Specifically, they said that the error is coming from 'amount_capture' status. And then I lost the connection with them. No idea what would have caused a $200 bump.
Comments.UserDisplayName: mc_burger
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-04-24T10:48:18.557Z
Comments.Text: That Stripe message indicates problems but it seems unlikely that is the cause of your extra $200.  Try setting up another Contribution Page & also test with the dummy processor.  Are you on the latest version of the Stripe extension?  What do you get if you enable debugging: https://docs.civicrm.org/stripe/en/latest/#troubleshooting
Comments.UserDisplayName: Aidan
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-04-24T13:06:57.180Z
Comments.Text: I had no idea there was a dummy processor option! I'll engage that and report back.
  
  With debugging enabled, the most interesting thing I can confirm is "2020-04-24T13:01:45.083Z civicrm_stripe.js: getTotalAmount: 250" (this is with $50 selected).
Comments.UserDisplayName: mc_burger
Tags: <civicontribute><stripe>
Title: CiviContribute adding $200 even to every transaction
ThreadText: # CiviContribute adding $200 even to every transaction
  
  (Asked by: username_0 on 2020-04-21)
  
  CiviCRM 5.24.4/WP 5.4
  
  Some freakish behavior going on with CiviContribute and Stripe processing. Based on Stripe logs, it *looks* like its originating with CiviContribute. Everything worked for at least one test transaction before I upgraded to 5.24.4, but, despite several restores and reconfigurations, I haven't been able to charge the right amount.
  
  Here's the deal: if a user opts to make a $25 contribution, CiviContribute sends the charge to Stripe as $225. If they opt for $100, the charge is $300. Exactly $200 every time. Pretty weird.
  
  **Tags:** civicontribute, stripe
  
  > **Comments:**
  > **username_1**: are you using any extensions that affect contributions?  
  > **username_0**: Not that I'm aware of (TinyMCE, Stripe, Firewall, MJWShared, FlexMailer, and Mosaico).  
  > **username_1**: and is this pure civi, not eg a webform_civicrm (Drupal) or Caldera_civicrm (WP)  
  > **username_0**: Straight up civi, created and controlled through CiviContribute.  
  > **username_1**: really no idea what to suggest without doing some audit of the process. sorry  
  > **username_0**: appreciate it anyway!  really drilling down now; if I manage to learn anything, I'll share it here.  
  > **username_2**: What amount is recorded for the Contribution?  What Line Items does it have? What happens if you use a different processor other than Stripe?  Is this via a Contribution Page?  If so, does it happen with all Contribution Pages?  
  > **username_0**: We just have the one contribution page--and the one payment processor--at the moment; just getting Stripe going was a bit of a challenge. I can confirm that it did work correctly for one test charge.  For the record of the test contribution, everything is correct. I'm still looking at Stripe logs and trying to keep a thread alive in reporting on extension bugs. I'll update this one if I learn anything there.  
  > **username_0**: Chatted with Stripe for a while about this, and they pointed to the error message I've been seeing (and reported in another thread here): "Credit Card This PaymentIntent's amount could not be updated because it has a status of requires_capture. You may only update the amount of a PaymentIntent with one of the following statuses: requires_payment_method, requires_confirmation, requires_action."  Specifically, they said that the error is coming from 'amount_capture' status. And then I lost the connection with them. No idea what would have caused a $200 bump.  
  > **username_2**: That Stripe message indicates problems but it seems unlikely that is the cause of your extra $200.  Try setting up another Contribution Page & also test with the dummy processor.  Are you on the latest version of the Stripe extension?  What do you get if you enable debugging: https://docs.civicrm.org/stripe/en/latest/#troubleshooting  
  > **username_0**: I had no idea there was a dummy processor option! I'll engage that and report back.  With debugging enabled, the most interesting thing I can confirm is "2020-04-24T13:01:45.083Z civicrm_stripe.js: getTotalAmount: 250" (this is with $50 selected).  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-04-27. Score: 1 | Accepted answer
  
  Problem turned out to be js conflicts with Themefy popup messing up the js files in civicrm.
  
  Disabling the plugin from /wp-admin/plugins.php?plugin\_status=all&paged=1&s removes this problem and contributions go through to Stripe as intended
  
  
  ---
  
  