Mensajeria Suiche7B

FIS ISO 8583 PROCESSOR INTERFACE MESSAGE
SPECIFICATIONS GUIDE
(IBM CONNEX V3.4B - Corporacin SUICHE 7B, C. A.)
VERSIN 1.1
Elaborado por:
Firma:
Revisado por:
Firma:
Aprobado por:
Firma:
Alexander Jos Azocar
Francisco Lpez
Giovanni Novellino
Coord. Organizacin y Calidad
Gerente de Tecnologa y Proyectos
Gerente General
26 de Abril de 2011
FIS ISO 8583 PROCESSOR INTERFACE

MESSAGE SPECIFICATIONS GUIDE
RIF.: J-00259842-5
FECHA:
CONTROL DE CAMBIOS
25/05/2011
Cambio
N
Descripcin del Cambio
Fecha
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
Observaciones
Elaborado por:
Revisado por:
Aprobado por:
Firma:
Firma:
Firma:
Nombre:
Nombre:
Nombre:
Alexander Azocar
Cargo:
Coordinador de Organizacin y
Calidad
Ubicacin Electrnica
Francisco Lpez
Cargo:
Gerente de Tecnologa y Proyectos
Giovanni Novellino
Cargo:
Gerente General
Sistema de Gestin de la Calidad (Aplicacin)
FIS ISO 8583 PROCESSOR INTERFACE MESSAGE SPECIFICATIONS GUIDE
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
0110 AUTHORIZATION RESPONSE...............................................................................................19
Description ....................................................................................................................................19
RIF.: J-00259842-5

TABLA DE CONTENIDO
FECHA:
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
0220/0221 FINANCIAL TRANSACTION ADVICE ............................................................................36
Description ....................................................................................................................................36
0230 FINANCIAL TRANSACTION ADVICE RESPONSE ................................................................40
Description ....................................................................................................................................40
0420/0421 ACQUIRER REVERSAL ADVICE...................................................................................42
Description ....................................................................................................................................42
0430 ACQUIRER REVERSAL RESPONSE .....................................................................................47
Description ....................................................................................................................................47
0620 ADMINISTRATIVE ADVICE.....................................................................................................49
Description ....................................................................................................................................49
0800 NETWORK MANAGEMENT REQUEST..................................................................................49
Description ....................................................................................................................................49
0810 NETWORK MANAGEMENT RESPONSE ...............................................................................50
Description ....................................................................................................................................50
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

TABLA DE CONTENIDO
FECHA:
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

TABLA DE CONTENIDO
FECHA:
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

PAGINA
I
CAMBIO N
USO DE ESTE DOCUMENTO
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
Nombre del Usuario
Tipo de Documento
Fsico
Gerencia de Tecnologa y Proyectos
Instituciones Miembros
Coordinacin de Organizacin y Sistemas
Cantidad de Ejemplares.
Electrnico.
Original
Copia
CAPITULO

RIF.: J-00259842-5
PAGINA
II
CAMBIO N
INTRODUCCIN
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
Effective
Date
W/Version
Chapter Change
March 2008
February
2008
V3.4B
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.
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
CAPITULO

RIF.: J-00259842-5
PAGINA
III
CAMBIO N
OVERVIEW
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

PAGINA
III
CAMBIO N
OVERVIEW
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

PAGINA
III
CAMBIO N
OVERVIEW
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.
CAPITULO

RIF.: J-00259842-5
PAGINA
IV
CAMBIO N
MESSAGE STRUCTURE
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.
CAPITULO

RIF.: J-00259842-5
PAGINA
IV
CAMBIO N
MESSAGE STRUCTURE
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

PAGINA
IV
CAMBIO N
MESSAGE STRUCTURE
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 online 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.
CAPITULO

RIF.: J-00259842-5
PAGINA
IV
CAMBIO N
MESSAGE STRUCTURE
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.
CAPITULO

RIF.: J-00259842-5
PAGINA
10
IV
CAMBIO N
MESSAGE STRUCTURE
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

PAGINA
11
IV
CAMBIO N
MESSAGE STRUCTURE
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

PAGINA
12
IV
CAMBIO N
MESSAGE STRUCTURE
FECHA:
26/04/2011
RIF.: J-00259842-5
CAPITULO

PAGINA
13
IV
CAMBIO N
MESSAGE STRUCTURE
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 subelements 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 The data element is required or mandatory.

M (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)
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.
CAPITULO

RIF.: J-00259842-5
PAGINA
14
V
CAMBIO N
FORMATO DE MENSAJES SUICHE 7B
FECHA:
26/04/2011

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
CAPITULO

RIF.: J-00259842-5
PAGINA
15
V
CAMBIO N
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
Bit Map,
Secondary
b 64
Processing Code
nP 6
Amount,
Transaction
nP 12
Transmission
Date and Time
11
System Trace
Audit Number
12
Time, Local
Transaction
hhmmss
nP 6
13
Date, Local
Transaction
MMDD
nP 4
18
Merchant Type
nP 4
Required for transactions from a pointof-sale device.
19
Acquiring
Institution Country
Code
nP 3
Sent if Acquiring Institutions Country

Code is not the same as the Issuing
Institutions Country Code.
23
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
Authorization
Identification
Response Length
nP 1
May be used by acquirers that cannot

accept 6-byte long authorization ID
28
Amount,
Transaction Fee
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.
32
Acquiring
Institution
Identification
Code
MMDDhhmmss
Valid codes are listed in Processing

Codes
nP 10
nP 6
LLVAR
nP..11
RIF.: J-00259842-5
CAPITULO

FECHA:
26/04/2011
33
Forwarding
Institution
Identification
Code
37
Retrieval
Reference
Number
an 12
41
Card Acceptor
Terminal
Identification
an 8
42
Card Acceptor
Identification
Code
an 15
43
Card Acceptor
Name and
Location
an 40
48
Merchant / Bank
Name
49
Currency Code,
Transaction
54
Additional
Amounts
LLLVAR
ans..120
This data element is sent if transactionrelated amounts are present.
55
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
National Point-ofService Condition

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

returned.
59
National Point ofService

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
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
Receiving
Institution ID Code
LLVAR
np.011
This data element indicates the ID of

the check guarantor.
102
Account ID 1
LLVAR
ans..28
May be required in outbound messages

if the processor looks up account
numbers of the issuer.
LLLVAR
nP..11
16
V
CAMBIO N
LLVAR
PAGINA
ans..025
Required if different from Acquiring

Institution Identification Code (bit032).
This data element is required only if it is

Reserved for private data unique to

private institutions.
nP 3
RIF.: J-00259842-5
CAPITULO

PAGINA
17
V
CAMBIO N
FECHA:
26/04/2011
123
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
Acquirer Trace
Data
LLLVAR
ans..050

128
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
12
CI Indica la Cdula de Identidad
34
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

PAGINA
18
V
CAMBIO N
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

PAGINA
19
V
CAMBIO N
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
Formato
Bit Map,
Secondary
b 64
Required if data elements specified in the

Secondary Bit Map (065 to128) are used.
Processing
Code
nP 6
Valid codes are listed.
Amount,
Transaction
nP 12
Copied from the 0100 message.
Transmission
Date and Time
11
System Trace
Audit Number
12
Time, Local
Transaction
13
Date, Local
Transaction
MMDDhhmmss
Atributo
Descripcin
nP 10
nP 6
hhmmss
nP 6
MMDD
nP 4
RIF.: J-00259842-5
CAPITULO

PAGINA
20
V
CAMBIO N
FECHA:
26/04/2011
23
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.
28
Amount,
Transaction
Fee
x+n8

Required if received in the 0100
message.
37
Retrieval
Reference
Number
an 12
In a pre-authorized request, this must be

the same value as in pre-authorization.
38
Authorization
Identification
Response
an 6
May be used by the authorizer to return

an authorization number for accepted
transactions.
39
Response
Code
an 2
If the response code is 30, then Additional

Response Data (bit 044) contains the bit
number in error.
41
Card Acceptor
Terminal
Identification
an 8
Copied from 0100 message.
44
Additional
Response
Data
an..25
If the response code (bit 039) is 30, then

this bit contains the bit number in error.
49
Currency
Code,
Transaction
nP 3
Copied from 0100 message.
55
Integrated
Circuit Card
(ICC) SystemRelated 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
61
Acquirer
Transport Data
LLLVAR
ans..030
Required if in the 0100 message.
127
Acquirer Trace
Data
LLLVAR
ans..050

requested by the acquirer.
128
Message
Authentication
Code
b 64

MACing messages and at least one of the
data elements from 065-127 is present in
the message.
LLVAR
RIF.: J-00259842-5
CAPITULO

PAGINA
21
V
CAMBIO N
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
Bit Map,
Secondary
Primary
Account
Number
Formato
Atributo
Descripcin
b 64
Required if data elements specified

in the Secondary Bit Map (065
to128) are used.
nP..19
Required
if
PAN
manually
entered.One
of
these
data
elements isrequired: 002, 035, or
045.
Processing
Code
nP 6
Valid codes are listed.
Amount,
Transaction
nP 12
Amount,
Transaction
nP 12
Transmission
Date and Time
Conversion
Rate,
Settlement
LLVAR
MMDDhhmmss
Require
if
transanction
and
settlement currencies are different
nP 10
nP 8
Require
if
transanction
and
RIF.: J-00259842-5
CAPITULO

PAGINA
22
V
CAMBIO N
FECHA:
26/04/2011
10
Conversion
Rate,
Cardholder
Billing
nP 8
11
System Trace
Audit Number
nP 6
12
Time, Local
Transaction
hhmmss
nP 6
13
Date, Local
Transaction
MMDD
nP 4
14
Date,
Expiration
YYMM
nP 4
15
Date,
Settlement
MMDD
nP 4
16
Date,
Conversion
MMDD
nP 4
Require
if
transanction
and
17
Date, Capture
MMDD
nP 4
This data element is required only

if it is requested by the issuer.
18
Merchant Type
nP 4
Required for transactions from a

point-of-sale device.
19
Acquiring
Institution
Code
nP 3
Sent if Acquiring Institutions

Country Code is not the same as
the Issuing Institutions Country
Code.
22
Point-ofService Entry
Mode.
nP 3

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
Card
Sequence
Number
nP 3
May be used to send a card

sequence (plastic) number if Track
2 (bit 035) is not sent.
26
Point-ofService PIN
Capture Code
nP 2
Required if PIN data (052) is in the

message, and the device cannot
accept 12-digit PINs.
27
Authorization
Identification
Response
Length
nP 1
May be used by acquirers that

cannot
accept
6-byte
long
authorization ID responses (bit
038).
This data is logged only
RIF.: J-00259842-5
CAPITULO

PAGINA
23
V
CAMBIO N
FECHA:
26/04/2011
28
Amount,
Transaction
Fee
x+n8
32
Acquiring
Institution
Identification
Code
LLVAR nP..11
33
Forwarding
Institution
Identification
Code
LLVAR nP..11

Institution
Identification
Code
(bit032).
35
Track 2 Data
LLVAR
nsP..37
Required if Track 2 was machine

read. One of these data elements
is required: 002, 035, or 045.
37
Retrieval
Reference
Number
an 12
In a pre-authorized request, this

must be the same value as in preauthorization.
41
Card Acceptor
Terminal
Identification
an 8
42
Card Acceptor
Identification
Code
an 15
43
Card Acceptor
Name and
Location
an 40
48
Merchant /
Bank Name
49
Currency
Code,
Transaction
nP 3
50
Currency
Code,
Settlement
nP 3
Required
if
transaction
and
settlement currencies are Different.
52
PIN Data.
B 64
Required if a PIN is required during

authorization processing.
54
Additional
Amounts
ans..120
Sent if transaction-related amounts

or balances are present.
LLLVAR
LLLVAR

present. The fee may be a
surcharge, rebate, or transaction
fee, (R) Si hay Comisin
Adicional x = D

ans..025
RIF.: J-00259842-5
CAPITULO

PAGINA
24
V
CAMBIO N
FECHA:
26/04/2011
55
Integrated
Circuit Card
(ICC) SystemRelated data
LLLVAR
b 255;

estipulado en las especificaciones
EMV 2000
58
National Pointof- 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
National Pointof- Service

Geographic
Data
LLLVAR
an..017
May be required to qualify for lower

fees from VISA or MasterCard.
61
Acquirer
Transport Data
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
Account ID 1
LLVAR
ans..28
May be required in outbound

messages if the processor looks up
account numbers for the issuer.
103
Account ID 2
LLVAR
ans..28

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
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
Account
Qualifiers
LLLVAR
an..006

122
Sponsor Bank
ID
LLLVAR
an..011

RIF.: J-00259842-5
CAPITULO

AVS/Check
Auth
LLLVAR
ans..050
Data
25
V
CAMBIO N
123
PAGINA
FECHA:
26/04/2011
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.
127
Acquirer Trace
Data
128
Message
Authentication
Code
LLLVAR
ans..050

b 64

MACing messages and at least
one of the data elements from 065127 is present in the message.
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+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. (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

PAGINA
26
V
CAMBIO N
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:
Largo:
Nmero Tarjeta:
0164988383040023537
016
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
14
Tipo de Transaccin:
NOMB = si es una Validacin de Beneficiario
TRAN = si es una Transferencia Interbancaria
PAGO = si es un Pago de Servicio.
55
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.
CAPITULO

RIF.: J-00259842-5
PAGINA
27
V
CAMBIO N
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
0001
0100
0200
0300
0400
0500
0099
0199
0299
0399
0499
0599
Tipos de Empresa / Servicio

Utilitarias
Telefona Inalmbrica
Franquicias
Clubes
Colegios y Universidades
Organizaciones Gubernamentales
A continuacin, los cdigos asignados:

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

RIF.: J-00259842-5
28
V
CAMBIO N

0405
0406
PAGINA
FECHA:
26/04/2011
URBE Universidad Rafael Belloso Chacn

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
12
CI Indica la Cdula de Identidad
34
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
12
"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:
Tipo:
Pregunta No:
Respuesta:
012
PD
01 Primeros dos dgitos de la cdula de identidad
00000010
CAPITULO

RIF.: J-00259842-5
29
V
CAMBIO N

Nota: El cdigo de respuesta igual a "80"
INCORRECTA de la misma.
PAGINA
FECHA:
26/04/2011
es designado para la respuesta
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
Requerimiento
a)
Respuesta
Red S7B
Banco Emisor
Verifica existencia
PAN Tarjeta
de la Cuenta
b)
f)
Cliente
Destino de los
Fondos
0200
0200
Hace
el Abono a
Notificar
Cuenta
Pago Destino
0210
0210
d)
h)
Verifica Afiliacin y
Disponibilidad
de los Fondos
y hace el Cargo
correpondiente
c)
Flujo de los Fondos
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)
ii)
iii)
iv)
v)
BIT 3 Processing Code 48COCD

BIT 4 Monto de la Transferencia.
BIT 22 Point of Service Entry Mode
BIT 23 Card Sequence Number
BIT 35 Track II del Tarjetahabiente.
CAPITULO

RIF.: J-00259842-5
30
V
CAMBIO N

vi)
vii)
viii)
ix)
x)
xi)
PAGINA
FECHA:
26/04/2011
BIT 52 PIN del Tarjetahabiente.

BIT 55 ICC System-Related Data
BIT 58 National Point-Of-Service Condition Code
BIT 103 Cuenta Receptora de los Fondos.
BIT 104 TRAN y el Concepto de la Operacin.
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
Requerimiento
a)
Respuesta
PAN Tarjeta
Cliente
d)
h)
Red
Banco Emisor
0200
0200
0210
0210
Autorizar
Pago
b)
f)
Notificar
Pago
Empresa / Servicio
c)
Flujo de los Fondos
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.
CAPITULO

RIF.: J-00259842-5
xi)
31
V
CAMBIO N
x)
PAGINA
FECHA:
26/04/2011
BIT 104 PAGO, Cdigo Identificador de la Empresa de Servicio en

blanco y el Concepto de la Operacin.
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
Expected Response
None
Message Structure
Following is the structure of the 0210 Financial Transaction Response message.
Bit
Status
Nombre del
Elemento
Bit Map,
Secondary
Primary Account
Number
Formato
LLVAR
Atributo
Descripcin
b 64
Required if data elements specified

in the Secondary Bit Map (bits 065
to 128) are used.
nP..19

message.
RIF.: J-00259842-5
CAPITULO

PAGINA
32
V
CAMBIO N
FECHA:
26/04/2011
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.
Amount,
Transaction
nP 12
Amount,
Settlement
nP 12
Required if transaction and

settlement currencies are different.
Transmission
Date and Time
MMDDhhmmss
nP 10
Amount,
8
nP 8
Cardholder
Billing Fee
Debe ser retornado por el Banco

Emisor, para informar al Banco
Adquiriente del monto de la
comisin cobrada al tarjetahabiente.
Conversion Rate,
Settlement
nP 8

10
Conversion Rate,
Cardholder Billing
nP 8
This data is logged only.
11
System Trace
Audit Number
nP 6
12
Time, Local
Transaction
Hhmmss
nP 6
13
Date, Local
Transaction
MMDD
nP 4
15
Date, Settlement
MMDD
nP 4
16
Date, Conversion
MMDD
nP 4
Returned if available. Required if

transaction and settlement
currencies are different.
18
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.
19
Acquiring
Institution Country
Code
nP 3

22
Point-of- Service
Entry Mode
nP 3

RIF.: J-00259842-5
CAPITULO

PAGINA
33
V
CAMBIO N
FECHA:
26/04/2011
RIF.: J-00259842-5
CAPITULO

PAGINA
34
V
CAMBIO N
FECHA:
26/04/2011
23
Card Sequence
Number
nP 3

28
Amount,
Transaction Fee
x+n8

message.
30
Amount,
Transaction
Processing Fee
x+n8
Requerido para notificar el pago

del IDB
32
Acquiring
Institution
Identification
Code
LLVAR
nP..11
33
Forwarding
Institution
Identification
Code
LLVAR
nP..11

message.
35
Track 2 Data
LLVAR
nsP..37

message.
37
Retrieval
Reference
Number
an 12
38
Authorization
Identification
Response
an 6
May be used by the authorizer to

return an authorization number for
accepted transactions.
39
Response Code
an 2
If the response code is 30, then

Additional Response Data (bit 044)
contains the bit number in error.
41
Card Acceptor
Terminal
Identification
an 8
42
Card Acceptor
Identification
Code
an 15

43
Card Acceptor
Name and
Location
an 40
44
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


C
Merchant / Bank
Name
49
50
35
V
CAMBIO N
48
PAGINA
FECHA:
26/04/2011
ans..025

Currency Code,
Transaction
nP 3
Currency Code,
Settlement
nP 3
Required if the transaction and

54
Additional
Amounts
LLLVAR
ans..120
Returned if additional amounts are

received in the 020x message or
balances are received from the
Authorizer.
55
Integrated Circuit
Card (ICC)
System-Related
data
LLLVAR
b 255;

estipulado en las especificaciones
EMV 2000
58

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

returned.
59
National Point-ofService
Geographic Data
LLLVAR
an..017
61
Acquirer
Transport Data
LLLVAR
ans..030
102
Account ID 1
LLVAR
ans..28
103
Account ID 2
LLVAR
ans..28
104
Transaction
Description
LLLVAR
ans..100

want the data element returned to
120
Account
Qualifiers
LLLVAR
an..006

122
Sponsor Bank ID
LLLVAR
an..011

LLLVAR
CAPITULO

RIF.: J-00259842-5
PAGINA
36
V
CAMBIO N
FECHA:
26/04/2011
123
AVS/Check Auth
Data
LLLVAR
ans..050
Required if the issuer returns the

address verification results.
127
Acquirer Trace
Data
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.
Bit
Status
Nombre del
Elemento
Formato
Message Type
nP 4
Bit Map, Primary
b 64
Bit Map, Secondary
b 64
Secondary Required if data

elements specified in the
Secondary Bit Map (065 to128)
are used.
Primary Account
Number
nP..19
Required if PAN manually

entered. One of these data
elements is required: 002 or
035.
Processing Code
nP 6
Valid codes are listed in

Appendix B.
Amount, Transaction
nP 12
LLVAR
Atributo
Descripcin
Value 0220 for initial advice;
0221 for repeat advice.
RIF.: J-00259842-5
CAPITULO

37
V
CAMBIO N
nP 12
PAGINA
FECHA:
26/04/2011
Amount, Transaction
Transmission Date
and Time
Conversion Rate,
Settlement

settlement currencies are
different.
10
Conversion, Rate,
Cardholder Billing.
This data is logged only
11
System Trace Audit

Number
12
Time, Local
Transaction
hhmmss
nP 6
13
Date, Local
Transaction
MMDD
nP 4
14
Date, Expiration
YYMM
nP 4
15
Date, Settlement
MMDD
nP 4 M
16
Date Conversion
MMDD
nP 4

different.
17
Date, Capture
MMDD
nP 4
This data element is required

only if it is requested by the
issuer.
18
Merchant Type
nP 4

point-of-sale device.
19
Acquiring Institution
Country Code
nP 3
Sent if Acquiring Institutions

Country Code is not the same
as the Issuing Institutions
Country Code.
22
Point-of-Service
Entry Mode.
nP 3

listed in Appendix B.
28
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.
32
Identification Code
MMDDhhmmss

different.
nP 10
nP 6
LLVAR
nP..11
RIF.: J-00259842-5
CAPITULO


R
Forwarding
Institution
Identification Code
35
37
LLVAR
38
V
CAMBIO N
33
PAGINA
FECHA:
26/04/2011
nP..11
Required if different from

Identification Code (bit032).
Track 2 Data LLVAR
nsP..37
Required if Track 2 was

machine read. One of these
data elements is required: 002,
035, or 045.
Retrieval Reference
Number
an 12

must be the same value as in
pre-authorization.
38
Authorization
Identification
Response
an 6
May be used by the authorizer

to return an authorization
number for accepted
transactions.
39
Response Code
an 2
41
Card Acceptor
Terminal
Identification
an 8
42
Card acceptor
Identification Code
an 15
43
Card Acceptor
Name and Location
an 40
48
Merchant/Bank
Name
49
Currency Code,
Transaction
nP 3
50
Currency Code
Settlement
nP 3

different.
54
Additional Amount
LLLVAR
ans..120
Sent if transaction-related
amounts or balances are
present.
58

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
59
Point-of-Service
National Geographic
Data
an..017
May be required to qualify for

lower fees from VISA or
MasterCard. This data element
is required only if itis requested
by the issuer.
LLLVAR
ans..025

issuer.
Bank Name Reserved for

private data unique to private
institutions.
RIF.: J-00259842-5
CAPITULO

PAGINA
39
V
CAMBIO N
FECHA:
26/04/2011
60
Advice/Reversal
Reason Code
LLLVAR
an..006
Required if available
61
Acquirer Transport
Data
LLLVAR
ans..030
This data is echoed to the

acquirer in the response to their
request, but it is not forwarded
to the issuer.
102
Account ID 1
LLVAR
ans..28

messages if the processor looks
up account numbers for the
issuer.
103
Account ID 2
LLVAR
ans..28

messages if the processor looks
up account numbers for the
issuer, and the transaction is a
transfer.
104
Transaction
Description
LLLVAR
ans..100
Sent if available.
120
Account Qualifiers
LLLVAR
an..006
This data element is
122
Sponsor Bank ID
LLLVAR
an..011
This data element is
123
AVS/Check Auth
Data
LLLVAR
ans..050
Three formats are supported:

drivers license, MICR number,
and plastic card number. (R)
Requerido en las Operaciones
de Retiro, Transferencia
Interbancarias y Pago de
Servicios en ATM para la PD
Pregunta de Desafo y para la
CI en Operaciones de Punto
de Ventas (POS)
127
Acquirer Trace Data
LLLVAR
ans..050

issuer.
RIF.: J-00259842-5
CAPITULO

PAGINA
40
V
CAMBIO N
FECHA:
26/04/2011
0230 FINANCIAL TRANSACTION ADVICE RESPONSE

