Credit Payment Processor

The scope of work involves the design and implementation of a credit payment processor module for identical websites called [login to view URL], [login to view URL] and Tracktout.com. The credit payment processor software is described in the following analysis: The standard Internet protocol “Hypertext Transfer Protocol?? (the http at the beginning of web sites) is used for most web pages. When a web browser tries to access a page, it sends a “GET?? request to the server where the web site is located. The web server then returns the appropriate data to the browser, and the browser displays the page. (“POST?? and “PUT?? are two other request methods. POST is often used with forms, and PUT is occasionally used for file transfers). This is the standard flow of an e-commerce transaction on the web: 1. The user is at a checkout screen on a web site. The user enters his/her credit card information (number, expiration date) and submits a form. 2. The form is sent to the web site’s server. 3. The web site’s server sends the credit card information to the payment gateway. 4. The payment gateway verifies the credit card. It responds to the web server with a reply of either confirmed or denied. 5. The web server returns a web page to the user. If the payment was confirmed, it is a thank you page or receipt. If it was denied, it is an error message. Using HTTPS in place of HTTP is virtually seamless. A small (freely available) program is added onto your web server, and then all data requested securely is encrypted. No HTML code needs to be modified to work over HTTPS. Very little PHP code needs to be modified to work with HTTPS (only the code that actually sends/receives encrypted data needs to be modified). When a browser is using a secure connection, a padlock is usually displayed in the bottom right-hand corner of the window. The project can be roughly divided into two parts. The first part is adding the shopping carts system. This component will allow users to add items to their cart, update quantities, enter their billing information, etc. Writing the code to interface with the credit card gateway is more straightforward. No user credit card data would need to be stored on the web site. There is actually less work involved if it is not stored on the web site. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Installation package that will install the software (in ready-to-run condition) on the platform(s) specified in this bid request. 3) Complete ownership and distribution copyrights to all work purchased. ## Platform Linux, Unix & Windows PHP & MySQL