CNG TecsWeb Interfaces

Request Token Helper Interface

TecsWeb Request Token is constructed as a URL to which customer has to be redirected.

Depending on your server-side technology (PHP, JAVA, C#) you can choose one of the prepared TecsWeb SDKs to create request token:

The interface (API) is the same for each SDK:

method params returns
__constructor privateSecretKey (string), mid (string), paygateUrl (string) -
createSignedUrl data (array) string

where data structure is as following:

key type mandatory desc
amt integer yes amount in cents
txid integer yes unique transaction id
txcur string yes transaction currency
txdesc string yes transaction descrip.
receiptnumber integer yes invoice/order number
rurl string yes return URL
User-Data string no special User Data if needed

CNG TecsWeb Interfaces

Response Token Helper Interface

TecsWeb Response Token is constructed as Return URL which is defined in TecsWeb Request Token with response parameters added to that URL.

Depending on your server-side technology (PHP, JAVA, C#) you can choose one of the prepared TecsWeb SDKs to check and get data from response token:

PHP - https://github.com/tecspayment/tecsweb-b2b-integration-php (please clone or download latest version)

The interface (API) is the same for each SDK:

method params description returns
__constructor privateSecretKey (string), data (array) -
isSignedCorrectly checks if response token is valid boolean
getResponseText returns response text such as "Authorized" string
getResponseCode returns response code such as 0 for Authorized string
getTXID returns Transaction ID string
getTXDateTime returns Transaction TimeStamp string
getAuthorizationNumber returns Authorization Number string
getVUNumber string
getOperatorID string
getSerieNumber string
getOriginalTXID string
getSTAN string
getOriginalSTAN string
getSVC string
getUserData string
getSign string
getAcquirerName string
getCardType string
getCardReferenceNumber string
getAllData returns payload of all data (for logging) array

NOTE: The list of response codes and texts is not a part of this document. The documentation will be provided by TECS when the integration process will start.