Description
The 0230 Financial Transaction Advice Response message acknowledges that the Connex
System or an issuer received the 0220/0221 financial transaction advice message. This
message ensures that critical 022x messages have been received.
The use of a 0230 message is optional for an endpoint to indicate the receipt of a 0220/0221
Financial Transaction Advice. If a 0230 message is not desired, a protocol acknowledgment is
the only verification that a 0220/0221 message was properly delivered.
Generated by
Connex System or issue
Expected Response
None
Message Structure
Following is the structure of the 0230 Financial Transaction Advice Response message.
Bit
No.
Status
Nombre del
Elemento
Formato
Message Type
nP 4
Bit Map, Primary
b 64
Processing Code
nP 6
Amount,
Transaction
nP 12
Amount,
Transaction
nP 12
Transmission
Date and Time
Conversion
Rate, Settlement
11
System Trace
Audit Number
12
Time, Local
Transaction
hhmmss
nP 6
13
Date, Local
Transaction
MMDD
nP 4
MMDDhhmmss
Atributo
Descripcin
Always 0230
Valid codes are listed in Appendix

B.

nP 10
nP 6
RIF.: J-00259842-5
CAPITULO

41
V
CAMBIO N

MMDD
PAGINA
FECHA:
26/04/2011
15
Date, Settlement
nP 4
22
Point-of-Service
Entry Mode.
nP 3

28
Amount,
Transaction Feed
x + n8

present. The fee may be a
surcharge, rebate, or transaction
fee.
37
Retrieval
Reference
Number
an 12

must be the same value as in preauthorization.
39
Response Code
an 2
Must be 00.
41
Card Acceptor
Terminal
Identification
an 8
44
Additional
Response Data
LLVAR
an 25
Response Data If the response

code (bit 039) is 30, then this bit
contains the bit number in error.
May contain
49
Currency Code,
Transaction
nP 3
50
Currency Code
Settlement
nP 3

settlement currenciesare different.
58

Code
nP..011

required, DEPS prefers that you
use this bit for all transactions.
Valid codes are listed in Appendix
B.
61
Acquirer
Transport Data
LLLVAR
ans..030
This data is echoed to the acquirer

in the response to their request,
but it is not forwarded to the issuer.
ans.050
The next two subelements are

defined in the eFunds message
standard.
an 2
Required to indicate the presence

of the subelements. Byte Map must
be the first subelement.
an 6
Required if present in the 022x

message.
63
eFunds Data
Byte Map
LLLVAR
LLLVAR
RIF.: J-00259842-5
CAPITULO

PAGINA
42
V
CAMBIO N
FECHA:
26/04/2011
64
Message
Authentication
Code
b 64

MACing messages and no data
element from 065-128 is present in
the message.
128
Message
Authentication
Code
b 64

MACing messages and at least
one of the data elements from 065127 is present in the message.
0420/0421 ACQUIRER REVERSAL ADVICE

Description
A 0420 Acquirer Reversal Advice message reverses (partially or wholly) an earlier
authorization or transaction.
Generated by
Expected Response
0430 Acquirer Reversal Advice
Message Structure
Following is the structure of the 0420/0421 Acquirer Reversal Advice message.
Bit
Statu
s
Nombre del
Elemento
Bit Map,
Secondary
Primary
Account
Number
Formato
Atributo
Descripcin
b 64
LLVAR
nP..19
Required if present in the 02xx or 01xx

message.
Processing
Code
nP 6
Copied from the 02xx or 01xx

message.
Amount,
Transaction
nP 12

message.
Transmission
Date and Time
Conversion
Rate,
Settlement
MMDDhhmmss
nP 10
nP 8

request message.
RIF.: J-00259842-5
CAPITULO

PAGINA
43
V
CAMBIO N
FECHA:
26/04/2011
10
Conversion
Rate,
Cardholder
Billing
nP 8
11
System Trace
Audit Number
nP 6

message.
12
Time, Local
Transaction
Hhmmss
nP 6

message.
13
Date, Local
Transaction
MMDD
nP 4

message.
14
Date,
Expiration
YYMM
nP 4

message. Is not sent to the issuer in
reversals unless the acquirer supplied
it, or for late or unsolicited responses
unless the issuer included this data
element in their response.
15
Date,
Settlement
MMDD
nP 4
16
Date,
Conversion
nP 4
Is not sent to the issuer in reversals

unless the acquirer supplied it, or for
late or unsolicited responses unless
the issuer included this data element in
their response.
18
Merchant Type
nP 4

their response.
19
Institution
Country Code
nP 3
Sent if Acquiring Institutions Country

Code is not the same as the Issuing
Institutions Country Code.
22
Point-ofService Entry
Mode.
nP 3

their response.
23
Card
Sequence
Number
nP 3

the issuer included this data
RIF.: J-00259842-5
CAPITULO

Amount,
transaction
Feed
32
Acquiring
Institution
Identification
Code
33
35
44
V
CAMBIO N
28
PAGINA
FECHA:
26/04/2011
x + n8

element in their response. (R) si hay
Comisin Adicional x = C
LLVAR
nP..11

message.
Forwarding
Institution
Identification
Code
LLVAR
nP..11

Institution Identification Code (bit 032).
Track 2 Data
LLVAR
nsP..37

message.
37
Retrieval
Reference
Number
an 12

message.
38
Authorization
Identification
Response
an 6
Copied from the 0210 or 0110

message, if available.
39
Response
Code
an 2
Copied from the 0210 or 0110

message
41
Card Acceptor
Terminal
Identification
an 8

message.
42
Card Acceptor
identification
Code
an 15

their response. This data element is
required only if it is requested by the
issuer.
43
Card Acceptor
Name Location
an40

their response.
RIF.: J-00259842-5
CAPITULO

Merchant/
Bank name
49
Currency
Code,
Transaction
54
Additional
Amounts
57
58
FECHA:
26/04/2011
ans..025
Bank Name Is not sent to the issuer in

it, or forlate or unsolicited responses
nP 3

message.
LLLVAR
ans..120
This data element is sent if

transaction-related amounts are
present. It is not sent to the issuer in
Authorization
Life Cycle
LLLVAR
n..003
Required if present in the 01xx

message.
National Pointof-Service
Condition Code
LLLVAR
nP..011

required, DEPS prefers that you use
this bit for all transactions. Valid codes
are listed at the end of msnual.
59
National Pointof-Service
GeographicDat
a
LLLVAR
an..017

issuer.
60
Advice/
Reversal
Reason Code
LLLVAR
an..006
Required if available.
61
Acquirer
Transport Data
LLLVAR
This data is echoed in the response,

bit it is only sent by FIS if the host is
sending totals or the data element is
requested by theissuer.
Original Data
Elements
nP 42
90
LLLVAR
45
V
CAMBIO N
48
PAGINA
ans..030
Original message type required on

inbound messages to the CONNEX
System; remaining sub-elements are
zero-filled. Outbound from the
CONNEX System, the original
message type is sent. Original system
trace audit number and local date and
time are sent if available. Note: These
values will usually match those in
elements 011, 012, and 013.
RIF.: J-00259842-5
CAPITULO

Replacement
Amounts
102
Account ID 1
103
104
46
V
CAMBIO N
95
PAGINA
FECHA:
26/04/2011
an 42
Required if partial dispense.
LLVAR
ans..28

Account ID 2
LLVAR
ans..28

Transaction
Description
LLLVAR
ans..100
Sent if available.
120
Account
Qualifiers
LLLVAR
an..006

issuer.
122
Sponsor Bank
ID
LLLVAR
an..011
This data element is required only if it

is requested by the Issuer
123
AVS/Check
Auth Data
LLLVAR
ans..050
Sent if present in the 01xx or 02xx

message.
127
Acquirer Trace
Data
LLLVAR
ans..050
This data element is required only if it

is requested by the issuer.
NOTA: En caso de utilizarse la Comisin Adicional BIT 28 y la transaccin es

REVERSADA 0420, el adquirente est en la obligacin de enviar la opcin C + el importe
cobrado.
28
Amount,
transaction
Feed
x + n8

reversals unless the acquirer supplied it,
or for late or unsolicited responses unless
the issuer included this data
element in their response. En caso de
REVERSO en una transaccin con
Comisin Adicional, se deber colocar
el Identificador C + importe de la
comisin.
RIF.: J-00259842-5
CAPITULO

PAGINA
47
V
CAMBIO N
FECHA:
26/04/2011
0430 ACQUIRER REVERSAL RESPONSE

Description
The 0430 Acquirer Reversal Response message acknowledges that the Connex System or
an issuer received the 0420 or 0421 Acquirer Reversal Advice message.
The use of a 0430 is optional for a 0420/0421 message.
Generated by
Expected Response
None
Message Structure
Following is the structure of the 0430 Acquirer Reversal Response message.
Bit
Statu
s
Nombre del
Elemento
Formato
Atributo
Descripcin
Bit Map,
Secondary
b 64
Processing
Code
nP 6
Amount,
Transaction
nP 12
Transmission
Date and Time
Conversion
Rate
Settlement
nP 8
Returned if received in the 042x

message.
11
System Trace
Audit Number
nP 6
Copied from the 042x message.
12
Time, Local
Transaction
Hhmmss
nP 6
13
Date, Local
Transaction
MMDD
nP 4
15
Date,
Settlement
MMDD
nP 4
MMDDhhmmss
nP 10
RIF.: J-00259842-5
CAPITULO

PAGINA
48
V
CAMBIO N
FECHA:
26/04/2011
28
Amount
Transaction
Feed
x + n8

Required if received in the 04xx
message. En caso de REVERSO en
una transaccin con Comisin
Adicional, se deber colocar el
Identificador C + importe de la
comisin.
37
Retrieval
Reference
Number
an 12
39
Response
Code
an 2
Must be 00.
44
Additional
Response Data
an..25
If the response code (bit 039) is 30,

then this bit contains the bit number in
error. May contain statement print
information.
49
Currency
Code,
Transaction
nP 3
90
Original Data
Elements
nP 42
95
Replacement
Amounts
an 42
Required if present in the 042x

message.
128
Message
Authentication
Code
b 64

MACing messages and at least one of
the data elements from 065-127 is
present in the message.
LLVAR
RIF.: J-00259842-5
CAPITULO

PAGINA
49
V
CAMBIO N
FECHA:
26/04/2011
0620 ADMINISTRATIVE ADVICE

Description
The 0620 Administrative Advice message is used to notify the message originator that an
unrecognized message was received, such as an error in parsing a bit map or a mandatory
data element is not present.
Generated by
Acquirer or issuer
Expected Response
None
Message Structure
Following is the structure of the 0620 Administrative Advice message.
Bit
Status
Nombre del
Elemento
Formato
Atributo
Bit Map,
Secondary
Transmission
Date and Time
11
System Trace
Audit Number
nP 6
70
Network
Management
Information
Code
nP 3
124
Info, Text
Descripcin
b 64
MMDDhhmmss
LLLVAR
nP 10
Must be 900.
ans..255
0800 NETWORK MANAGEMENT REQUEST

Description
The 0800 Network Management Request message is used by any two communicating
endpoints to coordinate system or network events or tasks, and to communicate network
status conditions. For example, the request can contain sign on, sign off, key change, cutoff,
or handshake information.
The recipient of a 0800 Network Management Request message must reply with a 0810
Network Management Response message within a specified time interval.
CAPITULO

RIF.: J-00259842-5
PAGINA
50
V
CAMBIO N
FECHA:
26/04/2011
Generated by
Connex System or endpoint (acquirer or issuer)
Expected Response
0810 Network Management Response
Message Structure
Following is the structure of the 0800 Network Management Request message.
Bit
Status
Nombre del
Elemento
Formato
Atributo
Message Type
nP 4
Bit Map, Primary
b 64
Bit Map, Secondary
b 64
Transmission Date
and Time
11
System Trace Audit

Number
15
Date, Settlement
70
Network
Management
Information Code
125
Network
Management
Information
MMDDhhmmss
Descripcin
Value 0800.
nP 10
nP 6
MMDD
nP 4
nP 3
LLLVAR
ans..050
Required when the value of bit 070 is

005, 101, 161, 171, 281, or 282.
0810 NETWORK MANAGEMENT RESPONSE

Description
A 0810 Network Management Response message is sent in response to a 0800 Network
Management Request message.
Generated by
Connex System or endpoint (acquirer or issuer)
Expected Response
None
RIF.: J-00259842-5
CAPITULO

PAGINA
51
V
CAMBIO N
FECHA:
26/04/2011
Message Structure
Following is the structure of the 0810 Network Management Response message.
Bit
Status
Nombre del
Elemento
Formato
Atributo
Descripcin
Message Type
NP 4
Always 0810
Bit Map, Primary
b 64
Bit Map,
Secondary
b 64
Transmission Date
and Time
11
System Trace
Audit Number
15
Date Settlement
39
Response Code
an 2
70
Network
Management
Information Code
nP 3
MMDDhhmmss
nP 10
nP 6
MMDD
Secondary required if data

elements specify in the secondary
Bit Map (bits 065 to 128) are used.
nP 4
CAPITULO

RIF.: J-00259842-5
PAGINA
52
VI
CAMBIO N
DATA ELEMENT DEFINITIONS
FECHA:
26/04/2011

This section provides detail for each ISO data element referenced in Message Structure.
With the exception of the first two elements (Message Type and Primary Bit Map), the data
element definitions are listed in order by bit number. The following information is included for
each data element.
FORMAT
The format of the data element is provided, where applicable. Following is a legend for the
abbreviations used for data format.
Notation
Description
MM
Month
DD
Day
YY
Year
hh
Hour
mm
Minute
SS
Second
LL
Length of variable data element that follows, from 01-99. If the packing option is not set,
the variable length sub-element is two numeric characters. Otherwise, the variable
length subelements 1-byte binary.
LLL
Length of variable data element that follows, from 001-999. If the packing option is not
set, the variable length sub-element is three numeric characters. Otherwise, the variable
length sub-element is 1-byte binary.
VAR
Variable length data element.
ATTRIBUTES
The data element attributes are included in abbreviated form for the following:
The FIS implementation of the ISO standard
ISO standard representation
See Legend for Attribute Abbreviations, which explains the abbreviations that are used
throughout the section.
DESCRIPTION
The ISO definition of the data element is provided.
DATA EDIT
Editing performed on the data element; the information the element should contain.
CAPITULO

RIF.: J-00259842-5
PAGINA
53
VI
CAMBIO N
FECHA:
26/04/2011
STATUS
The FIS data element requirements for the applicable message types.
LEGEND FOR ATTRIBUTE ABBREVIATIONS Explanation
Notation
Explanation
Alphabetic characters only.
Numeric digits only.
nP
Numeric data element that is capable of being packed, based on the data base setting.
The data element contains numeric digits in unsigned packed format (4-bit BCD) when
the numeric packing option is set. The number indicates the number of digits the data
element contains.
Note: When the numeric packing option is set, all lengths are 1- byte binary. Oddlength packed numerics have a leading zero to ensure data elements begin and end on
byte boundaries.
Special characters.
an
Alphabetic and numeric characters only.
as
Alphabetic and special characters.
ns
Numeric digits and special characters
ans
Alphabetic, numeric, and special characters.
Fixed length of three characters.
..17
Variable length up to a maximum of 17 characters. All variable length fields will also
contain two or three positions at the beginning of the field to identify the number of
positions following to the end of that field.
Indicates a positive or negative amount. For example, x + n 16 in amount, net

settlement means prefix C or D and 16 digits of amount, net settlement.
C indicates a positive amount (credit).
D indicates a negative amount (debit).
Note: For financial transactions, the value of the amount (credit or debit) is given from
the cardholders perspective.
Binary representation of data. If packing option is not set, contains hexadecimal

characters.
bcd
Binary coded decimal. Always contains hexadecimal characters.
CAPITULO

RIF.: J-00259842-5
PAGINA
54
VI
CAMBIO N
FECHA:
26/04/2011
DATA ELEMENTS
El resto de este captulo describe con ms detalle cada uno de los Data Elements (DE).
Message Type
Attributes:
FIS: nP 4
ISO: n 4
Description:
Identifies the type of message being interchanged. Each message must

begin with the message type indicator.
Data Edit:
Valid ISO Message ID.
Status:
Required for all message types.
Bit Map, Primary

Attributes:
FIS: b 8 bytes (packing maps)

FIS: 16 hex bytes (packing maps option not set)
ISO: b 64
Description:
A series of 64 bits used to identify the presence (denoted by 1) or

absence (denoted by 0) of data elements 001 through 064. The Primary
Bit Map must follow the message type indicator of each message.
Data Edit:
Must include minimum bit map required by ISO and Installation,

depending upon the message type indicator of each message.
Status:
Required for all message types.
001 Bit Map, Secondary

Attributes:

ISO: b 64
Description:

absence (denoted by 0) of data elements 065 through 128.
Data Edit:
Must include minimum bit map required by ISO and Installation,

depending upon the message ID.
Status:
Conditional on the presence of one or more data elements from 65 to

128.
CAPITULO

RIF.: J-00259842-5
PAGINA
55
VI
CAMBIO N
FECHA:
26/04/2011
002 Primary Account Number (PAN)

Format:
LLLVAR
Attributes:
FIS: nP..19
ISO: n..19
Description:
A series of digits used to identify a customer account or relationship.
Data Edit:
Numeric. Required if PAN entry mode indicates manual entry.
Status:
Refer to the following chart for the FIS data element requirements.
Message Types
Status Information
0100, 0120
Conditional. Required if PAN is manually entered.
0200, 0220
One of these data elements is required: 002, 035, or 045.
0420
0110, 0210
Conditional. Required if received in the request message.
0302, 0312
Conditional. Either data element 002 or 034 is required if bit 101 equals
PI-NEGATIVE.
003 Processing Code

Attributes:
FIS: nP 6
ISO: n 6
Description:
A series of digits used to describe the effect of a transaction on the

customer account and identify the accounts affected. Refer to
Processing Codes (bit 003), Authorization Messages and Processing
Codes (bit 003), Financial Transaction Messages for lists of valid
processing codes.
Data Edit:
Matching table entry.
Status:
Message Types
Status Information
0100, 0110, 0120, 0130
Required.
0200, 0210, 0220, 0230

0420, 0430
CAPITULO

RIF.: J-00259842-5
PAGINA
56
VI
CAMBIO N
FECHA:
26/04/2011
004 Amount, Transaction

Attributes:
FIS: nP 12
ISO: n 12
Description:
Funds requested by the cardholder in the local currency of the acquirer

or source location of the transaction, exclusive of transaction fee
amount.
Data Edit:
Must be numeric, no greater than 999999999. This amount must remain

unchanged throughout the life of the transaction.
Status:
Message Types
Status Information
0100, 0110, 0120, 0130
Required.
0200, 0210, 0220, 0230

0420, 0430
005 Amount, Settlement

Attributes:
FIS: nP 12
ISO: n 12
Description:
Funds to be transferred between the acquirer and issuer. This amount

equals the transaction amount in the currency of settlement.
Note: FIS does not perform currency conversion.
Data Edit:
Must be numeric, no greater than 999999999.
Status:
Message Types
Status Information
0100, 0110, 0120, 0130
Conditional. Required if transaction and
0200, 0210, 0220, 0230
0420, 0430
RIF.: J-00259842-5
CAPITULO

PAGINA
57
VI
CAMBIO N
FECHA:
26/04/2011
006 Amount, Cardholder Billing (not supported)

Attributes:
FIS: nP 12
ISO: n 12
Description:
The amount billed to the cardholder in the currency of the cardholder

account, exclusive of cardholder billing fees.
Data Edit:
Status:
This data element is not currently supported.
007 Transmission Date and Time

Format
MMDDhhmmss
Attributes:
FIS: nP 10
ISO: n 10
Description:
The date and time the message entered into the data
interchange system, expressed in Greenwich Mean Time (GMT).
Note: FIS calculates the time in outbound Zessages.
Data Edit:
Must be valid date (MMDD) and time (hhmmss).
Status:
Required in all messages.
008 Amount, Cardholder Billing Fee

Attributes:
FIS: nP 8
ISO: n 8
Description:
The fee to be billed to the cardholder by the card issuing institution in the
same currency as the cardholder billing amount.
Data Edit:
Status:
RIF.: J-00259842-5
CAPITULO

PAGINA
58
VI
CAMBIO N
FECHA:
26/04/2011
Message Types
Status Information
0100, 0120
Optional. Present in financial requests outbound if AP is calculating

service fees.
0200, 0220
0420
Optional (if available).
0110
Optional. Present in financial responses if the card issuing institution is

billing the cardholder for this transaction.
0210
009 Conversion Rate, Settlement

Attributes:
FIS: nP 8
ISO: n 8
This data element is in the format ABBBBBBB, where:
A = the decimal position from the right
B = the actual conversion factor
Description:
The factor used in the conversion from the transaction to settlement

amount. The transaction amount is multiplied by the settlement
conversion rate to determine the settlementamount.
Data Edit:
Numeric. Required if settlement amount is present and different from

transaction amount.
Status:
Message Types
Status Information
0100, 0110, 0120
Conditional. Required if transaction and settlement currencies are

different
0200, 0210, 0220

0420
0130
Optional.
0230
0430
RIF.: J-00259842-5
CAPITULO

PAGINA
59
VI
CAMBIO N
FECHA:
26/04/2011
010 Conversion Rate, Cardholder Billing

Attributes:
FIS: nP 8
ISO: n 8
This data element is in the format ABBBBBBB, where:
A = the decimal position from the right
B = the actual conversion factor
Description:
The factor used in the conversion from the transaction to cardholder

billing amount. The transaction amount is multiplied by the cardholder
billing conversion rate to determine the cardholder billing amount.
Data Edit:
Numeric. Required if cardholder amount is present and different from

transaction amount.
Status:
Message Types
Status Information
0100, 0110, 0120
0200, 0210, 0220

0420
011 System Trace Audit Number

Attributes:
FIS: nP 6
ISO: n 6
Description:
A number assigned by the message initiator to uniquely identify a

transaction. The trace number remains unchanged for all messages
throughout the life of the transaction. For example:
0200 > 0210 > 0420 > 0430
all must have the same trace number.
Data Edit:
Numeric.
Status:
Required in all messages. Must remain unchanged

throughout the life of the transaction.
CAPITULO

RIF.: J-00259842-5
PAGINA
60
VI
CAMBIO N
FECHA:
26/04/2011
012 Time, Local Transaction

Format:
hhmmss
Attributes:
FIS: nP 6
ISO: n 6
Description:
The local time at which the transaction takes place at the point of the
card acceptor location. This time must remain unchanged throughout the
life of the transaction. For example,
0200 > 0210 > 0420 > 0430
all must have the same local transaction time.
Data Edit:
Valid time (hhmmss).
Status:
Message Types
Status Information
0100, 0120, 0130,
Required. Must remain unchanged throughout the life of the transaction.
0200, 0220, 0230

0420, 0430
013 Date, Local Transaction

Format:
MMDD
Attributes:
FIS: nP 4
ISO: n 4
Description:
The local month and day on which the transaction takes place at the
card acceptor location. This date must remain the same throughout the
life of the transaction. For example,
0200 > 0210 > 0420 > 0430
all must have the same local transaction date.
Data Edit:
Valid date (MMDD).
Status:
CAPITULO

RIF.: J-00259842-5
PAGINA
61
VI
CAMBIO N
FECHA:
26/04/2011
Message Types
Status Information
0100, 0120, 0130
Required. Must remain unchanged throughout the life of the transaction.
0200, 0220, 0230

0420, 0430
014 Date, Expiration

Format:
YYMM
Attributes:
FIS: nP 4
ISO: n 4
Description:
The year and month after which the card expires.
Data Edit:
Numeric.
Status:
Message Types
Status Information
0100, 0120
Conditional. Required if PAN manually entered. Either bit 014, 035 or

045 is required.
0200, 0220
0420
0110
0210
0302, 0312
Optional. Required if you want to receive this data element in a reversal

for a late or unsolicited response.
Future use. Date to expire this record from the negative file.
CAPITULO

RIF.: J-00259842-5
PAGINA
62
VI
CAMBIO N
FECHA:
26/04/2011
015 Date, Settlement

