1 Reply Latest reply on Dec 8, 2016 8:01 AM by user7109

    Best way to process recurring subscription costs?

    ezeitgeist

      I am using WebDirect and will then move to a php-based site. What I need is the ability for users to start (and later be able to cancel) recurring billing and enter all the payment items themselves so that I am PCI compliant (and do not have to do it all myself).

       

      I was recommended to use Authorize.net, but for recurring billing that the user sets up, it would appear I would likely need 360Works Plastic Enterprise License to have it put on the server, and I am still not fully understanding if that would do it.

       

      The developer I am working with is fx.php based for that side of things rather than API. It seems like API would solve things via Authorize.net, but this is not my field of expertise. Does anyone have any recommendations of best practices/best routes?

        • 1. Re: Best way to process recurring subscription costs?
          user7109

          The Plastic plug-in supports the following Authorize.Net services: Automated Recurring Billing (ARB) and Customer Information Manager (CIM).

           

          With ARB, you enter the parameters of the subscription (start date, recurring amount, frequency, etc.) and Authorize.Net takes care of the rest. When you create a subscription, you get an ID in return that you can use to update certain aspects of the subscription or cancel it, but you cannot get transaction feedback via the plug-in.

           

          With CIM, you create a customer profile and then you can create one or more payment profiles tied to that customer. When you create a customer profile, you get an ID in return that you use to create a payment profile. When you create a payment profile, you also get an ID in return. You use the combination of a customer profile ID and a payment profile ID to perform a transaction on demand, for which you will receive response feedback from Authorize.Net.

           

          Since CIM gives you the ability to perform a transaction on demand, you could roll your own recurring mechanism purely in FileMaker and use the plug-in to perform the transactions scheduled for a given day in a looping script. That way you could record the success or failure of each transaction and any auxiliary information directly in the database. It's certainly more work, but it gives you feedback that you won't get using ARB.

           

          If you have additional questions, feel free to send us an e-mail at plugins@360works.com or support@360works.com.

           

          Sterling Rouse

          360Works