Manual Integración CP Web Services XML doc 11.1 0 I

Confidential Document 1 de 44 Manual Integración CP Web Services XML doc 11.1 0 I

CENTRO DE PAGOS

XML Web Services

Version 11.0

Integration Manual

This document and/or the presentation to be shown is owned by Mercadotecnia, Ideas y Tecnología, and is considered an industrial secret, therefore, it must be deemed as confidential information. Pursuant to Article No. 85 of the Industrial Property Law (Ley de la Propiedad Industrial), any person who access this document and/or presentation, shall refrain from revealing, disclosing, copying, distributing or using the information contained herein. In addition, please note that the software and the transaction models are owned by Mercadotecnia, Ideas y Tecnología, and are protected by the Copyright Federal Law (Ley Federal de Derechos de Autor).

Document Identification


Document Identification

Type Integration Document Solution CENTRO DE PAGOS Web Service xml Date of issuance

July/2009

# of pages 44

Name Position Area Date of review

Made by Claudia Arvizu Brand Manager Development 07/2009

Translated by Claudia Arvizu Brand Manager Marketing 08/2009

Contents


Contents

Document Identification ...................................................................... 2

Contents .............................................................................................. 3

Prefacio ................................................................................................ 5

What is the Purpose of this Guide? .......................................................................... 5

Who should read this Guide? .................................................................................. 5

Translator Note ..................................................................................................... 5

1. CENTRO DE PAGOS Web Service XML ............................................ 6

Introduction ......................................................................................................... 6

How it works ........................................................................................................ 6

Integration Documents .......................................................................................... 6

Security ............................................................................................................... 7

Encryption/Un-encryption ................................................................................... 7

Work Environments ............................................................................................... 8

Service Request .................................................................................................... 9

2. XML Web Service Transactions ................................................... 10

3. Data Models and XML Chains ...................................................... 11

Card Present Transactions .................................................................................... 12

Band Direct Sale (VMCAMEXB) ........................................................................... 12

Band Check-In (VMCAMEXBCHECKIN) ................................................................ 14

Band Pre Sale (VMCAMEXBPREVENTA) ................................................................ 16

Card No Present Transactions ............................................................................... 18

MOTO Sale (VMCAMEXM) .................................................................................. 18

MOTO Forced Sale (VMCAMEXMFORZADA) .......................................................... 20

MOTO Check-In (VMCAMEXMCHECKIN) .............................................................. 22

MOTO Reauthorization (VMCAMEXMREAUTORIZACION) ........................................ 24

MOTO Check-Out (VMCAMEXMCHECKOUTEXPRESS) ............................................. 26

MOTO Pre Sale Closure (VMCAMEXMCIERREPREVENTA) ........................................ 28

MOTO Cancelation or Refund (VMCAMEXMCANCELACION) ..................................... 30

Special Transactions ............................................................................................ 32

Voucher Reprint (REPRINTVOUCHER) ................................................................. 32

CENTRO DE PAGOS Response (CENTEROFPAYMENTS) .......................................... 33

Approved Transaction ....................................................................................... 34

Error Transaction ............................................................................................. 34

4. Input Parameters ....................................................................... 35

Business Element ................................................................................................ 35

Transaction Element ............................................................................................ 35

Payment Parameters ........................................................................................ 36

Industry Parameters ......................................................................................... 36

5. Response Parameters ................................................................. 37

Response (CENTEROFPAYMENTS) .......................................................................... 37

6. Interpretation of the Voucher chain ............................................ 38

Appendix ............................................................................................ 39

Response Codes ................................................................................. 40

Contents


Error Codes ........................................................................................ 41

Supported Bank Terminals ................................................................. 42

MIT Help Desk Contact ....................................................................... 43

Change Control Sheet ......................................................................... 44

Prefacio


Prefacio

What is the Purpose of this Guide?

This guide provides the details required to successfully integrate merchant

applications to CENTRO DE PAGOS.

The guide resumes the business logic around CENTRO DE PAGOS, as its functioning and different options.

Who should read this Guide?

This guide is oriented to business analysts and integrators who want to

effectively integrate CENTRO DE PAGOS solution to a merchant application.

Translator Note

Some words in this document were intentionally left in Spanish because they refer to names of variables, fields, documents and/or programs.

CENTRO DE PAGOS Web Service XML


1. CENTRO DE PAGOS Web Service XML

Introduction

