<?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 Re: Authorize.net with membership plugin issues in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Authorize-net-with-membership-plugin-issues/m-p/39219#M21392</link>
    <description>&lt;P&gt;Should be SIM or DPM, not AIM API&lt;/P&gt;</description>
    <pubDate>Tue, 18 Feb 2014 12:12:13 GMT</pubDate>
    <dc:creator>RaynorC1emen7</dc:creator>
    <dc:date>2014-02-18T12:12:13Z</dc:date>
    <item>
      <title>Authorize.net with membership plugin issues</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Authorize-net-with-membership-plugin-issues/m-p/39207#M21386</link>
      <description>&lt;P&gt;I migrated site from one membership platform to another. With the current platform, after importing members connection between authorize.net and the membership plugin is lost. The silent post url is being used so that for new members, the connection exists. However, for old members, there is no way for authorize.net to communicate with the membership plugin when for example, a user's billing fails due to incorrect info or insufficient funds. Is there a API function with Authorize.net such that when blillling fails or succeed, authorize.net can communicate to membership plugin on site to carry out certain actions on user (for instance, temporarily deactivate account when billing fails)?&lt;/P&gt;</description>
      <pubDate>Mon, 17 Feb 2014 21:07:20 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Authorize-net-with-membership-plugin-issues/m-p/39207#M21386</guid>
      <dc:creator>JJThompson</dc:creator>
      <dc:date>2014-02-17T21:07:20Z</dc:date>
    </item>
    <item>
      <title>Re: Authorize.net with membership plugin issues</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Authorize-net-with-membership-plugin-issues/m-p/39209#M21387</link>
      <description>&lt;P&gt;Since there is only one silent post url allow on an authorize.net. You could use the relay response url(if you are using the AIM API), which could have multiples url, although not sure if it work with your plugin.&lt;/P&gt;</description>
      <pubDate>Mon, 17 Feb 2014 21:19:33 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Authorize-net-with-membership-plugin-issues/m-p/39209#M21387</guid>
      <dc:creator>RaynorC1emen7</dc:creator>
      <dc:date>2014-02-17T21:19:33Z</dc:date>
    </item>
    <item>
      <title>Re: Authorize.net with membership plugin issues</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Authorize-net-with-membership-plugin-issues/m-p/39219#M21392</link>
      <description>&lt;P&gt;Should be SIM or DPM, not AIM API&lt;/P&gt;</description>
      <pubDate>Tue, 18 Feb 2014 12:12:13 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Authorize-net-with-membership-plugin-issues/m-p/39219#M21392</guid>
      <dc:creator>RaynorC1emen7</dc:creator>
      <dc:date>2014-02-18T12:12:13Z</dc:date>
    </item>
  </channel>
</rss>