Format:
MMDD
Attributes:
FIS: nP 4
ISO: n 4
Description:
The month and day funds are transferred between the acquirer and
issuer or any intermediate network facility. Depending on the message,
this data element may contain the following information:
Inbound requests: This data element may contain the acquirer's
settlement date for the transaction.
Inbound responses: This data element may contain the issuer's
settlement date for the transaction.
Outbound requests or responses: This date is taken from the
internal calendar record.
Totals messages: This data element contains the date of the
settlement totals.
Note: FIS does not guarantee 100% synchronization with Settlement
end-of-day due to cutoff and suspense times.
Data Edit:
Valid date (MMDD).
Status:
Message Types
Status Information
0100, 0110, 0120, 0130
Required.
0200, 0210, 0220, 0230

0420, 0430
0520, 0522, 0530, 0532
CAPITULO

RIF.: J-00259842-5
PAGINA
63
VI
CAMBIO N
FECHA:
26/04/2011
016 Date, Conversion

Format:
MMDD
Attributes:
FIS: nP 4
ISO: n 4
Description:
The month and day the conversion rate is effective to convert the
transaction amount from the original to settlement currencies.
Data Edit:
Valid date (MMDD). Required if a conversion rate is present.
Status:
Message Types
Status Information
0100, 0110, 0120
Conditional. Required if transaction and settlement currencies are

different.
0200, 0210, 0220

0420
017 Date, Capture

Format:
MMDD
Attributes:
FIS: nP 4
ISO: n 4
Description:
The month and day the transaction date was processed by the acquirer.
Data Edit:
Numeric.
Status:
Message Types
Status Information
0100, 0120
Optional.
0200, 0220
CAPITULO

RIF.: J-00259842-5
PAGINA
64
VI
CAMBIO N
FECHA:
26/04/2011
018 Merchant Type

Attributes:
FIS: nP 4
ISO: n 4
Description:
The classification of the merchant's type of business product or service.
Data Edit:
Numeric.
Status:
Message Types
Status Information
0100, 0120
Conditional. Required in financial request messages if from a point-ofsale device.
0200, 0220
0110
0210
0420
Optional. Required in responses if you want to receive this data element

in a reversal for a late or unsolicited response.
019 Acquiring Institution Country Code

Attributes:
FIS: nP 3
ISO: n 3
Description:
The code of the country where the acquiring institution is located. (See
ISO 3166.)
Data Edit:
Numeric.
Status:
Message Types
Status Information
0100, 0120
Conditional. Sent whenever the Issuing Institutions Country Code is not

the same as the Acquiring Institutions Country Code.
0200, 02200100, 0120

0200, 0220
0110
0210
0420
Conditional. Required if you want to receive this data element in a

reversal for a late or unsolicited response.
Conditional (if available).
RIF.: J-00259842-5
CAPITULO

PAGINA
65
VI
CAMBIO N
FECHA:
26/04/2011
020 Primary Account Number (PAN) Extended Country Code

Attributes:
FIS: nP 3
ISO: n 3
Description:
The code of the country where the issuer institution is located. (See ISO
3166.)
Data Edit:
Numeric.
Status:
Message Types
Status Information
0100, 0110, 0120
Conditional. Required if PAN Extended (bit 034) is sent.
0200, 0210, 0220

0420
021 Forwarding Institution Country Code

Attributes:
FIS: nP 3
ISO: n 3
Description:
The code of the country where the issuer institution is located. (See ISO
3166.)
Data Edit:
Numeric.
Status:
Message Types
Status Information
0100, 0120
Conditional. Required if the acquiring institution country code is different

from the forwarding institution country code.
0200, 0220
0420
0110
Conditional. Required if received in the 0100 or 0200 message.
0210
CAPITULO

RIF.: J-00259842-5
PAGINA
66
VI
CAMBIO N
FECHA:
26/04/2011
022 Point-of-Service Entry Mode

FIS: nP 3
Attributes:
ISO: n 3
Description:
Two numerics to indicate the method by which the primary account

number was entered into the system and one numeric to indicate PIN
entry capabilities.
Data Edit:
Numeric.
Status:
Message Types
Status Information
0100, 0120
Conditional. Required if the transaction was entered at a point-of-service

device or from an ATM acquirer participating in a CVV program.
0200, 0220
0110
Optional. Required if you want to receive the data element in a reversal

0210
0420
PAN Entry Mode Codes

ISO Code
Positions 1-2
Description
00
Unspecified.
01
Manual.
02
Magnetic stripe.
03
Bar code.
04
OCR.
05
Integrated Circuit Card.
06
Manual (key-entered).
07-60
Reserved for ISO use.
61-78
Reserved for national use.
79
Chip card or chip-capable terminal was unable to process the transaction using
the data on the chip or magnetic stripe, the PAN was entered manually, or the
Acquirer is not certified to process the value 80.
80
Chip card or chip-capable terminal was unable to process the transaction using
the data on the chip, the PAN was entered via magnetic stripe. The full track data
was read from the data encoged on the card and transmitted within the
authorization request on Track-2 Data (data element 35 a) or Track-1 Data (data
CAPITULO

RIF.: J-00259842-5
PAGINA
67
VI
CAMBIO N
FECHA:
26/04/2011
element 45) without alteration or truncation.

81
From file.
82-89
Reserved for private use.
90
Full magnetic stripe read (optionally supported).
91-94
95
Integrated circuit card, CVV data may be unreliable.
96-99
ISO Code
Positions 3
Description
Unspecified.
PIN entry capability
No PIN entry capability
3-5
Reserved for ISO use.
PIN pad inoperative.
Reserved for national use
8-9
Reserved for private use
023 Card Sequence Number

Attributes:
FIS: nP 3
ISO: n 3
Description:
A number distinguishing between separate cards with the same primary

account number or primary account number extended. (See ISO 4909.)
Data Edit:
En las operaciones EMV, este campo debe ser llenado con la data del
TAG 5F34
Status:
Message Types
Status Information
0100, 0120
Conditional. Required if cards have plastic numbers and Track 2 (bit

035) is not sent.
0200, 0220
0110
0210
0420

RIF.: J-00259842-5
CAPITULO

PAGINA
68
VI
CAMBIO N
FECHA:
26/04/2011
024 Network International Identifier

Attributes:
FIS: nP 3
ISO: n 3
Description:
Identifies a single international network of card issuers. Note: This data

element is being removed by the ISO committee.
Status:
Not used.
025 Point-of-Service Condition Code

Attributes:
FIS: nP 2
ISO: n 2
Description:
An identification of the condition under which the transaction takes place

at the point-of-service.
Refer to Point-of-Service Condition Codes (bit 025) for a list of valid
point-of-service condition codes.
Note: FIS prefers the use of bit 058 in place of this data element.
Data Edit:
Numeric. Either bit 025 or 058 is required.
Status:
Message Types
Status Information
0100, 0110, 0120
Conditional. Either data element 025 or 058 is required. The value

received from the acquirer may change to indicate CVV results. Note:
The pre-authorized debit indication of 06 takes precedence.
0200, 0210, 0220

0420
026 Point-of-Service PIN Capture Code

Attributes:
FIS: nP 2
ISO: n 2
Description:
A code indicating the technique and/or maximum number of PIN

characters accepted by the point-of-service device used to construct the
PIN data.
Data Edit:
Numeric.
Status:
RIF.: J-00259842-5
CAPITULO

Status Information
0100
Optional.
69
VI
CAMBIO N
Message Types
PAGINA
FECHA:
26/04/2011
0200
027 Authorization Identification Response Length

Attributes:
FIS: nP 1
ISO: n 1
Description:
The maximum length of authorization response which the acquirer can

accommodate. The issuer or agent is expected to limit the response
length.
Note: The authorization code is truncated in the response if the issuer or
agent does not limit the length.
Data Edit:
Numeric.
Status:
Message Types
Status Information
0100, 0200
Optional.
028 Amount, Transaction Fee