CENTRO DE PAGOS Web Service XML uses the benefits of Web Services and XML, to ease its integration with Merchants applications.

How it works

CENTRO DE PAGOS Web Service XML is invoked by a requester agent, using a XSD definition schema. When invoking the service, the requester

provides the transaction data, which CENTRO DE PAGOS uses to make a Transaction Authorization request to the card Issuing Bank. The Transaction Authorization request result is given back to the requester according to the response schema specifications.

Integration Documents

CENTRO DE PAGOS delivers to the following documentation:

Centro de Pagos Web Service Guide: It’s the document you are reading, includes all the needed information to

allow the merchant to integrate CENTRO DE PAGOS Web Service XML to its applications.

RC4 Encryption Algorithm (Java and php, accordingly with

Merchant needs). � RC4.java file. Source file with the RC4 encryption algorithm JAVA code

thought Salaa method.

� RC4.class file. Executable to integrate RC4 algorithm.

� RC4_php.php file. Source file with the RC4 encryption algorithm JAVA code thought Salaa method.



Security

To guarantee security, CENTRO DE PAGOS is implemented in a SSL (Security Socket Layer) Server, which certifies it as a secure site to perform transactions. Also, sensible data of the transaction must be sent encrypted, for what we use encryption algorithms under RSA standard.

The Web Service de CENTRO DE PAGOS sends the sensible data of the transaction in an encrypted way using algorithm under the RSA standards. The data of the payment chain that will have to be encrypted are: Los datos de la cadena de cobro que deberán ir cifrados son: 1. User Password

2. Card Data

� - Cardholder name

� - Card number

� - Card Expiration month

� - Card expiration year

� - Card security code

Encryption/Un-encryption

MIT will provide the encryption key, so the Merchant can encrypt the sensible data.

As a security mean, the key will be provided via phone call.

Encryption example encryptedChain=crpt.StringToHexString(crpt.Salaa(chainToEncrypt,ke

y));

Un-encryption example enc.Pura(enc.hexStringToString(data),key)

There is an URL available for encryption testing: http://ssl.e-pago.com.mx/pgs/jsp/cpagos/demo_encripta.jsp



Work Environments

To access CENTRO DE PAGOS a connection is made through the HTTPS protocol to the MIT transaction server, so it is necessary that the Merchant server has enabled access to such transaction server. During the process of any integration, MIT uses three work environments: 1. Development. Used to test the functioning of the code with a emulated

response.

2. QA. Used for testing real parameters, users and affiliations.

3. Production. Once the code works correctly in QA, is set in the production

environment and is released to end users.

Listed below are the URLs of the 3 working environments. All URLs respond on port 443.

Environment URL

Development https://dev.mitec.com.mx QA https://qa.mitec.com.mx Production https://ssl.e-pago.com.mx



Service Request

CENTRO DE PAGOS Web Service uses a different URL to invoke each transaction type, thought POST method over http. The URLs list is:

Transaction URL

Direct Sale https://ssl.e-pago.com.mx/pgs/cobroXml Cancelation https://ssl.e-pago.com.mx/pgs/CancelacionXml CheckIn https://ssl.e-pago.com.mx/pgs/CheckInXml CheckOut https://ssl.e-pago.com.mx/pgs/CheckOutXml Presale closure https://ssl.e-pago.com.mx/pgs/CierrePreventaXml Presale https://ssl.e-pago.com.mx/pgs/PreventaXml Reauthorization https://ssl.e-pago.com.mx/pgs/ReAutorizacionXml Reprint https://ssl.e-pago.com.mx/pgs/reImpresionXml Forced Sale https://ssl.e-pago.com.mx/pgs/VentaForzadaXml

Use the following sintax to process a transaction:

<URL><xml> where: xml = Parameter that contains transaction data according to

the definition schema.

Type of data = Alfanumeric

Nature = Mandatory

XML parameter contents the file that defines the transaction. The

component returns an XML document (defined by the schema) with the

information of the transaction results.

XML Web Service Transactions


2. XML Web Service Transactions

CENTRO DE PAGOS XML Web Service performs the following transactions:

The nomenclature used for transaction names is:

<Card Brand><Type of transaction><Operation> where: The sintax

Card Brand = Name of the card brand: V = Visa, MC = MasterCard, Amex = American Express.

Type of transaction = Indicates if the transaction is Card Present (Banda) or Card Not Present (MOTO): B = Banda, M = Moto.

