Mensajeria Suiche7B

VERSIN 1.1 Elaborado por: Revisado por: Aprobado por:

Firma:

Firma:

Firma:

Alexander Jos Azocar Coord. Organizacin y Calidad

Francisco Lpez Gerente de Tecnologa y Proyectos

Giovanni Novellino Gerente General

26 de Abril de 2011

FIS ISO 8583 PROCESSOR INTERFACE MESSAGE SPECIFICATIONS GUIDE

(IBM CONNEX V3.4B - Corporacin SUICHE 7B, C. A.)

RIF.: J-00259842-5


CONTROL DE CAMBIOS FECHA:

25/05/2011


Cambio N Descripcin del Cambio Fecha Observaciones

1

Modificacin en el Capitulo IX PROCESSING CODES (BIT 003) AUTHORIZATION MESSAGES, en la pagina 172, tabla NETWORK MANAGEMENT INFORMATION CODES (BIT 070) Information Code 271

25/05/2011

Elaborado por: Revisado por: Aprobado por: Firma:

Firma:

Firma:

Nombre: Nombre: Nombre:

Alexander Azocar Francisco Lpez Giovanni Novellino Cargo: Cargo: Cargo:

Coordinador de Organizacin y Calidad Gerente de Tecnologa y Proyectos Gerente General

Ubicacin Electrnica Sistema de Gestin de la Calidad (Aplicacin)

RIF.: J-00259842-5


TABLA DE CONTENIDO FECHA:

26/04/2011


USO DE ESTE DOCUMENTO..........................................................................................................1 PROPSITO.......................................................................................................................................1 ALCANCE ...........................................................................................................................................1 CONTROL DEL DOCUMENTO..........................................................................................................1 CONFIDENCIALIDAD.........................................................................................................................1 LISTA DE DISTRIBUCIN .................................................................................................................1

INTRODUCCIN ...............................................................................................................................2 LOG DE REVISION ............................................................................................................................2

OVERVIEW ........................................................................................................................................3 ISO MESSAGE STRUCTURE............................................................................................................3 OPTIONS............................................................................................................................................3

Message Text Options ....................................................................................................................3 Encryption and Logon Options........................................................................................................4 Messages and Bit Maps..................................................................................................................4 Totals Processing Option ................................................................................................................4 Duplicate Monitoring .......................................................................................................................4 Network Management Options........................................................................................................4 Reversal Processing Options..........................................................................................................4 Multiple Message Transactions.......................................................................................................5 EMV Chip Card Support..................................................................................................................5

MESSAGE STRUCTURE..................................................................................................................6 MESSAGE COMPONENTS................................................................................................................6 MESSAGE TYPE IDENTIFIER...........................................................................................................6 PRIMARY BIT MAP ............................................................................................................................6

Data Elements.................................................................................................................................6 Additional Data Element Support ....................................................................................................6 Message Repeats ...........................................................................................................................6

MESSAGE TYPES..............................................................................................................................7 Authorization Messages..................................................................................................................7 Financial Transaction Messages.....................................................................................................7 Negative File Maintenance Messages ............................................................................................8 Authorization Processor (AP) Maintenance Messages...................................................................8 Reversal Messages.........................................................................................................................8 Reconciliation/Totals Messages......................................................................................................9 Administrative Messages ................................................................................................................9 Network Management Messages..................................................................................................10 Message Arrangement..................................................................................................................10 Message Description.....................................................................................................................10 Message Structure ........................................................................................................................10

FORMATO DE MENSAJES SUICHE 7B.......................................................................................14 MESSAGES 0100/0101 CHECK GUARANTEE/CONFORMACIN CHEQUES REQUEST...........14

Description ....................................................................................................................................14 Message Structure ........................................................................................................................15

0110 AUTHORIZATION RESPONSE...............................................................................................19 Description ....................................................................................................................................19 Message Structure ........................................................................................................................19

RIF.: J-00259842-5



26/04/2011


0200/0201 FINANCIAL TRANSACTION REQUEST ........................................................................21 Description ....................................................................................................................................21 Esquema Transaccional de una Operacin de Transferencia Interbancaria ................................29 Esquema Transaccional para la Operacin de Pago de Servicios ...............................................30

0210 FINANCIAL TRANSACTION RESPONSE...............................................................................31 Description ....................................................................................................................................31 Message Structure ........................................................................................................................31

0220/0221 FINANCIAL TRANSACTION ADVICE ............................................................................36 Description ....................................................................................................................................36 Message Structure ........................................................................................................................36

0230 FINANCIAL TRANSACTION ADVICE RESPONSE ................................................................40 Description ....................................................................................................................................40 Message Structure ........................................................................................................................40

0420/0421 ACQUIRER REVERSAL ADVICE...................................................................................42 Description ....................................................................................................................................42 Message Structure ........................................................................................................................42

0430 ACQUIRER REVERSAL RESPONSE.....................................................................................47 Description ....................................................................................................................................47 Message Structure ........................................................................................................................47

0620 ADMINISTRATIVE ADVICE.....................................................................................................49 Description ....................................................................................................................................49 Message Structure ........................................................................................................................49

0800 NETWORK MANAGEMENT REQUEST..................................................................................49 Description ....................................................................................................................................49 Message Structure ........................................................................................................................50

0810 NETWORK MANAGEMENT RESPONSE ...............................................................................50 Description ....................................................................................................................................50 Message Structure ........................................................................................................................51

DATA ELEMENT DEFINITIONS.....................................................................................................52 FORMAT...........................................................................................................................................52 ATTRIBUTES....................................................................................................................................52 DESCRIPTION..................................................................................................................................52 DATA EDIT .......................................................................................................................................52 STATUS............................................................................................................................................53 LEGEND FOR ATTRIBUTE ABBREVIATIONS Explanation ............................................................53 DATA ELEMENTS ............................................................................................................................54 ABREVIACIN PARA LOS ESTADOS DE VENEZUELA: ...............................................................79

TRAZAS MENSAJERA ISO 8583 SUICHE 7B ..........................................................................147 FLUJO MANEJO DE LA RED.........................................................................................................147

MSG 0800...................................................................................................................................147 MSG 0810...................................................................................................................................147

FLUJO MANEJO DE LOS REVERSOS EN LA RED SUICHE 7B..................................................148 MSG 0420...................................................................................................................................149 MSG 0430...................................................................................................................................149

DATA ELEMENTS CODE TABLES.............................................................................................150 TRANSACTION TYPES..................................................................................................................150

Debits ..........................................................................................................................................150

RIF.: J-00259842-5



26/04/2011


Credits.........................................................................................................................................151 Inquiry Services...........................................................................................................................151 Transfer/Transfer Payment Services ..........................................................................................151 Payment Services .......................................................................................................................151

PROCESSING CODES (BIT 003), AUTHORIZATION MESSAGES..........................................152 PROCESSING CODES (BIT 003), AUTHORIZATION MESSAGES..............................................152

01xx Check Guarantee ..............................................................................................................152 PROCESSING CODES (BIT 003), FINANCIAL TRANSACTION MESSAGES..............................152

02xx Purchase of Goods and Services .......................................................................................152 02xx Cash Withdrawal ................................................................................................................153 02xx Purchase Return.................................................................................................................153 02xx Available Finds Inquiry .......................................................................................................153 02xx Balance Inquiry...................................................................................................................154 02xx Generic Balance Inquiry .....................................................................................................154 02xx Transfers and Payment Services .......................................................................................154

POINT-OF-SERVICE ENTRY MODE (BIT 022) .............................................................................157 PAN Entry Mode Codes..............................................................................................................157 PIN Entry Mode Codes ...............................................................................................................157

