Payment Gateway » Mexico Banamex TNS

h1. Specification

h1. Activity Diagram

Figure 1 showing the process flow from Mexico mall to TNS Payment Gateway Page.

!gw.png!

Figure 2 showing the process flow of TNS Payment Gateway redirect back to Mexico Mall.

!recv.png!

h1. Programming Guide

h2. Resources

h3. SCM

see [[wiki#SCM]]

h3. Classes

* *my.com.eCosway.tns.commons*      - CommonConstants

* *my.com.eCosway.tns.model*        - Transaction, TransCommon, TransResponse

* *my.com.eCosway.tns.service*      - TNSService (interface)

* *my.com.eCosway.tns.service.impl* - TNSServiceImpl (implementation of interface)

* *my.com.eCosway.tns.tnsInterface* - TNSInterfaces (Data Persistence)

* *my.com.eCosway.tns.utils*        - SecureHash, URLUtils

* *test.my.com.eCosway.tns.utils*   - SecureHashTest, URLUtilsTest (JUnit Test)

h3. properties file

* *jdbc.properties* 

   # *tns.interface.table.name* - table name of TNS interface

* *log4j.properties*

* *transaction.properties*

   # *vpc_Version*        - The version of the Virtual Payment Client API being used.

   # *vpc_Command*        - Indicates the desired operation to be performed.

   # *vpc_AccessCode*     - Authenticates the merchant on the Payment Server.

   # *vpc_Merchant*       - The Merchant ID identifies the merchant account against which settlements will be made. 

   # *vpc_SecureHash*     - A secure hash which allows the Virtual Payment Client to authenticate the merchant and check the integrity of the Transaction Request.

   # *vpc_SecureHashType* - The type of hash algorithm used to generate the secure hash.

   # *vpc_ReturnAuthResponseData* - Specifies whether the authorisation response data must be included in the Transaction Response.