Attributes:
FIS Corporation: x + n 8
ISO: x + n 8
Description:
The fee charged (for example, by the acquirer) for transaction activity in
the currency of the transaction amount. The fee may be a surcharge,
rebate, or transaction fee. This amount must be the same value in the
response as in the request. The value is a debit for a fee and a credit for
a rebate. (The debit or credit reflects the cardholder's perspective.)
Notes:
FIS only calculates on-line fees for surcharging.
See the description for 055 Additional Fees (not supported)
Data Edit:
Must be numeric. x must be 0, C, or D.

C = Credit amount (MSG 0420/0430)
D or 0 = Debit amount (MSG 0200/0210)
Status:
In Suiche 7B: This bit is used for the Additional Commission.
(*) BIT UTILIZADO PARA LA COMISIN ADICIONAL (ver formato en estructura de los
MSGS 0200/0210 y =420/0430.
CAPITULO

RIF.: J-00259842-5
PAGINA
70
VI
CAMBIO N
FECHA:
26/04/2011
Message Types
Status Information
0100, 0120
Conditional. Required when the defined fee is present. The value is a

debit for a fee and a credit for a rebate. The sign indicator is reversed to
indicate the reversal of a fee.
0200, 0220
0420
0110, 0130
0210, 0230
0430
Note: FIS does not calculate on-line fees, except for surcharges.
Conditional. Required if the Amount, Transaction Fee is received in the
request message. The response value must be the same as the value in
the request.
029 Amount, Settlement Fee

Attributes:
FIS: x + n 8
ISO: x + n 8
Description:
The fee transferred between the acquirer and the issuer equal to the
transaction fee amount in the currency of the settlement amount. This
amount must be the same value in the response as in the request. The
value is a debit for a fee and a credit for a rebate. (The debit or credit
reflects the cardholder's perspective.)
Notes:
FIS does not perform currency conversion and only calculates
on-line fees for surcharging.
See the description for 055 Additional Fees (not supported)
Data Edit:

C = Credit amount
D or 0 = Debit amount
This data element is required if transaction fee amount (028) and
settlement amount (005) are present.
Status:
RIF.: J-00259842-5
CAPITULO

PAGINA
71
VI
CAMBIO N
FECHA:
26/04/2011
Message Types
Status Information
0100, 0120
Conditional. Required when a surcharge or a rebate is present and the

transaction and settlement currencies are different. Following is
additional detail you need to know.
The value is a debit for a fee and a credit for a rebate.
The sign indicator is reversed to indicate the reversal of a fee.
FIS does not calculate on-line fees.
FIS does not perform currency conversion.
0200, 0220
0420
0110, 0130
0210, 0230
0430
Conditional. Required if the Amount, Transaction Fee is received in the

request message. The value in the response must be the same as the
value in the request.
030 Amount, Transaction Processing Fee

Attributes:
FIS: x + n 8
ISO: x + n 8
Description:
The fee charged (for example, by the acquirer, issuer or

intermediate network facility) for the handling and routing of
messages in the currency of the transaction amount. (The debit or
credit reflects the cardholder's perspective.)
Note: FIS does not calculate on-line fees.
Data Edit:

C = Credit amount
Status:
In Suiche 7B: Utilized by the Issuer to inform of the Payment of

the IDB (Impuesto al Dbito Bancario)
Message Types
Status Information
0100, 0110, 0120
Optional. May be sent if performing on-line processing fees in financial

requests and responses.
0200, 0210, 0220

0420
RIF.: J-00259842-5
CAPITULO

PAGINA
72
VI
CAMBIO N
FECHA:
26/04/2011
031 Amount, Settlement Processing Fee

Attributes:
FIS Corporation: x + n 8
ISO: x + n 8
Description:
The fee charged by the acquirer, issuer or intermediate network facility

for the handling and routing of messages in the currency of the
settlement amount. (The debit or credit reflects the cardholder's
perspective.)
Note: FIS Corporation does not calculate on-line fees and does not
perform currency conversion.
Data Edit:

C = Credit amount
Required if transaction processing fee amount (030) and settlement
amount (005) are present.
Status:
Message Types
Status Information
0100, 0110, 0120
Optional. Required if bit 030 is present, and the currency of the

transaction amount and settlement amount are different.
0200, 0210, 0220

0420
032 Acquirer Institution Identification Code

Format:
LLVAR
Attributes:
FIS Corporation: nP..11

ISO: n..11
This code is normally an institution identification code (IID) in the format
1NNNNNNNNC, where:
NNNNNNNN = the institution ID code
C = a check digit
Description:
A code identifying the acquiring institution (for example, merchant bank)

or its agent. This can be any uniquely identifying number agreed upon
by the network.
Data Edit:
Numeric. If the element begins with a 1, it must be an institution

identification code with a valid check digit.
Status:
RIF.: J-00259842-5
CAPITULO

Status Information
0100, 0110, 0120
Required.
73
VI
CAMBIO N
Message Types
PAGINA
FECHA:
26/04/2011
0200, 0210, 0220

0420
033 Forwarding Institution Identification Code

Format:
LLVAR
Attributes:
FIS Corporation: nP..11

ISO: n..11
Description:
If not the same institution as specified in the acquiring institution

identification code, the identity of the institution forwarding a request or
advice message in an interchange system.
Data Edit:
Numeric.
Status:
Message Types
Status Information
0100, 0120
Conditional. Required if the acquiring institution and the forwarding

institution are different.
0200, 0220
0420
0110
Conditional. Required if received in the 0100 or 0200 message.
0210
034 Primary Account Number (PAN), Extended

Format:
LLVAR
Attributes:
FIS Corporation: nsP..28

ISO: ns..28
Description:
This data element is used only when the primary account number begins
with 59 and is used to identify a customer account or relationship.
Data Edit:
Numeric.
Status:
Note: This data is logged in inbound messages, and is not supported in outbound messages.
RIF.: J-00259842-5
CAPITULO

PAGINA
74
VI
CAMBIO N
FECHA:
26/04/2011
Message Types
Status Information
0100, 0120
Conditional. Required if PAN is manually entered. One of these data

elements is required: 002, 035, or 045.
0200, 0220
0420
0110
Conditional. Required if received in the request message.
0210
0302, 0312
Conditional. Either data element 002 or 034 is required if bit 101 equals
PI-NEGATIVE.
035 Track 2 Data

Format:
LLVAR
Attributes:
FIS: nsP..37
ISO: LLVAR ns..37
Description:
The information encoded on Track 2 of the magnetic stripe as defined in

ISO 7813, excluding beginning and end sentinels and LRC characters
as defined therein.
Data Edit:
Valid ISO Track 2 required. Not allowed if manual entry.
Status:
Message Types
Status Information
0100, 0120
Conditional. Required if PAN is manually entered. One of these data

elements is required: 002, 035, or 045.
0200, 0220
0420
0110
Conditional. Required if received in request.
0210
CAPITULO

RIF.: J-00259842-5
PAGINA
75
VI
CAMBIO N
FECHA:
26/04/2011
036 Track 3 Data (not supported)

Format:
LLLVAR
Attributes:
FIS Corporation: nsP..104

ISO: ns..104
Description:

ISO 4909, excluding beginning and end sentinels and LRC characters
as defined therein.
Status:
037 Retrieval Reference Number

Attributes:
FIS Corporation: an 12
ISO: an 12
This data element can contain up to 12 alphanumeric characters. The
recommended format is shown below.
Position Data
Description:
1-4
Julian date (YDDD)
5-12
Actual terminal sequence number
A document reference supplied by the system retaining the original

source document and used to assist in locating that document or a copy
of the document. The value of this data element must remain unchanged
throughout the life of the transaction.
As the messages flow from 0200 > 0210 > 0420 > 0430, all must
have the same retrieval reference number. In a preauthorized purchase,
this data element must contain the same value as the original preauthorization. That is, preauthorization
0100 > 0110, pre-authorized purchase 0200/
0220 > 0210/0230 all must have the same retrieval reference number.
Data Edit:
Alphanumeric.
Status:
Message Types
Status Information
0100, 0110, 0120, 0130
Required.
0200, 0210, 0220, 0230

0420, 0430
CAPITULO

RIF.: J-00259842-5
PAGINA
76
VI
CAMBIO N
FECHA:
26/04/2011
038 Authorization Identification Response

Attributes:
ISO: an 6
Description:
The response identification assigned by the authorizing institution.
Data Edit:
None.
Status:
Message Types
Status Information
0110
Conditional. May be used by the authorizer to return an authorization

number for accepted transactions.
0210
0120
Conditional. Sent if available.
0220
0420
039 Response Code

Attributes:
ISO: an 2
Description:
A code that defines the disposition of a message. When the response

code is 30, then Additional Response Data (bit 044) contains the bit
number in error.
Note: Although either bit 039 or 060 is required in negative completions,
FIS prefers the use of bit 060. Refer to Response Codes (bit 039) for a
list of valid response codes.
Data Edit:
None.
Status:
RIF.: J-00259842-5
CAPITULO

PAGINA
77
VI
CAMBIO N
Message Types
Status Information
0110, 0120, 0130

0210, 0220, 0230
0312, 0392
0430
0530, 0532
0610
0810
Required.
0302
Optional. Required on adds and inquiries.
0420
Required. This must be the value from the original request.
FECHA:
26/04/2011
040 Service Restriction Code (not supported)

Attributes:
FIS: an 3
ISO: an 3
Description:
An identification of geographic/service availability.
Data Edit:
Numeric.
Status:
041 Card Acceptor Terminal Identification

Attributes:
FIS: an 8
ISO: an 8
Description:
A unique code identifying a terminal at the card acceptor location.
Data Edit:
None.
Status:
Message Types
Status Information
0100, 0110, 0120
Required.
0200, 0210, 0220

0420
RIF.: J-00259842-5
CAPITULO

PAGINA
78
VI
CAMBIO N
FECHA:
26/04/2011
042 Card Acceptor Identification Code

Attributes:
ISO: an 15
Description:
A code identifying the card acceptor that defines the point of the
transaction in both local and interchange environments.
Data Edit:
None.
Status:
Message Types
Status Information
0100, 0120
Optional.
0200, 0220
0110
0210
0420

043 Card Acceptor Name/Loc

Format:
Attributes:
ISO: an 40
El desglose de este campo cuya longitud es de 40 caracteres
alfanumricos se basa en las especificaciones de las normas del
estndar ANSI X9.2-1988. El Card Acceptor/Name/location debe ser
subdividido de la siguiente manera:
Position
1-23
24-36
37-38
39-40
Data
direccin
ciudad/Sector
estado
pas
Description:
En este campo se refleja la ubicacin fsica de los dispositivos ATM de

las Instituciones Bancarias.
Data Edit:
None.
Status:
CAPITULO

RIF.: J-00259842-5
PAGINA
79
VI
CAMBIO N
FECHA:
26/04/2011
Message Types
Status Information
0100, 0120
Optional.
0200, 0220
Required.
0110
Optional. Required if reversals for late response require this data

element.
0210
0420
Required, if available.
ABREVIACIN PARA LOS ESTADOS DE VENEZUELA:

ESTADO
ABREVIACIN
ESTADO
ABREVIACIN
ESTADO
ABREVIACIN
Zulia
ZU
Trujillo
TR
Monagas
MO
Falcn
FA
Tchira
TA
Delta
Amacuro
DA
Nueva
Esparta
NE
Mrida
ME
Apure
AP
Lara
LA
Barinas
BA
Bolvar
BO
Yaracuy
YA
Portuguesa
PO
Amazonas
AM
Aragua
AR
Cojedes
CO
Sucre
SU
Carabobo
CB
Gurico
GU
Anzotegui
AN
Distrito
Capital
DC
Miranda
MI
(*) La abreviacin utilizada para el pas (Venezuela) es: VE
RIF.: J-00259842-5
CAPITULO

PAGINA
80
VI
CAMBIO N
FECHA:
26/04/2011
044 Additional Response Data

Format:
LLVAR
Attributes:
FIS Corporation: an..25

ISO: an..25
Additional response data is subdivided as follows:
For an edit error with response code of 30, then positions 1-3 are
the bit number in error.
For authorizations and financial responses, positions 1-10 are
the phone number, and positions 11-25 are additional response
data.
For statement print responses, position 1 is either a Y indicating
this is the last message in the series, or an N indicating
additional data for the request is available. Positions 2-3 are set
to 00 if the host has preformatted the data returned in bit 121,
and 01 if the acquirer will format the statement receipt data in bit
121.
Other valid values are:
201 Reversal cannot be matched to original transaction.
235
Processor value on the pseudo-terminal

record in the data base is invalid for processor.
236
Invalid pseudo-terminal (value not found in data base).
Description:
Other data (for example, a telephone number) required in response to

an authorization or transaction request.
Data Edit:
None.
Status:
Message Types
Status Information
0110, 0130
Optional.
0210, 0230
0430
0312
Conditional.
0302
Future version.
CAPITULO

RIF.: J-00259842-5
PAGINA
81
VI
CAMBIO N
FECHA:
26/04/2011
045 Track 1 Data

Format:
LLVAR
Attributes:
FIS Corporation: ans..76

ISO: ans..76
Description:

ISO 7813, including field separators, but excluding beginning and ending
sentinels and LRC characters as defined therein.
Data Edit:
Valid ISO Track 1 required. Not allowed if manual entry.
Status:
Message Types
Status Information
0100, 0120
Conditional. Required if Track 1 is machine read; cannot be present if

the PAN is entered manually. One of these data elements is required:
002, 034, 035, 036, 045, or 100.
0200, 0220
0420
0110, 0130
Conditional. Is returned in the response if received in the request.
0210, 0230
0430
046 Additional Data, ISO

Format:
LLLVAR
Attributes:

ISO: ans..999
Description:
Data supplemental to that already conveyed in the specific data

requirements.
Status:
Not used.
RIF.: J-00259842-5
CAPITULO

PAGINA
82
VI
CAMBIO N
FECHA:
26/04/2011
047 Additional Data, National (not supported)

Format:
LLLVAR
Attributes:

ISO: ans..999
Description:
Reserved for national organizations to define data unique to country

applications.
MasterCard SecureCode for AAV and UCAF
Visa 3-D Secure
Status:
Message Types
Status Information
0100, 0120, 0200,
Required in check verification/guarantee.
0220
0110, 0120, 0200
Optional. Required if needed in reversal for late or unsolicited

response.
0220
0110, 0210
Conditional. Required if the issuer returns the address

verification data, CVV2 data, or check verification/guarantee
data.
0420
Conditional. Sent if present in the 01xx or 02xx message.
048 Institution/Merchant Name/Consumer Name (FIS-defined)

Format:
LLLVAR
Attributes:

ISO: ans..999
Description:
This data element is reserved by ISO for private data unique to private
institutions.
FIS Corporation defines this data element as Institution/Merchant
Name/Consumer, the name of the financial institution that owns the
ATM, or name of the merchant where the POS terminal is located, or the
name of the consumer for home banking.
Data Edit:
None.
Status:
CAPITULO

RIF.: J-00259842-5
Status Information
0100, 0120
Optional.
83
VI
CAMBIO N
Message Types
PAGINA
FECHA:
26/04/2011
0200, 0220
0420
0110
Optional. Required if needed in reversal for late or unsolicited response.
0210
049 Currency Code, Transaction

Attributes:
FIS Corporation: nP 3
ISO: n 3
Description:
The local currency of the acquirer or source location of the transaction.

Currency used in transaction amount and transaction fee amount.
Data Edit:
Numeric.
Status:
Message Types
Status Information
0100, 0110, 0120, 0130
Required.
0200, 0210, 0220, 0230

0420, 0430
050 Currency Code, Settlement

Attributes:
ISO: n 3
Description:
A code defining the currency of the settlement amount and the

settlement fee amount.
Note: FIS Corporation does not perform currency conversion.
Data Edit:
Numeric. Required if settlement amount is included in the message.
Status:
CAPITULO

RIF.: J-00259842-5
PAGINA
84
VI
CAMBIO N
FECHA:
26/04/2011
Message Types
Status Information
0100, 0110, 0120, 0130
Conditional. Required if settlement amount is included in the message
0200, 0210, 0220, 0230

0420, 0430
0520, 0522, 0530, 0532
Required.
051 Currency Code, Cardholder Billing

Attributes:
ISO: n 3
Description:
A code defining the currency of the cardholder billing amount and the
cardholder billing fee amount.
Data Edit:
Numeric. Required if settlement amount is included in the message.
Status:
Notes:
This data is logged in inbound messages, and is not supported in

outbound messages.
Message Types
Status Information
0100, 0110, 0120
Conditional. Required if cardholder billing amount is included in the

message.
0200, 0210, 0220

0420
052 Personal Identification Number (PIN) Data

Attributes:
FIS: b 8 bytes (if using numeric packing option)

FIS: 16 hex bytes (if not using numeric packing option) ISO: b 64
Description:
A number assigned to a cardholder intended to uniquely identify that

cardholder at the point-of-service. The use of the PIN is subject to a
bilateral agreement.
Note: If using clear PINs with the packing option, the 16-digit PIN field is
left-justified and padded with hex F on the right side prior to packing
the field.
Data Edit:
None.
Status:
RIF.: J-00259842-5
CAPITULO

PAGINA
85
VI
CAMBIO N
FECHA:
26/04/2011
Message Types
Status Information
0100
Conditional. Required if the card issuing institution requires this data

element for authorization.
0200
053 Security Related Control Information (not supported)

Attributes:
FIS: nP 16
ISO: n 16
Description:
This data element has not been defined by ISO. FIS defines this data
element as Security Related Control Information, consisting of data
needed to process PINs and perform message authentication, or
MACing. This data element is subdivided as follows:
Data Content/
Attributes
Notes
PIN and MAC key * Values are 00 or 01.

index (nP 2)
MAC key index

(nP 2)
* Contains
only PIN key index

when PIN and MAC keys are
exchanged in independent
messages.
Defined for future use.

Zero-filled.
* Contains MAC key index when
PIN and MAC keys exchanged
in independent messages.
*
Future use (nP12) Zero-filled.

Status:
CAPITULO

RIF.: J-00259842-5
PAGINA
86
VI
CAMBIO N
FECHA:
26/04/2011
054 Additional Amounts

Format:
LLLVAR
Attributes:
FIS: ans..120
ISO: ans..120
The data element breakdown, occurring six times, is:
Description:
Position
Data
1-2
Account Type (n 2)
3-4
Amount Type (n 2)
5-7
Currency Code (n 3)
8-20
Amount (x + n 12)
Information on up to six amounts and related account data for which

specific data elements are not defined.
Required on 0210 replies for ATM Check Deposits (processing code
24xxxx) when Cashback is present. Cashback Amount type (40) and
Gross Check Amount type (90) must be echoed on replies. Required on
0110/0210 Partial Pre-Authorization replies where
response code equals 10 or T7 Amount Type = 91
Data Edit:
Must be alphanumeric or numeric for Positions 1-4. Must be numeric for

Positions 5-20. The amount must not be greater than 999999999. x
must be 0, C, or D.
C or 0 = Credit amount
D = Debit amount
Status:
Message Types
Status Information
0100, 0120
Optional. This data element may be used for floor limits, hold amounts,
cash back amounts, pre-authorized amounts, or forwarding balances.
0200, 0220
0420
0110
0210
Optional. This data element may be used for returning balances or the
authorized amount.
RIF.: J-00259842-5
CAPITULO

PAGINA
87
VI
CAMBIO N
FECHA:
26/04/2011
055 Integrated Circuit Card (ICC) System-Related Data

Format:
LLLVAR
Attributes:
ISO b 255
Description:
Contiene los TAGS utilizados para soportar la tecnologa EMV (chip)
Data Edit:
ver tabla a continuacin.
Status:
ICC
Nota: Ver anexo Descripcin de los TAG que conforman el BIT 55
CAPITULO

RIF.: J-00259842-5
PAGINA
88
VI
CAMBIO N
FECHA:
26/04/2011
056 Replacement Additional Fees (not supported)

Format:
LLLVAR
Attributes:
FIS: ans..88
ISO: ans..999
The data element breakdown, occurring four times, is as follows:
Data Content / Position Attributes
1-2
Fee Type (n 2) Values are:

00 Transaction fee
15 Multiple Currency
Conversion Rate (MasterCard MCCR)
70 Surcharge
71 Optional Issuer Fee (Visa OIF)
Settle/Memo
Indicator (n 1)
Decimalization Value is 0; reserved for

Indicator (n 1) future use.
5-13
Fee Amount
(x+n8)
Settle Fee
Amount (x+n8)
14-22
Description:
Notes
If a surcharge is indicated,
then the settle indicator is
set using a value of 1.
If a transaction fee is indicated, then the settle
indicator is not set, indicated by a value of 0.
Information on up to four fees in addition to the fees defined in data

elements 095 (Replacement Amounts).
In this specific link, if data element 028 is defined to be used for
surcharge amounts only, then this field must not contain a surcharge.
Likewise, if data element 028 is defined as a transaction fee, then this
field must not contain a transaction fee.
Data element 095 is used for any replacement fee related to data
elements 028 and 029. Data element 056 is used for replacement fees
related to data element 055.
Data Edit:

C = Credit amount
Status:
CAPITULO

RIF.: J-00259842-5
PAGINA
89
VI
CAMBIO N
FECHA:
26/04/2011
057 Authorization Life Cycle (ANSI-defined)

Format:
LLLVAR
Attributes:
FIS: n..003
ISO: ans..999
Description:
The ANSI X9.2-1988 standard defines this data element as the

Authorization Life Cycle, a value in calendar days, hours, or minutes that
identifies the time period for which an acquirer is requesting guarantee
of funds. This data element is subdivided into the following two
subelements:
Life Cycle Indicator (n 1) indicates the type of time interval in effect
for a pre-authorization. Possible values are:
1 = calendar days
2 = hours
Data Edit:
3 = minutes
Life cycle (n 2) is the time interval in effect for a pre-authorization.
Numeric, if present. Length must be 003. Life Cycle

Indicator must be 1, 2, or 3.
Status:
Message Types
Status Information
0100, 0120
Conditional. Required for pre-authorizations.
0420
0110
RIF.: J-00259842-5
CAPITULO

PAGINA
90
VI
CAMBIO N
FECHA:
26/04/2011
058 National Point-Of-Service Condition Code (ANSI-defined)

Format:
LLLVAR
Attributes:
FIS Corporation: n..011

ISO: ans..999
Description:
Bit 22 and Bit 58 have many similar values. In agreement with other
endpoints, determine which fields are mandatory and which are optimal.
This data element is reserved for definition and use by national
standards organizations. The first 10 bytes are required. Byte 11 can be
used as a supporting alternative to bit 22.
The ANSI X9.2-1988 standard defines this data element as the National
Point-Of-Service Condition Code, a series of codes intended to identify
terminal class, presentation data, and security condition. This data
element is subdivided as follows:
Option 1
Terminal Class (an 3)
Presentation Data (an 4)
Security Condition (an 1)
Terminal Type (an 2), advice reason redefined by FIS
Corporation as terminal type. Data element 060 contains the
advice reason.
Card Data Input Capability (an 1)
Note: Refer to National POS Condition Code (bit 058) for a list of valid
codes.
Data Edit:
Either bit 025 or 058 is required; numeric if present.
Status:
Message Types
Status Information
0100, 0110, 0120
Conditional. Either data element 058 or 025 is required. The value of the
security condition may change from the value received from the acquirer
to indicate the CVV result.
0200, 0210, 0220

0420
RIF.: J-00259842-5
CAPITULO

PAGINA
91
VI
CAMBIO N
FECHA:
26/04/2011
059 National Point-Of-Service Geographic Data (ANSI-defined)

Format:
LLLVAR
Attributes:
FIS: an..017
ISO: ans..999
Description:

standards organizations.
The ANSI X9.2-1988 standard defines this data element as National
Point-Of-Service Geographic Data, a series of codes to identify the
state, county, postal service code, and country code where the point-ofservice device is physically located. This data element is subdivided as
follows:
State Code (n 2)
County Code (n 3)
Postal Service Code (an 5 or an 9)
Country Code (n 3)
If the county code is unavailable, this data element may be zero-filled if
later data elements are included. If the country code is included, blankfill the unused postal code positions.
Data Edit:
Numeric. State, County, and Country Codes must be numeric.
Status:
Message Types
Status Information
0100, 0120
Optional. May be required to qualify for lower fees from VISA or

MasterCard.
0200, 0220
0110
0210
0420
RIF.: J-00259842-5
CAPITULO

PAGINA
92
VI
CAMBIO N
FECHA:
26/04/2011
060 Advice/Reversal Reason Code (FIS-defined)

Format:
LLLVAR
Attributes:
FIS: an..006
ISO: ans..999
Description:
This data element is reserved for private definition.

FIS defines this data element as the following
sub-elements. These sub-elements identify the reason for a reversal
or an advice. The elements included depend on certain criteria:
For a reversal, the reversal reason is the only data sub-element
included.
For a reversal of an advice, the reversal and advice reason
(reason for the original advice) data subelements are included.
For an advice, the advice reason is the only data sub-element
included:
Sub-element
For-
Mask Description
Name
mat
Value
Byte Map
an 2
To determine the byte Map value, add the

mask value columns together for the data
elements that are present, and convert
the total to hexadecimal. For example, if
both subelements are present, the byte map
is C0.
Reversal
an 2
80
The code that
Reason
Advice
Reason
identifies why the transaction is reversed.

Refer to Advice/Reversal Reason Codes
(bit 060) for a list of reversal reason codes.
an 2
40
The code that

identifies why the advice is initiated.
Refer to Advice/Reversal Reason Codes
(bit 060) for a list of advice reason codes.
Data Edit:
None
Status:
Message Types
Status Information
0120
0220
0420
Optional.
RIF.: J-00259842-5
CAPITULO

PAGINA
93
VI
CAMBIO N
FECHA:
26/04/2011
061 Acquirer Transport Data (FIS-defined)

Format:
LLLVAR
Attributes:
FIS: ans..30
ISO: ans..999
Description:

FIS defines this data element as Acquirer Transport Data, free format
data of up to 100 bytes that is echoed to the acquirer in the response to
their request. This data element is not passed on to the issuer.
Data Edit:
None
Status:
Message Types
Status Information
0100, 0120
Optional.
0200, 0220
0420
0110, 0130
Conditional. Required if received in request
0210, 0230
0430
062 Issuer Transport Data (FIS-defined)

Format:
LLLVAR
Attributes:
FIS: ans..30
ISO: ans..999
Description:

FIS defines this data element as Issuer Transport Data, free format data
of up to 100 bytes that is echoed to the issuer in the response to their
request. This data element is not passed on to the acquirer.
Data Edit:
None
Status:
CAPITULO

RIF.: J-00259842-5
PAGINA
94
VI
CAMBIO N
FECHA:
26/04/2011
Message Types
Status Information
0302
Optional. Data length must be 40 or less.
0382
Optional. Data length must be 26 or less.
0312, 0392
Conditional. Required if received from the issuer.
063 FIS Data (FIS-defined)

Format:
LLLVAR
Attributes:
FIS: ans..050
ISO: ans..999
Description:

FIS defines this data element as FIS Data. The following is the division
of the subelements.
Sub-element
For-
Mask Description
Name
mat
Value
Byte Map
an 2
To determine the byte

Map value, add the mask value columns
together for the data elements that
are present, and convert the total to
hexadecimal. For example, if all
subelements are present, the byte map
value would be F8.
Pseudo-
an 6
80
The network-assigned Terminal

terminal ID that allows FIS to group
terminals under one ID.
Issuer
an 3
40
Used for direct routing Network

and telling the ID acquirer which
network authorized the transaction.
Acquirer
an 3
20
Tells the issuer which Network

network acquired the ID transaction.
Processor
an 6
10
Tells the issuer which ID

processor acquired The transaction (data
base value) and tells the acquirer which
processor authorized the transaction (data
base value). This is not a pass-through
data element. If received by the Connex
System, the data element is ignored.
CAPITULO

RIF.: J-00259842-5

n2
08
95
VI
CAMBIO N
Auth
PAGINA
FECHA:
26/04/2011
Tells the issuer the Timeout
amount of time prior to a financial request
being timed out. The value is the minimum
of either the field Auth Timeout or
Cardholder Processor Record Transaction
Timeout field. The Auth Timeout field can
be set by the Intercept Processor based on
The Intercept Record Transaction Timeout
field.
Data Edit:
None
Status:
Sub-element Name
Message Types
Status Information
Pseudo - Terminal
0100, 0110, 0120, 0130
Conditional. Required if multiple
0200, 0210, 0220, 0230
pseudo-terminals are required.
0420, 0430
Issuer Network ID
0100, 0120
Conditional. Required if
0200, 0220
implementing direct routing
0420
0110
Optional.
0210
Acquirer
0100, 0120
Network ID
0200, 0220
Optional.
0420
Processor ID
0100, 0110, 0120
Optional.
0200, 0210, 0220

0420
RIF.: J-00259842-5
CAPITULO

PAGINA
96
VI
CAMBIO N
FECHA:
26/04/2011
Sub-element Name
Message Types
Status Information
Auth Timeout
0100, 0110, 0120

0200, 0210, 0220
0420
Optional.
Open Account
Relationship Data
0100, 0110, 0120

0200, 0210, 0220
0420
Future.
Processing Flags
0100, 0110, 0120

0200, 0210, 0220
0420
Conditional. Required when supporting

externally settled transactions, also
required when the acquirer terminal is
capable of supporting partial
authorizations or when the acquiring
terminal does not support partial
authorizations, but want the issuers to
return balance amounts so the
transaction could be resubmitted with
that amount. See the document titled
Externally Settled Transactions for more
information.
064 Message Authentication Code (MAC) (not supported)

Attributes:
FIS: b 8 bytes (if using numeric packing option) or FIS: 16 hex bytes (if
not using numeric packing option)
ISO: b 64
Description:
Used to validate the source and the text of the message between the
sender and receiver. FIS performs MACing of the entire message.
Note: This field is currently zero-filled.
Data Edit:
MAC verification occurs. If the verification fails, the message is rejected

with a 0620 message.
Status:
This data element is used if MAC verification is enabled and the ISO
message contains a maximum of 64 data elements.
CAPITULO

RIF.: J-00259842-5
PAGINA
97
VI
CAMBIO N
FECHA:
26/04/2011
065 Bit Map, Extended

Attributes:

ISO: b 64
Description:

absence (denoted by 0) of data elements 129 through 192. These bits
are used for EMV Chip Card support.
Status:
Not implemented.
066 Settlement Code

Attributes:
FIS: nP 1
ISO: n 1
Values are:
Value
Description
In balance
Out of balance
Error
Description:
A code indicating the result of a reconciliation request.
Data Edit:
Must be 1, 2, or 3.
Status:
Message Types
Status Information
0530, 0532
Required.
067 Extended Payment Code (Not supported)

Attributes:
FIS: nP 2
ISO: n 2
Description:
The number of months that the cardholder prefers to pay for this item if
permitted by the issuer.
Data Edit:
Numeric.
Status:
CAPITULO

RIF.: J-00259842-5
PAGINA
98
VI
CAMBIO N
FECHA:
26/04/2011
068 Receiving Institution Country Code

Attributes:
FIS: nP 3
ISO: n 3
Description:
The code of the country where the receiving institution is located.
Status:
Not implemented
069 Settlement Institution Country Code

Attributes:
FIS: nP 3
ISO: n 3
Description:
The code of the country where the receiving institution is located.
Status:
Not implemented.
070 Network Management Information Code

Attributes:
FIS: nP 3
ISO: n 3
Description:
Used to identify network status. Refer to Network

Management Information Codes (bit 070) for valid values.
Data Edit:.
Valid network management code
Status:
Message Types
Status Information
0600, 0610, 0620

0800, 0810, 0820
Required.
071 Message Number

Attributes:
FIS: nP 4
ISO: n 4
Description:
A sequential, cyclic number assigned to a message by the message

initiator and used to monitor the integrity and interchange.
Data Edit:.
Numeric.
Status:
Message Types
Status Information
0600
Conditional. Required to indicate multiple message number.
CAPITULO

RIF.: J-00259842-5
PAGINA
99
VI
CAMBIO N
FECHA:
26/04/2011
072 Message Number Last

Attributes:
FIS: nP 4
ISO: n 4
Description:
A sequential, cyclic number assigned to a message by the message

initiator and used to monitor the integrity and interchange.
Data Edit:.
Numeric.
Status:
Message Types
Status Information
0600
Conditional. Required if bit 071 is present.
073 Date, Action

Attributes:
FIS: nP 6
ISO: n 6
Description:
This data element is intended to contain non-standard dates related to

authorization, such as the expiration date of a driver's license or a birth
date.
Data Edit:.
None.
Status:
Not implemented.
074 Credits, Number

Attributes:
FIS: nP 10
ISO: n 10
Description:
The number of credit transactions processed.
Data Edit:.
None.
Status:
Message Types
Status Information
0520, 0522
Required.
CAPITULO

RIF.: J-00259842-5
PAGINA
100
VI
CAMBIO N
FECHA:
26/04/2011
075 Credits, Reversal Number

FIS: nP 10
Attributes:
ISO: n 10
Description:
The number of credit reversal transactions processed.
Data Edit:.
None.
Status:
Message Types
Status Information
0520, 0522
Required.
076 Debits, Number

Attributes:
FIS: nP 10
ISO: n 10
Description:
The number of debit transactions processed.
Data Edit:.
None.
Status:
Message Types
Status Information
0520, 0522
Required.
077 Debits, Reversal Number

Attributes:
FIS: nP 10
ISO: n 10
Description:
The number of debit reversal transactions processed.
Data Edit:.
None.
Status:
Message Types
Status Information
0520, 0522
Required.
CAPITULO

RIF.: J-00259842-5
PAGINA
101
VI
CAMBIO N
FECHA:
26/04/2011
078 Transfer, Number

Attributes:
FIS: nP 10
ISO: n 10
Description:
The number of transfer transactions processed.
Data Edit:.
None.
Status:
Message Types
Status Information
0520, 0522
Required.
079 Transfer, Reversal Number

Attributes:
FIS: nP 10
ISO: n 10
Description:
The number of reversal transfer transactions processed.
Data Edit:.
None.
Status:
Message Types
Status Information
0520, 0522
Required.
080 Inquiry, Number

Attributes:
FIS: nP 10
ISO: n 10
Description:
The number of inquiry transactions processed.
Data Edit:.
None.
Status:
Message Types
Status Information
0520, 0522
Required.
CAPITULO

RIF.: J-00259842-5
PAGINA
102
VI
CAMBIO N
FECHA:
26/04/2011
081 Authorization, Number

Attributes:
FIS: nP 10
ISO: n 10
Description:
The number of authorization transactions processed.
Data Edit:.
None.
Status:
Message Types
Status Information
0520, 0522
Required.
082 Credits, Processing Fee Amount

Attributes:
FIS: nP 12
ISO: n 12
Description:
The amount of all processing fees associated with the handling and
routing of credit transactions.
Note: FIS does not calculate fees on-line.
Data Edit:.
None.
Status:
Message Types
Status Information
0520, 0522
Conditional. Required when surcharge fees or rebates are present.
083 Credits, Transaction Fee Amount

Attributes:
FIS: nP 12
ISO: n 12
Description:
The amount of all fees resulting from the processing of all credit
transactions.
Data Edit:.
None.
Status:
RIF.: J-00259842-5
CAPITULO

PAGINA
103
VI
CAMBIO N
FECHA:
26/04/2011
Message Types
Status Information
0520, 0522
Future. ISO fee definition is incomplete for transactions other than debit
and credit.
084 Debits, Processing Fee Amount

Attributes:
FIS: nP 12
ISO: n 12
Description:
The amount of all processing fees associated with the handling and
routing of debit transactions.
Data Edit:.
None.
Status:
Message Types
Status Information
0520, 0522
Future. ISO fee definition is incomplete for transactions other than debit
and credit.
085 Debits, Transaction Fee Amount

Attributes:
FIS: nP 12
ISO: n 12
Description:
The amount of all fees resulting from the processing of all debit
transactions.
Data Edit:.
None.
Status:
Message Types
Status Information
0520, 0522
Conditional. Required when surcharge fees or rebates are present.
CAPITULO

RIF.: J-00259842-5
PAGINA
104
VI
CAMBIO N
FECHA:
26/04/2011
086 Credits, Amount

Attributes:
FIS: nP 16
ISO: n 16
Description:
The amount of all credit transactions processed, exclusive of any fees.
Data Edit:.
None.
Status:
Message Types
Status Information
0520, 0522
Required.
087 Credits, Reversal Amount

Attributes:
FIS: nP 16
ISO: n 16
Description:
The amount of all credit reversals processed, exclusive of any fees.
Data Edit:.
None.
Status:
Message Types
Status Information
0520, 0522
Required.
088 Debits, Amount

Attributes:
FIS: nP 16
ISO: n 16
Description:
The amount of all debit transactions processed, exclusive of any fees.
Data Edit:.
None.
Status:
Message Types
Status Information
0520, 0522
Required.
CAPITULO

RIF.: J-00259842-5
PAGINA
105
VI
CAMBIO N
FECHA:
26/04/2011
089 Debits, Reversal Amount

Attributes:
FIS: nP 16
ISO: n 16
Description:
The amount of all debit reversals processed, exclusive of any fees.
Data Edit:.
None.
Status:
Message Types
Status Information
0520, 0522
Required.
090 Original Data Elements

Attributes:
FIS: nP 42
ISO: n 42
Description:
The data elements contained in the original message, intended to

identify a transaction for correction or reversal. These five data elements
are in fixed-length format totaling 42 numerics. Absence of data is
indicated by zeroes.
Original message type (n 4)
Original system trace audit number (n 6)
Original transmission date and time (n 10)
Note: FIS uses this field to hold the original local transaction date
and time.
Original acquiring institution identification code (n 11)
Original forwarding institution identification code (n 11)
Data Edit:.
Numeric.
Status:
CAPITULO

RIF.: J-00259842-5
PAGINA
106
VI
CAMBIO N
FECHA:
26/04/2011
Message Types
Status Information
0100, 0120
Conditional. Outbound from the Connex System, original message

type, original system trace audit number, and original local date and time
are sent if available.
0200, 0220
Inbound to the Connex System, element 090 is not supported.

0420, 0430
Required. Inbound to the Connex System, only subelement original

message type is implemented by FIS. The rest of the subelements must
be zero-filled. Outbound from the Connex System, original message
type is sent. Original system trace audit number and original local date
and time are sent if available.
Note: The trace number, date and time will either be zero-filled because
the information was not available or they will match data elements 011,
012, and 013.
091 File Update Code

Attributes:
FIS: an 1
ISO: an 1
Description:
A code that indicates to the system maintaining the file which procedure
to follow. Refer to File Update Codes (bit 091) for a list of valid values.
Data Edit:.
None.
Status:
Message Types
Status Information
0302, 0312, 0382, 0392
Required.
092 File Security Code

Attributes:
FIS: an 2
ISO: an 2
Description:
A file updates security code to indicate that the message originator is

authorized to update the file.
Status:
Not used.
CAPITULO

RIF.: J-00259842-5
PAGINA
107
VI
CAMBIO N
FECHA:
26/04/2011
093 Response Indicator

Attributes:
FIS: an 5
ISO: an 5
Description:
An indication of the update action taken by the point-of-service.
Status:
Not used.
094 Service Indicator

Attributes:
FIS: an 7
ISO: an 7
Description:
An indication of the type of support service required by the recipient of

the file update message. Used for coordinationof the file update
messages.
Status:
Not used.
095 Replacement Amounts

Attributes:
FIS: an 42
ISO: an 42
This data element consists of four data elements, which are in fixedlength format totaling 42 characters. Absence of data is indicated by
zeros. Following is a breakdown of the data contained in this data
element.
Actual amount, transaction (n 12)
Actual amount, settlement (n 12)
Actual amount, transaction fee (x + n 8)
Actual amount, settlement fee (x + n 8)
Description:
The new actual amount data elements, necessary to perform a partial

reversal on a financial transaction.
Note: See the description for 056 Replacement AdditionalFees
Data Edit:.
Numeric except x. For transaction and settlement, the maximum amount

is 999999999. For fees, the maximum amount is 9999. x must be 0, C,
or D.
C = Credit amount
Status:
CAPITULO

RIF.: J-00259842-5
Status Information
0420, 0430
Conditional. Required for partial reversals.
108
VI
CAMBIO N
Message Types
PAGINA
FECHA:
26/04/2011
096 Message Security Code

Attributes:
FIS: an 8
ISO: b 64
Description:
A verification between a card acceptor and an issuer that a message is

authorized to update or modify a special file.
Data Edit:.
None.
Status:
Message Types
Status Information
0302, 0382
Required.
0800, 0820
Conditional. Required when the value of bit 070 is 001, 002, 061, 062,
071, 072, 101, 161, or 171.
097 Amount Net Settlement

Attributes:
FIS: x + n 16
ISO: x + n 16
Description:
The net value of all gross amounts.

x must be 0, C, or D, where:
C or 0 = Credit amount
D = Debit amount
Data Edit:.
None.
Status:
Message Types
Status Information
0520, 0522, 0530, 0532
Required.
CAPITULO

RIF.: J-00259842-5
PAGINA
109
VI
CAMBIO N
FECHA:
26/04/2011
098 Payee (Not supported)

Attributes:
FIS: ans 25
ISO: ans 25
Description:
The third party beneficiary in a payment transaction.
Data Edit:.
None.
Status:
099 Settlement Institution Identification Code

Format:
LLLVAR
Attributes:
FIS: nP..11
ISO: n..11
Description:
A code identifying the settlement institution or its agent.
Data Edit:.
None.
Status:
Message Types
Status Information
0520, 0522, 0530, 0532
Required.
100 Receiving Institution Identification Code

Format:
LLLVAR
Attributes:
FIS: nP..11
ISO: n..11
Description:
The identity of the institution receiving a request or advice message in

an interchange system if it is not the same as identified in the primary
account number.
Data Edit:.
None.
Status:
RIF.: J-00259842-5
CAPITULO

PAGINA
110
VI
CAMBIO N
FECHA:
26/04/2011
Message Types
Status Information
0100.
(Check Verification /Guarantee Request) - (Conformacin de

Cheques)
Required. This data element holds the FIS assigned ID of the
check guarantor
0110
Conditional. Required if in the request message.
101 File Name

Format:
LLLVAR
Attributes:
FIS: ans..17
ISO: ans..17
Description:
The actual or abbreviated name of the file being accessed.
Data Edit:.
Following are the required data element values for the corresponding
message types.
Message Type
Value
0302
PI-NEGATIVE for cardholder

file update
0382
CHnn for cardholder file maintenance

ADnn for account detail file maintenance where
nn = the AP file segment ID
Status:
Message Types
Status Information
0302, 0382
Required.
CAPITULO

RIF.: J-00259842-5
PAGINA
111
VI
CAMBIO N
FECHA:
26/04/2011
102 Account Identification 1

Format:
LLLVAR
Attributes:
FIS: ans..28
ISO: ans..28
Description:
A series of digits used to identify a customer account or relationship.

Account identification 1 identifies the account involved for a single
account transaction. In the case of transfers, Account Identification 1
identifies the from account in a transaction.
Data Edit:.
None.
Status:
Message Types
Status Information
0100, 0110, 0120
Optional.
0200, 0210, 0220

0420
103 Account Identification 2

Format:
LLLVAR
Attributes:
FIS: ans..28
ISO: ans..28
Description:
Series of digits used to identify a customer account or relationship.

Account identification 2 is primarily used for the to account in a transfer
transaction. (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.
Data Edit:.
None.
Status:
Message Types
Status Information
0100, 0110, 0120
Optional.
0200, 0210, 0220

0420
Nota: La estructura alfanumrica del Bit 103 en una Transferencia Interbancaria o Pago de
Servicios se compone de una serie de dgitos, tal y como fue informado anteriormente.
CAPITULO

RIF.: J-00259842-5
PAGINA
112
VI
CAMBIO N
FECHA:
26/04/2011
104 Transaction Description

Format:
LLLVAR
Attributes:
FIS: ans..100
ISO: ans..100
Description:
Data describing additional characteristics of the transaction for billing

purposes. The first position may contain a reimbursement attribute. See
the following for more information:
_ Statement Print Transaction Format
_ Advanced ATM Transaction Format
Data Edit:.
Numeric. Required if PAN entry mode indicates manual entry.
Status:
Message Types
Status Information
0100, 0120,
Conditional. Sent if the data is present. Required on a 0100 for

statement printing, stop payment, check reorder, check inquiry, mail
statement, information inquiry, and notification to bank transactions
0200, 0220,
0420
0110, 0210
Optional. This data element 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.
0110
Required on a 0110 for stop payment, check reorder, check inquiry, mail
statement, information inquiry, and notification to bank transactions.
Nota: 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, tal y como fue informado
anteriormente.
RIF.: J-00259842-5
CAPITULO

PAGINA
113
VI
CAMBIO N
FECHA:
26/04/2011
Statement Print Transaction Format

Pos.
Format
Description
1-4
CCCC
The statement type, which can be one of the following

MINI = Mini statement
FULL = Full statement
5-6
CC
7-19
The class of statement, which identifies to the host what data the
customer wants to include in the statement print. Examples might include
whether or not ATM, POS or Teller transactions are to be included in the
statement. Values are user-defined.
Not used at this time.
20-25
YYMMDD
The statement start date. This data is optional.
26-31
YYMMDD
The statement end date. This data is optional.
32-55
56-59

CCCC
Device characteristics, which identifies to the host

various characteristics of the terminal which is
initiating the request for a statement. Values are
defined entirely by the installation via the CR. The
host may define this field to identify printer or screen characteristics.
60-64
NNNNN
Requested number of pages, which contains the total number of

statement pages or entries that are expected to make up the statement
print request. This number may be used to prompt the customer to
proceed with printing, given the number of entries found.
65-69
NNNNN
Completed number of pages, which contains the total number of

statement pages or entries that were actually printed during the statement
print request. This value is determined by unique code within the
acquirer.
70-100
RIF.: J-00259842-5
CAPITULO

PAGINA
114
VI
CAMBIO N
FECHA:
26/04/2011
Advanced ATM Transaction Format

Pos.
Format
Description
1-4
an 4
The statement type, which can be one of the following:

'STOP' = Stop payment
'CHKR' = Check reorder
'ITEM' = Check inquiry
'SRQ ' = Mail statement
' ' = Information inquiry
' ' = Notification to bank
5-6
an 2
7-8
The class of statement, a transaction qualifier which is used to identify to

the host what data the customer wants to include in advanced ATM
functions. Values are defined by the host.
9-14
n6
The check number, which identifies one of the following:

The check number for check inquiries.
The starting check number for check reorders.
The check number to stop for stop payments.
15-18
n4
The check quantity, which identifies the number of checks for check
reorders.
19-100
105 Large Private Data 1 (not supported)

Format:
LLLVAR
Attributes:
FIS: ans..255
ISO: ans..999
Description:
This data element is used with data elements 106-108 to return large
amounts of data.
Status:
CAPITULO

RIF.: J-00259842-5
PAGINA
115
VI
CAMBIO N
FECHA:
26/04/2011
Reserved Tags
The following tags are reserved for data elements 105-108.
Code
Description
VA
Verified by Visa
V0 = CAVV data
V1 = XID data
Tagged Format
Tags are assigned to represent and identify the specific information immediately following a
tag identifier. The tag ID is 5 positions long, always beginning with an asterisk (*), followed by
the 2-character tag ID, followed by another asterisk (*), followed by a backslash (\). For
example: *xx*\ where: xx is an alphanumeric value that represents the tag.
Tagged Length Indicator
The 4-digit length indicator identifies the length of information immediately following the tag,
versus the actual length of the data element. Tagged data can be transported using fields
105, 106, 107, and 108 in combination, and can be as long as the total of all four fields
combined. The maximum data length for a single tag is 1011 bytes.
Each field (105, 106, 107, and 108) carries up to 255 bytes of information. However, nine
positions are used with the tag:
Five positions are used for the tag ID layout.
Four positions are used for the length of the tagged information.
See the following examples of the different variations using a single tag and multiple tags.
Example 1
This example shows a single tag in a single large private data field.
105LLL|*T1*\| T1 data (maximum 255 characters)
Example 2
This example shows a single tag over multiple large private data fields.
105LLL|*T1*\|first 250 bytes of data |
106LLL|rest of data (up to 255 bytes)
Example 3
This example shows multiple tags in a single large private data field.
105LLL|*T1*\|T1 length|T1 data|*T2*\|T2 length|T2 data|
CAPITULO

RIF.: J-00259842-5
PAGINA
116
VI
CAMBIO N
FECHA:
26/04/2011
Example 4
This example shows multiple tags in multiple large private data fields.
105LLL|*T1*\|T1 length|T1 data (more than 255 bytes)|
106LLL|remaining T1 data|*T2*\|T2 length|T2 data|
9X10 Open Account Relationship (OAR) Format
Following are requirements for OAR response data:
Delimiters are required between subfields to identify subfields without data.

Delimiters for trailing empty subfields are not required.
The backslash (\) is used to separate subfields.
An asterisk (*) is used to separate accounts.
FIS Corporation requires that the Account Number sub-element and OAR
Select Type sub-element be returned in the response from the host.
The account data is repeated for each account, up to 10 accounts.
The layout of the account information follows.

NOTE: Although OAR is FIS Corporation-defined, a tag is not necessary because it has a
unique message type. No other usage of large private data is available for the OAR-type
messages
Sub-Element Name/Contents
Length
Status
28 maximum
Required
Field delimiter.
Value: \
Required
OAR Select Type (service line). For values, see

Account Type under Additional Amounts Codes (bit 054)
Required
Field delimiter.
Value: \
Optinal
4 maximum
Optinal
Required
Account Number.
Account Type. For example, NOW, SNOW

Field delimiter.
Value: \
Account Access. Values are:
0 = DB+CR (default)
1 = DB
2 = CR
Field delimiter.
Value: \
Optional
Requiered
RIF.: J-00259842-5
CAPITULO

117
VI
CAMBIO N
FECHA:

Account Qualifier.
PAGINA
26/04/2011
3 maximum
Optinal
Requiered
28 maximum
Optional
Field delimiter.
Value: \
Requiered
Balance Data:
Balance Type (2 bytes). For values, see
Additional Amounts Codes (bit 054) .
Currency Code (3 bytes). For example, 840 = U.S.
dollars.
Balance Amount (13 bytes maximum)
18
Optinal
Field delimiter.
Value: \
Account Description.
Example 1
In this example, information is provided for two accounts:
246813579\20\NOW\1\Checking 1*1357924\20\NOW\\Checking 2*
Example 2
In this example, three 16-digit accounts use 20 bytes per account, including delimiters:
1234567890123456\20*2345678901234567\20*3456789012345678\20*
Status:
Refer to the following chart for the FIS Corporation data element requirements:
Messages Types
Status Information
0110
Optional. This data is sent if available and you are using FIS
Corporation-defined private data elements.
0600
Conditional. Required when data element 070 equals 810, 811, 812,
821, or 822.
9110, 9210
Required.
RIF.: J-00259842-5
CAPITULO

PAGINA
118
VI
CAMBIO N
FECHA:
26/04/2011
106 Large Private Data 2 (Not supported)

Format:
LLLVAR
Attributes:
FIS: ans..255
ISO: ans..999
Description:
This data element is used when the amount of data exceeds the data
sent in data element 105.
Status:

Format:
LLLVAR
Attributes:
FIS: ans..255
ISO: ans..999
Description:
sent in data elements 105 and 106.
Status:

Format:
LLLVAR
Attributes:
FIS: ans..255
ISO: ans..999
Description:
sent in data elements 105-107.
Status:
109 through 110 Reserved for ISO Use

Format:
LLLVAR
Attributes:
FIS: ans..255
ISO: ans..999
Description:
These data elements are reserved for future definition and use by ISO.
Status:
Not used.
RIF.: J-00259842-5
CAPITULO

PAGINA
119
VI
CAMBIO N
FECHA:
26/04/2011
111 Additional Data, Private Acquirer (FIS-defined)

Format:
Attributes:
LLLVAR
FIS: ans..255
ISO: ans..999
Description:
This data element is reserved by ISO for private definition and use. FIS
defines this data element as Additional Data, Private Acquirer, which
contains additional information for VISA and American Express. See the
following for more information:
American Express Format
VISA DCS Format
VISA EVES Format
VISA DCS CRIS Format
Status:
This data element is currently supported for American Express and

VISA.
112 Reserved for National Use

Format:
LLLVAR
Attributes:
FIS: ans..255
ISO: ans..999
Description:

Status:
Not used.
RIF.: J-00259842-5
CAPITULO

PAGINA
120
VI
CAMBIO N
FECHA:
26/04/2011
113 Authorizing Agent Institution ID Code (ANSI-defined)

Format:
LLLVAR
Attributes:
FIS: n..011
ISO: ans..999
This code is normally an institution identification code (IID) in the format
1NNNNNNNNC, where:
NNNNNNNN = the institution ID code
C = a check digit
Description:

The ANSI X9.2-1988 standard defines this data element as the
Authorizing Agent Institution ID Code, which identifies the institution
approving or denying an authorization, financial transaction, or reversal.
This code can be any uniquely identifying number agreed upon by the
network.
Data Edit:
Numeric. If the element begins with a 1, this data element must be an

Institution ID (IID) code with a valid check digit.
Status:
Refer to the following chart for the FIS data element Requirements.
Message Types
Status Information
0100, 0110, 0120
Optional.
0200, 0210, 0220

0302
0420
0382
Required.
RIF.: J-00259842-5
CAPITULO

PAGINA
121
VI
CAMBIO N
FECHA:
26/04/2011
114 Country Code, Authorizing Agent (ANSI-defined) (Not supported)

Format:
LLLVAR
Attributes:
FIS: an..3
ISO: ans..999
Description:

The ANSI X9.2-1988 standard defines this data element as Country
Code, Authorizing Agent, the code identifying the country where the
authorizing agent institution is located as set out in ISO 3166.
Data Edit:
Numeric.
Status:
Refer to the following chart for the FIS data element Requirements.
115 through 119 Reserved for National Use

Format:
LLLVAR
Attributes:
FIS: ans..255
ISO: ans..999
Description:
These data elements are reserved for definition and use by national
Status:
Not used.
RIF.: J-00259842-5
CAPITULO

PAGINA
122
VI
CAMBIO N
FECHA:
26/04/2011
120 Account Qualifiers (FIS-defined)

Format:
LLLVAR
Attributes:
FIS: an..6
ISO: ans..999
Description:
This data element is reserved by ISO for private definition and use.
FIS defines this data element as Account Qualifiers 1 and 2. The data
element identifies the account(s) involved for a transaction, and is made
up of the following subelements.
Sub-element/Attributes
Description
Account Qualifier 1 (an 3)
Identifies the account involved for a single

account transaction, or in the case of
transfers, it identifies the from side of the
transaction.
Account Qualifier 2 (an 3)
Used only in the case of transfers; it

identifies the to side of the transaction.
Data Edit:
None.
Status:
Message Types
Status Information
0100, 0110, 0120
Optional.
0200, 0210, 0220

0420
RIF.: J-00259842-5
CAPITULO

PAGINA
123
VI
CAMBIO N
FECHA:
26/04/2011
121 Additional Data, Private Issuer (FIS-Defined)

Format:
LLLVAR
Attributes:
FIS: ans..255
ISO: ans..999
Description:
For statement print transactions:
This data element has no current defined use in statement print
transactions, but it can be used if the host wants to return information to
the ATM or Format 8 PI. The format of the field is LLLVAR, with a
maximum length of 255 bytes.
For advanced ATM transactions:
In Check Inquiry responses, this data element contains the check
posting date and the amount of the check in the following format:
YYMMDD\nnnnnnnn\\
For MasterCard information, see MasterCard CIS Format See
VISA SMS
Status:
Message Types
Status Information
0110
Optional. This data element is used in check inquiry responses.

Note: This data element can be used in statement print transactions if
the host wants to return atatement print information to the ATM or
Format 8 PI.
122 Sponsor Bank ID (FIS-Defined)

Format:
LLLVAR
Attributes:
FIS: an..11
ISO: ans..999
Description:
FIS defines this data element as Sponsor Bank ID, which identifies the
institution serving the merchant POS terminal. In the case of VISA, it is a
bank identification number (BIN). In the case of MasterCard, it is an MCI
customer ID.
Data Edit:
None.
Status:
RIF.: J-00259842-5
CAPITULO

Status Information
0100, 0110, 0120
Optional.
124
VI
CAMBIO N
Message Types
PAGINA
FECHA:
26/04/2011
0200, 0210, 0220

0420
123 AVS/Check Auth Data/New PIN (FIS-defined)

Format:
LLLVAR
Attributes:

ISO: ans..999
Description:
FIS Corporation defines this data element as AVS/Check Auth
Data/New PIN, data required for check transactions (check guarantee
and check verification), or financial transactions (such as address
verification and new PIN transactions).
The check transaction data and financial transaction data are sent in
either multiple-tag or single-tag format.
Check Transactions, Multiple-Tag Format
Check Transactions, Single-Tag Format
Financial Transactions, Multiple-Tag Format
Financial Transactions, Single-Tag Format
Overview Multiple-Tag Data Format

The ISO subfields have a definite layout. If a field within a tag is present, all defined preceding
fields must be present. Adding a trailing field can be dynamic.
The multiple-tagged data is sent in the following format:
TD AA AALength AAdata BB BBLength BB data CC length CC data
where:
TD = Tagged Data format code

AA = Subformat code 1
BB = Subformat code 2
CC = Subformat code 3
Check Transactions, Multiple-Tag Format

The following multiple-tag data formats are supported for check authorization transactions.
NOTE: The single-tag format is not allowed within the multiple-tag format.
CAPITULO

RIF.: J-00259842-5
125
VI
CAMBIO N
Format Type and Field Name
PAGINA
FECHA:
26/04/2011
Length /
Attributes
Pos.
Values
Tagged Data
ISO Subfield
MICR Formatted
Format Code
Length
Routing & Transit
Account Number
Check Serial Number
Validation Type
Process Control
2
2
n9
n18
an12
an1
an6
MF
01-46
01-09
10-27
28-39
40
41-46
Cdula de Identidad
Format Code
Length
State Code
Drivers License
Validation Type
2
2
an2
an28
an6
CI
01-31
01-02
03-30
31
Plastic Card
Format Code
Length
PAN (plastic card)
Validation Type
2
2
an28
an1
PL
01-29
01-28
29
MICR Unformatted
Format Code
Length
Validation Type
MICR Data
2
2
an1
an65
MU
01-66
0102-66
Social Security Number
Format Code
Length
State Code
Social Security #
2
2
an1
an9
SS
01-11
01-02
03-11
State ID
Format Code
Length
State Code*
State ID
2
2
an2
an22
SI
01-24
01-02
03-24
CAPITULO

RIF.: J-00259842-5
PAGINA
126
VI
CAMBIO N
FECHA:
26/04/2011
* With FIS Authorization Systems, for military IDs, use a

state code of MY.
Date of Birth
Format Code
Length
Date of Birth (yyyymmdd)
2
2
an2
DB
01-08
01-08
Phone Number
Format Code
Length
Phone Number
2
2
an10
PN
01-10
01-10
Zip Code
Format Code
Length
Zip Code
2
2
an10
ZC
01-10
01-10
Propietary ID
Format Code
Length
Propietary ID
2
2
an28
PI
01-28
01-28
Check Number * (manually Entered)
Format Code
Length
Check Number
2
2
an12
CN
01-12
01-12
*For FISSM Authorization System, if bit 022 equals 900,

then CN is required. If bit 022 is not equal to 900, CN is
optional
Check Transactions, Single-Tag Format

The following single-tag data formats are supported for check authorization transactions.
However, these formats are not used for FISSM Authorization Systems.
NOTE: When you are using the single-tag format, only one tag is allowed.
CAPITULO

RIF.: J-00259842-5
127
VI
CAMBIO N
PAGINA
FECHA:
26/04/2011
Length /
Attributes
Pos.
Values
MICR
Format Code
State Code
MICR Inst ID
MICR Number
Check Number
Zip Code
2
an2
an8
an10
an6
an9
01-02
03-10
11-20
21-26
27-35
MR
2
an2
an22
an6
an6
01-02
03-24
25-30
31-36
2
an2
an19
an6
01-02
03-21
22-27
Cdula de Identidad
Format Code
State Code
Drivers License Number
Check Number
Date of Birth
CI
Plastic Card
Format Code
State Code
PAN (plastic card)
Check Number
PC
Financial Transactions, Multiple-Tag Format

The following multiple-tag data formats are supported for financial transactions.
NOTE: The single-tag format is not allowed within the multiple-tag format.
CAPITULO

RIF.: J-00259842-5
PAGINA
128
VI
CAMBIO N
FECHA:
26/04/2011
Length
Values
Tagged Data
TD
ISO Subfield
AVS Data
Format Code
Length
Data
Result
2
2
01-29
1
Note: The AVS data may be in two formats:

Address with optional AVS result
AVS result only
AV
01-29
AVS result (see values under Financial
Transactions, Single-Tag Format
------------ OR ------------AVS Result
Format Code
Length
Present Indicator
2
2
1
Response Type
Data
Result
1-4
Note: The CVV2 may be in two formats:

CVV2 data with result
CVV2 result only
CV
01-07
0=CVV2 not present
1=CVV2 present
2=CVV2 not legibe
9=CVV2 not imprinted
0=Response code only
1=Response code and result
The actual CVV2 data
M=Match
N=No match
P=No processed
S=Not on card
U=No key, not certified, or both
------------- OR -------------CVV2 Result

Format Code
Length
Result
2
2
1
CR
01
See values in CVV2 formar above
RIF.: J-00259842-5
CAPITULO

PAGINA
129
VI
CAMBIO N
FECHA:
26/04/2011
CAVV Result
Format Code
Length
Result
2
2
1
CR
01
Blank or not present = CAVV not
present
0 = CAVV authentication results invalid
1 = CAVV failed validation
authentication
2 = CAVV passed validation
authentication
3 = CAVV passed validation attempt,
CAVV generated by issuer ACS.
4 = CAVV failed validation attempt,
CAVV generated by issuer ACS.
5 = Not currently used, reserved for
future use.
6 = CAVV not validated, issuer not
participating in CAVV validation.
CAVV generated by Visa ACS.
8 = CAVV passed validation attempt,
CA VV generated by Visa ACS.
CAVV generated by Visa ACS, issuer
ACS not available.
A = CAVV passed validation attempt,
CAVV generated by Visa ACS, issuer
ACS not available.
B = CAVV passed validation information
only, no liability shift.
C = CAVV was not validated attempt.
D = CAVV was not
validatedauthentication.
DCVV Result
Format Code
Length
Result
2
2
2
DC
02
01=Valid
02=Invalid
03=Not Validated
ATC Result
Format Code
Length
Result
2
2
2
AT
02
01=Valid
02=Out of Range
03=Seq Duplicate
04=Not Validated
CAPITULO

RIF.: J-00259842-5
PAGINA
130
VI
CAMBIO N
FECHA:
26/04/2011
Financial Transactions, Single-Tag Format

The following single-tag data formats are supported for financial transactions.
Format Type and Field
Name
Length
Pos.
Values
Note: The AVS data may be in two formats:
Address with optional AVS result
AVS result only
AVS Data
AV
Format Code
Zip Code
Address or 5 digits of
address
2
9
20
1
AVS Result
Format Code
Zip Code
Address or 5 digits of
address
2
9
20
1-2
3-11
12-31
32
1-2
3-11
12-31
A=Address matches, zip code does not.

N=Nothing matches
R=Retry, system unable to process.
S=AVS not supported (converted by Visa to
U before response is sent to the acquier)
U = No data from issuer/Banknet Switch.
W = 9-digit zip code matches, but
address does not.
X = Address and 9-digit zip code
match exactly (converted by Visa to a
Y before response is sent to the
acquirer).
Y = Yes, all digits match 5-digit zip code.
Z = 5-digit zip code matches, but address does

not (converted by Visa to a W before response
is sent to the acquirer).
------ OR -------AVS Result
Format Code
AVS Result
2
1
1-2
3
AR
2
48
1-2
3-50
UM
Note: Passing this data is not
supported for check Authorization
2
1
1-2
3-18
NP
Unformatted MICR
Format Code
Unformatted MICR
New PIN
Format Code
New PIN (encrypted)
currently
CAPITULO

RIF.: J-00259842-5
PAGINA
131
VI
CAMBIO N
FECHA:
26/04/2011
Data
Length
Sub-Element Name/Contents
Data Identifier. Value is VR to indicate validation results on the AAV data that was
passed in the 3-D Secure 0100 or 0200 message requesting purchase authorization.
Data Length. Identifies the length of the byte map including the variable data. The value
may be a maximum of 01.
123.1 - Value of the AAV Result Code for MasterCard SecureCode.
FISSM AAV Result Code Values for MasterCard SecureCode

AAV Validation Result Code
Description
Definition
Blank or Not
NOT PRESENT:
AAV Not Present
This value means that the authorization

message did not contain any data in
Field 48 sub element 43 and that DE48
sub element 42 was not a value of 2.
No liability shift.
INVALID:
AAV authentication results
invalid
There was data in Field 48 sub-element

43 but it could not be processed due to
an incorrect field format or incorrect
data components. No liability shift (if
declined).
FAILED:
AAV failed validation
authentication
The validation of the Message

Authentication Code (MAC) failed for an
authenticated transaction. This is an
indication of potential bad or fraudulent
data submitted in field 48 sub-element
43 of the authorization message. No
liability shift (if declined).
PASSED:
AAV passed validation authentication.
The validation of the MAC for an

authenticated transaction was
approved. Liability shift.
FAILED:
AAV not validated, issuer
keys not on file.
This value is an indication of a possible

problem that the authorization
contained the MAC (DE 48 sub-element
43) but the issuer keys were not on file.
Also, the option may not be configured
in the database (Card Options). No
liability shift (if transaction was
declined).
Present
Nota: La estructura del Bit 123 (Msg. 0100, 0120 y 0200) depende de la transaccin u
operacin a realizarse; es decir: de la Conformacin de Cheques, la Transferencia
Interbancaria, el Pago de Servicios y las operaciones originada en los Punto de Ventas.
CAPITULO

RIF.: J-00259842-5
PAGINA
132
VI
CAMBIO N
FECHA:
26/04/2011
Message Types
Status Information
0100, 0120, 0200, 0220
Required in check verification/guarantee (Conformacin de Cheques).
0100, 0120, 0200, 0220
Conditional. Required when doing address verification.
0110, 0210
Conditional. Required if the issuer returns the address verification result.
0420
Conditional. Sent if present in the 01xx or 02xx message.
Pregunta de Desafo
A fin de complementar la informacin relativa al cdigo de rechazo utilizado en las Preguntas
de Desafo (cdigo 80), se requiere 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 se manejan las operaciones
rechazadas por PIN invlido, se 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 con algunos bancos, 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.
CAPITULO

RIF.: J-00259842-5
PAGINA
133
VI
CAMBIO N
FECHA:
26/04/2011
Ejemplo:
Los Bancos manejan lo relacionado a PIN INVALIDO (55), a travs de un contador
que va desde mnimo 3 intentos a mximo 5 Intentos, lo que depende del Banco; es
decir a cada intento fallido el Banco responde con el Cdigo 55 (INCORRECT PIN),
tanta veces como lo haya establecido el Banco (3 o 5 veces) luego de este lmite, al
prximo intento el cdigo que enva el banco es 75 (ALLOWED NUMBER OF PIN
TRIES EXCEEDED) y as sucesivamente.
En conformidad con lo anterior, se propone manejar lo relacionado a PD
INCORRECTA (80) igual a travs de un contador y con los mismos lmites. Ahora
bien, una vez excedido el limite de intentos establecido por los Bancos (3 o 5 veces)
los bancos deberan contestar al prximo intento fallido con el cdigo 75 (ALLOWED
NUMBER OF PIN TRIES EXCEEDED) y luego de esto proponemos utilizar el cdigo
62 (RESTRICTED CARD) o el cdigo 59 (SUSPECT FRAUD).
124 Info, Text (FIS-defined)
Format:
LLLVAR
Attributes:
FIS: ans..255
ISO: ans..999
Msg
Network
Data
Type
Code
Length
Data Content
0382
Cardholder or account file maintenance data

defined as Field Record Length in the Format 8
Interface Specifications Manual.
(This data begins in position 42 of an I51 message.)
0600
800
01-206
801
0620
900
01-06 Character source name 07-12 Character

destination name (The field is set to all blanks when it
is received by the final destination) 13-206 Processor
to processor mail * Message must displayable.
01-255 ANA-generated messages. (Not Implemented)
01-255 First 255 bytes of message in error
Description:
This data element is reserved by ISO for private definition and use. FIS defines
this data element as Info, Text, additional information used for administrative and
network management transactions. It is also used for AP file update information in
AP file update transactions.
Status:
CAPITULO

RIF.: J-00259842-5
134
VI
CAMBIO N
FECHA:
Message Types
Status Information
0382, 0392
Required.
PAGINA
26/04/2011
0620
0600
Conditional. Required when data element 070 equals 800.
125 Network Management Information (FIS-defined)

Format:
LLLVAR
Attributes:
FIS: ans..50
ISO: ans..999
Description:
FIS defines this data element as Network Management Information.
Network
Data
Code
Length
Data Content
005
01-50
Text message to Connex operator. All characters in

the message must be displayable.
101
36 For
* 32 character PIN encryption
PIN
Key (for both IWK and AWK)
encryption * 4 character check digits
key only
(first 4 bytes of the result of encrypting 16 zeros with
the key being transmitted)
56 For
MACing
Also
161
Data for sending PIN

encryption
key (see above) plus the following:
16 character MAC key (for both issuer and
acquirer)
4 character check digits (first 4 bytes of the result
of encrypting 16 zeros with the MAC key being
transmitted)
36 For
* 32 character PIN
PIN
encryption key (an IWK)
encryption * 4 character check digits
key only
CAPITULO

RIF.: J-00259842-5
171
36 For
PIN
encryption
key only
135
VI
CAMBIO N
56 For
MACing
Also
PAGINA
FECHA:
26/04/2011

encryption
14 16 character MAC key (from issuer)
transmitted)
* 32 character PIN
encryption key (an AWK)
* 4 character check digits
56 For
MACing
encryption
Also

16 character MAC key (from acquirer)
transmitted)
281
23-30
* 6 character pseudo-terminal ID
* 15 character real terminal ID or ALL
* 2 character settlement type (96-99)
* 7 character amount (used with settlement type 97-98)
282
2 character settlement type (00-09)
Status:
Message Types
Status Information
0800, 0820
Required in 0800 and 0820 messages with Network Management Code (bit
070) of 005, 101, 161, 171, 281, and 282.
RIF.: J-00259842-5
CAPITULO

PAGINA
136
VI
CAMBIO N
FECHA:
26/04/2011
126 Issuer Trace Data (FIS-defined)

Format:
LLLVAR
Attributes:
FIS: ans..050 (ans..040 for Star and Honor)

ISO: ans..999
Description:
FIS defines this data element as Issuer Trace Data. Used to return the
issuer's trace data that is stored in the IMM Processor Data Area, this
data element allows information that is stored by the PI communicating
to the issuer to be returned to the acquirer.
Data Edit:
None.
Status:
Message Types
Status Information
0100, 0110, 0120
Optional.
0200, 0210, 0220

0420
127 Acquirer Trace Data (FIS-defined)

Format:
LLLVAR
Attributes:
FIS: ans..050 (ans..040 for Star and Honor)

ISO: ans..999
Description:
This data element is reserved by ISO for private definition and use. FIS
defines this data element as Acquirer Trace Data. It is used to send the
acquirer's trace data, stored in the IMM Acquirer Data Area. This allows
information that is stored by the PI communicating to the acquirer to be
sent to the issuer.
Data Edit:
None.
Status:
Message Types
Status Information
0100, 0110, 0120
Optional.
0200, 0210, 0220

0420
CAPITULO

RIF.: J-00259842-5
PAGINA
137
VI
CAMBIO N
FECHA:
26/04/2011
128 Message Authentication Code (MAC) (not supported)

Format:
LLLVAR
Attributes:
FIS: b 8 bytes (if using numeric packing option)

FIS: 16 hex bytes (if not using numeric packing option) ISO: b 64
Used to validate the source and the text of the message between the
sender and receiver. FIS performs MACing of the entire message.
Description:
Note: This field is currently zero-filled.

Data Edit:
MAC verification occurs. If the verification fails, the message is rejected

with a 0620 message.
Status:
Not implemented.
Terminal Capability Profile

Attributes:
FIS Corporation: 3 bytes

EMV: 24 bits, 3 bytes
EMV Tag:
9F33
Description:
A series of 24 bits used to identify the card data input, the Cardholder
Verification Method (CVM), and the security capabilities supported by the
terminal. Visa requires this as a retain and return field for chargeback and
representments.
Status Notes:
This data element is optional for MasterCard and required for Visa when the
financial transaction card is equipped with an integrated circuit and when that
mode is activated and selected by the cardholder for the transaction.
Terminal Verification Results (TVR)

Attributes:
FIS Corporation: bcd 5 bytes

EMV Tag:
95
Description:
A series of 40 bits used to indicate from a terminal perspective the results of

offline and online processing by setting a series of indicators in this field.
Status Notes:
This data element is required when the financial transaction card is equipped
with an integrated circuit and when that mode is activated and selected by the
cardholder for the transaction.
CAPITULO

RIF.: J-00259842-5
PAGINA
138
VI
CAMBIO N
FECHA:
26/04/2011
Unpredictable Number
Attributes:

EMV: 8 hex, 4 bytes
EMV Tag:
9F37
Description:
A number used in the generation of the cryptogram. It provides variability and

uniqueness.
Status Notes:
Terminal Serial Number

Attributes:
FIS Corporation: an 8 bytes

EMV: an 8 bytes
EMV Tag:
9F1E
Description:
A unique and permanent serial number assigned by the manufacturer.
Status Notes:
This data element is optional when the financial transaction card is equipped
CAPITULO

RIF.: J-00259842-5
PAGINA
139
VI
CAMBIO N
FECHA:
26/04/2011
Visa Discretionary Data

Attributes:
FIS Corporation: LLVAR bcd..6
EMV Tag:
Not assigned
Description:
This field contains the Visa discretionary part of the issuer application data that
is transmitted from the card to the issuer. This packet of data contains the
following three subfields concatenated in the following order.
Derivation Key Index (Field 134.1) 2 hexadecimal digits; 1 byte Contains an
index into the issuers list of keys for use in online Card Authentication, Issuer
Authentication, and validation of the clearing cryptogram.
Cryptogram Version Number (Field 134.2) 2 hexadecimal digits; 1 byte Used
to calculate the cryptogram contained in the message. It indicates which version
of the cryptogram algorithm was used for ARQT, TC, AAC, or ARPC generation.
Card Verification Results (Field 134.3) Variable length, 1 byte binary + up to
24-bit string; maximum 4 bytes Contains a series of indicators from the card
perspective. The card records the results of offline and online processing by
setting a series of indicators in this field. These indicators are available to
members in the online message and clearing transaction.
Status Notes:
This data element is required by Visa when the financial transaction card is
equipped with an integrated circuit and when that mode is activated and
selected by the cardholder for the transaction.
Issuer Application Data

Attributes:

EMV: b VAR up to 32 bytes
EMV Tag:
9F10
Description:
Contains proprietary application data for transmission to the issuer in an online

transaction.
Status Notes:
CAPITULO

RIF.: J-00259842-5
PAGINA
140
VI
CAMBIO N
FECHA:
26/04/2011
Cryptogram
Attributes:
FIS Corporation: 16 hex, bcd 8 bytes

EMV: b 8 bytes
EMV Tag:
9F26
Description:
Contains an Authorization Request Cryptogram (ARQC)

Transaction Certificate (TC) or an Application Authentication
Cryptogram (ACC). The card verification results field indicates which cryptogram
is present in this field.
Status Notes:
The FIS Connex on Tandem (Advantage) System stores this data element
to be available for settlement reporting.
Application Transaction Counter

Attributes:

EMV: b 2 bytes
EMV Tag:
9F36
Description:
Contains a count of the transactions performed within the card application and is
incremented by one each time a transaction is initiated. This field is a retain and
return field for Visa.
Status Notes:
The FIS Connex on Tandem (Advantage) System stores this data element
to be available for settlement reporting.
Application Interchange Profile

Attributes:
FIS Corporation: 16 bit, bcd 2 bytes

EMV: b 2 bytes
EMV Tag:
82
Description:
Contains a 16 bit series of indicators that reflect the specific functions supported
by the chip card account.
Status Notes:
CAPITULO

RIF.: J-00259842-5
PAGINA
141
VI
CAMBIO N
FECHA:
26/04/2011
Issuer Authentication Data

Attributes:

EMV: b 8, 16 bytes
EMV Tag:
91
Description:
The application Interchange profile consists of two subfields.

In the response message, the first 8 bytes contains the authorization response
cryptogram used to authenticate the issuer.
The next 1 - 8 bytes contains proprietary data.
Visa uses bytes 9 - 10 as the ARPC response code. It is the response value
used by the issuer to create the ARPC.
Status Notes:
This data element is required when the issuer authentication occurred when the
financial transaction card is equipped with an integrated circuit and when that
mode is activated and selected by the cardholder for the transaction.
Issuer Script Command

Attributes:
FIS Corporation: LLLVAR bcd..255

EMV: b VAR up to 255
EMV Tag:
71
Description:
This field contains proprietary information that the issuer wants to communicate
to the card. This script is processed before issuing the second Generate AC
command.
Status Notes:
Issuer Script Command 2

Attributes:

EMV Tag:
72
Description:
to the card. This script is processed after issuing the second Generate AC
command.
Status Notes:
CAPITULO

RIF.: J-00259842-5
PAGINA
142
VI
CAMBIO N
FECHA:
26/04/2011
Issuer Script Results

Attributes:
EMV Tag:
Not assigned
Description:
to the card.
Transaction Type
Attributes:
FIS Corporation: 2n, bcd 1 byte

EMV: n2 1 byte
EMV Tag:
9C
Description:
The type of financial transaction as represented by the first two digits of the ISO
8583:1987 processing code.
Status Notes:
Terminal Country Code

Attributes:
FIS Corporation: 3n, bcd 2 bytes

EMV: n3 2 bytes
EMV Tag:
9F1A
Description:
The country where the merchant terminal is located, represented according to

ISO 3166.
Status Notes:
Transaction Date
Attributes:
FIS Corporation: 6n, bcd 3 bytes YYMMDD

EMV: n6 3 bytes YYMMDD
EMV Tag:
9A
Description:
The local date the transaction was authorized.
Status Notes:
CAPITULO

RIF.: J-00259842-5
PAGINA
143
VI
CAMBIO N
FECHA:
26/04/2011
Amount, Authorized
Attributes:

EMV: n12 6 bytes
EMV Tag:
9F02
Description:
The transaction amount used when calculating the cryptogram.
Status Notes:
Transaction Currency Code

Attributes:

EMV: n3 2 bytes
EMV Tag:
5F2A
Description:
The currency code used when calculating the cryptogram, according to ISO
4217.
Status Notes:
Amount, Other
Attributes:

EMV: n12 6 bytes
EMV Tag:
9F03
Description:
The secondary amount associated with the transaction, representing a cash

back amount.
Status Notes:
This data element is required when supplied by the acquirer.
COPAC Cardholder Card Scheme Cryptogram

Attributes:
EMV Tag:
Not assigned
Description:
Contains a transaction certificate calculated with a Visa derived key and used
by Visa to arbitrate disputes between issuer and acquirer.
Status Notes:
This data element is present if supplied by the acquirer.
CAPITULO

RIF.: J-00259842-5
PAGINA
144
VI
CAMBIO N
FECHA:
26/04/2011
Additional Chip Information

Attributes:
FIS Corporation: LLLVAR ans..030
EMV Tag:
Not assigned
Description:
The first 4 bytes of this field are defined. The remaining 26 bytes are reserved
for future use. The four subfields are defined as follows.
Chip Condition Code (1 byte)
Values are:
0 Not applicable.
1
Service code begins with 2 or 6; the valid value 2 does not apply (that is,
the last read was not a chip transaction or was a successful chip
transaction).
Service code begins with 2 or 6; last transaction read at the chip-capable

terminal failed.
Chip Transaction Indicator (1 byte)

Values are:
0
Not applicable.
The acquirer identified the transaction as a chip-based transaction.
Chip Card Authentication Reliability Indicator (1 byte)

Values are:
0
Not applicable.
Acquirer indicates that Card Authentication may not be reliable.
Acquirer inactive for Card Authentication.
Issuer inactive for Card Authentication
Card Authentication Results Code (ARQC) (1 byte)

Values are:
Blank Card Authentication was not performed, or some other situation or
problem prevented verification. For example, issuer is not participating in the
Card Authentication service, or a system or cryptographic error occurred.
1
The Authorization Request Cryptogram (ARQC) was checked but failed

verification.
The ARQC was checked and passed verification.
Status Notes:
CAPITULO

RIF.: J-00259842-5
PAGINA
145
VI
CAMBIO N
FECHA:
26/04/2011
Cryptogram Information Data

Attributes:
FIS Corporation: bcd 1 byte

EMV: b 1 byte
EMV Tag:
9F27
Description:
Indicates the type of cryptogram and the actions to be performed by the

terminal.
Status Notes:
This data element is required for MasterCard when the financial transaction
card is equipped with an integrated circuit and when that mode is activated and
Cardholder Verification Method (CVM) Results

Attributes:

EMV: b 3 bytes
EMV Tag:
9F34
Description:
The results of the last cardholder verification performed.
Status Notes:
Terminal Type
Attributes:

EMV: n2 1 byte
EMV Tag:
9F35
Description:
Indicates the environment of the terminal, its communication capability, and its
operational control.
Status Notes:
Dedicated File Name

Attributes:

EMV: b 5, 16 bytes
EMV Tag:
84
Description:
Identifies the name of the dedicated file as described in ISO/IEC 7968-4.
Status Notes:
card is equipped with an Integrated Circuit and when that mode is activated and
CAPITULO

RIF.: J-00259842-5
PAGINA
146
VI
CAMBIO N
FECHA:
26/04/2011
Terminal Application Version Number

Attributes:

EMV: b 2 bytes
EMV Tag:
9F09
Description:
The version number assigned by the payment system for the application.
Status Notes:
Transaction Sequence Counter

Attributes:

EMV: n4-8, 2-4 bytes
EMV Tag:
9F41
Description:
Counter maintained by the terminal that is incremented by one for each

transaction.
Status Notes:
Transaction Category Code

Attributes:
FIS Corporation: an 1 byte

EMV: an 1 byte
EMV Tag:
9F53
Description:
MasterCard has defined an additional terminal resident data element that is

available to assist with Card Risk Management.
Status Notes:
Message Authentication Code (MAC)

Attributes:
FIS Corporation:
b 8 bytes if using packing option
16 hex bytes if not using numeric packing ISO: b 64
EMV Tag:
Not applicable
Description:
Used to validate the source and the text of the message between the sender
and receiver.
Status Notes:
This data element is required when MACing messages and at least one of the
data elements from 129-191 is present in the message.
RIF.: J-00259842-5
CAPITULO

PAGINA
147
VII
CAMBIO N
TRAZAS MENSAJERA ISO 8583 SUICHE7B
FECHA:
26/04/2011
TRAZAS MENSAJERA ISO 8583 SUICHE 7B

Para simplificar el anlisis y el diseo de la data transmitida desde las entidades Bancarias a
travs del Aplicativo CONNEX usando la mensajera ISO 8583 de FIS, a continuacin se
muestran algunas TRAZAS que servirn de ayuda para visualizar de manera sencilla los
diferentes Tipos de Mensajes y Contenido de los Campos utilizados en la ejecucin de las
diferentes operaciones e implementaciones en la Red SUICHE 7B.
FLUJO MANEJO DE LA RED.
MSG 0800
MSG 0810
RIF.: J-00259842-5
CAPITULO

PAGINA
148
VII
CAMBIO N
FECHA:
26/04/2011
FLUJO MANEJO DE LOS REVERSOS EN LA RED SUICHE 7B

A continuacin se muestra las TRAZAS de una transaccin con su respectivo REVERSO,
donde se resaltan con una serie de colores los campos utilizados por el sistema para
determinar cual es la transaccin original.
Bit 011 System Trace Audit Number.

Un nmero asignado por el iniciador del mensaje para identificar una transaccin
unvocamente. El nmero del trace permanece inalterado para todos los mensajes a lo
largo de la vida de la transaccin.
Por ejemplo: 0200 0210 0420 0430 todos deben tener el mismo nmero de
trace.
Bit 012 Time, Local Transaction.

Es la hora local en la que la transaccin tiene lugar desde el punto o ubicacin donde
la transaccin se origin por el tarjetahabiente (ATM/POS). Esta hora debe
permanecer inalterada a lo largo de la vida de la transaccin.
Por ejemplo: 0200 0210 0420 0430 todos los mensajes deben tener la misma
Hora local.
Bit 013 Date, Local Transaction.

Es el mes y el da local, en formato MMDD, en donde la transaccin tuvo lugar desde
la ubicacin del tarjetahabiente. Esta fecha debe permanecer inalterada para todos los
mensajes durante la vida de la transaccin.
Por el ejemplo: 0200 0210 0420 0430. Todos los mensajes deben tener la
misma Fecha local.
Bit 037 Retrieval Reference Number.

Una referencia documentada proporcionada por el sistema que retiene la informacin
fuente original y es usado para asistir en la ubicacin de esa transaccin o de una
copia de la misma. El valor de este elemento de los datos debe permanecer inalterado
a lo largo de la vida de la transaccin. En la medida en que los mensajes fluyen desde
el 0200 0210 0420 0430, todos los mensajes deben tener el mismo Nmero
de Referencia de Recuperacin.
En una compra preautorizada, este data elemento debe contener el mismo valor que
la preautorizacin original. Es decir, preautorizacin 0100 0110, compra
preautorizada 0200/0220 0210/0230 todos los mensajes deben tener el mismo
Nmero de Referencia de Recuperacin.
Bit 028 Amount, Transaction Fee (Comisin Adicional).

En la medida en que los mensajes fluyen desde el 0200 0210 0420 0430,
todos los mensajes deben tener el mismo monto o cargo, pero el identifcador vara de
D en los 0200 a C en los 0400.
RIF.: J-00259842-5
CAPITULO

PAGINA
149
VII
CAMBIO N
MSG 0420
MSG 0430
FECHA:
26/04/2011
CAPITULO

RIF.: J-00259842-5
PAGINA
150
VIII
CAMBIO N
DATA ELEMENT CODE TABLES
FECHA:
26/04/2011
DATA ELEMENTS CODE TABLES

TRANSACTION TYPES
The ISO Transaction Type in the following table is the first two digits of the ISO Processing
Code.
Debits
ISO TRANSACTION
TYPE
DESCRIPTION
00
Goods and service
01
Cash
02
Adjustment (Unsupported)
03
Check guarantee
04
Check verification
05
Eurocheck (Unsupported)
06
Traveler check
07
Letter of credit (Unsupported)
08
Giro (Unsupported)
09
Goods and services with cash disbursement
10
Non-cash financial instrument (Unsupported)
11
Quasi-Cash and scrip
18
Deferred goods and services (Unsupported)
19
Deferred goods and services with cash disbursement (Unsupported)
ISO
CAPITULO

RIF.: J-00259842-5
DATA ELEMENT CODE TABLES
Credits
DESCRIPTION
20
Returns
21
Deposits/Deposit payments
22
Adjustment (Unsupported)
23
Check deposit guarantee (Unsupported)
24
Check deposit (Unsupported)
28
Payment return
29
29 Commercial deposit (Unsupported)
Inquiry Services
ISO TRANSACTION
TYPE
DESCRIPTION
30
Available funds inquiry
31
31 Balance inquiry
39
Generic balance inquiry (Unsupported)
Transfer/Transfer Payment Services

ISO TRANSACTION
TYPE
DESCRIPTION
40
Cardholder accounts transfer
Payment Services
ISO TRANSACTION
TYPE
DESCRIPTION
50
Payment to another party
58
Payment transaction
59
Payment enclosed (Unsupported)
151
VIII
CAMBIO N
ISO TRANSACTION
TYPE
PAGINA
FECHA:
26/04/2011
CAPITULO

RIF.: J-00259842-5
PAGINA
152
IX
CAMBIO N
PROCESSING CODES (BIT 003) AUTHORIZATION MESSAGES
FECHA:
25/05/2011
PROCESSING CODES (BIT 003), AUTHORIZATION MESSAGES

You need to be aware of these two factors when you use the processing code tables.
1. Pre-Authorization is indicated by the presence of data element 057.
2. The FIS ISO message processing code makes no distinction of transactions with cash
back.
PROCESSING CODES (BIT 003), AUTHORIZATION MESSAGES
01xx Check Guarantee
ISO Processing
Code
Description
030000
CONFORMACIN CHEQUE
PROCESSING CODES (BIT 003), FINANCIAL TRANSACTION MESSAGES

02xx Purchase of Goods and Services
ISO Processing
Code
Description
000000
COMPRA DESDE LA CUENTA PRINCIPAL
005000
COMPRA DESDE LA CUENTA FAL
001000
COMPRA DESDE LA CUENTA AHORROS
002000
COMPRA DESDE LA CUENTA CORRIENTE
003000
COMPRA DESDE LA CUENTA CRDITO
CAPITULO

RIF.: J-00259842-5
PAGINA
153
IX
CAMBIO N
FECHA:
25/05/2011
02xx Cash Withdrawal

ISO Processing
Code
Description
010000
COMPRA DESDE LA CUENTA PRINCIPAL
015000
COMPRA DESDE LA CUENTA FAL
011000
COMPRA DESDE LA CUENTA AHORROS
012000
COMPRA DESDE LA CUENTA CORRIENTE
013000
COMPRA DESDE LA CUENTA CRDITO
02xx Purchase Return

ISO Processing
Code
Description
200000
DEVOLUCIN DESDE LA CUENTA PRINCIPAL
200050
DEVOLUCIN DESDE LA CUENTA FAL
200010
DEVOLUCIN DESDE LA CUENTA AHORROS
200020
DEVOLUCIN DESDE LA CUENTA CORRIENTE
200030
DEVOLUCIN DESDE LA CUENTA CRDITO
02xx Available Finds Inquiry

ISO Processing
Code
Description
300000
CONSULTA DISPONIBILIDAD DE FONDOS CUENTA PRINCIPAL
305000
CONSULTA DISPONIBILIDAD DE FONDOS CUENTA FAL
301000
CONSULTA DISPONIBILIDAD DE FONDOS CUENTA AHORROS
302000
CONSULTA DISPONIBILIDAD DE FONDOS CUENTA CORRIENTE
303000
CONSULTA DISPONIBILIDAD DE FONDOS CUENTA CRDITO
RIF.: J-00259842-5
CAPITULO

PAGINA
154
IX
CAMBIO N
FECHA:
25/05/2011
02xx Balance Inquiry

ISO Processing
Code
Description
310000
CONSULTA BALANCE CUENTA PRINCIPAL
315000
CONSULTA BALANCE CUENTA FAL
311000
CONSULTA BALANCE CUENTA AHORROS
312000
CONSULTA BALANCE CUENTA CORRIENTE
313000
CONSULTA BALANCE CUENTA CRDITO
02xx Generic Balance Inquiry

ISO Processing
Code
Description
390000
CONSULTA BALANCE GENRICO CUENTA PRINCIPAL
395000
CONSULTA BALANCE GENRICO CUENTA FAL
391000
CONSULTA BALANCE GENRICO CUENTA AHORROS
392000
CONSULTA BALANCE GENRICO CUENTA CORRIENTE
393000
CONSULTA BALANCE GENRICO CUENTA CRDITO
02xx Transfers and Payment Services

ISO Processing
Code
Descripcin
481010
TRANSFERENCIA INTERBANCARIA DE AHORROS A AHORROS
481020
TRANSFERENCIA INTERBANCARIA DE AHORROS A CTA. CORRIENTE
481050
TRANSFERENCIA INTERBANCARIA DE AHORROS A FAL
482010
TRANSFERENCIA INTERBANCARIA DE CTA. CORRIENTE A AHORROS
RIF.: J-00259842-5
CAPITULO

155
IX
CAMBIO N
ISO Processing
Code
PAGINA
FECHA:
25/05/2011
Descripcin
482020
TRANSFERENCIA INTERBANCARIA DE CTA. CORRIENTE A CTA.

CORRIENTE
482050
TRANSFERENCIA INTERBANCARIA DE CTA. CORRIENTE A FAL
481030
TRANSFERENCIA INTERBANCARIA DE AHORROS A CRDITO
482030
TRANSFERENCIA INTERBANCARIA DE CTA. CORRIENTE A CRDITO
485030
TRANSFERENCIA INTERBANCARIA DE FAL A CRDITO
485010
TRANSFERENCIA INTERBANCARIA DE FAL A AHORROS
485020
TRANSFERENCIA INTERBANCARIA DE FAL A CTA. CORRIENTE
485050
TRANSFERENCIA INTERBANCARIA DE FAL A FAL
483010
TRANSFERENCIA INTERBANCARIA DE CRDITO A AHORROS
483020
TRANSFERENCIA INTERBANCARIA DE CRDITO A CTA. CORRIENTE
483050
TRANSFERENCIA INTERBANCARIA DE CRDITO A FAL
402020
TRANSFERENCIA CTA. CORRIENTE A CTA. CORRIENTE
402010
TRANSFERENCIA CTA. CORRIENTE A AHORROS
402050
TRANSFERENCIA CTA. CORRIENTE A FAL
402030
TRANSFERENCIA CTA. CORRIENTE A CRDITO
401010
TRANSFERENCIA AHORROS A AHORROS
401020
TRANSFERENCIA AHORROS A CTA. CORRIENTE
401050
TRANSFERENCIA AHORROS A FAL
RIF.: J-00259842-5
CAPITULO

Descripcin
401030
TRANSFERENCIA AHORROS A CRDITO
405050
TRANSFERENCIA FAL A FAL
405010
TRANSFERENCIA FAL A AHORROS
405020
TRANSFERENCIA FAL A CTA. CORRIENTE
405030
TRANSFERENCIA FAL A CRDITO
403030
TRANSFERENCIA CRDITO A CRDITO
403020
TRANSFERENCIA CRDITO A CTA. CORRIENTE
403010
TRANSFERENCIA CRDITO A AHORROS
403050
TRANSFERENCIA CRDITO A FAL
502000
PAGO SERVICIOS DESDE CUENTA CORRIENTE
501000
PAGO SERVICIOS DESDE CUENTA DE AHORROS
503000
PAGO SERVICIOS DESDE CRDITO
505000
PAGO SERVICIOS DESDE FAL
50CO00
PAGO SERVICIOS DESDE CUENTA PRINCIPAL
156
IX
CAMBIO N
ISO Processing
Code
PAGINA
FECHA:
25/05/2011
CAPITULO

RIF.: J-00259842-5
POINT-OF-SERVICE ENTRY MODE (BIT 022)

PAN Entry Mode Codes
Description
00
Unspecified
01
Manual
02
Magnetic stripe
03
Bar code
04
OCR
05
Integrated Circuit Card
06
Manual (key-entered)
07-60
Reserved for ISO use
61-79
80
Fallback
81
From file
82-89
90
Full magnetic stripe read (optionally supported)
91-99
PIN Entry Mode Codes

ISO Code Positions 3
Description
Unspecified
PIN entry capability
No PIN entry capability
3 -5
PIN pad inoperative
8-9
157
IX
CAMBIO N
ISO Code Positions

1-2
PAGINA
FECHA:
25/05/2011
RIF.: J-00259842-5
CAPITULO

POINT-OF-SERVICE CONDITION CODES (BIT 025)

Description
00
Normal presentment
01
Customer not present
02
Unattended terminal able to retain card
03
Merchant suspicious
04
Electronic card register interface
05
Customer present, card not present
06
Pre-Authorized request
07
Telephone device request
08
Mail and/or telephone order
09
Security alert
10
Customer identity verified
11
Suspected fraud
12
Security reasons
15
Customer terminal (home terminal)
16
Administration terminal
27
Unattended terminal unable to retain card
28-40
41-50
51
52
CVV verified and valid
53
CVV verified and invalid
54-99
158
IX
CAMBIO N
ISO Code
PAGINA
FECHA:
25/05/2011
CAPITULO

RIF.: J-00259842-5
PAGINA
159
IX
CAMBIO N
FECHA:
25/05/2011
RESPONSE CODES (BIT 039)

The FIS ISO 8583 PI requires that the response code mappings be defined in the data base.
Although there is no default response code table, FIS recommends the use of the following
Response Code Mappings. Description
ISO Code
Description
00
Approved or completed successfully
01
Refer to card issuer
02
Refer to card issuers special conditions
03
Invalid merchant
04
Pick-up
05
Do not honor
06
Error
07
Pick-up card, special conditions
08
Honor with identification
09
Request in progress
10
Approved for partial amount
11
Approved (VIP)
12
Invalid transaction
13
Invalid amount
14
Invalid card number (no such number)
15
No such issuer
16
Approved, update track 3
17
Customer cancellation, reversal (unsupported)
18
Customer dispute, chargeback (future)
19
Re-enter transaction
20
Invalid response
21
No action taken, reversal (unsupported)
22
Suspected malfunction, reversal (unsupported)
23
Unacceptable transaction fee
RIF.: J-00259842-5
CAPITULO

PAGINA
160
IX
CAMBIO N
ISO Code
Description
24
File update not supported by receiver (only in 03xx)
25
Unable to locate record on file (only in 03xx)
26
Duplicate file update record, no action (only in 03xx)
27
File update field edit error (only in 03xx)
28
File update record locked out (only in 03xx)
29
File update not successful, contact acquirer (only in 03xx)
30
Format error (may also be a reversal)
31
Bank not supported by switch
32
Completed partially, reversal (unsupported)
33
Expired card, pick-up
34
Suspected fraud, pick-up
35
Card acceptor contact acquirer, pick-up
36
Restricted card, pick-up
37
Card acceptor call acquirer security, pick-up
38
Allowable PIN tries exceeded, pick-up
39
No credit account
40
Requested function not supported
41
Lost card, pick-up
42
No FAL account
43
Stolen card, pick-up
44
No investment account
45
46
47
48
49
50
FECHA:
25/05/2011
RIF.: J-00259842-5
CAPITULO

PAGINA
161
IX
CAMBIO N
ISO Code
Description
51
Insufficient funds
52
No checking account
53
No savings account
54
Expired card
55
Incorrect PIN
56
No card record
57
Transaction not permitted to cardholder
58
Transaction not permitted to terminal (may also be a chargeback)
59
Suspected fraud
60
Card acceptor contact acquirer
61
Exceeds withdrawal amount limit
62
Restricted card
63
Security violation (may also be a chargeback)
64
Original amount incorrect, reversal (unsupported)
65
Exceeds withdrawal frequency limit
66
Card acceptor call acquirer security
67
Hard capture, pick-up
68
Response received too late, reversal (unsupported)
69
Reserved for ISO
70
Reserved for ISO
71
Reserved for ISO
72
Reserved for ISO
73
Reserved for ISO
74
Reserved for ISO
75
Allowable number of PIN tries exceeded
76
Key synchronization error (FIS)
77
FECHA:
25/05/2011
RIF.: J-00259842-5
CAPITULO

PAGINA
162
IX
CAMBIO N
ISO Code
Description
78
Customer not eligible for POS (STAR)
79
80
Respuesta a la Pregunta de Desafo Incorrecta
81
82
Count exceeds limit (VISANet)
83
84
Time limit for pre-authorization reached (VISANet)
85
86
Cannot verify PIN (VISANet)
87
Check already posted
88
Information not on file
89
Card verification value (CVV) verification failed (no pickup)
90
Cutoff is in progress
91
Issuer or switch is inoperative
92
Financial institution or intermediate network unknown for routing
93
Transaction cannot be completed, violation of law
94
Duplication transaction
95
Reconcile error
96
System malfunction
97
98
99
0Z-9Z
N0
Authorization life cycle unacceptable
N1
Authorization life cycle expired
N2
Non-receipt of requested item (future)
N3
Non-receipt of requested item, illegible copy (future)
FECHA:
25/05/2011
RIF.: J-00259842-5
CAPITULO

PAGINA
163
IX
CAMBIO N
ISO Code
Description
N4
Transaction exceeds floor limit (future)
N5
Declined authorization (future)
N6
Non-matching account numbers (future)
N7
Error in addition (future)
N8
Altered amount (future)
N9
Incorrect account number (future)
P0
Missing signature (future)
P1
Slip without card imprint (future)
P2
Imprinting of multiple slips (future)
P3
Canceled pre-authorization transaction (future)
P4
Delinquent settlement (future)
P5
Currency conversion error (future)
P6
Credit posted as a debit (sale) (future)
P7
Claim or defense (future)
P8
Non-receipt of goods (future)
P9
Defective merchandise (future)
R0
Fraudulent transaction prior to embossed valid date (future)
R1
Credit not received (future)
C2-MZ
Reserved for national use (X9.2)
N0-ZZ
FECHA:
25/05/2011
CAPITULO

RIF.: J-00259842-5
ADDITIONAL AMOUNTS CODES (BIT 054)

Account Type
This code is found in positions 1 and 2 of each amount.
Description
00
Cuenta Principal
09
Other
10
Cuenta de Ahorros
20
Cuenta Corriente
30
Crdito
40
Universal account (Unsupported)
50
Cuenta FAL
60
70
80
97
Unknown
Amount Type
This code is found in positions 3 and 4 of each amount.
ISO Code
Description
00
Funding (Default) account
01
Account ledger balance
02
Account available balance
03
Amount owing (Unsupported)
04
Amount due (Unsupported)
05-10
11-15
16
Credit line (FIS) (Unsupported)
17
POS balance (FIS) (Unsupported)
164
IX
CAMBIO N
ISO Code
PAGINA
FECHA:
25/05/2011
RIF.: J-00259842-5
CAPITULO

Description
18-19
20
Amount remaining this cycle (Unsupported)
21-30
31-35
36-39
165
IX
CAMBIO N
ISO Code
PAGINA
FECHA:
25/05/2011
Amount Type (Transaction-Related)

This code is found in positions 3 and 4 of each amount for transaction-related amounts.
ISO Code
Description
40
Amount cash
41
Amount goods and services (Unsupported)
42-50
51-55
56
Hold amount
57
Pre-Authorized amount (Unsupported)
58
Authorized amount
59
Floor limit (Unsupported)
60-79
80-89
90
91
Original amount
Note: Amount type 91 is used by Issuer to return Original amounts for a
partially authorized transaction. The Original amount is in Transaction
currency ( Field 49).
99
3S
Co-payment
4S
Healthcare amount
4T
Transit amount
CAPITULO

RIF.: J-00259842-5
Description
4U
Prescription/Rx amount
4V
Vision/Optical amount
4W
Clinic/Medicals amount
4X
Dental
166
IX
CAMBIO N
ISO Code
PAGINA
FECHA:
25/05/2011
NATIONAL POS CONDITION CODE (BIT 58)

Terminal Type Codes
Within the national POS condition code, positions 1-3 identify the terminal class and positions
9-10 identify the terminal type.
Terminal Class (Posiciones 1-3)
Posicin 1
ISO Code
Description
Attended
Unattended
2-7
8-9
Posicin 2
ISO Code
Description
Customer-operated
Card acceptor-operated
Administrative
3-7
8-9
RIF.: J-00259842-5
CAPITULO

PAGINA
167
IX
CAMBIO N
FECHA:
25/05/2011
Posicin 3 POS Terminal Location

ISO Code
Description
On premise
Off premise
2-7
8-9
Presentation Type (Posiciones 4-7)

Within the national POS condition code, positions 4-7 identify the presentation type.
Posicin 4 POS Cardholder Presence
ISO Code
Description
Customer present
Customer not present
Mail or telephone order (customer not present)
Customer not present, standing order/recurring payment
5-7
Pre-Authorized purchase
Posicin 5
ISO Code
Description
Card present
Card not present
2-7
Pre-Authorized purchase
RIF.: J-00259842-5
CAPITULO

PAGINA
168
IX
CAMBIO N
FECHA:
25/05/2011
Posicin 6
ISO Code
Description
Device does not have card retention capability
Device has card retention capability
2-7
8-9
Posicin 7
ISO Code
Description
Original presentment
First representment
Second representment
Third representment
Previously authorized request
Resubmission
6-7
8-9
Security Condition (Posicin 8)

The security condition code is found in position 8 of the national POS condition code.
Posicin 8
ISO Code
Description
No security concern
Suspected fraud
Identification verified
Electronic commerce transaction with digital signature
Nonsecure/Security unknown electronic commerce transaction
Secure electronic transaction with cardholder certificate
Secure electronic transaction without cardholder certificate
Channel-encrypted electronic commerce transaction
CVV validated and valid
CVV validated and invalid
CAPITULO

RIF.: J-00259842-5
PAGINA
169
IX
CAMBIO N
FECHA:
25/05/2011
Terminal Type (Posiciones 9-10)

The terminal type code is found in positions 9-10 of the national POS condition code.
Posiciones 9-10
ISO Code
Description
00
Administrative terminal
01
POS terminal
02
ATM
03
Home terminal
04
ECR
05
Dial terminal
06
Travelers check machine
07
Fuel machine
08
Scrip machine
09
Coupon machine
10
Ticket machine
21
Smart phone
24
Screen phone
Card Data Input Capability (Posicin 11)

The card data input capability code is found in position 11 of the national POS condition code.
This can be used as a supporting alternative to Bit 61 that is used by MDS.
Posicin 11
ISO Code
Description
Unknown
Manual, no terminal
Magnetic stripe
Bar code
OCR
ICC
Key entered
CAPITULO

RIF.: J-00259842-5
PAGINA
170
IX
CAMBIO N
ISO Code
Description
File
Magnetic stripe reader and key entry
Magnetic stripe reader and key entry and EMV-compatible ICC reader
Magnetic stripe reader and key EMV-compatible ICC reader
FECHA:
25/05/2011
ADVICE/REVERSAL REASON CODES (BIT 060)

Reversal Reason Codes
Position 1 of the reason code indicates who reversed this transaction. It is allocated as
follows:
Posicin 1
ISO Code
Description
Not as reversal
Card acceptor-originated reversal
Acquirer-originated reversal
Intermediate facility-originated reversal
4-9
Reserved
Posicin 2
Position 2 values are FIS-defined.
ISO Code
Pos 1
ISO Code
Pos 2
Description
Not a reversal
1-3
Terminal processor errorr
1-3
System time out
1-3
Terminal error/misdispense
1-3
Terminal communication error
1-3
Terminal error
1-3
Late or unsolicited response - inbound
CAPITULO

RIF.: J-00259842-5
PAGINA
171
IX
CAMBIO N
FECHA:
25/05/2011
Advice Reason Codes

Position 1 of the advice reason code indicates who stood in for this transaction. It is allocated
as follows:
Posicin 1
ISO Code
Description
Not as advice
Card acceptor-originated advice
Acquirer-originated advice
Stand-in agent-originated advice
4-9
Reserved
Posicin 2
Position 2 values 5-9 are FIS-defined.
ISO Code
Pos 1
ISO Code
Pos 2
Description
Not an advice (forced post)
1-3
Timed-out request message
1-3
Issuer not available (in delay)
1-3
Issuer signed off (logged off)
1-3
Within business agreement
1-3
POS alternate authorization
1-3
POS merchant authorization
1-3
POS switch authorization under floor limit
1-3
Encryption key not established
4-7
5-7
8-9
RIF.: J-00259842-5
CAPITULO

PAGINA
172
IX
CAMBIO N
NETWORK MANAGEMENT INFORMATION CODES (BIT 070)

Message
Type
Information
Code
Description
0800
001
Sign on, both issuer and acquirer
0800
002
Sign off, both issuer and acquirer
0800
005
Special instructions (message to network operator)
0800
061
Sign on as issuer
0800
062
Sign off as issuer
0800
071
Sign on as acquirer
0800
072
Sign off as acquirer
0800
101
Key change, both issuer and acquirer
0800
161
Issuer key change
0800
171
Acquirer key change
0800
180
Issuer/acquirer key change request
0800
181
Acquirer key change request
0800
191
Issuer key change request
0800
201
Initiate cutoff, issuer and acquirer
0800
202
Cutoff complete, issuer and acquirer
0800
261
Initiate cutoff as issuer
0800
262
Cutoff complete as issuer
0800
271
Initiate cutoff as acquirer
0800
272
Cutoff complete as acquirer
0800
281
Terminal cutoff
0800
282
Cardholder application cutoff
0800
301
Echo test (reply required handshake)
0820
301
Echo test (protocol acknowledgment handshake)
0800
361
Issuer echo test (reply required)
0820
361
Issuer echo test (protocol acknowledgment)
FECHA:
25/05/2011
CAPITULO

RIF.: J-00259842-5
Message
Type
Information
Code
Description
0800
371
Acquirer echo test (reply required)
0820
371
Acquirer echo test (protocol acknowledgment)
0600
800
Processor to processor mail
0620
900
Message format/syntax error messages
FILE UPDATE CODES (BIT 091)

Negative File Update Codes (0302s)
Description
Unassigned
Add record
Change record
Delete record
Bulk replacement (not supported)
Inquiry
Purge expired records (not supported)
Add file (not supported)
Delete file (not supported)
Unassigned
A-F
G-N
O-Z
173
IX
CAMBIO N
ISO Code
PAGINA
FECHA:
25/05/2011
CAPITULO

RIF.: J-00259842-5
Authorization Processor File Update Codes (0382s)

Description
Unassigned
Add
Change
Delete record
Bulk replacement (not supported)
Inquiry (not supported)
Purge expired records (not supported)
Add file (not supported)
Delete file (not supported)
Unassigned
A-F
G-N
O-Z
174
IX
CAMBIO N
ISO Code
PAGINA
FECHA:
25/05/2011
CAPITULO

RIF.: J-00259842-5
PAGINA
175
X
CAMBIO N
DATA ELEMENTS ISO 8583 (BIT 55)
FECHA:
26/04/2011

NOMBRE DEL SUBELEMENTO
TAG Valor a
Longitud b
Application Cryptogram (AC) ARQC
9F26
9F27
Issuer Application Data (IAD) c
9F10
132
9F37
9F36
Terminal Verification Result (TVR)
95
Transaction Date
9A
Transaction Type
9C
Transaction Amount or Amount

Authorized
9F02
5F2A
82
9F1A
Amount Other d
9F03
a) Hexadecimal representation: 2 Characters = 1 Byte Binary.

b) This column shows the actual character length of the data for the sub-element. The
actual length designator in the TLV is the one-byte binary designation of the data that
follows.
EMV define una forma para identificar las variables o elementos de datos dentro de
una tarjeta chip EMV y dentro del campo DE 55 en un mensaje de red:
Representacin TLV
Tag
Length en bytes
Value
Un ejemplo de representacin TLV

9F10120110A00003220400000000000000000000FF
TAG = 9F10
Length =12 (Expresada en Hexadecimal)
Value = 0110A00003220400000000000000000000FF
RIF.: J-00259842-5
CAPITULO

PAGINA
176
X
CAMBIO N
FECHA:
26/04/2011
a) The acquirer must provide this Valor if the corresponding data object (EMV tag 9F10)
is provided by the card to the terminal.
b) When the product rules do not allow cash back, then 9F03 must be absent, or zerofilled.
When the product rules allow cash back:
Cash back Amount - 9F03 will carry the cash back amount and this data
element is mandatory
No Cash back Amount - The Valor of 9F03 will be zero, in which case 9F03
may be absent or present with a zero Valor.
a) BIT 2 PAN (EMV 5A) Utilizado en la derivacin de llaves maestras del EMV
b) BIT 12 Hora, Transaccin Local (Debe estar presente)
c) BIT 13 Fecha, Transaccin Local (Debe estar presente)
d) BIT 22 Point of Service Entry Mode. How PAN was entered in Terminal
Valor 05x identifica transacciones de contacto EMV EMV.
BIT 55 est presente si el adquirente es full grade
BIT 55 no est presente si el adquirente es grado parcial
Valor 80x identifica transacciones en modo de FALLBACK
En cuyo caso BIT 55 no est presente y
BIT 35 contiene los datos fsicos del Track 2
a.- BIT 23 Card Sequence Number (EMV 5F34) Utilizado en la derivacin de
maestras del EMV
llaves
b.- BIT 35 Data del Track 2 data (EMV 57)