POINT-OF-SERVICE CONDITION CODES (BIT 025) ...................................................................158 RESPONSE CODES (BIT 039) ......................................................................................................159 ADDITIONAL AMOUNTS CODES (BIT 054)..................................................................................164

Account Type ..............................................................................................................................164 Amount Type...............................................................................................................................164 Amount Type (Transaction-Related) ...........................................................................................165

NATIONAL POS CONDITION CODE (BIT 58) ...............................................................................166 Terminal Type Codes..................................................................................................................166

ADVICE/REVERSAL REASON CODES (BIT 060).........................................................................170 Reversal Reason Codes .............................................................................................................170

NETWORK MANAGEMENT INFORMATION CODES (BIT 070) ...................................................172 FILE UPDATE CODES (BIT 091) ...................................................................................................173

Negative File Update Codes (0302s) ..........................................................................................173 Authorization Processor File Update Codes (0382s) ..................................................................174

DATA ELEMENTS ISO 8583 (BIT 55)..........................................................................................175 TAGs EMV Obligatorios en el BIT 55 (0100 / 0200 ) .................................................................177 TAGs EMV Opcionales en el BIT 55 (0100 / 0200) ..................................................................178 TAGs EMV Condicionales (0110 / 0210) ...................................................................................178

SERVICIOS DE CONVERSIN OBS DE SUICHE 7B................................................................179 ESPECIFICACIONES TCNICAS..................................................................................................179 OPCIONES DEL EMISOR..............................................................................................................179 RESUMEN IMPACTO EN LOS EMISORES...................................................................................180 REQUERIMIENTOS ADQUIRENTE...............................................................................................180

CAM para Adquirentes Full Grade ..............................................................................................180 RESUMEN IMPACTO EN LOS ADQUIRIENTES...........................................................................180

CONSIDERACIONES PARA EL SIGRI (ON LINE BATCH)....................................................181 CONDICIONES A EVALUAR:.........................................................................................................181 ON BEHALF SERVICES EN SUICHE 7B.......................................................................................181

Bco. Adquiriente:.........................................................................................................................181

RIF.: J-00259842-5



26/04/2011


SUICHE 7B / Bco. Emisor:..........................................................................................................181 ANEXO...........................................................................................................................................182

ANEXO 1 - DESCRIPCIN DE LOS TAG QUE CONFORMAN EL BIT 55 ...................................182 ELEMENTOS DEL MENSAJES 0200........................................................................................182 ELEMENTOS OPCIONALES......................................................................................................185 ELEMENTOS MENSAJES DE RESPUESTA 0210...................................................................188

ANEXO 2 - CAMPOS MNIMOS PARA EL CLCULO/VERIFICACIN DEL ARQC Y ARPC ......189 Verificacin ARQC ......................................................................................................................189

RESPONSES CODES.-..................................................................................................................190 RECOMENDACIONES PARA LA REALIZACIN DE PRUEBAS EMV EN LA RED S7B .............190

RIF.: J-00259842-5


CAPITULO

I PAGINA

1

USO DE ESTE DOCUMENTO CAMBIO N

FECHA:

26/04/2011


USO DE ESTE DOCUMENTO

PROPSITO

Documentar las especificaciones de la mensajera ISO8583 de FIS adaptada a los requerimientos de la Red SUICHE 7B, en concordancia con los documentos y servicios que han sido autorizados por FIS.

ALCANCE

Este documento es de uso exclusivo de los Miembros que integran la Red SUICHE 7B (Definir Alcance).

CONTROL DEL DOCUMENTO

Este documento para su revisin, actualizacin, aprobacin y publicacin, se rige por lo establecido en el Procedimiento de Control de Documentos.

CONFIDENCIALIDAD.

La informacin contenida en este documento es propiedad de la Corporacin SUICHE 7B, C.A., y se califica como confidencial. Este material no podr ser reproducido, copiado o trascrito en Venezuela o en otro pas, en idioma espaol o traducido, sin la debida autorizacin escrita de la Corporacin SUICHE 7B C.A. La violacin de las disposiciones antes mencionadas ser sancionada de acuerdo a la Legislacin Venezolana vigente.

LISTA DE DISTRIBUCIN Tipo de Documento Cantidad de Ejemplares. Nombre del Usuario Fsico Electrnico. Original Copia

Gerencia de Tecnologa y Proyectos X

Instituciones Miembros X

Coordinacin de Organizacin y Sistemas X 1

RIF.: J-00259842-5


CAPITULO

II PAGINA

2

INTRODUCCIN CAMBIO N

FECHA:

26/04/2011


INTRODUCCIN El manual FIS SM ISO 8583 PI Specifications Guide constituye una fuente de informacin que sirve de ayuda a las instituciones, redes, u otros proveedores que quieren disear el intercambio de los mensajes de las transacciones financieras o administrativas utilizando la estructura ISO8583 de FIS a travs del Sistema Connex . Su objetivo principal es mantener informado a los especialistas de aplicaciones, de todos los detalles y definiciones, especificando todos los elementos de datos, variables y estructuras de los mensajes para minimizar los esfuerzos en la programacin. La informacin tcnica completa sobre la estructura de los mensajes y temas similares, son responsabilidad de los especialistas que estn desarrollando las aplicaciones. Este manual aplica para la versin 3.4B del Connex dentro de la plataforma IBM . y las anteriores a sta; sin embargo, contiene los elementos que han sido adaptados a los requerimientos exigidos por los Miembros que integran la red Suiche 7B, tomando como base los documentos y servicios que han sido autorizados por FIS.

LOG DE REVISION

Date Effective W/Version Chapter Change

March 2008 V3.4B 4 Updated the table information for: VISA SMS. Modified the Data Edit description for Data Element: 004 Amount, Transaction. Modified the Description for Data Element: 054 Additional Amounts. DE 111 - MasterCard IPM 0220 Posting Items Format - Added the Subelement: 111.13 - Payment Transaction Initiator.

February 2008

3 4

Updated the message structure of: Added Bit No.124 & 125 for 0100/0101 Authorization Request Added Bit No.124 & 125 for 0110 Authorization Response Added Bit No.124 & 125 for 0120/0121 Authorization Advice Added Bit No.124 & 125 for 0200/0201 Financial Transaction Request Added Bit No.124 & 125 for 0210 Financial Transaction Response Added Bit No.124 & 125 for "0220/0221 Financial Transaction Advice Added Bit No.124 & 125 for 0420/0421 Acquirer Reversal Advice

RIF.: J-00259842-5


CAPITULO

III PAGINA

3

OVERVIEW CAMBIO N

FECHA:

26/04/2011


OVERVIEW The FIS ISO 8583 Processor Interface (PI) is an optional component of the IBM-Based Connex application. It specifies a common interface for bank card-originated messages that relate to EFT, ATM, and POS transactions between acquiring and cardissuing institutions or their agents. The processor interface provides system messages based on the International Standards Organization's (ISO) standard set for ISO 8583-1987 - Bank Card Originated Messages - Interchange Message Specifications - Content for Financial Transactions. It optionally incorporates the American National Standards Institute's (ANSI) standard set in ANSI X9.2 Interchange Message Specification for Debit and Credit Card Message Exchange Among Financial Institutions, dated May 16, 1989.

ISO MESSAGE STRUCTURE

The figure below shows the general structure of each standard message in the FIS ISO 8583 PI.

Message Type Identifier

Primary Bit Map

Secondary Bit Map

Data Elements 002 through 064

Data Elements 065 through 128

