Professional Documents
Culture Documents
28.03.2014 10:45:03
Contents
OVERVIEW ....................................................................................................................................... 5
CBSCOMMUNICATION PROTOCOL ......................................................................................... 6
CBS ISO-8583 MESSAGE TYPES .................................................................................................. 7
1.
2.
3.
4.
4.1.
4.2.
4.3.
4.4.
4.5.
4.6.
4.7.
4.8.
4.9.
4.10.
4.11.
4.12.
4.13.
4.14.
4.15.
4.16.
4.17.
4.18.
4.19.
4.20.
SmartVista Front-End
SmartVista Front-End
SmartVista Front-End
OVERVIEW
This document describes specifications for the SmartVista Front End (SVFE) Core Banking
System (CBS) external message protocol. The protocol can be used to provide authorization and
information services to card processing hosts or transaction concentrators.
The current software releases are implementing an external message based on the International
Organization for Standardization (ISO) 8583-2:1993 standard.
The message specifications in this manual are applicable to the ISO-based external message only.
SmartVista Front-End
CBSCOMMUNICATION PROTOCOL
CBS Interface supports the TCP/IP transport protocol.
TCP/IP is a point to point communication protocol with a delivery guarantee and data sequence
guarantee. The connection party, which initiates a connection, is a TCP/IP client. The connection
party, which accepts the connection, is a TCP/IP server. TCP/IP client establishes connection
identifying target application with an IP address of the host and a port number within that host. If
the connection is dropped by any reason it should be re-established by the client application.
SVFE host can act in a TCP/IP connection as a client or as a server depending on the host
configuration. For data transmission TCP/IP uses sessions. Each session is a bi-directional data
stream. SVFE protocol uses a single TCP/IP session to transfer data between hosts in both
directions. The continuous TCP/IP data stream is split into frames. Each ISO 8583 message is sent
in a separate frame. A Frame consists of a 2-byte length header and a message body. The header
contains the length of the following message. The high byte of value is transmitted first, and the low
byte of value is transmitted second.
2 bytes
Message Length = N
N bytes
ISO 8583 Message
SmartVista Front-End
1.
Authorization Messages
SmartVista Front-End
2.
Reversal Messages
3.
Administrative Messages
4.
SmartVista Front-End
Authorization Messages
sd Auth
SVFE
CBS
1100()
1110()
2.
Message 1121 is sent when there is no response to message 1120. Message 1121 is sent not more
than three times.
Message 1121 is sent 60 seconds after sending message 112X, for which a response has not been
received.
sd Auth Adv ice
SVFE
CBS
1120()
1130()
1121()
1130()
3.
Reversal Messages
SmartVista Front-End
CBS
1420()
1430()
1421()
1430()
SmartVista Front-End
CBS
1420()
1430()
1420()
1430()
1421()
1430()
4.
Administrative Messages
sd Administrativ e
SVFE
CBS
1600()
1610()
5.
SmartVista Front-End
CBS
1804()
1804()
1814()
SVFE
1804()
1804()
1814()
SmartVista Front-End
SVFE
Connection Lost
Stand-In processing()
Stand-In processing()
1804(Test of connection)
1814()
1804(Sign-On)
1814()
1120()
1130()
1120()
1130(Last transaction)
1814()
SmartVista Front-End
DATA FIELDS
1.
Special characters
an
As
ns
ans
16
Variable length up to a maximum of 16 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
Bit
Map
8 bytes (64 bits) in binary format. Each bit signifies the presence (1) or the absence (0) in the message
of the data field associated with that particular bit
C for credit, D for debit and shall always be associated with a numeric amount data field, i.e., x+n
16 in amount, net reconciliation means prefix C or D and 16 digits of amount, net reconciliation
2.
Month
DD
Day
YY
Year
hh
Hour
mm
Minute
SS
Second
SmartVista Front-End
Length of variable data field that follows, from 01-99. The variable length subelement is two numeric
characters.
LLL
Length of variable data field that follows, from 001-999. The variable length subelement is three
numeric characters.
VAR
3.
C Conditional. Field/value is present in the message under certain conditions, which are explained
in Data Field Description.
M Mandatory. Field/value must be present in the message.
O Optional. Field/value presence in the message is up to the message initiator or the responder.
4.
4.1.2. Description
This field is a bit map indicating the presence or absence of fields in the secondary portion of the
message, bits 65-128. This field should only be present if there is at least one field from the
secondary range in the message.
4.2.2. Description
This field contains the cardholders card number.
SmartVista Front-End
4.3.2. Description
The processing code is a series of three two-byte codes. The first two bytes (bytes 1 and 2) indicate
the type of transaction.
See the following table for valid values.
Transaction
Code
00
00
01
01
03
11
16
17
17
17
18
18
18
19
19
20
20
20
21
21
21
21
21
22
26
27
28
SVFE Transaction
Type
774
680
700
777
740
781
596
612
670
659
736
677
671
737
678
775
681
669
585
618
705
712
711
750
570
760
698
TRANSACTION
DESCRIPTION
POS Purchase/P2P Debit/Utility Payment
E-POS Purchase
ATM Cash withdrawal
POS Cash Advance
Check guarantee transaction
P2P Debit
Installment Purchase
BN Bill Payment
Manual Cash withdrawal
Debit account with presentment
POS Pre-authorisation
E-POS Pre-authorisation
Manual Purchase
POS Completion
E-POS Completion
POS Return or Refund
E-POS Return or Refund
Manual Refund Completion
Cash Deposit Account
ATM Cash Deposit
Deposit
POS Cash Deposit
E-POS Cash Deposit
Credit Adjustment
Service Reimbursement
Credit account with presentment
Credit Payment
SmartVista Front-End
SVFE Transaction
Type
785
702
784
757
676
684
796
704
703
613
530
692
508
510
893
588
471
707
493
644
672
782
797
798
603
751
753
474
TRANSACTION
DESCRIPTION
P2P Credit
Balance Inquiry
POS Balance Inquiry
Balance Inquiry on Screen
E-POS Balance Inquiry
Advanced Repayment Information
Account Verification
Mini-Statement
Funds Transfer
ATM BN IBFT
Transfer to external account
Transfer to foreign account
Utility Payment
Predefined Payment
Predefined Service Payment
Full Advanced Repayment
Prepaid Card
Payment from Envelope
Block Card
Activate Card
Change Card Status
Validate Card
Service On
Service Off
Forced PIN Change
PIN Change
New PIN Reentry
Change Account Status
The second and third two bytes (bytes 3 and 4, and bytes 5 and 6) indicate the account 1 and account
2 type, respectively .
See the following table for valid values.
ACCOUNT TYPE
0X
1X
2X
3X
4X
5X
6X
7X
ACCOUNT DESCRIPTION
Default (unspecified) account
Savings account
Checking account
Credit account
Others Account
Loans Account
Envelope Account
Escrow Account
SmartVista Front-End
ACCOUNT DESCRIPTION
Money Market Account
Loyalty Account
The second byte in each pair (i.e. byte 4 and 6) indicates an order of account that is used in
transaction in the list of card accounts with the same type. Valid values are 0-8.
4.4.2. Description
Funds requested by the cardholder in the local currency of the acquirer or source location of the
transaction, exclusive of amounts, fees.
In the 1100 balance inquiry request, this field will contain zeroes. In the 1110 balance inquiry
response, this field will contain the account balance or zeroes if account balance is negative.
4.5.2. Description
Amount in cardholder account currency, including fees.
In requests field contains transaction amount, in responses the actual account balance.
4.6.2. Description
SmartVista Front-End
4.7.2. Description
This field contains the rate used to convert the transaction amount (Field 4) to the cardholder
billing amount (Field 6). The Field 4 amount multiplied by this rate equals the Field 6 amount. The
left-most digit denotes the number of positions the decimal separator shall be moved from the right
(allowable values are 0 to 7). Positions 28 of the field are the actual rate.
For example: 69985022 = 9.985022.
4.8.2. Description
This field contains the rate used to convert the Cardholder Billing amount (Field 6) to the
Cardholder Account amount (Field 4). The left-most digit denotes the number of positions the
decimal separator shall be moved from the right (allowable values are 0 to 7). Positions 28 of the
field are the actual rate.
For example: 69985022 = 9.985022.
SmartVista Front-End
4.9.2. Description
A number assigned by a transaction originator to assist in identifying a transaction uniquely. The
trace number remains unchanged for all messages within the transaction.
This field is also used to match a response message with its original message.
4.10.2.Description
The local year, month, day, and time the transaction takes place at the card acceptor location in
authorization and financial messages.
This field is also used to match a response message with its original message.
4.11.2.Description
The year and month that the card will become expired.
4.12.2.Description
SmartVista Front-End
4.13.2.Description
A code describing the merchants type of business product or service. See ISO-8583 standard
documentation for the list of valid categories.
4.14.2.Description
A series of codes intended to identify terminal capability, terminal environment and presentation
security data. It shall be used to indicate specific conditions that are (or were) present at the time a
transaction took place at the point of service and/or when the transaction has been initiated.
See the following table for valid values.
Position
1
Position Description
Card data input
capability
Cardholder
authentication
capability
Valid Values
0 Unknown
1 Manual
2 Magnetic stripe reader
3 Bar code reader
4 OCR reader
5 EMV compatible ICC reader
6 Key entry
7 Magnetic stripe reader and key entry
8 Magnetic stripe reader, key entry and
EMV compatible ICC reader */
9 Contactless read
0 No electronic authentication
1 PIN
2 Electronic signature analysis
3 Biometrics
4 Biographic
5 Electronic authentication
6 Other
SmartVista Front-End
Position Description
Card
capability
capture
Operating
environment
Cardholder
indicator
Card presence
Cardholder
authentication method
Cardholder
authentication entity
presence
Valid Values
0 None
1 Capture
0 no terminal used
1 on premises of card acceptor, attended
2 on premises of card acceptor, untended
3 Off premises of card acceptor, attended
4 Off premises of card acceptor, unattended
5 On premises of card cardholder, unattended
9 On premises of card cardholder, attended
0 Present
1 Not present, unspecified
2 Not present, mail order
3 Not present, telephone order
4 Not present, standing order (recurring payment)
5 Not present, electronic order
S Not present, postponed payment
0 Not present
1 Present
0 Unspecified
1 Manual, no terminal
2 Magnetic stripe read
3 BAR read
4 OCR read
5 ICC read
6 Key entered
7 Contactless ICC read
8 Contactless magnetic stripe read
9 Contactless read
S E-commerce, merchant certificate only
T E-commerce, merchant and cardholder certificate / 3-D Secure
transaction
U E-commerce, no security
V E-commerce, channel encryption
0 No authentication
1 PIN
2 Electronic signature analysis
3 Biometrics
4 Biographic
5 Manual signature
6 Other manual authentication
T E-commerce, UCAF / 3DS authentication is not supported by
merchant
U E-commerce, UCAF / 3DS authentication is supported by
merchant but is not provided by issuer
V E-commerce, UCAF / 3DS authentication is supported by
merchant and is provided by issuer
0 Not authenticated
1 ICC
3 Authorizing agent, online PIN
4 Merchant/card acceptor, signature
5 Other
S Merchant suspicious
SmartVista Front-End
Position Description
10
Card
data
capability
output
11
Terminal
capability
output
12
Valid Values
0 Unknown
1 None
2 Magnetic stripe write
3 ICC
0 Unknown
1 None
2 Printing capability only
3 Display capability only
4 Printing and display capability
0 No PIN capture capability
1 Unknown
4 PIN capture capability 4 characters maximum
5 PIN capture capability 5 characters maximum
6 PIN capture capability 6 characters maximum
7 PIN capture capability 7 characters maximum
8 PIN capture capability 8 characters maximum
9 PIN capture capability 9 characters maximum
A PIN capture capability 10 characters maximum
B PIN capture capability 11 characters maximum
C PIN capture capability 12 characters maximum
4.15.2.Description
Code indicating the specific purpose of the message within its message class.
See the following table for valid values.
FUNCTION
CODE
801
802
831
841
DESCRIPTION
Sign-On
Sign-Off
Echo-test
SAF list end
MESSAGE
TYPE
1804
1804
1804
1804
SmartVista Front-End
4.16.2.Description
This code identifies the financial institution acting as the acquirer of this cardholder transaction. The
acquirer is a member or system user that installed the terminal. The ID can be a Visa BIN, a
MasterCard BIN, or another code that identifies the financial institution or branch within
SmartVista Front-End. BINs are usually six digits, but the code may be up to 11 digits long. The
value length specifies the number of digits in the ID code.
4.17.2.Description
A reference supplied by the system retaining the original source information and used to assist in
locating that information or a copy thereof.
If no reply was received to the original transaction Field 037 must still be present, but it should
contain a string of spaces.
4.18.2.Description
An authorization code provided by the CBS when a transaction is approved, or a no-reason-todecline code provided for successful verifications. Value of field 38 is based on value of field 37.
In the C program shown below the input parameter u of function auth is value of Field 37, and
output parameter a is value of field 38.
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
char *voc[6]={
SmartVista Front-End
4.19.2.Description
A code which defines the action taken or to be taken as well as the reason for taking the action.
SVFE RC
CBS RC
Description
-1
000
Successful transaction
826
001
Successful transaction, but MCC is in list 6010, 4829, 6051, 7995, 7511
818
111
SmartVista Front-End
CBS RC
Description
928
112
Account is blocked
915
116
913
124
4811
Customer
cancellation
The cardholder aborted the transaction after an authorisation request had
been sent
482
Completed
partially
Used in reversal messages to indicate that a transaction was completed,
but for an amount less than that given in the original 0100 request
483
Response
received
too
late
Used to indicate the reason for sending a reversal an authorisation
response was not returned within the time limit set by the acquirer
496
System
malfunction
The message could not be successfully processed due to a system
malfunction (see also Note below)
812
902
802
907
959
909
802
910
959
914
This code is sent from CBS in case the cancellation request 703 was
sent when the operational day in CBS is closed.
811
913
Duplicate transaction
959
916
894
894
895
895
SmartVista Front-End
CBS RC
Description
997
997
4.20.2.Description
A code that uniquely identifies a particular terminal at the card acceptors location. An identification
code of less than eight positions must be left-justified and the remainder of the field space-filled.
This field is mandatory if the terminal id is available.
4.21.2.Description
The name and location of the card acceptor. This field is required in authorization requests, advice
messages and related reversal requests for all card-read transactions. It contains the information
necessary for printing on customer account statements and on credit card billing statements.
Subfield
Type and
length of data
ans 38
ans 2
Data dictionary
Merchant number of bank name;
Separator >
Merchant city or location of the terminal device
Trailing spaces
ISO code of the country
SmartVista Front-End
4.22.2.Description
This field is used to carry SmartVista Front-End internal information. There is a number of tags packed
in field 48. The tags have the TLV structure. It means they are repeated groups of Tag IDs, Tag Lengths
and Tag Values.
Banking Production Center may occasionally introduce new Field 48 tags between SVFE releases to
facilitate special processing. Banking Production Center requires members using SVFE CBS
specification to be able to successfully process various online messages that may contain new
unannounced Field 48 tags.
Refer to Appendix A (Field 48).
4.23.2.Description
This field is used in any message related to a cardholder transaction that contains one or more of the
amount fields listed above, even when the amount is zero. This field is also used in balance inquiry
requests, even when the value of field 4 equals zero. This code specifies the currency in which the
acquirer wants the balance amount to be expressed.
4.24.2.Description
SmartVista Front-End
4.25.2.Description
This field contains a 3-digit numeric code that identifies the currency used by the issuer to bill the
cardholders account.
4.26.2.Description
This field is used to carry SmartVista Front-End account balance information. There is a number of
tags packed in Field 54. The tags have the TLV structure. It means they are repeated groups of Tag IDs,
Tag Lengths and Tag Values.
Banking Production Center may occasionally introduce new Field 54 tags between SVFE releases to
facilitate special processing. Banking Production Center requires members using SVFE CBS
specification to be able to successfully process various online messages that may contain new
unannounced Field 54 tags.
5.
Tag No
Size
Data
011
Ans 32
Service Data.
If available must be present in 1100/1120/1121 messages.
SmartVista Front-End
6.
Tag No
Size
Data
012
ans 28
7.
Tag No
Size
Data
013
ans 6
Contract ID.
If available must be present in 1100/1120/1121 messages.
8.
Tag No
Size
Data
014
Ans 30
Cardholder address
If available must be present in 1100 messages.
9.
Tag No
Size
Data
015
Ans 9
Size
Data
016
n3
Size
Data
017
Ans 99
SmartVista Front-End
Size
Data
018
n2
Size
Data
019
n4
Size
Data
020
ans ..25
SmartVista Front-End
Size
Data
021
ans ..99
Size
Data
022
ans ..32
Length
Data
023
an 1
Length
Data
024
ans ..255
Size
Data
090-099
ans ..25
SmartVista Front-End
19.1.2.Description
This field is used to carry SmartVista Front-End account balance information. There is a number of
tags packed in Field 61. The tags have the TLV structure. It means they are repeated groups of Tag IDs,
Tag Lengths and Tag Values.
Banking Production Center may occasionally introduce new Field 61 tags between SVFE releases to
facilitate special processing. Banking Production Center requires members using SVFE CBS
specification to be able to successfully process various online messages that may contain new
unannounced Field 61 tags.
Length
Data
008
an 12
Length
Data
009
an 12
SmartVista Front-End
21.1.2.Description
Field contains mini-statement data, only for 704 SVFE Transaction Type, up to 10 sets:
N
Description
Attributes
Comments
Transaction Date
n6
YYMMDD
ans 3
A1
C credit transaction,
D debit transaction
noop transaction
Amount Transaction
N 12
SmartVista Front-End
21.2.2.Description
Account balance.
21.3.2.Description
The Primary Message Authentication Code data field carries the message authentication code
(MAC) for the message. This code is generated by ANSI X9.19 Method. Fields at MAC are filled
in according type of message formats represented at next chapter MASSAGE FORMAT (look at
last column Field Used For Mac Y or N)
If the message contains secondary data fields, Field 128 is used to carry the message authentication
code. If the message authentication code is carried in Field 128, Field 64 is not included in the
message.
21.4.2.Description
This field is used to indicate type of operation. See table bellow.
Value
Description
Add operation
SmartVista Front-End
Description
Delete operation
21.5.2.Description
This field is used to carry SmartVista Front-End amount information. There is a number of tags packed
in Field 95. The tags have the TLV structure. It means they are repeated groups of Tag IDs, Tag Lengths
and Tag Values.
Banking Production Center may occasionally introduce new Field 95 tags between SVFE releases to
facilitate special processing. Banking Production Center requires members using SVFE CBS
specification to be able to successfully process various online messages that may contain new
unannounced Field 95 tags.
Length
Data
003
n 15
or n 30
or n 45
SmartVista Front-End
22.1.2.Description
Field contains SVFE Issuer Institution Identifier.
22.2.2.Description
Field is used in cardholder transactions. Field identifies an account number of cardholder
relationship.
22.3.2.Description
Field is used in cardholder transactions. Field identifies second account number of cardholder
relationship. For example, TO account for transfers.
22.4.2.Description
The Secondary Message Authentication Code data field carries the message authentication code
(MAC) for the message. See Field 61: Additional Amounts and Counters
22.4.3.Format
lllvar an999
22.4.4.Description
This field is used to carry SmartVista Front-End account balance information. There is a number of
tags packed in Field 61. The tags have the TLV structure. It means they are repeated groups of Tag IDs,
Tag Lengths and Tag Values.
Banking Production Center may occasionally introduce new Field 61 tags between SVFE releases to
facilitate special processing. Banking Production Center requires members using SVFE CBS
specification to be able to successfully process various online messages that may contain new
unannounced Field 61 tags.
Length
Data
008
an 12
Length
Data
009
an 12
SmartVista Front-End
24.1.2.Description
Field contains mini-statement data, only for 704 SVFE Transaction Type, up to 10 sets:
N
Description
Attributes
Comments
Transaction Date
n6
YYMMDD
ans 3
A1
C credit transaction,
D debit transaction
noop transaction
Amount Transaction
N 12
24.2.2.Description
Account balance.
.
SmartVista Front-End
MESSAGE FORMATS
1.
Authorization Message
1.1. Request
Bit
No.
Field Used
For Mac
Y or N
Attributes
Status
Comments / Remarks
Message Type
n4
Value is 1100
b64
b64
Primary Account
Number
n24
Processing Code
n6
Amount, Transaction
n12
Amount, Account
n12
Amount, Cardholder
Billing
n12
Conversion Rate,
Cardholder Billing
n8
10
Conversion Rate,
Account
n8
11
n6
12
YYMMDDhhmmss
n12
14
Date, Expiration
YYMM
n4
15
Settlement Date
YYMMDD
n6
18
Merchant Type
n4
22
ans12
MO
32
Acquiring Institution
Identification Code
n11
37
Retrieval Reference
Number
an12
41
Card Acceptor
Terminal Identification
ans 8
Format
LLVAR
LLVAR
SmartVista Front-End
Bit
No.
Field Used
For Mac
Y or N
Format
Attributes
Status
43
LLLVAR
ans136
48
Additional Data
LLLVAR
ans.. 999
49
Currency Code,
Transaction
n3
50
Currency Code,
Account
n3
51
Currency Code,
Cardholder Billing
n3
54
Additional Amounts
ans.. 999
64
b8
91
Action Code
an 1
Must be present if
Transaction Code = 92
100
LLVAR
ans 4
102
Account Identification
LLVAR
ans32
103
Account Identification2
LLVAR
ans32
128
b8
Attributes
Status
Comments / Remarks
Value is 1110
LLLVAR
Comments / Remarks
1.2. Response
Field Used
For Mac
Y or N
Bit
No.
Message Type
n4
b64
b64
Primary Account
Number
n24
Processing Code
n6
Amount, Transaction
n12
Amount, Account
n12
11
n6
37
Retrieval Reference
an12
Format
LLVAR
SmartVista Front-End
Bit
No.
Format
Attributes
Status
Comments / Remarks
Field Used
For Mac
Y or N
Number
38
Authorisation
Identification Response
ans6
39
Response Code
An3
41
Card Acceptor
Terminal Identification
ans 8
48
Additional Data
ans.. 999
50
Currency Code,
Account
n3
54
Additional Amounts
LLLVAR
ans.. 999
62
Mini-statement data
LLLVAR
ans220
63
Account Balance
n 12
64
b8
102
Account Identification
ans32
128
b8
2.
LLLVAR
LLVAR
N
Y
2.1. Request
Bit
No.
Field Used
For Mac
Y or N
Attributes
Status
Comments / Remarks
Message Type
n4
Value is 1120
b64
b64
Primary Account
Number
n24
Processing Code
n6
Amount, Transaction
n12
Amount, Account
n12
Amount, Cardholder
Billing
n12
Conversion Rate,
Cardholder Billing
n8
Format
LLVAR
SmartVista Front-End
Bit
No.
Format
Attributes
Status
Comments / Remarks
Field Used
For Mac
Y or N
10
Conversion Rate,
Account
n8
11
n6
12
YYMMDDhhmmss
n12
14
Date, Expiration
YYMM
n4
15
Settlement Date
YYMMDD
n6
18
Merchant Type
n4
22
ans12
MO
32
Acquiring Institution
Identification Code
n11
37
Retrieval Reference
Number
an12
38
Authorisation
Identification Response
ans6
39
Response Code
An3
41
Card Acceptor
Terminal Identification
ans 8
43
LLLVAR
ans136
48
Additional Data
LLLVAR
ans.. 999
49
Currency Code,
Transaction
n3
50
Currency Code,
Account
n3
51
Currency Code,
Cardholder Billing
n3
64
b8
91
Action Code
an 1
Must be present if
Transaction Code = 92
100
LLVAR
ans 4
102
Account Identification
LLVAR
ans32
103
Account Identification2
LLVAR
ans32
LLVAR
SmartVista Front-End
Bit
No.
128
Format
Attributes
Status
Comments / Remarks
b8
Attributes
Status
Comments / Remarks
Value is 1130
Field Used
For Mac
Y or N
N
2.2. Response
Field Used
For Mac
Y or N
Bit
No.
Message Type
n4
b64
b64
Primary Account
Number
n24
Processing Code
n6
11
n6
37
Retrieval Reference
Number
an12
39
Response Code
An3
41
Card Acceptor
Terminal Identification
ans 8
48
Additional Data
ans.. 999
50
Currency Code,
Account
n3
54
Additional Amounts
ans.. 999
63
Account Balance
n 12
64
b8
102
Account Identification
ans32
128
b8
Format
LLVAR
LLLVAR
LLLVAR
LLVAR
SmartVista Front-End
N
Y
3.
Reversal Messages
3.1. Request
Bit
No.
Field Used
For Mac
Y or N
Attributes
Status
Comments / Remarks
Message Type
n4
Value is 1420
b64
b64
Primary Account
Number
n24
Processing Code
n6
Amount, Transaction
n12
Amount, Account
n12
Amount, Cardholder
Billing
n12
Conversion Rate,
Cardholder Billing
n8
10
Conversion Rate,
Account
n8
11
n6
12
YYMMDDhhmmss
n12
14
Date, Expiration
YYMM
n4
15
Settlement Date
YYMMDD
n6
18
Merchant Type
n4
22
ans12
MO
32
Acquiring Institution
Identification Code
n11
37
Retrieval Reference
Number
an12
39
Response Code
An3
41
Card Acceptor
Terminal Identification
ans 8
43
ans136
Format
LLVAR
LLVAR
LLLVAR
SmartVista Front-End
Bit
No.
Format
Attributes
Status
48
Additional Data
LLLVAR
ans.. 999
49
Currency Code,
Transaction
n3
50
Currency Code,
Account
n3
51
Currency Code,
Cardholder Billing
n3
54
Additional Amounts
ans999
64
b8
91
Action Code
an 1
Must be present if
Transaction Code = 92
95
Replacement Amounts
LLLVAR
ans999
100
LLVAR
ans 4
102
Account Identification
LLVAR
Ans32
103
Account Identification2
LLVAR
ans32
128
b8
Attributes
Status
Comments / Remarks
Value is 1430
LLLVAR
Comments / Remarks
3.2. Response
Field Used
For Mac
Y or N
Bit
No.
Message Type
n4
b64
b64
Primary Account
Number
n24
Processing Code
n6
11
n6
37
Retrieval Reference
Number
an12
39
Response Code
An3
41
Card Acceptor
Terminal Identification
ans 8
Format
LLVAR
SmartVista Front-End
Bit
No.
Format
Attributes
Status
54
Additional Amounts
LLLVAR
ans.. 999
64
b8
Attributes
Status
Comments / Remarks
Value is 1600
4.
Comments / Remarks
Field Used
For Mac
Y or N
Y
N
Administrative Messages
4.1. Request
Field Used
For Mac
Y or N
Bit
No.
Message Type
n4
b64
Primary Account
Number
n24
11
n6
12
n12
41
Card Acceptor
Terminal Identification
ans 8
48
Additional Data
LLLVAR
ans.. 999
61
Additional Amounts
and Counters
LLLVAR
ans.. 999
64
b8
Attributes
Status
Comments / Remarks
Value is 1610
Format
LLVAR
YYMMDDhhmmss
4.2. Response
Field Used
For Mac
Y or N
Bit
No.
Message Type
n4
b64
Primary Account
Number
n24
11
n6
12
n12
Format
LLVAR
YYMMDDhhmmss
SmartVista Front-End
Bit
No.
Format
Attributes
Status
Comments / Remarks
Field Used
For Mac
Y or N
Transaction
39
Response Code
An3
41
Card Acceptor
Terminal Identification
ans 8
64
b8
5.
5.1. Request
Bit
No.
Attributes
Status
Comments / Remarks
Message Type
n4
Value is 1804
b64
11
n6
12
n12
24
Function Code
N3
Attributes
Status
Comments / Remarks
Value is 1814
Format
YYMMDDhhmmss
5.2. Response
Bit
No.
Message Type
n4
b64
11
n6
24
Function Code
N3
39
Response Code
An3
Format
SmartVista Front-End
MESSAGE MATCHING
1.
2.
Message Type.
Key fields in matching response with request are Primary Account Number (field 2), and System
Trace Audit Number (field 11). Appropriate request message type (1100/1120/1420) is used as
value for matching.
The 810 response matching fields are Message Type and System Trace Audit Number (field 11).
Appropriate request message type (0800) is used as value for matching.
SmartVista Front-End
Structure Field 48
Size
Data
LLL
Tag 001
LLL 3
2.
Tag 002
Tag No
Length
Data
NNN
NNN
Ans .. 993
3.
Tag N
NNN bytes
Tag No
Length
Data
001
n1
Settlement type:
1 US-ON-US
2 US-ON-THEM
Must be present in 1100/1120/1121/1420/1421/1600 messages.
4.
Tag No
Size
Data
002
n3
5.
Tag No
Size
Data
004
ans 40
Full Name.
Must be present in 1110 message for 684 SVFE transactions
type only.
SmartVista Front-End
6.
Tag No
Size
Data
005
n3
Credit Type.
Must be present in 1110 message for 684 SVFE transactions
type only.
7.
Tag No
Size
Data
006
N6
8.
Tag No
Size
Data
007
N6
9.
Tag No
Size
Data
008
N6
YYMMDD
Must be present in 1110 message for 684 SVFE transactions
type only.
Size
Data
009
N6
YYMMDD
Must be present in 1110 message for 684 SVFE transactions
type only.
SmartVista Front-End
Size
Data
010
Ans8
Service Identifier.
If available must be present in 1100/1120/1121 messages.
Size
Data
011
Ans 32
Service Data.
If available must be present in 1100/1120/1121 messages.
Size
Data
012
ans 28
Size
Data
013
ans 6
Contract ID.
If available must be present in 1100/1120/1121 messages.
Size
Data
014
Ans 30
Cardholder address
If available must be present in 1100 messages.
Size
Data
015
Ans 9
SmartVista Front-End
Size
Data
016
n3
Size
Data
017
Ans 99
Size
Data
018
n2
SmartVista Front-End
Size
Data
019
n4
Size
Data
020
ans ..25
Size
Data
021
ans ..99
Size
Data
022
ans ..32
SmartVista Front-End
Length
Data
023
an 1
Length
Data
024
ans ..255
Size
Data
090-099
ans ..25
SmartVista Front-End
Structure Field 54
Size
Data
LLL
Tag 001
LLL 3
2.
Tag 002
Tag No
Length
Data
NNN
NNN
Ans .. 99
3.
Tag N
NNN bytes
Tag No
Length
Data
001
N12
4.
Tag No
Length
Data
002
N12
SmartVista Front-End
5.
Tag No
Length
Data
003
N13
Transaction Currency.
Must be present in 1100/1420/1421 messages for 775, 705, 750,
703, 691, 692, 785 SVFE transactions type only.
For 703 SVFE transactions type it contains Account TO
Currency.
6.
Tag No
Length
Data
004
N12
7.
Tag No
Length
Data
005
n 12
8.
Tag No
Length
Data
006
an 16
SmartVista Front-End
9.
Tag No
Length
Data
007
an 16
Length
Data
008
an 12
Length
Data
009
an 12
SmartVista Front-End
Structure Field 61
Size
Data
LLL
Tag 001
LLL 3
2.
Tag 002
Tag No
Length
Data
NNN
NNN
Ans .. 99
3.
Tag N
NNN bytes
Tag No
Length
Data
001
n 15
or n 30
or n 45
or n 60
4.
n 12 - amount in cassette
Tag No
Length
Data
002
n 15
or n 30
or n 45
5.
n 12 - amount in cassette
Tag No
Length
Data
003
n 15
or n 30
or n 45
SmartVista Front-End
Structure Field 95
Size
Data
LLL
Tag 001
LLL 3
2.
Tag 002
Tag No
Length
Data
NNN
NNN
Ans .. 99
3.
Tag N
NNN bytes
Tag No
Length
Data
001
N12
4.
Tag No
Length
Data
002
N12
5.
Tag No
Length
Data
003
N12
6.
Tag No
Length
Data
006
N3
Transaction Currency
SmartVista Front-End
7.
Tag No
Length
Data
007
N3
Account Currency
8.
Tag No
Length
Data
008
N3
SmartVista Front-End
LIST OF REVISIONS
Date
Name, Surname
Modifications
2010-10-14
Grigoriev A.S.
2010-11-24
Grigoriev A.S.
2011-02-04
Sasin S.S.
2011-02-21
Ustinchenko A.G.
2011-05-25
Dudnikov V.M.
2011-05-27
Ustinchenko A.G.
2011-07-29
Dudnikov V.M.
Added tags 16, 17, 18 to field 48. Added field 91, Added
SVFE transaction types 493, 508, 510, 596, 603, 644, 672,
751, 753, 782, 797, 798, transaction codes 16, 91, 92, 93.
Added value 841 to field 24. Changed transaction code for
transaction types 585, 618. Removed transaction type 587.
2011-08-30
Sasin S.S.
2011-09-19
Kondrashin E.K.
10
2011-09-19
Sasin S.S.
11
2011-09-28
Dudnikov V.M.
12
2011-10-18
Ustinchenko A.G.
13
2011-11-03
Dudnikov V.M.
14
2011-12-16
Dudnikov V.M.
15
2011-12-27
Dudnikov V.M.
SmartVista Front-End