I. Debe contener el valor de T2 equivalente a la data del EMV
II. En transacciones FALLBACK (BIT 22 = 80x), su valor es igual al ledo
fsicamente del TRACK 2 de la banda magntica
c.- BIT 37 Retrieval reference Lumber (Debe estar presente)
d.- BIT 41 Card Acceptor Identification Code (Debe estar presente)
e.- BIT 55 Datos de EMV
I. No est presente si es una transaccin de FALLBACK (BIT 22 = 80x)
II. Presente en todas las transacciones procesadas por un adquirente FULL.
III. Contiene datos del On-line Mutual Authentication (OMA) (criptograma de EMV y
datos de calculo e informacin)
RIF.: J-00259842-5
CAPITULO

PAGINA
177
X
CAMBIO N
FECHA:
26/04/2011
f.- BIT 61 POS Data Terminal Capabilities (SOLO MASTERCARD)

Byte 5 (SE 5) debe indicar que la tarjeta est presente (valor= 0)
Byte 11(SE 11) indica la capacidad de lectura del Terminal:
o EMV Contact (valor = 5)
o Magnetic Stripe (valor=2)
TAGs EMV Obligatorios en el BIT 55 (0100 / 0200 )
9F26 Application Cryptogram
9F27 Cryptogram information data

o Diferencia TC o ARQC
Tarjeta
9F10 Issuer application data
Tarjeta
Tal como lo gener la tarjeta en la respuesta de la