The bit map associates each data element in a message with a specific bit in the bit maps. If the bit associated with a particular data element is set to 1, that data element is present in the message. If that bit is set to 0, that data element is not present in the message. In the ISO message structure, each message always contains a primary bit map, indicating the presence of bits 002 through 064. If a message contains any data elements associated with bit numbers 065 through 128, the Secondary Bit Map is also included.

OPTIONS

The FIS ISO 8583 PI can be set up to suit your individual business and performance requirements.

Message Text Options

This document details the recommended FIS ISO bit and message settings for SUICHE 7B. These values include the required messages, bit elements, and options for the SUICHE 7B implementation.

Message Structure Options

The message text is EBCDIC characters. The bit map is expanded. (Character format) The numeric data is unpacked. (Character format) The variable data fields will be variable (not fixed length).

RIF.: J-00259842-5


CAPITULO

III PAGINA

4

OVERVIEW CAMBIO N

FECHA:

26/04/2011


Encryption and Logon Options

Connex system will be the Master. The endpoints (client) will log on to Connex. The PIN key must be dynamic and key exchange could occur dynamic. No MAC verification will be done. No data encryption will be done. (The PINBLOCK must be encrypted)

Messages and Bit Maps

Options are: R o M: Requerido o Mandatorio. C: Condicional. (The data element is required when specific conditions are

satisfied. The applicable conditions are identified in the Notes column of the message structure chart).

O: Opcional. Totals Processing Option

A host may elect to send or receive totals. If the host is sending totals, the FIS ISO PI can be set up to save totals based on the host's business date. If FIS is sending totals, the FIS ISO PI can be set up to save totals based on the network business date.

Duplicate Monitoring

Duplicate monitoring affects the processing of repeat transaction types. Refer to FIS ISO 8583 Message Flows for more information about duplicate monitoring.

Network Management Options

Following are supported network management options. No on-line network management messages are sent. A single network management message is sent for both the issuer and the acquirer. Separate network management messages are sent to the acquirer and the issuer.

Reversal Processing Options

Following are available reversal processing options.

You can select to send/receive reversals for late/unsolicited responses or send/receive reversals at time-out.

You can select to receive partial reversals for misdispenses or a full reversal followed by a forced post/advice for misdispenses. (En Suiche 7B solo se permite el full reversal)

RIF.: J-00259842-5


CAPITULO

III PAGINA

5

OVERVIEW CAMBIO N

FECHA:

26/04/2011


Multiple Message Transactions

This functionality allows the issuer to send a series of continuation messages to the acquirer when the response data does not fit in one message. This option is used for transactions, such as statement print requests, that contain more than 255 bytes of information.

EMV Chip Card Support

Networks are implementing rules to replace magnetic stripe authentication with EuroPay MasterCard Visa (EMV) chip card authentication. The benefits of using EMV chip card authentications include:

More secure method of validating cardholders Decreased susceptibility to fraud schemes such as skimming.

See the information for Bit 55 for specific details about how to implement EMV chip card support at SUICHE 7B.

RIF.: J-00259842-5


CAPITULO

IV PAGINA

6

MESSAGE STRUCTURE CAMBIO N

FECHA:

26/04/2011


MESSAGE STRUCTURE

MESSAGE COMPONENTS

Each message in the FIS ISO 8583 PI consists of three (3) basic items:

Message type identifier One or more bit maps A series of data elements in the order of the bit map representation

MESSAGE TYPE IDENTIFIER

Each message begins with a four-position numeric message type indicator. The first two positions identify the message class:

01xx=Authorization Messages 02xx=Financial Transaction Messages 03xx=File Update Messages 04xx=Reversal/Chargeback Messages 05xx=Reconciliation/Totals Messages 06xx=Administrative Messages 08xx=Network Management Messages

PRIMARY BIT MAP

The primary bit map is the control record that describes which data elements are being sent.

Data Elements

The remainder of the message consists of a series of data elements in the order of the bit map representation. These data elements are described in detail in Data Element Definitions.

Additional Data Element Support

The data elements defined as conditional or optional may be required to interchange with endpoints using other message structures. Refer to the requirements specifications document for the specific link to determine additional data element requirements.

Message Repeats

Whenever a repeat message is identified, the repeat message is the same as the original message except for the message type identifier, which increases by one. For example, a repeat message for a 0220 Financial Transaction Advice has a message type identifier of 0221.

RIF.: J-00259842-5


CAPITULO

IV PAGINA

7


FECHA:

26/04/2011


MESSAGE TYPES

Authorization Messages

Authorization messages are passed between the acquirer and the issuer to obtain the approval necessary to complete a financial transaction.

Message Code

Description

0100 Authorization Request Check Verification/Guarantee/Conformacin de Cheques Request

0101 RepeatAuthorization Request Note: This message is not generated by the Connex System.

0110

Authorization Request Response Check Verification/Guarantee/ Conformacin de Cheques Response

0120 Authorization Advice

0121 Repeat 0120Authorization Advice

0130 Authorization Advice Response

Financial Transaction Messages

The Financial Transaction messages handle ATM and POS transactions generated by cardholders using their access cards at terminals driven by an acquirer or at terminals connected to the Connex

System.

RIF.: J-00259842-5


CAPITULO

IV PAGINA

8


FECHA:

26/04/2011


Negative File Maintenance Messages

The Negative File Maintenance messages are used by issuers who choose Stand-In (Delay) processing when communication is lost between the issuer and the Connex

System. The Negative File Maintenance messages allow the issuer to maintain the Negative File while on-line to the Connex System.

An issuer's Negative File can be completely replaced during a scheduled system outage. Before production and during certification testing, the issuer forwards a tape of Negative File messages to the network office.

Authorization Processor (AP) Maintenance Messages

Authorization Processor (AP) Maintenance messages perform AP cardholder and account maintenance on-line. These messages should only be used if a positive cardholder file resides in the Connex

System. In order to use these messages, AP must be configured into your system.

Reversal Messages

These messages inform the sender of the original message that the message cannot be processed as instructed. Following are some reasons why a Reversal message is sent:

The message cannot be delivered. The message cannot be processed. The message has been canceled by the receiver.

RIF.: J-00259842-5


CAPITULO

IV PAGINA

9


FECHA:

26/04/2011


Reconciliation/Totals Messages

These messages are used by the processor to communicate settlement-related information to the acquirer or issuer. All statistics are totals since the last settlement cutoff.

Administrative Messages

Administrative messages pass system-related information between the system and the issuer.

RIF.: J-00259842-5


CAPITULO

IV PAGINA

10


FECHA:

26/04/2011


Network Management Messages

Network Management messages are used to coordinate system or network events or tasks, and to communicate network status conditions. Within each network management request and response message is a related Network Management Information Code data element that is used to describe a specific purpose or function of each message. Refer to Network Management Information Codes (bit 070) for detailed information on the codes that are used within this message series.

Message Arrangement Each FIS ISO message is arranged as follows:

Message description Message structure

Message Description

The message description provides the purpose of the message along with suggestions for processing. Each definition includes a reference to the originator of the message and the expected response.

Message Structure

The message structure is provided in chart form. The following information is included in the chart for each message:

Bit Number Data Element Name Format Attributes Status Notes

RIF.: J-00259842-5


CAPITULO

IV PAGINA

11


FECHA:

26/04/2011


Bit Number and Data Element Name

In addition to providing information regarding which data elements are being sent in a message, the Bit Number is a key to finding a complete description of a data element in Data Element Definitions.

Format

This column indicates the format of the data element, where applicable. Following is a legend for the abbreviations used under this column.

Attributes

Los atributos representan el tipo y la longitud de la data de los data elementos. Ambas informaciones se muestran abreviadas en la estructura del mensaje.

