Questions:
(1) For recurring billing with Authorize.net, does the system make use of Authorize.net's Automated Recurring Billing (ARB) system, or does the system process recurring billing via a DotNetNuke scheduled task?
(2) For PayPal recurring payments, does it use PayPal's recurring system, or does it use a DotNetNuke scheduled task?
(3) I see that there is an option to not save credit card info in the database. Is this option applicable to recurring billing?
(4) With recurring billing, can a product be set up to charge a one-time setup fee with an initial payment, then not charge a setup fee for the recurring payments?
(5) Is there an option to save all credit card information in Authorize.net's Customer Information Manager (CIM) instead of storing it in the database? If not, this would be a terrific option for your customers to help with PCI compliance.
(6) With recurring billing, can customers see their payment history?
Answers:
(1) Th cart uses Authorize.net's Automated Recurring Billing (ARB) system.
(2) The cart uses PayPal's recurring system
(3) Yes
(4) Yes you can create a bundled product with a one time setup fee and the regular recurring charge.
(5) The cart has a setting not to save credit card numbers and Authorize.net stores all the credit card info including credit card number for later reference.
(6) Yes the cart comes with a seperate "My Accounts" module that allows the user to login and see their account history.