Operation = Is the operation to be performed. For example Direct Sale, Check-In, Check-Out, etc.

Example = VMCAMEXBCHECKIN is a Check-In Banda operation for any Visa, MasterCard or Amex card.

Data Models and XML Chains


3. Data Models and XML Chains

Here are the data models and examples of the XML string for each of the

CENTRO DE PAGOS transactions.

NOTE: The following examples are included newline characters (newline)

and tabs between components and elements for ease of reading. However

in the actual transaction information is all one line.

To perform Card Present transactions please consult the Manual

Integration Terminal EMV Banking DLL.



Card Present Transactions

Band Direct Sale (VMCAMEXB)



//BAND DIRECT SALE

<?xml version=”1.0” encoding=”UTF-8” ?>

<VMCAMEXB>

<business>

<id_company>0035</id_company>

<id_branch>700</id_branch>

<country>MEX</country>

<user>0035RRMI0</user>

<pwd>11AEA0D1F22CDB30FE</pwd>

</business>

<transacction>

<merchant>00127</merchant>

<reference>54D77</reference>

<tp_operation>9</tp_operation>

<creditcard>

<crypto>2</crypto>

<type>V/MC</type>

<tracks>04A1A8D19449A648FB7F4F308E67A79322DDE39BFB4AC083772

44A4B6ADAC85607AD345C46227312F2</tracks>

<chip>1</chip>

<fallback>0</fallback>

<tags>5F2A040484820458008414A0000000041010951000800080009A

060901059C02009F02120000000000019F03120000000000009F090400

849F1016010103A0A006EBC29F1A0404849F1E1631323832373139379F

2616AEC21D5456118E209F2702809F3306E0B8C09F34065E03009F3502

229F360409A09F37084C42F1819F4108000000019F5302525F340201</t

ags>

<chipname>71CCD6A7E93FD236EE193645FA1ECC885EAA99E48B28B4F9

6534</chipname>

<chipnameenc>1</chipnameenc>

</creditcard>

<amount>1.20</amount>

<currency>MXN</currency>

<emv>1</emv>

<version>pcpay 5.0.0</version>

</transacction>

</VMCAMEXB>



Band Check-In (VMCAMEXBCHECKIN)



//BAND CHECKIN

<?xml version="1.0" encoding="UTF-8" ?>

<VMCAMEXBCHECKIN>

<business>




<user>0048HAJA0</user>

<pwd>11AEA7DCE83FDC38FF</pwd>

</business>

<transacction>


<reference>3544</reference>


<creditcard>

<crypto>2</crypto>

<type>V/MC</type>



<chip>1</chip>


<tags>5F2A040484820458008414A0000000041010951000800080009A

060901059C02009F02120000000000019F03120000000000009F090400

849F1016010103A02006EBC29F1A0404849F1E1631323832373139379F

2616260A840DC6B834789F2702809F3306E0B8C09F34065E03009F3502

229F360409A19F370850B3CBA69F4108000000019F5302525F340201</t

ags>


6534</chipname>


</creditcard>



<room>101</room>

<emv>1</emv>


</transacction>

</VMCAMEXBCHECKIN>



Band Pre Sale (VMCAMEXBPREVENTA)



//BAND PREVENTA


<VMCAMEXBPREVENTA>

<business>




<user>0049MOKA0</user>

<pwd>11AEA7DDED31DD38FF</pwd>

</business>

<transacction>


<reference>SD444</reference>


<creditcard>

<crypto>2</crypto>

<type>V/MC</type>



<chip>1</chip>


<tags>5F2A040484820458008414A0000000041010951000800080009A

060901059C02009F02120000000000019F03120000000000009F090400

849F1016010103A02006EBC29F1A0404849F1E1631323832373139379F

2616EBC02FEDB9FCFE559F2702809F3306E0B8C09F34065E03009F35022

29F3604099E9F3708590FA4B79F4108000000019F5302525F340201</tag

s>


6534</chipname>


</creditcard>



<cd_mesero>JUAN</cd_mesero>

<cd_turno>VESP</cd_turno>

<emv>1</emv>


</transacction>

</VMCAMEXBPREVENTA>



Card No Present Transactions

MOTO Sale (VMCAMEXM)



//MOTO SALE


<VMCAMEXM>

<business>




<user>0035GPEA0</user>

<pwd>11AEA0D1E72ED338FE</pwd>

</business>

<transacction>


<reference>AGM01</reference>


<creditcard>

