My client is using amember. They have different levels of membership. The top levels is $3600 per year. Paypayl will not process something this large (even if you have a paypal account) without a phone call. We are looking into authorize.net, but the thought of storing credit card numbers in amember scares me. Even if we are on a secure site, its still scary (and I thought illegal..). So is there a way we cant take multiple payments? So every year we accept 2 payments of 1800? I've read through the manual, and there are options, but I'm not sure they would work (we could do a trial of 1800, and regular 1800, but that won't work on year two). Any ideas (besides lowering their price). Also is there a post giving all the details of using authorize.net and exactly what it requires (i've used paypal for everything). I need to know what I'm getting into. Dave Jackson www.podcastfastpass.com
Hello, David's solution is probably the simplest except you don't get $3600 up front but only $1800 and giving them the ability to cancel out within 6 months. I just got setup with Authorize.Net and will be using SIM since I don't have any recurring products. But I have seen this new service offered by Authorize.Net which claims can be used to store sensitive information such as credit card in order to simplify PCI compliance. I assume it uses a different API than either AIM or SIM or in conjunction with. Anyway it costs an extra $20.00 per month. I've already had to modify the aMember SIM plugin quite a bit since I want itemized product and taxes to show up on payment form so if I have to write a new plugin to support this API should not be a big deal. The following URL talks about the service. http://www.authorize.net/solutions/merchantsolutions/merchantservices/cim/ Quick synopsis is as follows: The Authorize.Net Customer Information Manager (CIM) allows merchants to create customer profiles that are stored on Authorize.Net’s secure servers. By providing quick access to stored customer information, CIM is ideal for businesses that: Process recurring transactions where the date and/or amount is different each month Process usage charges – where you only bill when the service is used. Are concerned with PCI compliance. Want to provide returning customers with the convenience of not having to re-enter personal data. The CIM API supports integration with a Web site payment form or a proprietary business application. The profiles, which include payment and shipping information, can then be referenced in future transactions, eliminating steps in the transaction process for repeat customers and potentially increasing customer loyalty The following URL is documentation for API. http://www.authorize.net/support/CIM_XML_guide.pdf It appears you can store customer profiles (i.e. credit card info, banking info, shipping address), and can do payments thru the interface. It might be just as easy to use AIM and modify aMember (i.e. enhance plugin interface) to call out to plugin (if supplied) for get_cc_info(), and save_cc_info() so that we can control where the cc info is stored. On the other hand it probably is easier to just write a new plugin. The API document was last revised on 08/05/2008 so I don't know how stable or reliable the system is. I think I will play around with the sample code they provided this weekend to see if I can put together a plugin that works with aMember. I would be willing to pay $20/month to be able to do rebilling and not store cc info on my local server if the system was reliable. Jimmy
...and more importantly for Dave, what are you selling for $3600 per member and how can I get a cut of that action ;-)
Contact Authorize.net about their recurring payments option. They can handle monthly subscriptions. I'll take a cut also.
You're doing $3600 per transaction, either get Paypal Pro (or whatever their merchant account option is called these days) or sign up with some other merchant account (not processor), like Authorize.net... end of story.