I just bought the registration module and have a few questions.

1. How to set this up using the authorize.net payment gateway in such a way that the user is NOT registered if the payment fails.  I think I had things setup correctly, but as a test to fail payment the user was still registered with the site.  In my case I'm having an event that is supposed to fire upon registration that assigns a user to a given role.  Maybe I need to attach the event to something else?

2.  How to setup recurring billing?  I see that one can tell the module to expire the assigned role a user is given after "X" number of days, but how to give the user the option of paying monthly, quarterly or annually?  How to sync this up with what authorize.net does?  It looks like there is a separate manual setting that once must setup for authorize.net -- seems like it would be easy to get in trouble there. 

Are credit card numbers stored in the DNN database? -- is that something I need to worry about?  seems like this is not the desired effect as the payment gateway can handle that (I think).

With the DNN "Advanced Settings" for Roles one can configure the Service Fee, Billing Period (every day, month, week, year, etc.).  Also important is the ability to set a free Trial Period as DNN provides.  Is this possible with this module?  If so how?

4.  Also, a true subscription based/membership site ought to send out a reminder 1 month or so prior to the subsciption ending, and then up to 3 follow up reminders (or some configurable number) up to the deadline date (i.e. send reminders after a certain PERIOD and a certain FREQUENCY.)  And maybe even one after the deadline "x" number of days/weeks later as a last Hail Mary to try and retain the client.  Any thoughts on this?

5.  And finally, when is 3.2 coming out?  Hopefully it will address these issues.  Or better yet, the version I have can handle what I'm wanting and I just need a few nudges in the right direction.

Thanks for your time.

Shawn,

Hi. Let me see if I can answer some of your questions.

1. A user should not be registered unless the payment is processed successfully. The payment gateway runs and processes before the user is added/update or any completion events fire. If its not working like this and you can for sure duplicate the issue (user is registered when payment fails), please let em know.  I cannot currently duplicate this locally as far as I can tell.

2. Yes, Dynamic Registration 3.2 will be synced up with PayPal for recurring billing (and allow each IPN within PayPal to fire off events such as adding days to the users security role etc...). Currently right now Dynamic Registration can accept payments from within Authorizenet however it is not setup for ARB (Authorizenets Recurring Billing method). So, if you are wanting to set this up you would either need to purchase the source code and add this feature, or we will continue to review this down the road. Simply put - Its easy to change the price for Authorizenet (such as a dropdownlist or radio button that represents the amount sent to Authorizenet) however, the integration for recurring billing is much more complicated and not something we could currently include (including what happens when their subscription for payment is created but Authorizenet needs to talk back to your site to add them to security roles etc...) This is covered with PayPal subscription within 3.2, however another alternative is to use a new module we have coming out called Renewal Reminder. This module is there to cover users who pay with Authorizenet, but you want them to get a reminder that they will need to go back in and resubscribe or 'add time to their subscription' basically. This might be another alternative to consider. Renewal Reminder is released as a beta but not a full release yet as we continue to test and enhance it.

As far as credit cards stored within the database. Within the 3.2 release there is a new feature to 'Do not save field responses to database' within advanced field settings. For now, you can review this post which will provide you with a work around for making sure credit card information is not stored within the database.

3. As far as the 'free trial period, service fee, etc.. That is all specifically related to the CORE and Dynamic Registration does not directly integrate with those properties.

4. Yes, this is what the Renewal Reminder module will do. You can send out 'x' number of days before the users role will expire and set the number of days before to send out, the message that goes out, the number of days for a 'time lapse' so that in case the scheduler process ran nightly it wouldn't email them every night (maybe a reminder every 7 days if they were within 14 days of losing their subscription etc...)

5. We are currently working on beta testing 3.2, documentation for 3.2, and some finishing development touches for the user-facing PayPal integration. We hope to have the full release out within the next few weeks. Its currently our highest priority and we do not plan to have any other modules released until its release.

-Chad