<crypto>2</crypto>

<type>V/MC</type>

<name>64D2B3A7EC37D3379A0A</name>

<number>11AFA1D3904FA648FF7C4E348A64AC97</number>

<expmonth>11AB</expmonth>

<expyear>10AE</expyear>

<cvv-csc>10ACA0</cvv-csc>

</creditcard>

<amount>.01</amount>


<usrtransacction></usrtransacction>

<version>dllcpintegra 4.1.6</version>

</transacction>

</VMCAMEXM>



MOTO Forced Sale (VMCAMEXMFORZADA)



//MOTO FORCED SALE


<VMCAMEXMFORZADA>

<business>






</business>

<transacction>


<reference>MIKREF</reference>


<creditcard>

<crypto>2</crypto>

<type>V/MC</type>

<name>64D2B3A7EC37D3379A0A</name>





</creditcard>



<auth>123456</auth>

<usrtransacction>USRTRX01</usrtransacction>


</transacction>

</VMCAMEXMFORZADA>



MOTO Check-In (VMCAMEXMCHECKIN)



//MOTO CHECK IN


<VMCAMEXMCHECKIN>

<business>




<user>0081BGLI1</user>

<pwd>63EDCCB1D31BE431811B</pwd>

</business>

<transacction>


<reference>MIKE01</reference>


<creditcard>

<crypto>2</crypto>

<type>V/MC</type>

<name>6BCBD2AA802ED32B8B155F51FE00DAFD</name>





</creditcard>




<room>1</room>


</transacction>

</VMCAMEXMCHECKIN>



MOTO Reauthorization (VMCAMEXMREAUTORIZACION)



//MOTO REATHORIZATION


<VMCAMEXMREAUTORIZACION>

<business>




<user>0048HAJA0</user>

<pwd>11AEA7DCE83FDC38FE</pwd>

</business>

<transacction>


<no_operacion>123456789</no_operacion>


<crypto>2</crypto>


</transacction>

</VMCAMEXMREAUTORIZACION>



MOTO Check-Out (VMCAMEXMCHECKOUTEXPRESS)



//MOTO CHECK OUT


<VMCAMEXMCHECKOUTEXPRESS>

<business>




<user>0002PEOJ</user>

<pwd>11AEA3D6F03BD933FF</pwd>

</business>

<transacction>




<crypto>2</crypto>


</transacction>

</VMCAMEXMCHECKOUTEXPRESS>



MOTO Pre Sale Closure (VMCAMEXMCIERREPREVENTA)



//MOTO PRESALE CLOSURE


<VMCAMEXMCIERREPREVENTA>

<business>




<user>0082BGLI0</user>

<pwd>11AEABD6E239DA30FC</pwd>

</business>

<transacction>



<crypto>2</crypto>

<propina>.01</propina>


</transacction>

</VMCAMEXMCIERREPREVENTA>



MOTO Cancelation or Refund (VMCAMEXMCANCELACION)



//MOTO CANCELATION


<VMCAMEXMCANCELACION>

<business>




<user>0002PEOJ</user>

<pwd>11AEA3D6F03BD933FF</pwd>

</business>

<transacction>



<auth>123456</auth>


<crypto>2</crypto>


</transacction>

</VMCAMEXMCANCELACION>



Special Transactions

Voucher Reprint (REPRINTVOUCHER)

//VOUCHER REPRINT


<REPRINTVOUCHER>

<business>






</business>


<crypto>2</crypto>

</REPRINTVOUCHER>



CENTRO DE PAGOS Response (CENTEROFPAYMENTS)



Approved Transaction

//CENTRO DE PAGOS RESPONSE

<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <CENTEROFPAYMENTS> <reference>5515009010</reference> <response>approved</response> <foliocpagos>000046733</foliocpagos> <auth>141530</auth> <cd_response>0C</cd_response> <cd_error/> <nb_error/> <time>11:11:08</time> <date>22/06/2009</date> ..<voucher>61FDFD86802DF717BA2E1165DE20BFAD528CB8C8EA3EB5F40C40345B50AA9B085ABF5A2938460202C7C346840D8072AA92DB69892

93586B4E0DF67320F47D748DD8846E40C3B6F775A16EA7218FF0921FD0

B7F0E736CEFCDB1FF504BBFC17A11121FCEAABAA16D59CBD64727A731

416FBE31AE7B5352ECB7FA3BECD726460271D096F266D7DCBFF8F32C4

