Ticket Exchange Inc. (TCL/TK Coding)

This project has already been fully designed, and about 95% of the code has already been written in tcl/tk. For an interface look go to [[login to view URL]][1]. The overall business/website process is as follows: **"Ticket Exchange, Inc.** provides the infrastructure for the most efficient and technologically advanced online marketplace to buy or sell sport and entertainment event tickets in TEXAS. [login to view URL] allows buyers and sellers to transact easily and securely by providing a managed trading platform, payment mechanism, and shipping mechanism. [login to view URL] users can buy tickets directly from season ticket holders, other fans, and ticket brokers- thus giving them access to premium tickets that may not be available through traditional outlets. Similarly, it enables users to easily sell tickets that you cannot use or just want to sell. In chronological order, our simple transaction process has the following components: 1. _Seller posts tickets for sale through our user-friendly web interface._ At this point the seller chooses his or her preferred method of receiving payment. The 2 methods available are via an electronic deposit into your bank account (Payment Resources International) or via physical delivery of a check from us. 2. _Buyer browses our marketplace for tickets using our visually intuitive seating charts_. Our entire marketplace is easily navigable by everyone. Once a buyer is satisfied with a ticket selection, he or she initiates the purchase using any major credit card. 3. _Seller is notified by email regarding the purchase of his tickets and is directed to our automated FedEx delivery system_. Seller prints a FedEx label (with all information already on it), places the tickets in a FedEx letter folder and sends the package to the buyer. 4. _Buyer receives the package containing the tickets._ Since we are fully integrated with FedEx we are notified of this and release the funds to the seller using his or her preferred method of receiving payment. Throughout the whole process buyers and sellers receive transaction information, tracking information, and expected delivery time of tickets. Moreover, Ticket Exchange customer service representatives monitor every transaction and are available to answer questions and ensure smooth transactions." ## Deliverables The parts of the code/website that have not been finished include: 1) Payment Resources International, our payment mechanism partner- make sure it works properly and our system-nighlty run-updates properly, both response and return files. 2) Email templates- Some parts need to be fine-tuned, change text. (Previously sent highlighted portions) 3) I was unable to verify this one. “When error comes on site…have some sort of automatic page for it if possible.?? Has this been done? 4) Make certain pages easily printable: Last page of Buying and Selling Process still print pretty bad. 5) Add help image link. Should only be a link (??Need Help??) in the page where ABA and bank account info is inputed. 6) the “save as default?? feature when the buyer is purchasing tickets does not work when you click it 7) The previous test which you said ACH transfer went through properly, registered as sold tickets in my account, is still registered as Qued for Payment instead of Completed---(Payment database vs. Tickets Sold Table) 8) Xxxx out routing transit number and bank account number for security on the sell process 9) Take the field/data out “buyer?? in ‘my acount’ ‘sold tickets’ and ‘purchased tickets’ - we want our system to be anonymous 10) New filter/order mechanism for events and/or inventory is not working for certain fields. 11) Minor text changes For the above items, which will be explained in greater detail after initiating contact with prospective developers, the following must be done: 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 In all internet browsers commonly used.