OK. I'm confused. Authorized.net is asking for an additional $10/month to handle recurring transactions. Do we need that? Or are the recurring transactions handled with aMember Pro, and submitted through Authorize.net each time as a unique transaction. Is my question making sense? Thanks, Mark
Perfect question... someone please clarify with an answer. At this point I DON'T think I need that feature to do recurring billing, but I won't know until the first payment comes due in 7 days...
For Authorize.AIM plugin, CC info will be stored in aMember database and aMember will resubmit transaction itself, so recurring billing service that providled by Authorize.Net is not required.
I know this is off topic, but when i try to post a new thread i get a db error... When ever somebody's CC errors out they get: "The transaction was unsuccessful." And no other info, how can I get the error description to show up form Authorize.net... Like declined, or insufficient funds, or AVS mismatch... Stuff like that... Thanks
Can you attach screenshot of error you got when try to post? In regards to Authorize.NET debug info available in payment record at the bottom. amember CP -> Payments -> Edit Payment
So if I'm understand correctly, you're saying that I can do recurring billing with the authorize_cim plugin by paying authorize.net for their CIM and do not have to pay for their ARB? Thanks for being so diligent in getting us answers, Alexander!