RIF.: J-00259842-5


CAPITULO

IV PAGINA

12


FECHA:

26/04/2011


RIF.: J-00259842-5


CAPITULO

IV PAGINA

13


FECHA:

26/04/2011


Fixed Length Data Elements

All fixed length n data elements are assumed to be right justified with leading zeros. All other fixed length data elements are left-justified with trailing blanks. All fixed length b data elements are assumed to be left-justified with trailing zeros.

Variable Length Data Elements

Throughout this section, the length of the variable length sub-element is shown as if the numeric packing option is not set. If the numeric packing option is set, all length sub-elements are one byte long.

The length of a variable data element may exceed the maximum message size defined by FIS. When this occurs, only the message size defined by FIS will pass through the processor.

Status Information

The data element status provides additional information regarding the completion of the data element. The message structure chart contains an abbreviation of the status for each data element. Following are the different data element statuses and a description of each.

Status Descripcin R (Requerido) o M (Mandatorio)

The data element is required or mandatory.

C (Condicional) The data element is required when specific conditions are satisfied. The applicable conditions are identified in the Notes column of the message structure chart.

O (Opcional)

The data element is optional and may be provided at the option of the originator of the message. If the data element is present in the message, it may be forwarded.

F (Futuro) Currently unsupported.

Notes Any special notes or format information is provided in this column. Do not rely solely on this information; refer to Data Element Definitions for additional detail and data element edits.

RIF.: J-00259842-5


CAPITULO

V PAGINA

14

FORMATO DE MENSAJES SUICHE 7B CAMBIO N

FECHA:

26/04/2011


FORMATO DE MENSAJES SUICHE 7B En el proceso de intercambio de la mensajera ISO 8583, se han identificado diferentes campos que permitirn estandarizar las aplicaciones de los miembros de la Red con las funcionalidades que se han activado. En el presente documento, estos campos han sido identificados a travs de colores que permiten resaltar su USO y al mismo tiempo simplificar el anlisis en la seleccin de dichos campos dentro de todas las estructuras de los formatos de los mensajes, siempre tomando como base los documentos y servicios autorizados por FIS.

Campos Modificados y Adaptados por la Red SUICHE 7B.

Campos Utilizados por la Red SUICHE 7B, dentro del Formato de la Mensajera ISO 8583 de FIS.

Campos Adicionales que deben ser Contemplados dentro del Formato de la Mensajera ISO 8583 de FIS para la Red SUICHE 7B.

Datos EMV

MESSAGES 0100/0101 CHECK GUARANTEE/CONFORMACIN CHEQUES REQUEST

Description

Either the Connex System generates the 0100 Check Verification/Guarantee (Conformacin Cheques) Request message in response to an incoming message from a direct-attached device, or an acquirer generates it in response to a foreign item received at one of its devices. In either situation, the Connex System routes the 0100 request to the appropriate issuer to process check verification and check guarantee transactions. This structure must be used if verification lookup is based on information other than the PAN, such as Driver's License Number, MICR number or Cdula de Identidad Number (C.I.).

Generated by

Connex System or acquirer

Expected Response

0110 Check Verification / Guarantee (Conformacin Cheques) Response from the issuer

RIF.: J-00259842-5


CAPITULO

V PAGINA

15


FECHA:

26/04/2011


Message Structure

Following is the structure of the 0100/0101 Check Guarantee / Conformacin de Cheque Request message.

Bit No.

Status Nombre del Elemento

Formato Atributo Descripcin

1 R Bit Map, Secondary

b 64

3 R Processing Code nP 6 Valid codes are listed in Processing Codes

4 R Amount, Transaction

nP 12

7 R Transmission Date and Time

MMDDhhmmss nP 10

11 R System Trace Audit Number

nP 6

12 R Time, Local Transaction

hhmmss nP 6

13 R Date, Local Transaction

MMDD nP 4

18 R Merchant Type nP 4 Required for transactions from a point-of-sale device.

19 C Acquiring Institution Country Code

nP 3 Sent if Acquiring Institutions Country Code is not the same as the Issuing Institutions Country Code.

23 O Card Sequence Number

n P3 El BIT 23 debe estar presente en todas las transacciones EMV donde el BIT 22 = 05x el cual incluye la certificacin del sistema EMV con la data del BIT 55 y donde la aplicacin PAN Sequence Number (Tag 5F34) es provisto por el EMV de la Tarjeta al Terminal.

27 O Authorization Identification Response Length

nP 1 May be used by acquirers that cannot accept 6-byte long authorization ID

28 C Amount, Transaction Fee

x + n 8 x = C (credit) or D (debit) amount. Required when the defined fee is present. The fee may be a surcharge, rebate, or transaction fee.

32 R Acquiring Institution Identification Code

LLVAR nP..11

RIF.: J-00259842-5


CAPITULO

V PAGINA

16


FECHA:

26/04/2011


33 R Forwarding Institution Identification Code

LLVAR nP..11 Required if different from Acquiring Institution Identification Code (bit032).

37 R Retrieval Reference Number

an 12

41 R Card Acceptor Terminal Identification

an 8

42 O Card Acceptor Identification Code

an 15 This data element is required only if it is requested by the issuer.

43 R Card Acceptor Name and Location

an 40

48 C Merchant / Bank Name

LLLVAR ans..025 Reserved for private data unique to private institutions.

49 R Currency Code, Transaction

nP 3

54 O Additional Amounts

LLLVAR ans..120 This data element is sent if transaction-related amounts are present.

55

O Integrated Circuit Card (ICC) System-Related data

LLLVAR

b 255;

El Sistema relativo a las tarjetas EMV, contiene la data de las tarjetas con EMV en el BIT 55, formateada de acuerdo con lo estipulado en las especificaciones EMV 2000

58 R National Point-of-Service Condition Code

LLLVAR nP..011 Either this bit or bit 025 must be returned.

59 O National Point of- Service Geographic Data

LLLVAR an..017 May be required to qualify for lower fees from VISA or MasterCard. This data element is required only if it is requested by the issuer.

61 O Acquirer Transport Data

LLLVAR ans..030 This data element is echoed to the acquirer in the response to their request, but it is not forwarded to the issuer.

100 R Receiving Institution ID Code

LLVAR np.011 This data element indicates the ID of the check guarantor.

102 R Account ID 1 LLVAR ans..28 May be required in outbound messages if the processor looks up account numbers of the issuer.

RIF.: J-00259842-5


CAPITULO

V PAGINA

17


FECHA:

26/04/2011


123 C AVS/Check Auth Data

LLLVAR ans..050 Three formats are supported: drivers license, MICR number, and plastic card number. (R) Requerido para la Conformacin Cheques (CI, Cdula de Identidad y Nmero de Cheque de acuerdo al formato indicado abajo). (R)para Cambio de Clave

127 C Acquirer Trace Data

LLLVAR ans..050 This data element is required only if it is requested by the issuer.

128 C Message Authentication Code

b 64 This data element is required when MACing messages and at least one of the data elements from 065-127 is present in the message.

Nota: La estructura del BIT 123 (Msgs. 0100, 0120 y 0200) depende de la transaccin u operacin a realizarse; es decir, para la Conformacin de Cheques, y operaciones originadas en los Puntos de Ventas el formato es el siguiente:

Posicin Descripcin 1 2 CI Indica la Cdula de Identidad

3 4 Blancos

5 26

Nmero de la Cdula de Identidad, alineado a la derecha y relleno de ceros (0) a la Izquierda, para la Conformacin de Cheques y transacciones de POS.

27 38

Nmero de Cheque, cuando es Conformacin de Cheques o CVC2 para operaciones con tarjetas de Dbito y Crdito alineados a la Derecha y relleno de Ceros (0) a la Izquierda.

