I need to tie plans to specifc profile attributes, e.g. when a customer subscribes to a plan I need to make sure that the customer has filled in some required details in his profile (like full address, contact number, etc...)

I could image this as a per plan setting:

Option: Check valid profile? (Yes / No)

if yes is selected then load the profile properties collection from the core and select required (additional) properties that a user has to fill in.

I need this quite quick so I would be willing to implement it myself; I just need to make sure it gets into your module - what do you think?

Here is some info on validating VAT numbers:
http://ec.europa.eu/taxation_customs/vies/en/faqvies.htm#item16

And a link to a WSDL file:
http://ec.europa.eu/taxation_customs/vies/api/checkVatPort?wsdl

Philipp,

I totally agree with you but this means a lot of work for Scott and I think we need to raise funds for this project. Including the VAT validation and all other goodies we think of this could mean weeks work for Scott.

I would like to ask Scott how many hours he needs to implement the suggestions made in this thread and it should be up to the group in this thread (others are welcome also) to do some fund raising!

Philipp, you are a developer so you may be able to work with Scott on this. I can't or maybe just very limited so donating some funds would be appropriate for me and not for you...

My 2 cts..

We can forget that part with is Business Client or not. The check if it is a business client from the EEC is an easy one. We should build a table with countries that are in the EEC. Check the users country setting from the Users table in DNN (or wherever the country is defined) with the EEC Country table and you have the answer wether that client is from within the EEC or not. That EEC table should be editable in the Module because countries are added every year.

Does this makes sense to you?

One thing is important. All data from the customer like address, country, VAT number should be stored in the Receipt table per transaction. The point is that I will use that data to import it into my Accounting software. An example:

Customer purchases a subscription at 01 Jan 2007 and expires at 01 March 2007. This subscription is bought with VAT Number 123456789.

Same customer comes back in March but the company that originally purchased the subscription merged with another company but the user purchases a new subscription with the same account. If the VAT number is drawn from some table where it was stored the first time the customer subscribed my tax declaration will fail because the companies merged and got a NEW and different VAT number. This means at each initial purchase, extension or renewal the VAT number MUST be validated.

In the company I previously owned and operated we did a lot of business inside the EEC and I can tell you that a tax declaration with wrong or non existing VAT number cause major headaches and problems.

For validation please have a look here:

Here is some info on validating VAT numbers:
http://ec.europa.eu/taxation_customs/vies/en/faqvies.htm#item16

And a link to a WSDL file:
http://ec.europa.eu/taxation_customs/vies/api/checkVatPort?wsdl

Ok, as my initial post may have sounded like a quick shot, I ordered my thoughts in the bath tub. Here's what I need exactly.

1. Set required profile properties per plan

This will render a list of all available properties to the admin, but only those properties that are not required per portal setting. Admins can make these proeprties required for the current plan. If one subscribes to the plan he will be presented the core ProfilePropertiesEditor (note that you can override the required attribute before ou render the editor). This screen will look like the core profile page to get the same look and feel throughout the page. As soon as all properties are set the user gets redirected to the payment processor.

2. Allow anonymous visitors to subscribe

This will present the visitor with a registration screen that looks like the core registration screen, In addition to the portal required fields the plan reuquired fields are marked as required. Again, the UserpropertiesEditor and the ProfilePropertiesEditor from the Core should be used for the reasons above.

Unfortunately the Core does not provide a ReturnURL attribute to be used in the registration pages, this would make things much easier

I  too don't believe storing required properties in the receipt table is a good idea. I would like to get to a point where all profile data is stored in the core. Storing thins like this in the module would lead to the opposite.

3. I need to set the end of the current year as the expire date of a role subscription, also I need to set a date where the role memebership effectively expires. Use case for this a club membership where memebrship usually expires at the end of the year while users have time until March 1st to pay for the next year. Until March 1st they need to sty  in the membership role. can this be done?

4. I need a way to allow users to subscribe to multiple subscriptions while they are already subscribed to one plan. Right now you see the current subscription on the landing page but not other subscriptions that are available. A better display would be

--------------------------------------

My current subscriptions

--------------------------------------

Additional available plans

--------------------------------------

5. I need an additional payment processor. A quite simple one actually: Bank Transfer. When selected the subscriptions becomes pending but the user needs to able to select hsi receipt (which would really be an invoice then) to see bank details for making the payment. This invoice would need to be templateable. Once paid the admin needs to be able to mark the subscription as paid.

I hope that was it for now. #2 is not immeditely important, while all others are. I'm prepared to fund $150 if you could start working on this soon, hopefully others are prepared to donate as well

Regarding the VAT, I still believe this is a valuable extension for the property types in the profile properties. I've seen others implementing user photos into the user profile - it's not that tricky. I could maybe do this for you Mariette

The existing registration control does not provide the redirectURL, however, you could just make your own copy of the control and include in the Sub Tools package. Then you would have the freedom of making changes as you see fit.

I agree that the best thing would be to add a list of available required fields to the plan editor. It may be easier to just list them all vs. looking at what is already included.