instruccin Generate AC
Contiene informacin del Card Verification Results (CVR).
9F37 Unpredictable number
Terminal
9C Transaction type
Terminal
9A Transaction date
Terminal
9F02 Amount, authorized
Terminal
5F2A Transaction currency code
Terminal
82 Application interchange profile
Tarjeta
9F1A Terminal country code
Terminal
95 Terminal verification results
Terminal
9F36 Application transaction counter
Tarjeta (*)
Tarjeta
RIF.: J-00259842-5
CAPITULO

PAGINA
178
X
CAMBIO N
FECHA:
26/04/2011
TAGs EMV Opcionales en el BIT 55 (0100 / 0200)
9F33 Terminal capabilities

o CVM y Capacidades Seguridad del terminal
Terminal (*)
9F34 Resultados del CVM
Terminal (*)
9F35 Terminal type

o Operational control and Environment
Terminal (*)
9F1E IFD serial number
9F53 Transaction category code

o Tipo de transaccin en el sector industrial
84
9F09 Terminal application version number
Terminal (*)
9F41 Transaction sequence counter
Terminal (*)
9F03 Amount, other terminal

o Monto del Cash back
o Valor pre-determinado cero
Dedicated file name
Terminal
Terminal (*)
Tarjeta (*)
TAGs EMV Condicionales (0110 / 0210)
91 Issuer Authentication Data

