ePay

Should be done in ASP. Project Description: The main page allows 2 activities: Customer login . Provider Login . The customer goes to a page where the providers general data , banners & payments form is and pays. The provider uses the report page to analyze his income Flow : -The provider opens an account (on a backoffice we provide, addressing the same sql tables as you will design ) , and get AccountNo(Ex:1234) + Password . -The provider calls his clients and tell them : "From now on , Pls pay me using the web site , Using AccountNo : 1234" . -The customer goes to the web site -> customer login -> and enters the account no . -The customer fills in the Payment form and clicks "Submit" . -At the end of the month (or maybe after 3 days) the provider goes to the web site , fills in his AccountNo and Pw , and runs the reports to view his incomes etc . Dynamic & Static : All banners are dynamic in all the website ??" i.e. replaceable via the backoffice . Command Buttons are fixed . The home page will look the same for all users , i.e. if I change the banners , logo , picture , text etc , all users will see a new banner . The banners at the Payment form may differ for each provider . Same for the payment approved page . The Report page may vary on the logo , but the banners are the same for all providers . The "Other Pages" ??" like customer service (EzPay_Page) ??" is a template for standard text pages that should have text coming from the backOffice , notice , there are X "general pages" for now , accessed by the buttons : OpenAccount|FAQ|[login to view URL]|Privacy|WhoRWe|Home But there all the same , Just a different Text . And last but not least , Payment -> Submit , Should open a general page without banners , that are the "I agree to the Terms" . Pls read the above and see the original spec(attached) , If you have any other questions , ask. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform ASP.NET