Answers.Body: <p>Gonna mark this as answered, for now, as I've logged it as an extension issue. </p>
  
  <p>The core of the problem, just FYI, seems to be that the auto-webhook process is failing (it appears to work, and a webhook does indeed appear on the Stripe dashboard, but the errors persist and I'm <em>hoping</em> that the real weirdness (the additional $200) is at least related to this.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-04-20T03:49:53.673Z
Answers.LastActivityDate: 2020-04-20T03:49:53.673Z
Answers.UserDisplayName: mc_burger
Body: <p>CiviCRM 5.24.4/Wordpress 5.4</p>
  
  <p>Getting hourly alerts from Cron, pertaining to some kind of API failure with Stripe. I suspect it has to do with the version-setting, but I'm unclear on how to address this.</p>
  
  <p>In fact, (as originally posted here), I'm getting really strange behavior from Stripe payment processing; in addition to returning an error 100% of the time ("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." -- there's another thread here about that already), the Stripe dashboard shows a consistent $200 addition to all payments (these are in steps of $25, $50, $100, &amp; $500 . . . and whatever I choose has exactly $200 extra tacked on).</p>
  
  <p>Seems a little nuts. Anyone have any idea?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-04-19T05:51:49.487Z
Comments.Text: Just restored a backup from a few days ago, pre-Stripe, and rebuilt everything, letting CiviCRM set the webhooks, etc. Same exact issue.
Comments.UserDisplayName: mc_burger
Tags: <civicontribute><stripe>
Title: (Stripe) CRM_Core_Payment_Manual::setAPIParams() Fatal Error
ThreadText: # (Stripe) CRM_Core_Payment_Manual::setAPIParams() Fatal Error
  
  (Asked by: username_0 on 2020-04-18)
  
  CiviCRM 5.24.4/Wordpress 5.4
  
  Getting hourly alerts from Cron, pertaining to some kind of API failure with Stripe. I suspect it has to do with the version-setting, but I'm unclear on how to address this.
  
  In fact, (as originally posted here), I'm getting really strange behavior from Stripe payment processing; in addition to returning an error 100% of the time ("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." -- there's another thread here about that already), the Stripe dashboard shows a consistent $200 addition to all payments (these are in steps of $25, $50, $100, & $500 . . . and whatever I choose has exactly $200 extra tacked on).
  
  Seems a little nuts. Anyone have any idea?
  
  **Tags:** civicontribute, stripe
  
  > **Comments:**
  > **username_0**: Just restored a backup from a few days ago, pre-Stripe, and rebuilt everything, letting CiviCRM set the webhooks, etc. Same exact issue.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2020-04-20. Score: 0 | Accepted answer
  
  Gonna mark this as answered, for now, as I've logged it as an extension issue.
  
  The core of the problem, just FYI, seems to be that the auto-webhook process is failing (it appears to work, and a webhook does indeed appear on the Stripe dashboard, but the errors persist and I'm *hoping* that the real weirdness (the additional $200) is at least related to this.
  
  
  ---
  
  