Description
A few key features need to be implemented.
I will use already provided Authentication system with a few changes, which will be most noticeable in the registration process. Therefore, few new user fields will be instated.
As I am planning to implement PayPal API for transactions (developer sandbox environment), certainly, user funds will be obligatory to be implemented in the WebApp. The app will stay with default classic input data, while requiring user's birth date, location (street, country, zip) and possibly a phone number.
After the user successfully inputs required data, user will select which kind of account does he want to possess and to act as on Apollo. There will be two types of users, which are: Classic and Agent. Both Classic and Agent will have a chance to rank-up their account to Premium which will provide several new features and possibilities. In case user selects agent as a type of the user he wants to be, there will be more checks and validations to provide as much as possible legal information required for verification and certification of the agent. Otherwise, in case Agent couldn't be identified and verified, IP will be hashed by using Bcrypt (most likely) and will be stored in the Database for further blocking. MAC address or other key credentials of the device/network, etc. might be included as well in the blocking system. Classic user will have several more options to complete and to continue to Apollo.
- Login view
- Login validation
- User new fields/columns
- Register view
- Register validation
- Forgot password
- Validation after register
- Other steps of register
- Choosing account type after register