Microsoft Access and .ASP changes needed

Currently our websites' backend administration is coded to communicate with [url removed, login to view], which is an online merchant account provider, and it is setup where we can charge credit cards from the backend administration. We currently use [[url removed, login to view]][1] to process credit cards and the frontend of our website is already integrated with echo.

We want the backend to to communicate with our echo-inc account rather than [url removed, login to view] and we would like the capability of processing charges and credits from within the backend administration, which is located at <[url removed, login to view]>. Echo-inc has online instructions on how web developers can integrate custom applications with their company. This information is located at <[url removed, login to view]>. We also would like the backend to store a history when credits or charges were issued so we can keep track of this information, and we would like custom emails sent to the customer whenever a credit or charge is processed.

## Deliverables

1a) Develop a .ASP module that processes credit card charges and credits through Echo-Inc and properly install and integrate this module into the backend administration. Provide integration in such a way that these features can be accessed from easy and logical locations within the backend administration.

2a) Develop a .ASP module that stores the following information from each customer when he/she places an order and when we process a charge or credit from the backend:

a.) Echo's "AVS Status" which is sent back during processing. This information explains whether the address matched, and/or zip matched. This should be stored in every order after it is submitted by us from the backend and/or after a customer places an order on our frontend part of the website. This will make it easier for us to verify orders.

b.) Echo's "CNP Response" which is also sent back during processing. This information explains whether the CVV security code that the customer typed in matched or not. This should also be stored in every order after it is submitted by us from the backend and/or after a customer places an order on our frontend part of the website. This will make it easier for us to verify orders as well.

c.) The "Echo Order Number", which is created anytime a charge is submitted, should also be stored in the backend because echo needs this information when submitting a credit.

d.) Everytime a customer places an order and/or when we submit charges and credits from the backend, the approved or declined status of each submittal should be stored in the order details and order details history so we can see if a charge or credit went through successfully.

3a.) An email should automatically be sent to the customer everytime a credit or charge is submitted from the backend. The email should have elements integrated that show the approval or declined status of the charge and/or credit that was processed. We also want the option to go in and change the email messages you program in to autosend.

4a.) Right now the backend only remembers the last four digits of the credit card used and it deletes the CVV security code after an order is placed. We would like all of the credit numbers and CVV security codes to be stored in the database so that future charges and credits can be made from the backend.

5a.) We have one other website that has the same backend structure as the above mentioned website, except for a few additional features, and we would like all modules and request made above to be installed in this second website. The second website has a SQL database instead of an Access database, so it may require a few small alterations to install the modules.

6a.) We want the option to approve the design of how these modules are visually integrated into the backend so that everything is layed out in a common sense way and it is convenient for us to use.

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

Windows and 3.0+ versions of Internet Explorer.

ASP PHP

Projektin tunnus: #3874570

Tietoa projektista