Body: <p>CiviCRM 5.70.2 on WordPress (6.5.2).</p>
  <p>Using the Stripe payment processor for contributions. The recurring payment schedule seems a bit … off. My specific was was supposed to be at 1200 today 4/29/2024. Recurring payments started 4/29/2023 0847. Stripe tells me the payment processed at 0947 today 4/29/2024 (and I got charged, can see the transaction on my credit card). But CiviCRM, over an hour later so far, has not recorded the payment at all.</p>
  <p>Is this expected behavior? Will I have to disable recurring contributions again and manually record this payment to get my account in working order?</p>
  <p>Thanks for any insight here.</p>
  <p>Michael</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-04-29T17:21:45.227Z
Comments.Text: Is it just the one contribution or all of them? Do you have webhooks configured (see administer - administration console - system status)? https://docs.civicrm.org/stripe/en/latest/webhook/
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-04-29T18:21:33.930Z
Comments.Text: Non-recurring contributions work fine. Stripe shows no errors and shows the web hooks as active. Curiously, the Administer->CiviContribute->Payment processor web hooks currently shows nothing. I seem to recall an error message before when the web hooks weren’t there a year or so ago, offering to create them. No indication like that now. We have very few recurring donations, and that functionality was enabled barely a year ago (and I was one of the test accounts) because it used to just throw errors on the contribution attempt.
Comments.UserDisplayName: Michael Matthews
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-04-29T19:00:50.900Z
Comments.Text: If you look in the stripe portal, under developer (it's a bit of a disguised "button" at the top of the dashboard), there's a tab for webhooks. If you click on the webhook it will give you some logs. Note especially in the right-hand sidebar what it says was the return message was.
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-04-29T19:10:06.617Z
Comments.Text: Yeah, Stripe says everything worked. The specific requests there all got a 200 response according to Stripe. I can even see the requests in the web server logs and confirm the response. CiviCRM just didn’t process anything. Guess I’ll have to manually record the response and hope that renews my membership, and maybe do an upgrade this weekend to the latest ‘n greatest.
Comments.UserDisplayName: Michael Matthews
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-04-29T20:14:05.340Z
Comments.Text: And in the right sidebar for the webhook response at stripe, does it say anything like "this is not for this processor"? Civi will just silently drop those if for some reason it thinks it's not for it (like a mismatch between test and live).
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2024-04-29T20:43:06.683Z
Comments.Text: Wouldn’t that be indicated by a request not working? Every single request is successful with HTTP 200 response, no response body, no errors at all. One thing that’s weird is I’m seeing some transactions (related to me removing test accounts) going to the WooCommerce Stripe endpoint URL, so clearly something is confused here. Not seeing the web hooks showing up in CiviCRM’s UI concerns me and is probably why nothing is getting recorded even though requests are not generating errors.
Comments.UserDisplayName: Michael Matthews
Tags: <stripe><recurring>
Title: Unexpected behavior for Stripe recurring contribution payments
ThreadText: # Unexpected behavior for Stripe recurring contribution payments
  
  (Asked by: username_0 on 2024-04-29)
  
  CiviCRM 5.70.2 on WordPress (6.5.2).
  
  Using the Stripe payment processor for contributions. The recurring payment schedule seems a bit … off. My specific was was supposed to be at 1200 today 4/29/2024. Recurring payments started 4/29/2023 0847. Stripe tells me the payment processed at 0947 today 4/29/2024 (and I got charged, can see the transaction on my credit card). But CiviCRM, over an hour later so far, has not recorded the payment at all.
  
  Is this expected behavior? Will I have to disable recurring contributions again and manually record this payment to get my account in working order?
  
  Thanks for any insight here.
  
  username_0
  
  **Tags:** stripe, recurring
  
  > **Comments:**
  > **username_1**: Is it just the one contribution or all of them? Do you have webhooks configured (see administer - administration console - system status)? https://docs.civicrm.org/stripe/en/latest/webhook/  
  > **username_0**: Non-recurring contributions work fine. Stripe shows no errors and shows the web hooks as active. Curiously, the Administer->CiviContribute->Payment processor web hooks currently shows nothing. I seem to recall an error message before when the web hooks weren’t there a year or so ago, offering to create them. No indication like that now. We have very few recurring donations, and that functionality was enabled barely a year ago (and I was one of the test accounts) because it used to just throw errors on the contribution attempt.  
  > **username_1**: If you look in the stripe portal, under developer (it's a bit of a disguised "button" at the top of the dashboard), there's a tab for webhooks. If you click on the webhook it will give you some logs. Note especially in the right-hand sidebar what it says was the return message was.  
  > **username_0**: Yeah, Stripe says everything worked. The specific requests there all got a 200 response according to Stripe. I can even see the requests in the web server logs and confirm the response. CiviCRM just didn’t process anything. Guess I’ll have to manually record the response and hope that renews my membership, and maybe do an upgrade this weekend to the latest ‘n greatest.  
  > **username_1**: And in the right sidebar for the webhook response at stripe, does it say anything like "this is not for this processor"? Civi will just silently drop those if for some reason it thinks it's not for it (like a mismatch between test and live).  
  > **username_0**: Wouldn’t that be indicated by a request not working? Every single request is successful with HTTP 200 response, no response body, no errors at all. One thing that’s weird is I’m seeing some transactions (related to me removing test accounts) going to the WooCommerce Stripe endpoint URL, so clearly something is confused here. Not seeing the web hooks showing up in CiviCRM’s UI concerns me and is probably why nothing is getting recorded even though requests are not generating errors.  
  
  ---
  
  ## 0 answers
  
  