Answers.Body: <p>You want to use the <a href="https://lab.civicrm.org/extensions/authnet" rel="nofollow noreferrer">authnet extension</a> instead which uses webhooks and not a silent post URL.</p>
  <p>Here is the <a href="https://docs.civicrm.org/authnetecheck/en/latest/setup/" rel="nofollow noreferrer">setup</a> guide and if you are <a href="https://docs.civicrm.org/authnetecheck/en/latest/migration/" rel="nofollow noreferrer">migrating from legacy core authnet</a>. The webhooks are created automatically if you check the system status page in Civi to generate them. FYI, the webhooks used are:
  <a href="https://i.sstatic.net/kjSSZ.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/kjSSZ.png" alt="enter image description here" /></a></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-04-30T19:45:23.293Z
Answers.Text: This is a correct answer, and one I would endorse - but to be clear, the "Silent Post URL" has been deprecated for many years and I don't think it will be disabled in the next several years.  So it's good to use the authnet extension, but Silent Post URL is still a workable solution.
Answers.UserDisplayName: Jon G - Megaphone Tech
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-05-04T18:36:14.943Z
Answers.Text: Agreed. I am wondering if it would work out okay to have the core authnet processor (using silent post URL and needed for existing ARB's) and the https://lab.civicrm.org/extensions/authnet (using webhook) in use at the same time? I *think* so.
Answers.UserDisplayName: Andy Burns
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-04-29T17:41:18.223Z
Answers.LastActivityDate: 2022-04-29T17:49:04.263Z
Answers.LastEditDate: 2022-04-29T17:49:04.263Z
Answers.UserDisplayName: Andy Burns
Body: <p>I'm nervous that Civi's documentation for Authorize.net is outdated. There appear to be cases where recurring ARB payments are processed by Authorize but the related Civi contributions &amp; memberships are not updated. <a href="https://docs.civicrm.org/sysadmin/en/latest/setup/payment-processors/authorize-net/#automated-recurring-billing" rel="nofollow noreferrer">This doc</a> seems to require the use of a &quot;Silent Post&quot;, but tech support at Authorize said Silent Post is deprecated. <a href="https://docs.hyros.com/authorize-net-integration/" rel="nofollow noreferrer">Other systems</a> that integrate with Authorize use webhooks instead of the Silent Post. Should I be using webhooks instead of the Silent Post? If so, should I use the same format, like this for Wordpress:</p>
  <pre><code>https://example.com/BASEPAGE/?civiwp=CiviCRM&amp;q=civicrm/payment/ipn/NN
  </code></pre>
  <p>If so continued... which events should be listened to?</p>
  <ul>
  <li>All Events</li>
  <li>Customer Events</li>
  <li>Subscription Events</li>
  <li>Payment Events</li>
  </ul>
  
Tags: <wordpress><payment-processor><authorize.net><integration>
Title: Does Authorize.net/CiviCRM integration require the use of "Webhooks" instead of "Silent Post"?
ThreadText: # Does Authorize.net/CiviCRM integration require the use of "Webhooks" instead of "Silent Post"?
  
  (Asked by: username_0 on 2022-04-29)
  
  I'm nervous that Civi's documentation for Authorize.net is outdated. There appear to be cases where recurring ARB payments are processed by Authorize but the related Civi contributions & memberships are not updated. This doc seems to require the use of a "Silent Post", but tech support at Authorize said Silent Post is deprecated. Other systems that integrate with Authorize use webhooks instead of the Silent Post. Should I be using webhooks instead of the Silent Post? If so, should I use the same format, like this for Wordpress:
  https://example.com/BASEPAGE/?civiwp=CiviCRM&q=civicrm/payment/ipn/NN
  
  If so continued... which events should be listened to?
  
  All Events
  Customer Events
  Subscription Events
  Payment Events
  
  **Tags:** wordpress, payment-processor, authorize.net, integration
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2022-04-29. Score: 3
  
  You want to use the [authnet extension](https://lab.civicrm.org/extensions/authnet) instead which uses webhooks and not a silent post URL.
  
  Here is the [setup](https://docs.civicrm.org/authnetecheck/en/latest/setup/) guide and if you are [migrating from legacy core authnet](https://docs.civicrm.org/authnetecheck/en/latest/migration/). The webhooks are created automatically if you check the system status page in Civi to generate them. FYI, the webhooks used are:
  [![enter image description here](https://i.sstatic.net/kjSSZ.png)](https://i.sstatic.net/kjSSZ.png)
  
  > **Comments:**
  > **username_2**: This is a correct answer, and one I would endorse - but to be clear, the "Silent Post URL" has been deprecated for many years and I don't think it will be disabled in the next several years.  So it's good to use the authnet extension, but Silent Post URL is still a workable solution.  
  > **username_1**: Agreed. I am wondering if it would work out okay to have the core authnet processor (using silent post URL and needed for existing ARB's) and the https://lab.civicrm.org/extensions/authnet (using webhook) in use at the same time? I *think* so.  
  
  ---
  
  