Answers.Body: <p>The culprit was the iThemes Security plugin. Here are the settings you should <strong>disable</strong> to avoid getting a 403 forbidden error that prevented the IPN from registering.</p>
  
  <p>Under Banned Users</p>
  
  <ul>
  <li>Hack Repair Default Blacklist</li>
  </ul>
  
  <p>Under System Tweaks</p>
  
  <ul>
  <li>Suspicious Query Strings</li>
  <li>Long URLs</li>
  </ul>
  
  <p>I also <strong>enabled</strong> Enable XML-RPC under Wordpress Tweaks. I had encountered failed IPN's from PayPal before so I assume this would be wise to enable as well.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2018-03-19T17:13:29.470Z
Answers.LastActivityDate: 2018-03-19T18:40:28.117Z
Answers.LastEditDate: 2018-03-19T18:40:28.117Z
Answers.UserDisplayName: Andy Burns
Body: <p>We are unable to get authorize.net talking back to CiviCRM in regards to recurring payments.</p>
  
  <p>In talking with authorize.net folks and they pointed out that query strings are not allowed to be used in the Silent Post URL: <a href="https://support.authorize.net/s/article/Why-Are-My-SIM-Relay-Response-Transactions-Timing-out-After-Submitting-the-Request" rel="nofollow noreferrer">https://support.authorize.net/s/article/Why-Are-My-SIM-Relay-Response-Transactions-Timing-out-After-Submitting-the-Request</a></p>
  
  <p><a href="https://i.sstatic.net/BjRL6.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/BjRL6.png" alt="query string dissallowed"></a></p>
  
  <p>However, CiviCRM docs say for Wordpress you need to use a query string? <a href="https://docs.civicrm.org/sysadmin/en/latest/setup/payment-processors/authorize-net/" rel="nofollow noreferrer">https://docs.civicrm.org/sysadmin/en/latest/setup/payment-processors/authorize-net/</a>
  <a href="https://i.sstatic.net/YGzVj.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/YGzVj.png" alt="WP silent post URL"></a>
  We've checked the logs and see that authorize.net is not communicating back to CiviCRM. The transaction ID's for recurring payments are missing.</p>
  
  <p>So who is right here and are people successfully using WP and Civi with authorize.net?</p>
  
  <p>We have checked that are servers support connections via TLS 1.2. </p>
  
  <p>On WP 4.9.4 and Civi 4.7.30</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-03-13T16:24:39.447Z
Comments.Text: The documentation says http for the silent post url. Would that make a difference? I would expect that that should be a secure URL instead ...
Comments.UserDisplayName: Andy Burns
Tags: <recurring-contributions><authorize.net>
Title: Authorize.net does not allow query strings for silent post URL?
ThreadText: # Authorize.net does not allow query strings for silent post URL?
  
  (Asked by: username_0 on 2018-03-13)
  
  We are unable to get authorize.net talking back to CiviCRM in regards to recurring payments.
  
  In talking with authorize.net folks and they pointed out that query strings are not allowed to be used in the Silent Post URL: <https://support.authorize.net/s/article/Why-Are-My-SIM-Relay-Response-Transactions-Timing-out-After-Submitting-the-Request>
  
  [![query string dissallowed](https://i.sstatic.net/BjRL6.png)](https://i.sstatic.net/BjRL6.png)
  
  However, CiviCRM docs say for Wordpress you need to use a query string? <https://docs.civicrm.org/sysadmin/en/latest/setup/payment-processors/authorize-net/>
  [![WP silent post URL](https://i.sstatic.net/YGzVj.png)](https://i.sstatic.net/YGzVj.png)
  We've checked the logs and see that authorize.net is not communicating back to CiviCRM. The transaction ID's for recurring payments are missing.
  
  So who is right here and are people successfully using WP and Civi with authorize.net?
  
  We have checked that are servers support connections via TLS 1.2.
  
  On WP 4.9.4 and Civi 4.7.30
  
  **Tags:** recurring-contributions, authorize.net
  
  > **Comments:**
  > **username_0**: The documentation says http for the silent post url. Would that make a difference? I would expect that that should be a secure URL instead ...  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2018-03-19. Score: 2 | Accepted answer
  
  The culprit was the iThemes Security plugin. Here are the settings you should **disable** to avoid getting a 403 forbidden error that prevented the IPN from registering.
  
  Under Banned Users
  
  * Hack Repair Default Blacklist
  
  Under System Tweaks
  
  * Suspicious Query Strings
  * Long URLs
  
  I also **enabled** Enable XML-RPC under Wordpress Tweaks. I had encountered failed IPN's from PayPal before so I assume this would be wise to enable as well.
  
  
  ---
  
  