Nota: La estructura del BIT 123 (MSG. 0100, 0110) que se muestra a continuacin es usada para realizar los cambios de clave en los ATM conectados directamente al CONNEX (Proccesing Code 900000).

RIF.: J-00259842-5


CAPITULO

V PAGINA

18


FECHA:

26/04/2011


Nota: Los Campos numricos deben ser Justificados a la derecha y rellenos de ceros (0) a la Izquierda

RIF.: J-00259842-5


CAPITULO

V PAGINA

19


FECHA:

26/04/2011


0110 AUTHORIZATION RESPONSE

Description The Connex System or the issuer generates the 0110 Authorization Response message in response to a 0100 Authorization Request or a 0101 Authorization Request repeat. The same structure is used for both accepted and denied transactions. The acquirer receives this message and processes or denies the cardholder's request based on information in the 0110 message. The Connex System generates a 0110 response if the system rejects the 0100 request (for example, a PIN Validation Failure of an Invalid Transaction Type) or if the system handles the transaction in Stand-In processing (for example, 0100 requests have timed out or the issuer is not logged on).

Generated by

Connex System or issuer

Expected Response

None

Message Structure

Following is the structure of the 0110 Authorization Response message.

Bit No.

Status Nombre del Elemento


1 C Bit Map, Secondary

b 64 Required if data elements specified in the Secondary Bit Map (065 to128) are used.

3 R Processing Code

nP 6 Valid codes are listed.


nP 12 Copied from the 0100 message.


MMDDhhmmss nP 10




hhmmss nP 6 Copied from the 0100 message.


MMDD nP 4 Copied from the 0100 message.

RIF.: J-00259842-5


CAPITULO

V PAGINA

20


FECHA:

26/04/2011


23

O

Card Sequence Number

n P3 El BIT 23 debe estar presente en todas las transacciones EMV donde el BIT 22 = 05x el cual incluye la certificacin del sistema EMV con la data del BIT 55 y donde la aplicacin PAN Sequence Number (Tag 5F34) es provisto por el EMV de la Tarjeta al Terminal.


x + n 8 x = C (credit) or D (debit) amount. Required if received in the 0100 message.


an 12 In a pre-authorized request, this must be the same value as in pre-authorization.

38 C Authorization Identification Response

an 6 May be used by the authorizer to return an authorization number for accepted transactions.

39 R Response Code

an 2 If the response code is 30, then Additional Response Data (bit 044) contains the bit number in error.


an 8 Copied from 0100 message.

44 C Additional Response Data

LLVAR an..25 If the response code (bit 039) is 30, then this bit contains the bit number in error.


nP 3 Copied from 0100 message.

55

R Integrated Circuit Card (ICC) System-Related data

LLLVAR

b 255;



LLLVAR ans..030 Required if in the 0100 message.


LLLVAR ans..050 This data element is required only if it is requested by the acquirer.



RIF.: J-00259842-5


CAPITULO

V PAGINA

21


FECHA:

26/04/2011


0200/0201 FINANCIAL TRANSACTION REQUEST

Description

The 0200 Financial Transaction Request message is sent to request approval for a transaction which, if approved, can be immediately applied to the cardholder's account for billing or statement purposes. Either the Connex System generates the 0200 request message in response to an incoming message from a direct-attached device, or an acquirer generates it in response to a foreign item received at one of its devices. In either situation, the Connex System routes the 0200 request to the appropriate issuer for approval or denial of the transaction.

Generated by


Expected Response

0210 Financial Transaction Request Response from the issuer

Message Structure

Following is the structure of the 0200/0201 Financial Transaction Request message.

Bit Status Nombre del Elemento



b 64 Required if data elements specified in the Secondary Bit Map (065 to128) are used.

2 R Primary Account Number

LLVAR nP..19 Required if PAN manually entered.One of these data elements isrequired: 002, 035, or 045.

3 R Processing Code

nP 6 Valid codes are listed.


nP 12

5 C Amount, Transaction

nP 12 Require if transanction and settlement currencies are different


MMDDhhmmss nP 10

9 C Conversion Rate, Settlement

nP 8 Require if transanction and settlement currencies are different

RIF.: J-00259842-5


CAPITULO

V PAGINA

22


FECHA:

26/04/2011


10 C Conversion

Rate, Cardholder Billing

nP 8 This data is logged only


nP 6


hhmmss nP 6


MMDD nP 4

14 C Date, Expiration

YYMM nP 4

15 R Date, Settlement

MMDD nP 4

16 C Date, Conversion

MMDD nP 4 Require if transanction and settlement currencies are different

17 R Date, Capture MMDD nP 4 This data element is required only if it is requested by the issuer.

18 C Merchant Type nP 4 Required for transactions from a point-of-sale device.

19 C Acquiring Institution Code


22 O Point-of-Service Entry Mode.

nP 3 Required for transactions from a point-of-sale device or from an ATM acquirer participating in a CVV program. Valid codes are listed at the end of this manual

23 O Card Sequence Number

nP 3 May be used to send a card sequence (plastic) number if Track 2 (bit 035) is not sent.

26 C Point-of- Service PIN Capture Code

nP 2 Required if PIN data (052) is in the message, and the device cannot accept 12-digit PINs.

27 O Authorization Identification Response Length

nP 1 May be used by acquirers that cannot accept 6-byte long authorization ID responses (bit 038).

RIF.: J-00259842-5


CAPITULO

V PAGINA

23


FECHA:

26/04/2011


28 C Amount,

Transaction Fee

x + n 8 x = C (credit) or D (debit) amount. Required when the defined fee is present. The fee may be a surcharge, rebate, or transaction fee, (R) Si hay Comisin Adicional x = D


LLVAR nP..11



35 C Track 2 Data LLVAR

nsP..37 Required if Track 2 was machine read. One of these data elements is required: 002, 035, or 045.




an 8




an 40


LLLVAR ans..025


nP 3

50 C Currency Code, Settlement

nP 3 Required if transaction and settlement currencies are Different.

52 C PIN Data. B 64 Required if a PIN is required during authorization processing.


LLLVAR ans..120 Sent if transaction-related amounts or balances are present.

RIF.: J-00259842-5


CAPITULO

V PAGINA

24


FECHA:

26/04/2011


55

O Integrated Circuit Card (ICC) System-Related data

LLLVAR

b 255;


58 R National Point-of- Service Condition Code

LLLVAR nP..011 Although either this bit or bit 025 is required, DEPS prefers that you use this bit for all transactions. Valid codes are listed at the end of manual.

59 O National Point-of- Service Geographic Data

LLLVAR an..017 May be required to qualify for lower fees from VISA or MasterCard. This data element is required only if it is requested by the issuer.


LLLVAR ans..030 This data is echoed to the acquirer in the response to their request, bit it is not forwarded to the issuer.

102 C Account ID 1 LLVAR ans..28 May be required in outbound messages if the processor looks up account numbers for the issuer.

103 C Account ID 2 LLVAR ans..28 May be required in outbound messages if the processor looks up account numbers for the issuer, and the transaction is a transfer. (R) Si es una Transferencia Interbancaria, indica la Cuenta Destino o el Nmero de Tarjeta de Crdito a cancelar. Si es un Pago de Servicio colocar el NIS, No. Telf. etc.

104 C Transaction Description

LLLVAR ans..100 Sent if available. (R) Indica el tipo de la transaccin en las Operaciones de las Transferencias Interbancaria y Pago de Servicio.

120 O Account Qualifiers

LLLVAR an..006 This data element is required only if it is requested by the issuer.