D8202BAFD92F715BEF90B4172A7BE74DB1E85879F420282E42C910D91

1AB52E905A04A053E8D27C11C0758F65F4AFE7415B7340AF539901FEFA

A9DCAE80E7E812EE27361ADC02D18E2923DBA50DD7E933F1278426C7A

D5ECA16A0F4A603F0AF0DAA785BD8CDCA2F08FA629315C6117E16AD00

F976DEBC9B51F8AE99A2F9A0F8DAF034F036FC7E2E9A8D9A58F87AA5A

400BB819CA5D8839A0B8874E1F04132ED11A9335311F46289E6E4F579C

4036F9BEEA00C0DD9BACDCA40EBB4B2B0ED45CB729137EC19FF5A147D

D8B329B580850131F0A89A14815FA3AC2B83BAD28917D5D4BF6BA0418

</voucher> </CENTEROFPAYMENTS>

Error Transaction

<?xml version=”1.0” encoding=”UTF-8” standalone=”yes”?> <CENTEROFPAYMENTS> <reference>5532249925</reference> <response>error</response> <foliocpagos/> <auth/> <cd_response/> <cd_error>11</cd_error> <nb_error>La transaccion ya fue aprobada el 22/06/2009

10:21:29</nb_error> <voucher/> </CENTEROFPAYMENTS>::

Input Parameters


4. Input Parameters

Following are the parameters used in the components, must be consulted on the data models which parameters corresponds to each transaction.

Business Element

This element identifies the Merchant and is present in all transactions.

Parameter Nature Description

country Mandatory Country of operation. id_branch Mandatory Branch reference number. id_company Mandatory Company reference number. pwd Mandatory Password. user Mandatory User name.

Transaction Element

To facilitate understanding, the parameters of the Transaction element have been classified by their function

� Payment Parameters

� Industry Parameters

This classification is purely illustrative. Transactions, depending on their nature, can include any parameters of the functions presented below. To identify which parameters correspond to each transaction data models should be consulted.

Input Parameters


Payment Parameters

The following are the parameters used in the payment functions, its use depends on whether a Card Present (Banda or EMV) or Card Not Present (MOTO / Web) transaction.


amount Mandatory Amount to charge.

auth Mandatory Operation authorization number.

crypto Depends on the operation

Flag that indicates if the credit card information is encrypted: Always must have a value of 2=all information encrypted.

currency Mandatory Currency

cvv-csc Depends on the operation

Card security code (CVV).

emv Optional Flag that indicates if it is an EMV transaction, it means, with possible chip presence. Always must have a value of 1=EMV.

iscallforauth Optional Flag tha indicates if the transaction result requested “call for authorization”.

merchant Mandatory Merchant afilliation number (Provided by MIT).

no_operacion Depends on the operation

Number assigned to the operation (same as foliocpagos).

reference Mandatory Transaction reference number.

serie Optional Point of Sale terminal serial number..

tp_operation Mandatory Operation type (Provided by MIT).

usrtransacction Optional User code per transaction.

version Optional CENTRO DE PAGOS version number, this data is given by MIT.

Industry Parameters

This parameters of the transaction element are special for the hotels and restaurants industries:


cd_mesero Optional Waiter name or code. Used only in Se utiliza únicamente en CENTRO DE PAGOS Restaurant.

cd_turno Optional Waiter shift. Used only in CENTRO DE PAGOS Restaurant.

room Optional Room number. Used only in CENTRO DE PAGOS Hotel.

Response Parameters


5. Response Parameters

Following are described the parameters used in CENTRO DE PAGOS response.

Response (CENTEROFPAYMENTS)


amount Optional Transaction amount. auth Optional Autorization number. Empty in case of error. avsauth Optional Autorization number when using AVS. cc_desc Optional Card type description. cc_expmonth Optional Card expiration month. cc_expyear Optional Card expiration year. cc_name Optional Cardholder name. cc_number Optional Card last four digits. cc_type Optional Card type. cd_error Optional Error code. Empty in case of successful transaction. See table in the

appendix.. cd_response Mandatory Response code. See table in the appendix.. date Optional Trasaction date. foliocpagos Optional Operation number. nb_company Optional Ciompany name nb_error Optional cd_error description. See table in the appendix. nb_merchant Optional Afilliation number. nb_street Optional Street name. reference Mandatory Transaction reference number (same used to request the service). response Mandatory Transaction result, can be approved, denied or error. time Optional Transaction time. tp_operation Optional Operation type. Voucher Optional Information for Voucher print out.

