Body: <p>We have authorize.net running for over 2 years, Added Automated Recurring Billing. It worked for a test, when we tried to use it for a real event it failed. Civicrm shows it working correctly but Authorize.net sees the initial transaction but does not see the ARB transaction. </p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-09-27T22:27:23.297Z
Comments.Text: While you seem to be asking about a chance in your systems (adding ARB), the timing of your question makes me wonder if you've been affected by [SSL changes on api.authorize.net](http://app.payment.authorize.net/e/es.aspx?s=986383348&e=949852&elq=6d50ae28150246fc9892054a5c7a7981). I would recommend reviewing that technical notice before debugging further.
Comments.UserDisplayName: Chris Burgess
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-09-28T12:56:36.107Z
Comments.Text: In addition to Chris' comments, I assume you checked to ensure the Silent Post URL is set up correctly in your Authorize settings?  Do you see anything in the Civi log indicating that the Authorize script at least tried to match something up?
Comments.UserDisplayName: Lesley Carter - BackOffice
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-09-28T17:10:56.210Z
Comments.Text: We setup silent post, but it is only involved after the ARB  confirms a transaction. is recieved by Authorize.net.  The SSL changes should have impacted all users. They receive out normal request. The SSL is provided by Civicrm, I don't know how to even check if it is correct.
Comments.UserDisplayName: user469
Tags: <pledges><authorize.net>
Title: Authorize.net and Automatic Recurring Billing (ARB)
ThreadText: # Authorize.net and Automatic Recurring Billing (ARB)
  
  (Asked by: username_0 on 2015-09-27)
  
  We have authorize.net running for over 2 years, Added Automated Recurring Billing. It worked for a test, when we tried to use it for a real event it failed. Civicrm shows it working correctly but Authorize.net sees the initial transaction but does not see the ARB transaction.
  
  **Tags:** pledges, authorize.net
  
  > **Comments:**
  > **username_1**: While you seem to be asking about a chance in your systems (adding ARB), the timing of your question makes me wonder if you've been affected by [SSL changes on api.authorize.net](http://app.payment.authorize.net/e/es.aspx?s=986383348&e=949852&elq=6d50ae28150246fc9892054a5c7a7981). I would recommend reviewing that technical notice before debugging further.  
  > **username_2**: In addition to Chris' comments, I assume you checked to ensure the Silent Post URL is set up correctly in your Authorize settings?  Do you see anything in the Civi log indicating that the Authorize script at least tried to match something up?  
  > **username_0**: We setup silent post, but it is only involved after the ARB  confirms a transaction. is recieved by Authorize.net.  The SSL changes should have impacted all users. They receive out normal request. The SSL is provided by Civicrm, I don't know how to even check if it is correct.  
  
  ---
  
  ## 0 answers
  
  