122 O Sponsor Bank ID

LLLVAR an..011 This data element is required only if it is requested by the issuer.

RIF.: J-00259842-5


CAPITULO

V PAGINA

25


FECHA:

26/04/2011


123 C AVS/Check

Auth

Data

LLLVAR ans..050 Three formats are supported: drivers license, MICR number, and plastic card number.

(R) Requerido de acuerdo a los formatos indicados a continuacin. En ATM para la Pregunta de Desafo PD en la Transaccin de RETIRO y en las operaciones de POS: CI, la Cdula de Identidad, Nmero de Cheque, CVC2. En las Transferencia Interbancaria: y Pago de Servicios igual que la Pregunta de Desafo PD de retiro.


LLLVAR ans..050 This data element is required only if it is requested by the issuer.



A continuacin algunas observaciones o ampliacin de la descripcin de los campos utilizados por la Red SUICHE 7B para los mensajes 0200/0210.: Comisin Adicional Bit 028.- Esta data elemento es Condicional y contiene la informacin correspondiente a la comisin Adicional y mantiene el siguiente formato:

x + n 8 x = C (credit) or D (debit) amount. Required when the defined fee is present. The fee may be a surcharge, rebate, or transaction fee. (R) Si hay Comisin Adicional

x + n 8 , donde x = al monto que se debe debitar D o acreditar C de acuerdo al valor de la comisin adicional y + n 8 significa el monto de la comisin en s, el cual es numrico de 8 posiciones. MSGS. 0200/0210, se debe colocar el identificador D que significa que la transaccin a ejecutar tiene un cargo, el cual debe ser aceptado por el Tarjetahabiente y que se coloca a continuacin del indentificador referido. MSGS. 0420/0430, se debe utilizar el identificador C seguido del monto de la comisin adicional, a fin de poder acreditar el monto de la comisin. En Resmen: Para cobrar la comisin de adquiriente o cargo adicional se deben cumplir estrictamente las siguientes premisas:

BIT 004 - AMOUNT TRANSACTION (Monto de la Transaccin nP 12) Se le asignar la cantidad del monto solicitado por el tarjetahabiente.

RIF.: J-00259842-5


CAPITULO

V PAGINA

26


FECHA:

26/04/2011


BIT 028 AMOUNT, TRANSACTION FEE (Monto del recargo x + 8) Se le asignar la cantidad del recargo aprobado por el cliente. El campo debe ser

numrico relleno de ceros y el valor de x debe ser 0, D o C, donde :

o D o 0 = Monto a debitar o C = Monto acreditar ( en caso de Reverso)

NOTA: Si la transaccin es reversada 0420, el adquirente esta en la obligacin de enviar la opcin C + el importe cobrado. La estructura alfanumrica del Bit 103 en una Transferencia Interbancaria o Pago de Servicios se compone de una serie de dgitos segn se indica en el siguiente formato:

Posicin Descripcin 1 - 28 Si es una Transferencia Interbancaria, indica la Cuenta Destino o el Nmero de Tarjeta

de Crdito a cancelar. Si es un Pago de Servicio colocar el NIS, No. Telf. etc.

Ejemplos: Transferencia Interbancaria: No. de Tarjeta de Crdito: 0164988383040023537

Largo: 016 Nmero Tarjeta: 4958383040023537

Pago de Servicio: (Solo referencial) No. Telefnico: 00702129988378

Largo: 007 Cdigo de rea: 0212 Nro. Telefnico: 9988378

La estructura del Bit 104 es de acuerdo a las funciones a realizarse: la Consulta del Beneficiario, la Transferencia Interbancaria y el Pago de Servicio y tiene el siguiente formato:

Posicin Descripcin 1 4 Tipo de Transaccin:

NOMB = si es una Validacin de Beneficiario TRAN = si es una Transferencia Interbancaria PAGO = si es un Pago de Servicio.

5 5 Blanco

6 40 Descripcin o Concepto de la Operacin y en el caso de Pago de Servicios colocar en la posicin (6 9) el Cdigo de Identificacin de la empresa de Servicio y desde la posicin (10 40) el nombre de la empresa.

Nota: Los campos son numricos, justificados a la derecha y rellenos de ceros 0 a la izquierda.

RIF.: J-00259842-5


CAPITULO

V PAGINA

27


FECHA:

26/04/2011


Ejemplos: a. Validacin de Beneficiario:

NOMB Pedro Prez b. Transferencia Interbancaria

TRAN Colegio El ngel c. Pago de Servicios:

PAGO 0001CANTV (Los Bancos SUICHE 7B utilizarn la tabla de Cdigo de Empresa de Servicio, razn por la cual los Bancos Adquirientes debern armar el Bit 104, y ser potestad del Bco. Emisor validarlo o no)

La Red SUICHE 7B es responsable de asignar los cdigos de identificacin de las Empresas de Servicio, la distribucin de las empresas se har en funcin del servicio que preste y en este sentido se ha hecho la siguiente clasificacin:

Cdigos Desde Hasta

Tipos de Empresa / Servicio

0001 0099 Utilitarias 0100 0199 Telefona Inalmbrica 0200 0299 Franquicias 0300 0399 Clubes 0400 0499 Colegios y Universidades 0500 0599 Organizaciones Gubernamentales

A continuacin, los cdigos asignados:

Cdigo Empresa / Servicio 0001 CANTV 0002 EDC 0003 HIDROCAPITAL 0101 F-MOVISTAR 0102 MOVILNET 0103 PP-MOVISTAR 0104 PP-MOVILNET 0105 FMOVILNET 0106 PP-DIGITEL 0107 INTERCABLE 0108 DIRECT TV 0401 UCV Universidad Central de Venezuela 0402 USB Universidad Simn Bolvar 0403 USM Universidad Santa Mara 0404 UNIMET Universidad Metropolitana

RIF.: J-00259842-5


CAPITULO

V PAGINA

28


FECHA:

26/04/2011


0405 URBE Universidad Rafael Belloso Chacn 0406 UCAB Universidad Catlica Andrs Bello

Nota: La estructura del Bit 123 (Msg. 0100, 0120 y 0200) depende de la transaccin u operacin a realizarse; es decir, para la Conformacin de Cheques y las operaciones originada en los Puntos de Venta (POS) el formato es el siguiente:

Posicin Descripcin

1 2 CI Indica la Cdula de Identidad

3 4 Blancos

5 26 Nmero de la Cdula de Identidad, alineado a la derecha y relleno de ceros (0) a la Izquierda, para la Conformacin de Cheques y transacciones originadas en Puntos de Venta.

27 38 Nmero de Cheque, cuando es Conformacin de Cheques o CVC2 para operaciones con tarjetas de Dbito y Crdito alineados a la Derecha y relleno de Ceros (0) a la Izquierda.

Asimismo, para las Operaciones de RETIRO, TRANSFERENCIA INTERBANCARIA y PAGO DE SERVICIOS realizada en los ATM, la estructura del Bit 123 en el Msg. 0200 es como sigue:

Posicin Descripcin

1 2 "PD" Preguntas de Desafo (2) posiciones constante alfanumrica

3 - 4 TIPO DE PREGUNTA "99" dos (2) dgitos numricos cuyos valores son: "01" Primero dos dgitos de la Cdula de Identidad "02" ltimos dos dgitos de la Cdula de Identidad "03" Da de nacimiento (Uso Futuro) "04" Mes de nacimiento (Uso Futuro) "05" Ao de nacimiento (Uso Futuro) "06" ltimos dos dgitos de su Cuenta Corriente (Uso Futuro)

5 12 RESPUESTA "99999999" Ocho (8) dgitos numrico justificado a la derecha y relleno de ceros 0 a la izquierda.

