Answers.Body: <p>So this actually didn't have anything to do with Stripe, CiviContribute, or WordPress. Apparently there's a bug in the Form Protection (reCaptcha) extension that was causing these errors. When I disabled the Form Protection extension, things worked as expected. See this thread for more details: <a href="https://chat.civicrm.org/civicrm/pl/5nh3ffsnopfcd8xxdhwsk36z4y" rel="nofollow noreferrer">https://chat.civicrm.org/civicrm/pl/5nh3ffsnopfcd8xxdhwsk36z4y</a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-09-01T21:34:30.897Z
Answers.Text: Patch available via https://github.com/civicrm/civicrm-core/pull/31020 and https://lab.civicrm.org/dev/core/-/issues/5421
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-08-31T17:38:52.797Z
Answers.LastActivityDate: 2024-08-31T17:38:52.797Z
Answers.UserDisplayName: Carl Sigmond
Body: <p>We had Stripe working, and then we did stuff in WordPress (moving a staging site to production), and now we're getting Stripe errors that we can't make sense of.</p>
  <p>When we try to submit a credit card on a contribution page, we get a Stripe error like:
  &quot;Sorry an error occurred and your request was not completed. (Error ID: Taxn-0HpC-Ruwx)&quot;</p>
  <p>When we use the Pay Later option on an event registration page, we get: &quot;Sorry, due to an error, we are unable to fulfill your request at the moment. You may want to contact your administrator or service provider with more details about what action you were performing when this occurred.
  No secret provided&quot;</p>
  <p>I've Googled &quot;No secret provided&quot; and I don't see anything related.</p>
  <p>We also updated the Stripe extension. Not sure if that contributed to this or not.</p>
  <p>WordPress 6.5.5</p>
  <p>CiviCRM 5.76.2</p>
  <p>Stripe Extension 6.11.2</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-08-30T14:21:53.180Z
Comments.Text: Update: even when I disable all payment processors and uninstall the Stripe extension, when I try the online registration for a paid event (using the Pay Later option), I still get the "No secret provided" error.
Comments.UserDisplayName: Carl Sigmond
Tags: <civicontribute><stripe>
Title: Stripe Error (I think): "No secret provided"
ThreadText: # Stripe Error (I think): "No secret provided"
  
  (Asked by: username_0 on 2024-08-29)
  
  We had Stripe working, and then we did stuff in WordPress (moving a staging site to production), and now we're getting Stripe errors that we can't make sense of.
  
  When we try to submit a credit card on a contribution page, we get a Stripe error like:
  "Sorry an error occurred and your request was not completed. (Error ID: Taxn-0HpC-Ruwx)"
  
  When we use the Pay Later option on an event registration page, we get: "Sorry, due to an error, we are unable to fulfill your request at the moment. You may want to contact your administrator or service provider with more details about what action you were performing when this occurred.
  No secret provided"
  
  I've Googled "No secret provided" and I don't see anything related.
  
  We also updated the Stripe extension. Not sure if that contributed to this or not.
  
  WordPress 6.5.5
  
  CiviCRM 5.76.2
  
  Stripe Extension 6.11.2
  
  **Tags:** civicontribute, stripe
  
  > **Comments:**
  > **username_0**: Update: even when I disable all payment processors and uninstall the Stripe extension, when I try the online registration for a paid event (using the Pay Later option), I still get the "No secret provided" error.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2024-08-31. Score: 2
  
  So this actually didn't have anything to do with Stripe, CiviContribute, or WordPress. Apparently there's a bug in the Form Protection (reCaptcha) extension that was causing these errors. When I disabled the Form Protection extension, things worked as expected. See this thread for more details: <https://chat.civicrm.org/civicrm/pl/5nh3ffsnopfcd8xxdhwsk36z4y>
  
  > **Comments:**
  > **username_1**: Patch available via https://github.com/civicrm/civicrm-core/pull/31020 and https://lab.civicrm.org/dev/core/-/issues/5421  
  
  ---
  
  