Interpretation of the Voucher chain


6. Interpretation of the Voucher chain

CENTRO DE PAGOS prepares the voucher with the information and format to comply with valid and legal requirements before all banks, so that only be interpreted and printed by the Merchant. The voucher is presented in a chain that, at the top of each line, has the format that must be printed. Avoid parsing the chain Voucher to extract any data in particular. Each line of the voucher chain begins with four characters indicating positional formatting instructions. Example:

Indicator of the beginning of the format

First position= text aligment Second Position = font size Third Position = Font density

@ l = left c = center r = right

n = normal s = small b = big

b = bold n = normal l = light

<voucher> @cnb Santander @cnn CREDITO @cnn VENTA @cnn COMERCIO UNO @cnn 0001 SUC DEL VALLE @cnn 1234567 EL COMERCIO 6M @lnn HERIBERTO FRIAS 1527 INT 603 @lnn COL.DEL VALLE CENTRO, DF @lnn 0634GUG3 @br @lnn No.Tarjeta: ************5679 @lnn Vence:0309 @br @lnn CREDITO/SANTANDER/MasterCard @br @lnn IMPORTE $ 245.26 MXN @br @lnn Oper.: 000995516 @lnn Ref:: 124567JU @lnn Aut: 000891 @br @lnn Fecha: 08/03/2006 12:57 @br @br @br @cnn ______________________________ @cnb EL CLIENTE @br @lsn POR ESTE PAGARÉ ME OBLIGO INCONDICIONALMENTE A </voucher>

Interpretation of the Voucher chain


Appendix

Response Codes


Response Codes

Code Response Description

approved Transaction approved by the issuing bank. denied Transaction denied by the issuing bank. error Information error at the service request.

Error Codes


Error Codes

Code Description del error

01 The XML document does not comply with the defined schema.

02 The XML document does comply with the defined schema, but there is an incongruity in the information.

03 Company, branch or user data is incorrect. 04 Invalid card number. 05 Branch not configured to perform that transaction type.

06 Card type validation error (Visa, MasterCard o Amex) or transaction type error depending on the instrument key word (credit or debit).

07 Deferred charges not allowed with this bank. 08 Minimum amount lower than the minimum amount defined for this affiliation. 09 Amount not allowed to be charged by this user.

10 Transaction date out of temporarily range for the referred affiliation. (Only for deferred charges affiliations).

11 Attempt to perform same approved or denied transaction twice (same day, same reference number, same amount).

12 Card cannot be processed with this affiliation. For example: attempting to process a Visa/Master Card with an Amex affiliation or vice versa.

13

AVS Response. Could be: D : Person not authenticated E : Attempted more than twice H : Could not authentic the person

Supported Bank Terminals


Supported Bank Terminals

CENTRO DE PAGOS supports POS for different brands and models, which area homologated according to their release to the domestic market. These terminals use EMV and magnetic stripe technology. The supported models supported in this version of for CENTRO DE PAGOS are:

Serial terminals can be connected through a USB converter, being the

drivers from the converter manufacturer and the operating system which

allows this possibility.

In case magnetic stripe reading is integrated via XML Web Service, MIT

will deliver a DLL that serves as an interface between the application and

the reading device.

Brand Model Conectivity USB Adaptor*

Picture

Ingenico 3070

Serial Supported

USB NA

Ingenico Aqua55 Serial Supported

Verifone V5 Serial Supported

Hypercom 4205 Serial Supported

Hypercom 4220 Ethernet Supported

MIT Help Desk Contact


MIT Help Desk Contact

For suport attention, we have a Help Desk with the following telephone number at Mexico City, to solve doubts and orientation to eficiently exploit our platform resources. Mexico City Telephone Number (01.55) 1500.9000

Electronic Mail Adress [email protected]

Change Control Sheet


Change Control Sheet

Doc Version Change Date Change Description

1.0 May/2006 Document creation.

10.0 Jun/2009

Modification to clarify some chapters: introduction update, inclusion of transactions tree, parameters restructuration, voucher chain interpretation, supported terminals appendix. Elimination of previous appendixes. Inclusion of xmls examples, encryption section and systems environments. Inclusión of 3DS appendix.

10.1 E Aug/2009 Elimination of introduction chapters. 10.1 I Aug/2009 Manual Translation.