<?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: What is the easiest method for integrating ARB into my secure site in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/What-is-the-easiest-method-for-integrating-ARB-into-my-secure/m-p/15848#M8992</link>
    <description>&lt;P&gt;I haven't run into this situation yet myself, but from what I'm reading, if a person's card expires and their payment fails as a result, updating the credit card info causes the subscription to resume - but at the next payment, not the one it failed on. This may not be a problem if you want to charge them immediately on update using AIM, but otherwise you'll have to change the billing date on your ARB subscription.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;All in all, you're probably going to find triggered CIM less complicated in the end. You just set up a payment profile for each person, then have an automated process run every morning and check for people coming due (you'd have stored that info in a database, of course) If they're due, it attempts payment. If payment fails, it sends them a message and then bumps the due date one day, and keeps doing this until it hits some failure cut-off. Way less complicated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;EDIT: Also, I believe CIM is included in the base price, so you can save $10 per month.&lt;/P&gt;</description>
    <pubDate>Mon, 08 Aug 2011 23:42:39 GMT</pubDate>
    <dc:creator>TJPride</dc:creator>
    <dc:date>2011-08-08T23:42:39Z</dc:date>
    <item>
      <title>What is the easiest method for integrating ARB into my secure site</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/What-is-the-easiest-method-for-integrating-ARB-into-my-secure/m-p/15828#M8982</link>
      <description>&lt;P&gt;Scenario is:&lt;/P&gt;&lt;P&gt;- Customer registers for a subscription (subscription amount will vary from person to person)&lt;/P&gt;&lt;P&gt;- PHP form is presented on site first with TOS then with the necessary fields for credit card payments&lt;/P&gt;&lt;P&gt;- Customer agrees to TOS then proceeds to fill in credit card information then submits&lt;/P&gt;&lt;P&gt;- Connection made with Authorize.net - payment accepted/declined etc.&lt;/P&gt;&lt;P&gt;- Customer receives email receipt from my site&lt;/P&gt;&lt;P&gt;- Customers card is due to expire - would like to send a notice to login to site and update&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp; credit card expiry date or have the option to change credit card details if he chooses (new card)&lt;/P&gt;&lt;P&gt;- Customers monthly recurring continues uninterrupted&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My concern is that I have looked through the documentation and SDK extensively and feel I have&lt;/P&gt;&lt;P&gt;backed myself into a corner of confusion.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there (does anyone have) a similar situation where you have created the necessary PHP forms&lt;/P&gt;&lt;P&gt;to accomodate my needs? Or can you point me to an ABC step-by-step guide on how to implement&lt;/P&gt;&lt;P&gt;the structure I laid out in the scenario above?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So basicly Customer Registers - Fills in the form - Pays - Is setup on a monthly, quarterly, semi or&lt;/P&gt;&lt;P&gt;annual basis (whichever they choose) - and when their CC needs updating they can login to my&lt;/P&gt;&lt;P&gt;system and make their changes without service and payment interruption.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for any help you can provide.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Chris Creighton&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 08 Aug 2011 19:26:01 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/What-is-the-easiest-method-for-integrating-ARB-into-my-secure/m-p/15828#M8982</guid>
      <dc:creator>Chris-Creighton</dc:creator>
      <dc:date>2011-08-08T19:26:01Z</dc:date>
    </item>
    <item>
      <title>Re: What is the easiest method for integrating ARB into my secure site</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/What-is-the-easiest-method-for-integrating-ARB-into-my-secure/m-p/15848#M8992</link>
      <description>&lt;P&gt;I haven't run into this situation yet myself, but from what I'm reading, if a person's card expires and their payment fails as a result, updating the credit card info causes the subscription to resume - but at the next payment, not the one it failed on. This may not be a problem if you want to charge them immediately on update using AIM, but otherwise you'll have to change the billing date on your ARB subscription.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;All in all, you're probably going to find triggered CIM less complicated in the end. You just set up a payment profile for each person, then have an automated process run every morning and check for people coming due (you'd have stored that info in a database, of course) If they're due, it attempts payment. If payment fails, it sends them a message and then bumps the due date one day, and keeps doing this until it hits some failure cut-off. Way less complicated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;EDIT: Also, I believe CIM is included in the base price, so you can save $10 per month.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Aug 2011 23:42:39 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/What-is-the-easiest-method-for-integrating-ARB-into-my-secure/m-p/15848#M8992</guid>
      <dc:creator>TJPride</dc:creator>
      <dc:date>2011-08-08T23:42:39Z</dc:date>
    </item>
  </channel>
</rss>

