re-develop the registration and payment functionality
Someone has done majority of the job but failed to complete it so I am looking for someone RELIABLE, with EXCELLENT communication (on chat) and someone who will not disappear for days without talking.
The scope of work will encompass the following requirements / tasks:
o The registration and payment gateway must be secure/encrypted
o Ability to for us to set and adjust Member and Non-Member prices for each event
o Ability for one person to register multiple attendees (both members and non-members) simultaneously (with one transaction)
o Attendee information (name, phone, email, member/non-member) should be entered on the registration page
o Retention of attendee contact information (name, phone #, email) in an easy-to-use format that allows us to pull a list of attendees by event
o Cardholder information (credit card #, ccv #, cardholder name, billing address, email, phone) should be entered on the payment page
o Payment screen should show the components of the total amount calculated (i.e. # of Members x Member Price, # of Non-Members x Non-Member price)
o Payment gateway must be linked through [url removed, login to view] (the payment information will be completed on our site, but [url removed, login to view] will process the payment with the information provided by our site)
o Upon completion of registration and payment – the cardholder should be sent an email confirming the payment amount. Attendees should be sent a separate email confirming that they are registered.
o Each event should be tied to the calendar on the front page of the site.
o Please do not include an Attendee/Sponsor designation such as the one that currently exists on the registration page
o Please do not include an Individuals/Company designation such as the one that currently exists on the registration page
o The only designation that the user should have to select for each attendee is Member/Non-Member (currently referred to as “Chapter Status”)
o Membership will not be validated.
o Appropriate input masks to ensure that information provided is valid (i.e. a user should not be permitted to enter alpha characters in the phone number field, this should consist entirely of numeric characters, etc.)