o ARPC
o ARPC response code
(Opcional)
71 Issuer Script Template Critical

o Contiene una cadena de instrucciones post
emisin a ser ejecutadas en el EMV antes
del 2nd Generate AC
(Opcional)
72 Issuer Script Template Non critical

o Contiene una cadena de instrucciones a ser
ejecutadas en el EMV despus del 2nd
Generate AC
(Opcional)
Nota 1: Los TAGs marcados en ROJOS, son los requeridos por VISA.
Nota 2: Como puede observarse, entre los TAGs requeridos por VISA el TAG 9F5B (Issuer
Script Results) no se encuentra definido, debito a que el mismo solo es usado para los
REVERSOS en VISA.
Nota 3: Los reversos sern manejados tal cual los manejas las franquicias.
RIF.: J-00259842-5
CAPITULO

PAGINA
179
XI
CAMBIO N
SERVICIOS DE CONVERSION OBS DE SUICHE 7B
FECHA:
26/04/2011
SERVICIOS DE CONVERSIN OBS DE SUICHE 7B

ESPECIFICACIONES TCNICAS
De acuerdo a los esquemas de implementacin del EMV (Emisores EMV Full y/o Emisores
Parciales EMV), disponibles por el estndar de las franquicias, la Red SUICHE 7B, pone a
disposicin de sus instituciones miembros las siguientes modalidades de OBS, las cuales
permitan cumplir con los esquemas mencionados.
OBS 1 (Identificado con la letra O): En esta modalidad, si el Sistema CONNEX de
SUICHE 7B, recibe una transaccin basada en EMV que debe ser enviada a un Banco
Emisor configurado como NO EMV, este quitar la data EMV correspondiente a los campos
BIT 55 y BIT 23 de la transaccin y enviar el requerimiento con el PAN o TRACK 2, tal cual
como la transaccin fue originada hacia el Emisor. Sin embargo, el Modo de Entrada del
Punto de Servicio (POINT OF SERVICE ENTRY MODE) BIT 22, se mantendr con el valor
de 051, indicando que la transaccin original estaba basada en data EMV.
OBS 2 (Identificado con la letra X): En esta modalidad, si el el Sistema CONNEX de
SUICHE 7B, recibe una transaccin basada en EMV que debe ser enviada a un Banco
Emisor configurado como EMV o NO EMV, le enviar la data tal cual viene del Banco Emisor,
y si el Banco Emisor retorna el BIT 55 con la respuesta, la transaccin ser considerada
como EMV, si el Emisor no retorna el BIT 55, el sistema la considerar como una transaccin
OBS. En esta modalidad el Banco Emisor est en capacidad de validar el ARQC, lo que
indicar que la tarjeta fue emitida por el Emisor, pero no generar el ARPC.
Nota 1: Tal y como fue referido anteriormente, se requiere que el Banco Adquiriente est
conteste con el servicio OBS, y no valide el BIT 22 a fin de completar el procesamiento de la
transaccin de respuesta (MSG. 0210), sin data EMV.
Nota 2: En ambas modalidades el Banco Emisor deber retornar siempre el BIT 22,
conjuntamente con el resto de los datos ISO.
OPCIONES DEL EMISOR
El ARQC (AUTHORISATION REQUEST CRYPTOGRAM) en el BIT 055 prueba al emisor
que la tarjeta es genuina y que los datos en el BIT 55 son confiables:
1.
Issuer Application data informa al emisor que:

