<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Need help configuring webhooks for subscription triggered payments / recurring billing events in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Need-help-configuring-webhooks-for-subscription-triggered/m-p/71123#M43778</link>
    <description>&lt;P&gt;We are integrating Authorize into our platform, and are facing difficulty in identifying the appropriate webhook events to use for identifying &lt;SPAN&gt;recurring billing transactions and associated data. We had gone through the integration guides and couldn't get a clear idea regarding the same.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;After successfully creating a subscription, we want to receive data regarding subsequent recurring transactions and also be able to know if a charge attempt failed for some reason.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;We have a accept.js and PHP integration in the works, and are using "authCaptureTransaction" method for processing single payments and have implemented subscription creation using the standard SDK.&lt;BR /&gt;&lt;BR /&gt;We only require webhook events for &lt;SPAN&gt;recurring billing transactions, including unique event data per recurring transaction (transaction id or invoice number) and status infromation incase such a transaction fails, so that we can update the same in our system.&amp;nbsp;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;Please let us know of the webhook events to use and subsequent API calls (if required) so that we get the above mentioned information for recurring transactions.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;Thank you.&lt;/P&gt;</description>
    <pubDate>Thu, 19 Mar 2020 21:27:52 GMT</pubDate>
    <dc:creator>cmdev</dc:creator>
    <dc:date>2020-03-19T21:27:52Z</dc:date>
    <item>
      <title>Need help configuring webhooks for subscription triggered payments / recurring billing events</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Need-help-configuring-webhooks-for-subscription-triggered/m-p/71123#M43778</link>
      <description>&lt;P&gt;We are integrating Authorize into our platform, and are facing difficulty in identifying the appropriate webhook events to use for identifying &lt;SPAN&gt;recurring billing transactions and associated data. We had gone through the integration guides and couldn't get a clear idea regarding the same.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;After successfully creating a subscription, we want to receive data regarding subsequent recurring transactions and also be able to know if a charge attempt failed for some reason.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;We have a accept.js and PHP integration in the works, and are using "authCaptureTransaction" method for processing single payments and have implemented subscription creation using the standard SDK.&lt;BR /&gt;&lt;BR /&gt;We only require webhook events for &lt;SPAN&gt;recurring billing transactions, including unique event data per recurring transaction (transaction id or invoice number) and status infromation incase such a transaction fails, so that we can update the same in our system.&amp;nbsp;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;BR /&gt;Please let us know of the webhook events to use and subsequent API calls (if required) so that we get the above mentioned information for recurring transactions.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Mar 2020 21:27:52 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Need-help-configuring-webhooks-for-subscription-triggered/m-p/71123#M43778</guid>
      <dc:creator>cmdev</dc:creator>
      <dc:date>2020-03-19T21:27:52Z</dc:date>
    </item>
  </channel>
</rss>

