Create osCommerce Payment Module

We require you to create an NEW osCommerce payment module that will integrate our Gateway with the merchants osCommerce site.

We have a current module that performs the transaction properly but is missing many of the features below. We have provided this module here for your review, and you can edit this module as you see fit or dis-guard it.

You must deliver to us an installable payment module to be used in osCommerce sites that is tested on our demo-oscommerce site located at: http://webbtrans.net/demo-oscommerce/catalog/.

The parameters that the merchant will input into the installation area are:

Enable iPayDNA Module: True/False

Merchant ID: (given by us to each Merchant. eg: bestlife001)

ePayment URL: (the URL that the transaction is sent to. Given by us to each Merchant. eg: https://www.ipaydna.info/aquarius/gatedna/process/acquirer/epaymentQW70.cfm))

Server static IP Address: (the IP address of the server that is transmitting the file to the Gateway. eg: 184.168.235.1)

Sending URL/File Name: (the path and file name that is sending the file to the gateway. eg: http://webbtrans.net/demo-oscommerce/catalog/checkout_confirmation.php)

Successful Transaction URL/File Name: (the path and file name of the file that the gateway will return the successful transaction information to. eg:http://webbtrans.net/demo-oscommerce/catalog/checkout_success.php)

Declined Transaction URL/File Name: (the path and file name of the file that the gateway will return the successful transaction information to. eg:http://webbtrans.net/demo-oscommerce/catalog/checkout_declined.php)

Transaction Currency: (various)

Payment Zone: (various)

Set Order Default: (various)

Sort order of display: (various)

Once these parameters are input, your module must email all of this information to an email address we specify so we can manually enter it into our Gateway for authentication purposes. At the same time your module must install the payment integration on the osCommerce site.

When the transaction is posted to the Gateway the resulting information returned by the Gateway must be saved in the transactions section of osCommerce and must include the error codes/decline codes or authorization code.

checkout_success.php - The file that handles the successful transactions must integrate with all of the osCommerce native functions

checkout_declined.php - the file that handles all of the declined/error transactions must integrate with all of the osCommerce native functions

Other incidental instructions will be provided to the successful candidate.

PLEASE, IF YOU HAVE NEVER CREATED A PAYMENT MODULE FOR osCOMMERCE, DO NOT APPLY FOR THIS JOB!!!