1.1.
1.2.
2.
Validacin Offline PIN fue realizada y si fue exitosa o no Valor de los

contadores fuera de lnea.
El estatus del procesamiento de Script en la transaccin anterior
El campo BIT 55 da informacin adicional (en caso de algn reclamo)

2.1.
TVR (Terminal Verification Result)
2.2.
CVM Results (Cardholder Verification Method)
2.3.
CVR (Card Verification Result)
RIF.: J-00259842-5
CAPITULO

PAGINA
180
XI
CAMBIO N
SERVICIOS DE CONVERSION OBS DE SUICHE 7B
FECHA:
26/04/2011
RESUMEN IMPACTO EN LOS EMISORES

1. Adecuar sistemas de autorizacin y compensacin para aceptar mensajes EMV
2. No es necesario crear nuevos BINES para el Proyecto EMV
3. Nuevos Valores en campos existentes: Terminal Capability y POS Entry Mode
4. Full EMV los impactos en el Host son mayores: para validar y generar criptogramas y
construccin de scripts
REQUERIMIENTOS ADQUIRENTE
CAM para Adquirentes Full Grade
Los ATM deben soportar solamente PIN en lnea. PIN fuera de lnea NO ES ACEPTADO.
RESUMEN IMPACTO EN LOS ADQUIRIENTES
1. Adecuar sistemas HOST adquirente para aceptar y adquirir transacciones EMV
2. Manejar como mnimo los CAM (SDA y/o DDA)
3. Prueba de Scripts provenientes de un Banco Emisor full grade EMV
4. Pasar proceso de certificacin de S7B como Emisor EMV
5. Pasar proceso de certificacin de S7B como ADQUIRENTE Full EMV
CAPITULO

RIF.: J-00259842-5
PAGINA
181
XII
CAMBIO N
FECHA:
CONSIDERACIONES PARA EL SIGRI (ON LINE BATCH)
26/04/2011
CONSIDERACIONES PARA EL SIGRI (ON LINE BATCH)

CONDICIONES A EVALUAR:
BIT 22
9F26
91
051 NORMAL
SI Presencia del ARQC
SI Presencia del ARPC
BIT 22
9F26
91
801 FALLBACK
NO PRESENCIA del ARQC
NO PRESENCIA del ARPC
ON BEHALF SERVICES EN SUICHE 7B

Bco. Adquiriente:
BIT 22
9F26
051
SI PRESENCIA del ARQC
SUICHE 7B / Bco. Emisor:

BIT 22
9F26
91
051
PRESENCIA O NO del ARQC (OBS 1 u OBS 2 en la Respuesta 0210)
NO PRESENCIA del ARPC
Notas: Se incorporar un indicador, mediante el cual el sistema de reclamos SIGRI podr

mostrar al Banco Adquiriente como fue tratada una transaccin reclamada, en funcin de las
situaciones mostradas arribas y resumidas en la siguiente tabla de resultado:
TABLA DE CONDICIONES
ICC
FB
Banda
OBS
(O / X)
Banda
Banda
Banda
0200/0210 MSG
BIT 22 (3 bytes)
051
801
051
021
901
0200/0210 ADQ
ARQC (8 bytes)
0210 EMI
ARPC (16 bytes)
FB = Fallback
RIF.: J-00259842-5
CAPITULO

PAGINA
182
XIII
CAMBIO N
ANEXOS
FECHA:
26/04/2011
ANEXO
ANEXO 1 - DESCRIPCIN DE LOS TAG QUE CONFORMAN EL BIT 55
ELEMENTOS DEL MENSAJES 0200
Application Cryptogram (AC) ARQC
EMV Tag:
Attributes:
9F26
EMV: b 8 bytes
Description: Contains an Authorization Request Cryptogram (ARQC) Transaction Certificate (TC) or

an Application Authentication Cryptogram (ACC). The card verification results field indicates which
cryptogram is present in this field.
Status Notes:
This data element is required when the financial transaction card is equipped with an
integrated circuit and when that mode is activated and selected by the cardholder for the transaction.
The FIS Connex on Tandem (Advantage) System stores (136)

EMV Tag:
Attributes:
9F27
FIS Corporation: bcd 1 byte
EMV: b 1 byte
Description:
Indicates the type of cryptogram and the actions to be performed by the terminal.
Status Notes:
This data element is required for MasterCard when the financial transaction card is
equipped with an integrated circuit and when that mode is activated and selected by the cardholder for
the transaction (160)
CAPITULO

RIF.: J-00259842-5
PAGINA
183
XIII
CAMBIO N
ANEXOS
FECHA:
26/04/2011
Issuer Application Data (IAD)

EMV Tag:
Attributes:
9F10
EMV: b VAR up to 32 bytes
Description:
transaction.
Contains proprietary application data for transmission to the issuer in an online
Status Notes:
(135)
EMV Tag:
Attributes:
9F37
EMV: 8 hex, 4 bytes
Description:
uniqueness.
A number used in the generation of the cryptogram. It provides variability and
Status Notes:
integrated circuit and when that mode is activated and selected by the cardholder for the transaction
(132)

EMV Tag:
Attributes:
9F36
EMV: b 2 bytes
Description:
Contains a count of the transactions performed within the card application and is
incremented by one each time a transaction is initiated. This field is a retain and return field for Visa.
Status Notes:
integrated circuit and when that mode is activated and selected by thecardholder for the transaction.
The FIS Connex on Tandem (Advantage) System stores this data element to be available for
settlement reporting. (137)
RIF.: J-00259842-5
CAPITULO

PAGINA
184
XIII
CAMBIO N
ANEXOS
FECHA:
26/04/2011
Terminal Verification Result (TVR)

EMV Tag:
95
Attributes:

Description:
A series of 40 bits used to indicate from a terminal perspective the results of offline
and online processing by setting a series of indicators in this field.
Status Notes:
This data element is required when the financial transaction card is equipped with
an integrated circuit and when that mode is activated and selected by the cardholder for the
transaction. (131)
Transaction Date
EMV Tag:
9A
Attributes:
FIS Corporation: 6n, bcd 3 bytes YYMMDD

EMV: n6 3 bytes YYMMDD
Description:
The local date the transaction was authorized.
Status Notes:
integrated circuit and when that mode isactivated and selected by the cardholder for the transaction.
(146)
Transaction Type
EMV Tag:
Attributes:
9C
EMV: n2 1 byte
Description:
The type of financial transaction as represented by the first two digits of the ISO
8583:1987 processing code.
Status Notes:
(144)
Transaction Amount or Amount Authorized

EMV Tag:
9F02
Attributes:

EMV: n12 6 bytes
RIF.: J-00259842-5
CAPITULO

185
XIII
CAMBIO N
ANEXOS
Description:
PAGINA
FECHA:
26/04/2011
The transaction amount used when calculating the cryptogram.
Status Notes:
(147)
ELEMENTOS OPCIONALES
Terminal Capability Profile
EMV Tag:
9F33
Attributes:
FIS Corporation: 3 bytes

Description:
A series of 24 bits used to identify the card data input, the Cardholder Verification
Method (CVM), and the security capabilities supported by the terminal. Visa requires this as a retain
and return field for chargebacks and representments.
Status Notes:
This data element is optional for MasterCard and required for Visa when the
financial transaction card is equipped with an integrated circuit and when that mode is activated and
selected by the cardholder for the transaction. (130).
Cardholder Verification Method (CVM) Results

EMV Tag:
9F34
Attributes:

EMV: b 3 bytes
Description: The results of the last cardholder verification performed.

Status Notes:
This data element is optional for MasterCard when the financial transaction card is
the transaction. (161)
Terminal type
EMV Tag:
Attributes:
9F35
EMV: n2 1 byte
RIF.: J-00259842-5
CAPITULO

PAGINA
186
XIII
CAMBIO N
ANEXOS
FECHA:
26/04/2011
Description:
Indicates the environment of the terminal, its communication capability, and its
operational control.
Status Notes:
the transaction. (162)
Terminal IFD serial Number

EMV Tag:
9F1E
Attributes:
FIS Corporation: an 8 bytes

EMV: an 8 bytes
Description:
A unique and permanent serial number assigned by the manufacturer.
Status Notes:
This data element is optional when the financial transaction card is equipped with an
(133)
Transaction category code

EMV Tag:
Attributes:
9F53
FIS Corporation: an 1 byte
EMV: an 1 byte
Description:
MasterCard has defined an additional terminal resident data element that is
available to assist with Card Risk Management.
Status Notes:
equipped with an integrated circuit and when that mode is activated and selected by the cardholder
for the transaction. (166)
Dedicated File Name

EMV Tag:
84
Attributes:

EMV: b 5, 16 bytes
Description:
Identifies the name of the dedicated file as described in ISO/IEC7968-4.
Status Notes:
for the transaction. (163).
RIF.: J-00259842-5
CAPITULO

PAGINA
187
XIII
CAMBIO N
FECHA:
ANEXOS
26/04/2011
Terminal Application Version Number

EMV Tag:
9F09
Attributes:

EMV: b 2 bytes
Description:
The version number assigned by the payment system for the application.
Status Notes:
the transaction. (164).
Transaction Sequence Counter

EMV Tag:
9F41
Attributes:

EMV: n4-8, 2-4 bytes
Description:
Counter maintained by the terminal that is incremented by one for each transaction.
Status Notes:
for the transaction. (165)
Amount, Other
EMV Tag:
Attributes:
Description:
mount.
Status Notes:
9F03
FIS Corporation: 12n, bcd 6 bytes EMV: n12 6 bytes
The secondary amount associated with the transaction, representing a cash back
This data element is required when supplied by the acquirer. (149).
RIF.: J-00259842-5
CAPITULO

PAGINA
188
XIII
CAMBIO N
ANEXOS
FECHA:
26/04/2011
ELEMENTOS MENSAJES DE RESPUESTA 0210

Issuer Authentication Data
EMV Tag:
Attributes:
91
EMV: b 8, 16 bytes
Description:
The application Interchange profile consists of two subfields. In the response
message, the first 8 bytes contains the authorization response cryptogram used to authenticate the
issuer.
The next 1 - 8 bytes contains proprietary data.
Visa uses bytes 9 - 10 as the ARPC response code. It is the response value used
by the issuer to create the ARPC.
Status Notes:
This data element is required when the issuer authentication occurred when the
financial transaction card is equipped with an integrated circuit and when that mode is activated and
selected by the cardholder for the transaction. (139)
Issuer Script Command

EMV Tag:
Attributes:
71
Description:
This field contains proprietary information that the issuer wants to communicate to
the card. This script is processed before issuing the second Generate AC command.
Status Notes:
integrated circuit and when that mode is activated and selected by the cardholder for the Transaction.
(141).
Issuer Script Command 2

EMV Tag:
Attributes:
72
Description:
This field contains proprietary information that the issuer wants to communicate to
the card. This script is processed after issuing the second Generate AC command.
Status Notes:
(142)
RIF.: J-00259842-5
CAPITULO

PAGINA
189
XIII
CAMBIO N
ANEXOS
FECHA:
26/04/2011
ANEXO 2 - CAMPOS MNIMOS PARA EL CLCULO/VERIFICACIN DEL ARQC Y ARPC

Verificacin ARQC
IMKac Session Key
Data:
ATC 9F36 (02)

UN
9F37 (04)
Calculo ARQC CDOL1, DATOS
Tag
Len
Source
Amount, Authorized
9F02
06
Terminal
Amount, Other Terminal
9F03
06
Terminal
9F1A
02
Terminal
Terminal Verification Results
95
05
Terminal
5F2A
02
Terminal
Transaction Date
9A
03
Terminal
Transaction Type
9C
01
Terminal
9F37
04
Terminal
82
02
ICC
Application transaction counter
9F36
02
ICC
Issuer Application Data.
9F10 (XX)
ICC
CARD VERIFICATION RESULT (CVR)
MasterCard: 6 bytes de las posiciones 3 a la 8 ambos

Inclusive.
VISA: 6 bytes de las posiciones 4 a la 9 ambos
Inclusive.
xCheck (Simulador S7B)

Tag 5A
Tag 5F34
PAN
BIT 23 = 000 o 001 (3 bytes) CSEQ = 00 o 01 (2 dos ltimos bytes del BIT 23)
PAD
X80
Generacin ARPC
Tag 9F26
ARC
Application Cryptogram (08)

Authorization Response Code (02)
Tag 91 =
ARQC + ARC
RIF.: J-00259842-5
CAPITULO

PAGINA
190
XIII
CAMBIO N
ANEXOS
FECHA:
26/04/2011
RESPONSES CODES.
CVR Decline
: 05 (do not honor)
TVR Decline
: 05 (do not honor)
ARQC Failure
: 06 (Error Clave No Sync)
Fallback Decline
: 12(Invalid transaction)
RECOMENDACIONES PARA LA REALIZACIN DE PRUEBAS EMV EN LA RED S7B
La institucin solicitante debe participar a la Gerencia de Operaciones, su intencin de

realizar pruebas e indicar la modalidad en la que participar, las cuales pueden ser:
o Implementacin Parcial (OBS) emisin del plstico EMV
o Implementacin Full EMV como Adquiriente y Emisor
Igualmente, deber proporcionar al menos tres (3) tarjetas EMV (chip) y las llaves
definidas en estas, para que sean cargarlas en el Simulador de S7B, a fin de poder
realizar las validaciones del ARQC y ARPC del Banco solicitante y as, permitir la
accin de EMISOR con el Simulador. Las llaves deben ser de doble longitud (32
Hexadecimales).
Una vez recibidas las tarjetas y llaves correspondientes de la institucin solicitante, se

asignarn las ventanas de pruebas para probar el buen funcionamiento de las
mismas, haciendo que el Simulador reciba transacciones como Emisor para validar el
ARQC y ARPC de estas.
Para ejecutar lo anterior y en funcin del mapa de Bancos que estn participando en
las pruebas EMV, se har la distribucin de las tarjetas EMV propias del Banco
solicitante a otros Bancos y a ste, se le enviar alguna(s) tarjeta(s) de los otros
Bancos.
Posteriormente, y una vez certificadas las llaves criptogrficas, se deber hacer

pruebas del Banco solicitante como Adquiriente, a fin de verificar la mensajera EMV.
Una vez realizado lo anterior, la institucin estar lista para realizar pruebas como
Adquiriente y Emisor conjuntamente con los otros Bancos en pruebas.
Para certificar deber ejecutar el Script de Prueba diseado por SUICHE 7B con la
participacin de los Bancos Miembros de la Red.

Mensajeria Suiche7B

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Mensajeria Suiche7B

Transféré par

Droits d'auteur :

Formats disponibles

FIS ISO 8583 PROCESSOR INTERFACE MESSAGE

Alexander Jos Azocar

Coord. Organizacin y Calidad

Gerente de Tecnologa y Proyectos

FIS ISO 8583 PROCESSOR INTERFACE

Descripcin del Cambio

Modificacin en el Capitulo IX PROCESSING CODES

Gerente de Tecnologa y Proyectos

Sistema de Gestin de la Calidad (Aplicacin)

FIS ISO 8583 PROCESSOR INTERFACE MESSAGE SPECIFICATIONS GUIDE

FIS ISO 8583 PROCESSOR INTERFACE

USO DE ESTE DOCUMENTO..........................................................................................................1

FORMATO DE MENSAJES SUICHE 7B .......................................................................................14

FIS ISO 8583 PROCESSOR INTERFACE

0200/0201 FINANCIAL TRANSACTION REQUEST ........................................................................21

DATA ELEMENT DEFINITIONS.....................................................................................................52

TRAZAS MENSAJERA ISO 8583 SUICHE 7B ..........................................................................147

DATA ELEMENTS CODE TABLES .............................................................................................150

FIS ISO 8583 PROCESSOR INTERFACE

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

DATA ELEMENTS ISO 8583 (BIT 55)..........................................................................................175

SERVICIOS DE CONVERSIN OBS DE SUICHE 7B................................................................179

CONSIDERACIONES PARA EL SIGRI (ON LINE BATCH)....................................................181

FIS ISO 8583 PROCESSOR INTERFACE

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

FIS ISO 8583 PROCESSOR INTERFACE MESSAGE SPECIFICATIONS GUIDE

FIS ISO 8583 PROCESSOR INTERFACE

USO DE ESTE DOCUMENTO

USO DE ESTE DOCUMENTO

Gerencia de Tecnologa y Proyectos

Coordinacin de Organizacin y Sistemas

FIS ISO 8583 PROCESSOR INTERFACE MESSAGE SPECIFICATIONS GUIDE

FIS ISO 8583 PROCESSOR INTERFACE

Updated the table information for:

FIS ISO 8583 PROCESSOR INTERFACE MESSAGE SPECIFICATIONS GUIDE

FIS ISO 8583 PROCESSOR INTERFACE

Data Elements 065

The message text is EBCDIC characters.

FIS ISO 8583 PROCESSOR INTERFACE MESSAGE SPECIFICATIONS GUIDE

FIS ISO 8583 PROCESSOR INTERFACE

Encryption and Logon Options

Messages and Bit Maps

C: Condicional. (The data element is required when specific conditions are

Totals Processing Option

Following are supported network management options.

Reversal Processing Options

You can select to send/receive reversals for late/unsolicited responses or send/receive

FIS ISO 8583 PROCESSOR INTERFACE MESSAGE SPECIFICATIONS GUIDE

FIS ISO 8583 PROCESSOR INTERFACE

Multiple Message Transactions

More secure method of validating cardholders

Decreased susceptibility to fraud schemes such as skimming.

FIS ISO 8583 PROCESSOR INTERFACE MESSAGE SPECIFICATIONS GUIDE

FIS ISO 8583 PROCESSOR INTERFACE

Message type identifier

One or more bit maps

A series of data elements in the order of the bit map representation

MESSAGE TYPE IDENTIFIER

FIS ISO 8583 PROCESSOR INTERFACE

Authorization Request Check

Authorization Request Response Check Verification/Guarantee/

Repeat 0120Authorization Advice

Authorization Advice Response

Financial Transaction Messages