Ejemplo: 012PD0100000010 Largo: 012 Tipo: PD Pregunta No: 01 Primeros dos dgitos de la cdula de identidad Respuesta: 00000010

RIF.: J-00259842-5


CAPITULO

V PAGINA

29


FECHA:

26/04/2011


Nota: El cdigo de respuesta igual a "80" es designado para la respuesta INCORRECTA de la misma.

Cdigo de Rechazo: A fin de complementar la informacin relativa al cdigo de rechazo que utilizaremos en las Preguntas de Desafo (cdigo 80), requerimos normar los nmeros de intentos fallidos que deben permitirse en el Banco Emisor y el posterior cdigo que deben enviar a la Red. En tal sentido y basndonos en la forma como en la actualidad estn manejando las operaciones rechazadas por Pn Invlido, la Red SUICHE 7B propone establecer los mismos lmites que actualmente el emisor maneja por este concepto y aplicarlos a las operaciones rechazadas por PD invlida y posteriormente enviar a la Red el cdigo que finalmente asociaron a la accin que se aplic a la tarjeta que efectu la operacin (Ejemplo: Cdigos: 75, 62, etc.). (Cdigos de Respuesta del CONNEX). De acuerdo a la experiencia recogida con algunos bancos que estn certificando esta operacin, se est manejando un lmite mnimo de 3 intentos fallidos y un mximo de 5 para posteriormente responder el cdigo de error correspondiente. En cualquiera de los casos es potestad del Banco Emisor establecer este lmite.

Esquema Transaccional de una Operacin de Transferencia Interbancaria

El Banco Adquiriente de la transaccin es el Banco que tiene la Cuenta Destino o Receptora de los fondos y la Cuenta Receptora debe estar Afiliada en el Banco Emisor:

Dispositivo Banco Adquiriente Red S7B Banco Emisor

Requerimiento 0200 0200

Respuesta 0210 0210c)

PAN Tarjeta Cliente f)

Notificar Pago h)

a)0200

Respuesta 0210 0210

PAN Tarjeta Cliente b)

Notificar Pago d)

0200

0210

PAN Tarjeta Cliente

Notificar Pago

0200 0200



Notificar Pago h)

a)0200 0200



Notificar Pago h)

a)0200

0210

Verifica existencia de la Cuenta Destino de los Fondos

b)

Hace el Abono aCuenta Destinod)

0200

0210

Flujo de los Fondos

Verifica Afiliacin yDisponibilidadde los Fondos y hace el Cargocorrepondiente

Dispositivo Banco Adquiriente Red S7B Banco Emisor

Requerimiento 0200 0200



Notificar Pago h)

a)0200

Respuesta 0210 0210


Notificar Pago d)

0200

0210

PAN Tarjeta Cliente

Notificar Pago

0200 0200



Notificar Pago h)

a)0200 0200



Notificar Pago h)

a)0200

0210

Verifica existencia de la Cuenta Destino de los Fondos

b)

Hace el Abono aCuenta Destinod)

0200

0210

Flujo de los Fondos

Verifica Afiliacin yDisponibilidadde los Fondos y hace el Cargocorrepondiente

a) El Tarjetahabiente hace el requerimiento al Banco Adquiriente para realizar

la Transferencia Interbancaria. b) El Banco Adquiriente, solicita el Nmero de Cuenta Receptora de los

Fondos y verifica la existencia de la misma, segn sus polticas internas antes de proceder a enviar la transaccin al Banco Emisor.

c) El Banco Adquiriente ensambla el Msg. 0200 de Transferencia Interbancaria, con los siguientes Campos Mandatorios o Requeridos en adicin a los campos regulares; i) BIT 3 Processing Code 48COCD ii) BIT 4 Monto de la Transferencia. iii) BIT 22 Point of Service Entry Mode iv) BIT 23 Card Sequence Number v) BIT 35 Track II del Tarjetahabiente.

RIF.: J-00259842-5


CAPITULO

V PAGINA

30


FECHA:

26/04/2011


vi) BIT 52 PIN del Tarjetahabiente. vii) BIT 55 ICC System-Related Data viii) BIT 58 National Point-Of-Service Condition Code ix) BIT 103 Cuenta Receptora de los Fondos. x) BIT 104 TRAN y el Concepto de la Operacin. xi) BIT 123 Introduzca los primeros dos o ltimos dgitos de la Cdula de

Identidad del Tarjetahabiente d) El Banco Emisor verifica la afiliacin de la cuenta, la disponibilidad de los

Fondos, confirma el Dbito a la cuenta del Tarjetahabiente y notifica al Banco Adquiriente a travs de un Msg. 0210 la completitud de la transaccin.

e) El Banco Emisor le paga el monto de la Transaccin al Banco Adquiriente en el proceso de Compensacin de Capitales correspondiente a la fecha en que se efectu la misma.

Esquema Transaccional para la Operacin de Pago de Servicios

Dispositivo Banco Adquiriente Red Banco Emisor

Requerimiento 0200 0200 Autorizar Pago



Notificar Pago h)

a)

Empresa / Servicio Flujo de los Fondos

0200 Autorizar Pago

Respuesta 0210 0210


Notificar Pago d)

Empresa / Servicio

0200 Autorizar Pago

0210

PAN Tarjeta Cliente

Notificar Pago






Notificar Pago h)

a)

Empresa / Servicio





Notificar Pago h)

a)


0200 Autorizar Pago

Respuesta 0210 0210


Notificar Pago d)

Empresa / Servicio

0200 Autorizar Pago

0210

PAN Tarjeta Cliente

Notificar Pago


a) El Tarjetahabiente hace el requerimiento al Banco Adquiriente para realizar el Pago del Servicio.

b) El Banco Adquiriente se encarga de verificar el Saldo Deudor y la Existencia del Servicio (NIS, No. Telf., etc.) con las empresas correspondientes segn sus polticas internas, antes o despus de obtener los fondos.

c) El Banco Adquiriente ensambla el Msg. 0200 de Pago de Servicios, con los siguientes Campos Mandatorios o Requeridos en adicin a los campos regulares; i) BIT 3 Processing Code 50CO00 (Donde 00 = Cdigo Genrico para

Pago de Servicio). ii) BIT 4 Monto del Pago. iii) BIT 22 Point of Service Entry Mode iv) BIT 23 Card Sequence Number v) BIT 35 Track II del Tarjetahabiente o Cliente. vi) BIT 52 PIN del Cliente. vii) BIT 55 ICC System-Related Data viii) BIT 58 National Point-Of-Service Condition Code ix) BIT 103 No. Telefnico, NIS, Contrato, Celular, etc.

RIF.: J-00259842-5


CAPITULO

V PAGINA

31


FECHA:

26/04/2011


x) BIT 104 PAGO, Cdigo Identificador de la Empresa de Servicio en blanco y el Concepto de la Operacin.

xi) BIT 123 Introduzca los primeros dos o ltimos dgitos de la Cdula de Identidad del Tarjetahabiente

d) El Banco Emisor confirma el Dbito a la cuenta del cliente y notifica al banco Adquiriente a travs de un MSG. 0210 la completitud de la transaccin.

e) El Banco Emisor le paga el monto de la Transaccin al Banco Adquiriente en el proceso de Compensacin de Capitales correspondiente a la fecha en que se efectu la misma.

0210 FINANCIAL TRANSACTION RESPONSE Description The Connex System or the issuer generates the 0210 Financial Transaction Response message in response to either a 0200 Financial Transaction Request or a 0201 Financial Transaction Request repeat. The same structure is used for both accepted and denied transactions. The acquirer receives this message and processes or denies the cardholder's request based on information in the 0210 message. An approval initiates the updating of settlement or reconciliation controls between the acquirer and card issuer.

Generated by

Connex System or issuer

Expected Response

None

Message Structure Following is the structure of the 0210 Financial Transaction Response message.




b 64 Required if data elements specified in the Secondary Bit Map (bits 065 to 128) are used.

2 C Primary Account Number

LLVAR nP..19 Required if received in the 0200 message.

RIF.: J-00259842-5


CAPITULO

V PAGINA

32


FECHA:

26/04/2011


3 R Processing Code nP 6 Normally copied from the 0200

message. Bytes 3-4 and 5-6 may be changed from an unspecified account type (00) to a specified account type. Processing Codes are listed at the end of manual.



5 C Amount, Settlement

nP 12 Required if transaction and settlement currencies are different.


MMDDhhmmss nP 10

8 O

Amount,

Cardholder

Billing Fee

nP 8

Debe ser retornado por el Banco Emisor, para informar al Banco Adquiriente del monto de la comisin cobrada al tarjetahabiente.


nP 8 Required if transaction and settlement currencies are different.

10 C Conversion Rate, Cardholder Billing

nP 8 This data is logged only.




Hhmmss nP 6 Copied from the 0200 message.


MMDD nP 4 Copied from the 0200 message.

15 R Date, Settlement MMDD nP 4

16 C Date, Conversion MMDD nP 4 Returned if available. Required if transaction and settlement currencies are different.

18 O Merchant Type nP 4 May be returned by the issuer if received in the request and they want this data element returned to them in reversals for late or unsolicited responses.


nP 3 May be returned by the issuer if received in the request and they want this data element returned to them in reversals for late or unsolicited responses.

22 O Point-of- Service Entry Mode

nP 3 May be returned by the issuer if received in the request and they want this data element returned to

RIF.: J-00259842-5


CAPITULO

V PAGINA

33


FECHA:

26/04/2011


them in reversals for late or unsolicited responses.

RIF.: J-00259842-5


CAPITULO

V PAGINA

34


FECHA:

26/04/2011


23 O Card Sequence

Number nP 3 May be returned by the issuer if

received in the request and they want this data element returned to them in reversals for late or unsolicited responses.


x + n 8 x = C (credit) or D (debit) amount. Required if received in the 0200 message.

30 C Amount, Transaction Processing Fee

x + n 8 Requerido para notificar el pago del IDB


LLVAR nP..11


LLVAR nP..11 Required if received in the 0200 message.

35 C Track 2 Data LLVAR nsP..37 Required if received in the 0200 message.


an 12 Copied from the 0200 message.



39 R Response Code an 2 If the response code is 30, then Additional Response Data (bit 044) contains the bit number in error.


an 8 Copied from the 0200 message.


an 15 May be returned by the issuer if received in the request and they want this data element returned to them in reversals for late or unsolicited responses.

43 O Card Acceptor Name and Location

an 40

44 O Additional Response Data

LLVAR an..25 If the response code (bit 039) is 30, then this bit contains the bit number in error.

RIF.: J-00259842-5


CAPITULO

V PAGINA

35


FECHA:

26/04/2011



LLLVAR ans..025 May be returned by the issuer if received in the request and they want this data element returned to them in reversals for late or unsolicited responses.



50 C Currency Code, Settlement

nP 3 Required if the transaction and settlement currencies are different.


LLLVAR ans..120 Returned if additional amounts are received in the 020x message or balances are received from the Authorizer.

55 O Integrated Circuit Card (ICC) System-Related data

LLLVAR b 255; El Sistema relativo a las tarjetas EMV, contiene la data de las tarjetas con EMV en el BIT 55, formateada de acuerdo con lo estipulado en las especificaciones EMV 2000

58 R National Point-of-Service Condition Code

LLLVAR nP..011 Either this bit or bit 025 must be returned.

59 O National Point-of- Service Geographic Data

LLLVAR an..017


LLLVAR ans..030

102 C Account ID 1 LLVAR ans..28

103 C Account ID 2 LLVAR ans..28

104 C Transaction Description

LLLVAR ans..100 May be returned by the issuer if received in the request and they want the data element returned to them in reversals for late or unsolicited responses.

120 O Account Qualifiers

LLLVAR an..006 May be returned by the issuer if received in the request and they want this data element returned to them in reversals for late or unsolicited responses.

122 O Sponsor Bank ID LLLVAR an..011 May be returned by the issuer if received in the request and they want this data element returned to them in reversals for late or unsolicited responses.

RIF.: J-00259842-5


CAPITULO

V PAGINA

36


FECHA:

26/04/2011


123 C AVS/Check Auth

Data LLLVAR ans..050 Required if the issuer returns the

address verification results.


LLLVAR ans..050 This data element is required only if it is requested by the acquirer.

0220/0221 FINANCIAL TRANSACTION ADVICE Description

The Connex System generates the 0220 Financial Transaction Advice message in response to a Store-and-Forward Stand-In authorization, or an acquirer generates it in response to a forced post generated by one of its endpoints. In both cases, the 0220 message is sent to the issuer. The issuer must accept and process the 0220/0221 message.

Generated by


Expected Response

0230 Financial Transaction Advice Response from the issuer

Message Structure Following is the structure of the 0220/0221 Financial Transaction Advice message.



- R Message Type nP 4 Value 0220 for initial advice; 0221 for repeat advice.

- R Bit Map, Primary b 64

1 C Bit Map, Secondary b 64 Secondary Required if data elements specified in the Secondary Bit Map (065 to128) are used.

2 C Primary Account Number

LLVAR nP..19 Required if PAN manually entered. One of these data elements is required: 002 or 035.

3 R Processing Code nP 6 Valid codes are listed in Appendix B.

4 R Amount, Transaction nP 12

RIF.: J-00259842-5


CAPITULO

V PAGINA

37


FECHA:

26/04/2011


5 C Amount, Transaction nP 12 Required if transaction and

settlement currencies are different.


MMDDhhmmss nP 10


Required if transaction and settlement currencies are different.

10 C Conversion, Rate, Cardholder Billing.

This data is logged only


nP 6


hhmmss nP 6


MMDD nP 4

14 C Date, Expiration YYMM nP 4

15 R Date, Settlement MMDD nP 4 M

16 C Date Conversion MMDD nP 4 Required if transaction and settlement currencies are different.

17 R Date, Capture MMDD nP 4 This data element is required only if it is requested by the issuer.

18 C Merchant Type nP 4 Required for transactions from a point-of-sale device.



22 C Point-of-Service Entry Mode.

nP 3 Required for transactions from a point-of-sale device or from an ATM acquirer participating in a CVV program. Valid codes are listed in Appendix B.

28 C Amount, Transaction Feed

x + n8 x = C (credit) or D (debit) amount. Required when the defined fee is present. The fee may be a surcharge, rebate, or transaction fee.


LLVAR nP..11

RIF.: J-00259842-5


CAPITULO

V PAGINA

38


FECHA:

26/04/2011




35 C Track 2 Data LLVAR nsP..37 Required if Track 2 was machine read. One of these data elements is required: 002, 035, or 045.





39 R Response Code an 2


an 8

42 O Card acceptor Identification Code



an 40

48 C Merchant/Bank Name

LLLVAR ans..025 Bank Name Reserved for private data unique to private institutions.


nP 3

50 C Currency Code Settlement

nP 3 Required if the transaction and settlement currencies are different.

54 O Additional Amount LLLVAR a

Mensajeria Suiche7B

Documents

Transcript of Mensajeria Suiche7B