Smartvista CBS Specification

8/10/2019 Smartvista CBS Specification

http://slidepdf.com/reader/full/smartvista-cbs-specification 1/62

SMARTVISTA FRONT END

EXTERNAL INTERFACE SPECIFICATIONISO-8583 CORE BANKING SYSTEM (CBS)

28.03.2014 10:45:03

Copyright © 1999-2011 Banking Production Center



Banking Production Center

SmartVista Front-End ISO-8583 CBS INTERFACE2

Contents

OVERVIEW ....................................................................................................................................... 5

CBSCOMMUNICATION PROTOCOL ......................................................................................... 6

CBS ISO-8583 MESSAGE TYPES .................................................................................................. 7

1. Authorization Messages ............................................................................................................................................. 7 2. Reversal Messages ..................................................................................................................................................... 8 3. Administrative Messages .......................................................... ........................................................... ....................... 8 4. Network Management Messages ........................................................ ........................................................... ............. 8

CBS ISO – 8583 MESSAGE FLOWS .............................................................................................. 9

1. Authorization Messages ............................................................................................................................................. 9 2. Authorization Advice Messages ......................................................... ........................................................... ............. 9 3. Reversal Messages ..................................................................................................................................................... 9

3.1. Normal processing ............................................................................................................... 9

3.2. Time-out processing .......................................................................................................... 104. Administrative Messages .......................................................... ........................................................... ..................... 11 5. Network Management Messages ........................................................ ........................................................... ........... 11

5.1. Normal processing ............................................................................................................. 11

5.2. SAF List End processing ................................................................................................... 12

DATA FIELDS ................................................................................................................................. 14

1. Data Field Attributes ................................................................................................................................................ 14

2. Data Field Format ........................................................... ........................................................... ............................... 14 3. Data Field Presence Conditions................................................................................................................................ 15 4. Data Field Description ............................................................................................................................................. 15

4.1. Field 1: Secondary Bit-Map............................................................................................... 15

4.2. Field 2: Primary Account Number .................................................................................... 15

4.3. Field 3: Processing Code ................................................................................................... 16

4.4. Field 4: Amount, Transaction ............................................................................................ 18

4.5. Field 5: Amount, Account ................................................................................................. 18

4.6. Field 6: Amount, Cardholder Billing ................................................................................. 18

4.7. Field 9: Conversion Rate, Cardholder Billing ................................................................... 19

4.8. Field 10: Conversion Rate, Account ................................................................................. 19

4.9. Field 11: Systems Trace Audit Number ............................................................................ 194.10. Field 12: Time, Local Transaction .................................................................................... 20

4.11. Field 14: Date, Expiration ................................................................................................. 20

4.12. Field 15: Settlement Date .................................................................................................. 20

4.13. Field 18: Merchant Type ................................................................................................... 21

4.14. Field 22: Point of Service Date Code ................................................................................ 21

4.15. Field 24: Function Code .................................................................................................... 23

4.16. Field 32: Acquiring Institution Identification Code .......................................................... 23

4.17. Field 37: Retrieval Reference Number .............................................................................. 24

4.18. Field 38: Authorisation Identification Response ............................................................... 24

4.19. Field 39: Response Code ................................................................................................... 25

4.20. Field 41: Card Acceptor Terminal Identification .............................................................. 27





4.21. Field 43: Card Acceptor Name and Location .................................................................... 27

4.22. Field 48: Additional Data .................................................................................................. 28

4.23. Field 49: Currency Code, Transaction ............................................................................... 28

4.24. Field 50: Currency Code, Account .................................................................................... 28

4.25. Field 51: Currency Code, Cardholder Billing .................................................................... 294.26. Field 54: Additional Amounts ........................................................................................... 29

4.27. Field 61: Additional Amounts and Counters ..................................................................... 33

4.28. Field 62: Mini-statement data ............................................................................................ 34

4.29. Field 63: Account Balance ................................................................................................ 35

4.30. Field 64: Primary MAC Data ............................................................................................ 35

4.31. Field 91: Action Code ....................................................................................................... 35

4.32. Field 95: Replacement Amounts ....................................................................................... 36

4.33. Field 100: SVFE Issuer Institution Identifier .................................................................... 37

4.34. Field 102: Account Identification ...................................................................................... 37

4.35. Field 103: Account Identification – 2 ................................................................................ 374.36. Field 128: Secondary MAC Data ...................................................................................... 37

MESSAGE FORMATS ................................................................................................................... 40

1. Authorization Message ................................................... ........................................................... ............................... 40

1.1. Request .............................................................................................................................. 40

1.2. Response ............................................................................................................................ 412. Authorization Advice Messages ......................................................... ........................................................... ........... 42

2.1. Request .............................................................................................................................. 42

2.2. Response ............................................................................................................................ 443. Reversal Messages ................................................................................................................................................... 45

3.1. Request .............................................................................................................................. 453.2. Response ............................................................................................................................ 464. Administrative Messages .......................................................... ........................................................... ..................... 47

4.1. Request .............................................................................................................................. 47

4.2. Response ............................................................................................................................ 475. Network Management Messages ........................................................ ........................................................... ........... 48

5.1. Request .............................................................................................................................. 48

5.2. Response ............................................................................................................................ 48

MESSAGE MATCHING ................................................................................................................ 49

1. Message Matching Data Fields................................................................................................................................. 49 2. Search of original request for responses ....................................................... ........................................................... . 49

APPENDIX A (FIELD 48) .............................................................................................................. 50

1. Structure Field 48 ..................................................................................................................................................... 50 2. Structure Tags of Data Field 48 ............................................................................................................................... 50 3. Tag 001 –Settlement type ......................................................... ........................................................... ..................... 50 4. Tag 002 – SVFE Transaction Type .......................................................................................................................... 50 5. Tag 004 – Full Name ...................................................... ........................................................... ............................... 50 6. Tag 005 – Credit Type ............................................................................................................................................. 51 7. Tag 006 – Credit Issue Date ..................................................................................................................................... 51 8. Tag 007 – Credit Issue Interval ................................................................................................................................ 51 9. Tag 008 – Credit End Date ....................................................... ........................................................... ..................... 51 10. Tag 009 – Credit Enable Date .................................................. ........................................................... ..................... 51

11. Tag 010 – Service Identifier ..................................................................................................................................... 52 12. Tag 011 – Service Data ............................................................................................................................................ 52





13. Tag 012 – Prepaid Card Type .................................................................................................................................. 52 14. Tag 013 – Contract ID .................................................... ........................................................... ............................... 52 15. Tag 014 – Address Verification Data ........................................................... ........................................................... . 52 16. Tag 015 – Postal Code Data ..................................................................................................................................... 52 17. Tag 016 – Installment Payment Quantity ...................................................................................................... ........... 53 18. Tag 017 – Text Information Data ....................................................... ........................................................... ........... 53 19. Tag 018 – Card status ..................................................... ........................................................... ............................... 53 20. Tag 019 – Account status ......................................................................................................................................... 54 21. Tag 020 – External code for operation ......................................................... ........................................................... . 54 22. Tag 021 – Customer external account number ....................................................... .................................................. 54 23. Tag 022 – Customer mobile phone number ............................................................................................................. 54 24. Tag 023 – Account Type .......................................................................................................................................... 55 25. Tag 090-099 – Payment specific data ...................................................................................................................... 55

APPENDIX B (FIELD 54)............................................................................................................... 56

1. Structure Field 54 ..................................................................................................................................................... 56 2. Structure Tags of Data Field 54 ............................................................................................................................... 56

3. Tag 001 – Acquirer Fee Amount ........................................................ ........................................................... ........... 56 4. Tag 002 – Transaction Amount, Transaction Currency........................................................................................... . 56 5. Tag 003 – Transaction Currency .............................................................................................................................. 57 6. Tag 004 – Amount, Credit Initial ............................................................................................................................. 57 7. Tag 005 – Amount, Total Credit .............................................................................................................................. 57 8. Tag 006 – Issuer Fee Amount and Currency .......................................................... .................................................. 57 9. Tag 007 – Current Account Available Balance and Currency ................................................... ............................... 58 10. Tag 008 – Amount, Exceed Limit ............................................................................. Error! Bookmark not defined. 11. Tag 009 – Amount, Available Exceed Limit .......................................................... .................................................. 58

APPENDIX C (FIELD 61) .............................................................................................................. 59

1. Structure Field 61 ..................................................................................................................................................... 59

2. Structure Tags of Data Field 61 ............................................................................................................................... 59 3. Tag 001 – Cash-In Counters ..................................................... ........................................................... ..................... 59 4. Tag 002 – Recycling Counters ................................................................................................................................. 59 5. Tag 003 – Recycling Cash-Out Counters ..................................................... ........................................................... . 59

APPENDIX D (FIELD 95) .............................................................................................................. 60

1. Structure Field 95 ..................................................................................................................................................... 60 2. Structure Tags of Data Field 95 ............................................................................................................................... 60 3. Tag 001 – Transaction Amount, Transaction Currency........................................................................................... . 60 4. Tag 002 – Transaction Amount, Account Currency ......................................................... ........................................ 60 5. Tag 003 – Transaction Amount, Cardholder Billing Currency ................................................................................ 60 6. Tag 006 – Transaction Currency .............................................................................................................................. 60 7. Tag 007 – Account Currency ................................................................................................................................... 61 8. Tag 008 – Cardholder Billing Currency ....................................................... ........................................................... . 61

LIST OF REVISIONS ..................................................................................................................... 62





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.





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 sentin 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 N bytes

Message Length = N ISO – 8583 Message





CBS ISO-8583 MESSAGE TYPES

Message Class: Authorization1100 Authorization Request

1110 Authorization Response

1120 Authorization Advice

1130 Authorization Advice Response

Message Class: Reversal

1420 Reversal Advice

1430 Reversal Advice Response

Message Class: Administrative1600 Administrative Request

1610 Administrative Response

Message Class: Network Management

1804 Network Management Request

1814 Network Management Response

1. Authorization Messages

1100 – Authorization Request

Message Type: 1100

Description: Authorization Request (1100) message requests approval authorization or guarantee

for the transaction to proceed. Authorization Response (1110) is expected in return for 1100

message, either approving or denying the request.

1110 – Authorization Response

Message Type: 1110

Description: Authorization Request Response (1110) is returned in response to Authorization

Request (1100) to approve or deny the request.

1120 – Authorization Advice

Message Type: 1120

Description: Authorization Advice (1120) advises CBS of a previously completed at SVFE (Stand-

In processing) transaction. Format and contents of fields at 1120 message are the same as at 1100

message. Each 1120 message must be acknowledged with 1130 message.

1130 – Authorization Advice Response

Message Type: 1130

Description: Authorization Advice Response (1130) is used to acknowledge the receipt of

1120 message. Format and contents of fields at 1130 message are the same as at 1110 message.





2. Reversal Messages

1420 – Reversal Advice Request

Message Type: 1420Description: Reversal Advice Request (1420) is advice to cancel part or all of a previously

approved transaction. Reversal Advice Response (1430) is expected in return for 1420 message,

either approving the request.

1421 – Reversal Advice Repeat

Message Type: 1421

Description: Authorization Request Repeat (1421) is identical to 1420 message, except that

it denotes to the receiver that it is a possible duplicate message. Format and contents of fields at

1421message are the same as at 1420 message. This message is used when an

expected acknowledgement to 1420 message was not received.

1430 – Reversal Response

Message Type: 1430

Description: Reversal Response (1430) is used to acknowledge the receipt of 1420 message.

3. Administrative Messages

1600 – Administrative Request

Message Type: 1600

Description: Administrative Request (1600) is used to Reset ATM Counters. Administrative

Response (1610) is expected in return for 1600 message, either approving or denying the request.

1610- Administrative Response

Message Type: 1610

Description: Administrative Transaction Response (1610) is used to acknowledge the receipt of

1600

4. Network Management Messages1804 – Network Management Request

Message Type: 1804

Description: Network Management Request (1804) message is used to perform echo tests.

1804 message always requires 1814 message in response.

1814 – Network Management Response

Message Type: 1814

Description: Network Management Response (1814) message is returned in response to Network

Management Request (1804) message.





CBS ISO – 8583 MESSAGE FLOWS

1. Authorization Messages

sd Auth

SVFE CBS

1100()

1110()

2. Authorization Advice Messages

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 Advice

SVFE CBS

1120()

1130()

1121()

1130()


3.1. Normal processing





SVFE sends 1420/1421 messages in case a request for authorization cancellation has been received

from terminal devices and payment networks, or in case of authorization cancellation in SVFE

system in stand-in mode.

Message 1420 is sent 5 seconds after sending the message 1100, for which there was no response.

Message 1421 is sent 60 seconds after sending the message 142X, for which there was no response.

Message 1421 is sent not more than three times. If after sending the last message 1421 there was

still no response, the authorization request, for which there was no response, is considered to be

processed in stand-in mode.

sd Reversal

SVFE CBS

1420()

1430()

1421()

1430()

3.2. Time-out processing

SVFE sends 1420/1421 messages in case the SVFE does not receive a response to 1100 message.

Message 1421 is sent in case the response to message 1420 is not received.





sd Reversal

SVFE CBS

1420()

1430()

1420()

1430()

1421()

1430()

4. Administrative Messagessd Administrative

SVFE CBS

1600()

1610()

5. Network Management Messages

5.1. Normal processing

The SVFE system periodically sends a message 1804 with a query of type 831 – “Test of

connection”. A repeated message 1804 is sent 60 seconds after sending the message 1804, for which

there was no response. In case there is no response to message 1804, the message 1804 is repeated

not more than three times.

If after the last message 1804 there was no response, or if there was a response message 1814 with

response code other than “000”, the SVFE system will send to CBS a message 1804 of query type

802 – “Sign Off” and starts to process authorization requests in stand-in mode.





sd Network Management SV-CBS

SVFE CBS

1804()

1804()

1814()

sd Network Management CBS-SV

SVFECBS

1804()

1804()

1814()

5.2. SAF List End processing

SAF List End message is used when required notification of CBS about finishing of the Stand-In

processed transactions.

In case of logical connection between SVFE and CBS lost SVFE could process transaction in Stand-

In mode. After the connection is established the SVFE upload all transactions as advices. When all

transactions are uploaded SVFE sends SAF List End message to inform CBS all the transactionswere uploaded.





sd SAF List End

SVFECBS

Connection LostConnection Lost

Stand-In processing()

Stand-In processing()

1804(Test of connection)

1814()

1804(Sign-On)

1814()

1120()

1130()

1120()

1130(Last transaction )

1804(SAF List End)

1814()





DATA FIELDS

1. Data Field Attributes

Table 1. Data Field Attributes

a Alphabetic characters only.

N Numeric digits only.

S 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.

4 Fixed length of 4 characters.

…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

b Binary representation of data.

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

x “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. Data Field Format

Table 2. Data Field Format

MM Month

DD Day

YY Year

hh Hour

mm Minute

SS Second





LL 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 Variable length data field.

3. Data Field Presence Conditions

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. Data Field Description

4.1. Field 1: Secondary Bit-Map

4.1.1. Format

Bit-Map

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. Field 2: Primary Account Number

4.2.1. Format

llvar n.. 24

4.2.2. Description

This field contains the cardholder’s card number.





This field is also used to match a response message with its original message.

4.3. Field 3: Processing Code

4.3.1. Format

n 6

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

SVFE Transaction

Type

TRANSACTION

DESCRIPTION

00 774 POS Purchase /P2P Debit/Utility Payment

00 680 E-POS Purchase

01 700 ATM Cash withdrawal

01 777 POS Cash Advance

03 740 Check guarantee transaction

11 781 P2P Debit

16 596 Installment Purchase

17 612 BN Bill Payment

17 670 Manual Cash withdrawal

17 659 Debit account with presentment

18 736 POS Pre-authorisation

18 677 E-POS Pre-authorisation

18 671 Manual Purchase

19 737 POS Completion

19 678 E-POS Completion

20 775 POS Return or Refund

20 681 E-POS Return or Refund

20 669 Manual Refund Completion

21 585 Cash Deposit Account

21 618 ATM Cash Deposit

21 705 Deposit

21 712 POS Cash Deposit

21 711 E-POS Cash Deposit

22 750 Credit Adjustment

26 570 Service Reimbursement

27 760 Credit account with presentment

28 698 Credit Payment





Transaction

Code

SVFE Transaction

Type

TRANSACTION

DESCRIPTION

29 785 P2P Credit

31 702 Balance Inquiry

31 784 POS Balance Inquiry

31 757 Balance Inquiry on Screen

31 676 E-POS Balance Inquiry

37 684 Advanced Repayment Information

38 796 Account Verification

39 704 Mini-Statement

40 703 Funds Transfer

44 613 ATM BN IBFT

50 530 Transfer to external account

50 692 Transfer to foreign account50 508 Utility Payment

50 510 Predefined Payment

50 893 Predefined Service Payment

51 588 Full Advanced Repayment

52 471 Prepaid Card

58 707 Payment from Envelope

91 493 Block Card

91 644 Activate Card

91 672 Change Card Status

91 782 Validate Card92 797 Service On

92 798 Service Off

93 603 Forced PIN Change

93 751 PIN Change

93 753 New PIN Reentry

94 474 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 .


ACCOUNT TYPE ACCOUNT DESCRIPTION

0X Default (unspecified) account

1X Savings account

2X Checking account

3X Credit account

4X Others Account

5X Loans Account

6X Envelope Account

7X Escrow Account





ACCOUNT TYPE ACCOUNT DESCRIPTION

8X Money Market Account

9X Loyalty Account

The second byte in each pair (i.e. byte 4 and 6) indicates an order of account that is used intransaction in the list of card accounts with the same type. Valid values are 0-8.

4.4. Field 4: Amount, Transaction

4.4.1. Format

n 12

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. Field 5: Amount, Account

4.5.1. Format

n 12

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. Field 6: Amount, Cardholder Billing

4.6.1. Format

n 12

4.6.2. Description





This field contains the transaction amount (Field 4), converted to the currency used to bill the

cardholder’s account. The conversion rate is in Field 10. No decimal point appears in this field; the

decimal place is implied based on the currency. If it is present, the following fields are also

required: “Field 10: Conversion Rate, Cardholder Billing”.

4.7. Field 9: Conversion Rate, Cardholder Billing

4.7.1. Format

n 8

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 2–8 of the field are the actual rate.

For example: 69985022 = 9.985022.

4.8. Field 10: Conversion Rate, Account

4.8.1. Format

n 8

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 2–8 of the

field are the actual rate.

For example: 69985022 = 9.985022.

4.9. Field 11: Systems Trace Audit Number

4.9.1. Format

n 6





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.


4.10. Field 12: Time, Local Transaction

4.10.1.Format

n 12

YYMMDDhhmmss

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.


4.11. Field 14: Date, Expiration

4.11.1.Format

n 4

YYMM

4.11.2.Description

The year and month that the card will become expired.

4.12. Field 15: Settlement Date

4.12.1.Format

n 6

YYMMDD

4.12.2.Description





Field contains the SmartVista Front-End Acquirer settlement date.

4.13. Field 18: Merchant Type

4.13.1.Format

n 4

4.13.2.Description

A code describing the merchant’s type of business product or service. See ISO-8583 standard

documentation for the list of valid categories.

4.14. Field 22: Point of Service Date Code

4.14.1.Format

ans 12

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.


Position Position Description Valid Values1 Card data input

capability0 – Unknown1 – Manual2 – Magnetic stripe reader3 – Bar code reader

4 – OCR reader – !M" co#patible $CC reader% – &ey entry' – Magnetic stripe reader and key entry( – Magnetic stripe reader) key entry and

!M" co#patible $CC reader *+, – Contactless read

2Card-olderaut-enticationcapability

0 – .o electronic aut-entication1 – /$.2 – !lectronic signature analysis3 – Bio#etrics4 – Biograp-ic

– !lectronic aut-entication% – Ot-er





Position Position Description Valid Values

3 Card capturecapability

0 – .one1 – Capture

4 Operatingeniron#ent

0 – no ter#inal used1 – on pre#ises o card acceptor) attended2 – on pre#ises o card acceptor) untended3 – O pre#ises o card acceptor) attended4 – O pre#ises o card acceptor) unattended – On pre#ises o card card-older) unattended, – On pre#ises o card card-older) attended

Card-older presenceindicator

0 – /resent1 – .ot present) unspeciied2 – .ot present) #ail order3 – .ot present) telep-one order4 – .ot present) standing order recurring pay#ent

– .ot present) electronic order – .ot present) postponed pay#ent

% Card presence0 – .ot present1 – /resent

' Card data input #ode0 – Unspeciied1 – Manual) no ter#inal2 – Magnetic stripe read3 – B5R read4 – OCR read – $CC read% – &ey entered' – Contactless $CC read

( – Contactless #agnetic stripe read, – Contactless read – !6co##erce) #erc-ant certiicate only7 – !6co##erce) #erc-ant and card-older certiicate + 368 ecuretransactionU – !6co##erce) no security" – !6co##erce) c-annel encryption

( Card-olderaut-entication #et-od

0 – .o aut-entication1 – /$.2 – !lectronic signature analysis3 – Bio#etrics4 – Biograp-ic

– Manual signature% – Ot-er #anual aut-entication7 – !6co##erce) UC59 + 38 aut-entication is not supported by#erc-antU – !6co##erce) UC59 + 38 aut-entication is supported by#erc-ant but is not proided by issuer" – !6co##erce) UC59 + 38 aut-entication is supported by#erc-ant and is proided by issuer

, Card-olderaut-entication entity

0 – .ot aut-enticated1 – $CC3 – 5ut-ori:ing agent) online /$.4 – Merc-ant+card acceptor) signature

– Ot-er – Merc-ant suspicious





Position Position Description Valid Values

10 Card data outputcapability

0 – Unknown1 – .one2 – Magnetic stripe write

3 – $CC

11 7er#inal outputcapability

0 – Unknown1 – .one2 – /rinting capability only3 – 8isplay capability only4 – /rinting and display capability

12 /$. capture capability0 – .o /$. capture capability1 – Unknown4 – /$. capture capability 4 c-aracters #a;i#u# – /$. capture capability c-aracters #a;i#u#% – /$. capture capability % c-aracters #a;i#u#' – /$. capture capability ' c-aracters #a;i#u#

( – /$. capture capability ( c-aracters #a;i#u#, – /$. capture capability , c-aracters #a;i#u#5 – /$. capture capability 10 c-aracters #a;i#u#B – /$. capture capability 11 c-aracters #a;i#u#C – /$. capture capability 12 c-aracters #a;i#u#

4.15. Field 24: Function Code

4.15.1.Format

n 3

4.15.2.Description

Code indicating the specific purpose of the message within its message class.


FUNCTION

CODE

DESCRIPTION MESSAGE

TYPE

801 Sign-On 1804802 Sign-Off 1804

831 Echo-test 1804

841 SAF list end 1804

4.16. Field 32: Acquiring Institution Identification Code

4.16.1.Format

llvar n.. 11





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, aMasterCard 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. Field 37: Retrieval Reference Number

4.17.1.Format

an 12

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. Field 38: Authorisation Identification Response

4.18.1.Format

ans 6

4.18.2.Description

An authorization code provided by the CBS when a transaction is approved, or a no-reason-to-decline 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]={





"123456789",

"0123456789ABCEFHKMNRSTUVWXYZ",


"0123456789",


"0123456789ABCEFHKMNRSTUVWXYZ"

};

void auth(long u, char *a) {

int i,l;

for (i=0; i<6; i++) {

l=strlen(voc[i]);

a[i]=voc[i][u%l];

u/=l;

}}

4.19. Field 39: Response Code

4.19.1.Format

an 3

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 Currency of the account in CBS is not the same as currency of account

in FRONT END






928 112 Account is blocked

915 116 Not enough money on account

913 124 Account not found

- 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 Incorrect type of request of code of transaction

802 907 CBS is not available

959 909 Internal errors in the interface software

802 910 CBS is in "log off" state

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 Errors in software of CBS

894 894 Operation could not be processed because of temporary moratorium

(TIME_MORATORIUM)

895 895 Absense of information about debt

(DEBTS_ABSENCE)

1 Response codes 4XX are sent by SVFE in 142X messages






997 997 The customer doesn't have the service of advance repayment of debt

(SERVICE_NOT_ALLOWED)

4.20. Field 41: Card Acceptor Terminal Identification

4.20.1.Format

ans 8

4.20.2.Description

A code that uniquely identifies a particular terminal at the card acceptor’s 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. Field 43: Card Acceptor Name and Location

4.21.1.Format

ans 40

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 dataData dictionary

1 ans 38 • Merchant number of bank name;• Separator ‘>’

• Merchant city or location of the terminal device

• Trailing spaces

2 ans 2 ISO code of the country





4.22. Field 48: Additional Data

4.22.1.Format

lllvar ans …999

Tag data format: 3 bytes for each tag name + 3 bytes for each tag length + tag data

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. Field 49: Currency Code, Transaction

4.23.1.Format

n 3

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. Field 50: Currency Code, Account

4.24.1.Format

n 3

4.24.2.Description





This code specifies the cardholder account currency.

4.25. Field 51: Currency Code, Cardholder Billing

4.25.1.Format

n 3

4.25.2.Description

This field contains a 3-digit numeric code that identifies the currency used by the issuer to bill the

cardholder’s account.

4.26. Field 54: Additional Amounts

4.26.1.Format

lllvar an…999

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.





5. Refer to Tag 011 – Service DataTag No Size Data

011 Ans… 32 Service Data.

If available must be present in 1100/1120/1121 messages.





6. Tag 012 – Prepaid Card Type

Tag No Size Data

012 ans 28 Prepaid Card Type

Must be present for 471 SVFE transaction type only.

7. Tag 013 – Contract ID

Tag No Size Data

013 ans 6 Contract ID.


8. Tag 014 – Address Verification Data

Tag No Size Data

014 Ans… 30 Cardholder address

If available must be present in 1100 messages.

9. Tag 015 – Postal Code Data

Tag No Size Data

015 Ans… 9 Cardholder postal/ZIP code


10. Tag 016 – Installment Payment Quantity

Tag No Size Data

016 n…3 Quantity of payments for Installment purchase

Must be present in 1100 messages if Transaction Code = 16.

11. Tag 017 – Text Information Data

Tag No Size Data

017 Ans… 99 Free form text data

Optional for 1110 messages





12. Tag 018 – Card status

Tag No Size Data

018 n…2 SVFE Card status:

0 – valid card

1 – call issuer

2 – warm card

3 – do not honor

4 – honor with id

5 – not permitted

6 – lost card, capture

7 – stolen card, capture

8 – call security, capture

9 – invalid card, capture

10 – pick up card, special condition

11 – call acquirer security

12 – card is not activated

13 – pin_attempts_exceeded

14 – forced pin change

15 – credit debts

17 – pin activation

18 – instant card personification waiting

19 – fraud prevention

20 – temprory blocked by client

21 – permanent blocked by client


13. Tag 019 – Account status

Tag No Size Data

019 n…4 New account status:

0 – No restrictions

1 – No withdrawals

2 – No withdrawals or transfers

3 – Only balance inquiries

4 – Only deposits

5 – Only balance inquiries and deposits6 – Only balance inquiries, deposits and transfers

7 – No operations allowed (account blocked)


14. Tag 020 – External code for operation

Tag No Size Data

020 ans ..25 External code for some service.






15. Tag 021 – Customer external account number

Tag No Size Data

021 ans ..99 External account number in service provider system.


16. Tag 022 – Customer mobile phone number

Tag No Size Data

022 ans ..32 Mobile phone number for mobile top-up services.


17. Tag 023 – Account Funds Type

Tag No Length Data

023 an 1 Account Funds Type:

Available value:

0 – Debit.

1 – Debit with overdraft.

2 – Credit.

Could be present in 1110 messages.

18. Tag 024 – Additional operation information

Tag No Length Data

024 ans ..255 Additional operation information

Free form text


19. Tag 090-099 – Payment specific data

Tag No Size Data

090-099 ans ..25 Specific data for payment services.






Appendix B (Field 54).

19.1. Field 61: Additional Amounts and Counters

19.1.1.Format

lllvar an…999

19.1.2.Description

This field is used to carry SmartVista Front-End account balance information. There is a number oftags packed in Field 61. The tags have the TLV structure. It means they are repeated groups of Tag IDs,

Tag Lengths and Tag Values.





20. Refer to Tag 008 – Amount, Installed Exceed Limit

Tag No Length Data

008 an 12 Exceed Limit. This amount used to show overdraft or credit limit

value assigned to card account.

Could be present in 1110 messages and contains Installed credit

limit for credit or debit with overdraft account.

21. Tag 009 – Amount, Available Exceed Limit

Tag No Length Data

009 an 12 Available Exceed Limit. This amount used to show available

overdraft or credit limit value assigned to card account.

Could be present in 1110 messages and contains Available credit






Appendix C (Field 61).

21.1. Field 62: Mini-statement data

21.1.1.Format

lllvar an…220

21.1.2.Description

Field contains mini-statement data, only for 704 SVFE Transaction Type, up to 10 sets:

N Description Attributes Comments

1 Transaction Date n 6 YYMMDD

2 Transaction Mnemonic Name ans 3 Transaction Mnemonic Name

3 Debit Credit Indicator A 1 “C” – credit transaction,

“D“ – debit transaction

“ ” – noop transaction

4 Amount Transaction N 12





21.2. Field 63: Account Balance

21.2.1.Format

n 12

21.2.2.Description

Account balance.

21.3. Field 64: Primary MAC Data

21.3.1.Format

b 8

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 atlast 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. Field 91: Action Code

21.4.1.Format

an 1

21.4.2.Description

This field is used to indicate type of operation. See table bellow.

Value Description

1 Add operation





Value Description

3 Delete operation

21.5. Field 95: Replacement Amounts

21.5.1.Format

lllvar an…999

21.5.2.Description

This field is used to carry SmartVista Front-End amount information. There is a number of tags packedin Field 95. The tags have the TLV structure. It means they are repeated groups of Tag IDs, Tag Lengths

and Tag Values.





22. Refer to Tag 003 – Recycling Cash-Out Counters

Tag No Length Data

003 n 15

or n 30

or n 45

Cash-out counters at each active cassette (from 1 to 3) in format:

n 3 – currency of cassette

n 12 - cash-out amount from cassette





Appendix D (Field 95).

22.1. Field 100: SVFE Issuer Institution Identifier

22.1.1.Format

LLVAR ans… 4

22.1.2.Description

Field contains SVFE Issuer Institution Identifier.

22.2. Field 102: Account Identification

22.2.1.Format

llvar ans.. 32

22.2.2.Description

Field is used in cardholder transactions. Field identifies an account number of cardholderrelationship.

22.3. Field 103: Account Identification – 2

22.3.1.Format

llvar ans.. 32

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. Field 128: Secondary MAC Data

22.4.1.Format

b 8





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 an…999

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.





23. Refer to Tag 008 – Amount, Installed Exceed Limit

Tag No Length Data






Tag No Length Data

009 an 12 Available Exceed Limit. This amount used to show availableoverdraft or credit limit value assigned to card account.







Appendix C (Field 61).

24.1. Field 62: Mini-statement data

24.1.1.Format

lllvar an…220

24.1.2.Description

Field contains mini-statement data, only for 704 SVFE Transaction Type, up to 10 sets:

N Description Attributes Comments

1 Transaction Date n 6 YYMMDD

2 Transaction Mnemonic Name ans 3 Transaction Mnemonic Name

3 Debit Credit Indicator A 1 “C” – credit transaction,

“D“ – debit transaction

“ ” – noop transaction

4 Amount Transaction N 12

24.2. Field 63: Account Balance

24.2.1.Format

n 12

24.2.2.Description

Account balance.

.





MESSAGE FORMATS

1. Authorization Message

1.1. Request

Bit

No.Data field Name Format

Attri-

butes

Sta-

tusComments / Remarks

Field Used

For Mac

Y or N

- Message Type n4 M Value is 1100 N

- Bit Map, Primary b64 M N

- Bit Map, Secondary b64 M N

2 Primary Account

Number

LLVAR n…24 M Y

3 Processing Code n6 M Y

4 Amount, Transaction n12 M Y

5 Amount, Account n12 M Y

6 Amount, Cardholder

Billing

n12 M Y

9 Conversion Rate,

Cardholder Billing

n8 M Y

10 Conversion Rate,

Account

n8 M Y

11 Systems Trace Audit

Number

n6 M Y

12 Date & Time, Local

Transaction

YYMMDDhhmmss n12 M Y

14 Date, Expiration YYMM n4 M Y

15 Settlement Date YYMMDD n6 M Y

18 Merchant Type n4 C Y

22 Point of Service Date

Code

ans12 MO Y

32 Acquiring Institution

Identification Code

LLVAR n…11 M Y

37 Retrieval Reference

Number

an12 M Y

41 Card AcceptorTerminal Identification

ans 8 M Y





Bit


Attri-

butes

Sta-


Field Used

For Mac

Y or N

43 Card Acceptor Name

and Location

LLLVAR ans…136 M Y

48 Additional Data LLLVAR ans.. 999 C Y

49 Currency Code,

Transaction

n3 M Y

50 Currency Code,

Account

n3 M Y

51 Currency Code,

Cardholder Billing

n3 M Y

54 Additional Amounts LLLVAR ans.. 999 C Y

64 Primary MAC Data b8 O For future used N

91 Action Code an 1 C Must be present if

Transaction Code = 92

Y

100 SVFE Issuer Institution

Identifier

LLVAR ans… 4 M Y

102 Account Identification LLVAR ans…32 M Y

103 Account Identification-

2

LLVAR ans…32 C Y

128 Secondary MAC Data b8 O For future used N

1.2. Response

Bit


Attri-

butes

Sta-


Field Used

For Mac

Y or N




2 Primary Account

Number

LLVAR n…24 M Y


4 Amount, Transaction n12 C Y



Number

n6 M Y

37 Retrieval Reference an12 C Y





Bit


Attri-

butes

Sta-


Field Used

For Mac

Y or N

Number

38 Authorisation

Identification Response

ans6 C Y

39 Response Code An3 M Y

41 Card Acceptor

Terminal Identification

ans 8 M Y


50 Currency Code,

Account

n3 C Y


62 Mini-statement data LLLVAR ans…220 C Y

63 Account Balance n 12 C Y


102 Account Identification LLVAR ans…32 C Y


2. Authorization Advice Messages

2.1. Request

Bit


Attri-

butes

Sta-


Field Used

For Mac

Y or N




2 Primary Account

Number

LLVAR n…24 M Y





Billing

n12 M Y

9 Conversion Rate,Cardholder Billing n8 M Y





Bit


Attri-

butes

Sta-


Field Used

For Mac

Y or N

10 Conversion Rate,

Account

n8 M Y


Number

n6 M Y


Transaction




18 Merchant Type n4 C Y

22 Point of Service DateCode

ans12 MO Y


Identification Code

LLVAR n…11 M Y


Number

an12 M Y

38 Authorisation

Identification Response

ans6 M Y


41 Card Acceptor


ans 8 M Y

43 Card Acceptor Name

and Location

LLLVAR ans…136 M Y


49 Currency Code,

Transaction

n3 M Y

50 Currency Code,

Account

n3 M Y

51 Currency Code,

Cardholder Billing

n3 M Y


91 Action Code an 1 C Must be present if

Transaction Code = 92

Y


Identifier

LLVAR ans… 4 M Y

102 Account Identification LLVAR ans…32 M Y


2

LLVAR ans…32 C Y





Bit


Attri-

butes

Sta-


Field Used

For Mac

Y or N


2.2. Response

Bit


Attri-

butes

Sta-


Field Used

For Mac

Y or N




2 Primary Account

Number

LLVAR n…24 M Y



Number

n6 M Y


Number

an12 C Y



ans 8 M Y


50 Currency Code,

Account

n3 C Y


63 Account Balance n 12 C Y


102 Account Identification LLVAR ans…32 C Y







3.1. Request

Bit


Attri-

butes

Sta-


Field Used

For Mac

Y or N




2 Primary Account

Number

LLVAR n…24 M Y





Billing

n12 M Y

9 Conversion Rate,

Cardholder Billing

n8 M Y

10 Conversion Rate,

Account

n8 M Y


Number

n6 M Y


Transaction




18 Merchant Type n4 M Y

22 Point of Service DateCode

ans12 MO Y


Identification Code

LLVAR n…11 M Y


Number

an12 M Y


41 Card Acceptor


ans 8 M Y

43 Card Acceptor Nameand Location

LLLVAR ans…136 O Y





Bit


Attri-

butes

Sta-


Field Used

For Mac

Y or N

48 Additional Data LLLVAR ans.. 999 M Y

49 Currency Code,

Transaction

n3 M Y

50 Currency Code,

Account

n3 C Y

51 Currency Code,

Cardholder Billing

n3 C Y

54 Additional Amounts LLLVAR ans…999 C Y


91 Action Code an 1 C Must be present ifTransaction Code = 92

Y

95 Replacement Amounts LLLVAR ans…999 C Y


Identifier

LLVAR ans… 4 M Y

102 Account Identification LLVAR Ans…32 C Y


2

LLVAR ans…32 C Y


3.2. Response

Bit


Attri-

butes

Sta-


Field Used

For Mac

Y or N




2 Primary Account

Number

LLVAR n…24 M Y



Number

n6 M Y


Number

an12 M Y



ans 8 M Y





Bit


Attri-

butes

Sta-


Field Used

For Mac

Y or N



4. Administrative Messages

4.1. Request

Bit


Attri-

butes

Sta-


Field Used

For Mac

Y or N



2 Primary Account

Number

LLVAR n…24 M Y


Number

n6 M Y


Transaction


41 Card Acceptor


ans 8 M Y


61 Additional Amounts

and Counters

LLLVAR ans.. 999 M Y


4.2. Response

Bit


Attri-

butes

Sta-


Field Used

For Mac

Y or N



2 Primary Account

Number

LLVAR n…24 M Y


Number

n6 M Y

12 Date & Time, Local YYMMDDhhmmss n12 M Y





Bit


Attri-

butes

Sta-


Field Used

For Mac

Y or N

Transaction


41 Card Acceptor


ans 8 M Y


5. Network Management Messages

5.1. RequestBit


Attri-

butes

Sta-


- Message Type n4 M Value is 1804

- Bit Map, Primary b64 M


Number

n6 M


Transaction

YYMMDDhhmmss n12 M

24 Function Code N3 M

5.2. Response

Bit


Attri-

butes

Sta-


- Message Type n4 M Value is 1814

- Bit Map, Primary b64 M

11 Systems Trace AuditNumber

n6 M

24 Function Code N3 M

39 Response Code An3 M





MESSAGE MATCHING

1. Message Matching Data Fields

Following set of fields takes part in message matching:

• Field 2. Primary Account Number;

• Field 11. Systems Trace Audit Number;

• Message Type.

2. Search of original request for responses

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.





APPENDIX A (FIELD 48)

1. Structure Field 48

Size Data

LLL Tag 001 Tag 002 … Tag N

3 LLL – 3

2. Structure Tags of Data Field 48

Tag No Length Data

NNN NNN Ans .. 993

3 3 NNN bytes

3. Tag 001 –Settlement type

Tag No Length Data

001 n 1 Settlement type:

1 – US-ON-US

2 – US-ON-THEM

Must be present in 1100/1120/1121/1420/1421/1600 messages.

4. Tag 002 – SVFE Transaction Type

Tag No Size Data

002 n 3 SVFE Transaction Type, refer to Field 3: Processing Code.

Must be present in 1100/1120/1121/1420/1421/1600 messages.

For 1600 message the value is 594.

5. Tag 004 – Full Name

Tag No Size Data

004 ans 40 Full Name.

Must be present in 1110 message for 684 SVFE transactions

type only.





6. Tag 005 – Credit Type

Tag No Size Data

005 n 3 Credit Type.


type only.

7. Tag 006 – Credit Issue Date

Tag No Size Data

006 N6 Credit Issue Date.

Format: YYMMDD


type only.

8. Tag 007 – Credit Issue Interval

Tag No Size Data

007 N6 Credit Issue Interval.

YYMMDD


type only.

9. Tag 008 – Credit End Date

Tag No Size Data

008 N6 YYMMDD


type only.

10. Tag 009 – Credit Enable Date

Tag No Size Data

009 N6 YYMMDD


type only.





11. Tag 010 – Service Identifier

Tag No Size Data

010 Ans…8 Service Identifier.


12. Tag 011 – Service Data

Tag No Size Data

011 Ans… 32 Service Data.


13. Tag 012 – Prepaid Card Type

Tag No Size Data

012 ans 28 Prepaid Card Type

Must be present for 471 SVFE transaction type only.

14. Tag 013 – Contract ID

Tag No Size Data

013 ans 6 Contract ID.


15. Tag 014 – Address Verification Data

Tag No Size Data

014 Ans… 30 Cardholder address


16. Tag 015 – Postal Code Data

Tag No Size Data

015 Ans… 9 Cardholder postal/ZIP code






17. Tag 016 – Installment Payment Quantity

Tag No Size Data

016 n…3 Quantity of payments for Installment purchase


18. Tag 017 – Text Information Data

Tag No Size Data

017 Ans… 99 Free form text data

Optional for 1110 messages

19. Tag 018 – Card status

Tag No Size Data

018 n…2 SVFE Card status:

0 – valid card

1 – call issuer

2 – warm card

3 – do not honor

4 – honor with id

5 – not permitted6 – lost card, capture

7 – stolen card, capture

8 – call security, capture

9 – invalid card, capture

10 – pick up card, special condition

11 – call acquirer security

12 – card is not activated

13 – pin_attempts_exceeded

14 – forced pin change

15 – credit debts

17 – pin activation

18 – instant card personification waiting19 – fraud prevention

20 – temprory blocked by client

21 – permanent blocked by client






20. Tag 019 – Account status

Tag No Size Data

019 n…4 New account status:

0 – No restrictions

1 – No withdrawals

2 – No withdrawals or transfers

3 – Only balance inquiries

4 – Only deposits

5 – Only balance inquiries and deposits

6 – Only balance inquiries, deposits and transfers

7 – No operations allowed (account blocked)


21. Tag 020 – External code for operation

Tag No Size Data

020 ans ..25 External code for some service.


22. Tag 021 – Customer external account number

Tag No Size Data

021 ans ..99 External account number in service provider system.


23. Tag 022 – Customer mobile phone number

Tag No Size Data

022 ans ..32 Mobile phone number for mobile top-up services.






24. Tag 023 – Account Funds Type

Tag No Length Data

023 an 1 Account Funds Type:

Available value:

0 – Debit.

1 – Debit with overdraft.

2 – Credit.


25. Tag 024 – Additional operation informationTag No Length Data

024 ans ..255 Additional operation information

Free form text


26. Tag 090-099 – Payment specific data

Tag No Size Data

090-099 ans ..25 Specific data for payment services.






APPENDIX B (FIELD 54)


Size Data


3 LLL – 3


Tag No Length Data

NNN NNN Ans .. 99

3 3 NNN bytes

3. Tag 001 – Acquirer Fee Amount

Tag No Length Data

001 N12 Acquirer Fee Amount

Could be present in 1100/1120/1420/1421 messages if acquirer

fee is available.

4. Tag 002 – Transaction Amount, Transaction

Currency

Tag No Length Data

002 N12 Transaction Amount, Transaction Currency.

Must be present in 1100/1420/1421 messages for 775, 705, 750,

703, 691, 692, 785 SVFE transactions type only.





5. Tag 003 – Transaction Currency

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 004 – Amount, Credit Initial

Tag No Length Data

004 N12 Amount, Credit Initial.


type only.

7. Tag 005 – Amount, Total Credit

Tag No Length Data

005 n 12 Amount, Total Credit.

Must be present in 1110 message for 684 SVFE transactionstype only.

8. Tag 006 – Issuer Fee Amount and Currency

Tag No Length Data

006 an 16 Issuer Fee Amount and Currency:

Position 1 – Fee Sign (C or D)

Positions 2-3 – Fee Amount

Positions 14-16 – Fee Currency (ISO N3 Format)

Could be present in 1100/1120/1420/1421 messages if issuer fee

is available.





9. Tag 007 – Current Account Available Balance and

Currency

Tag No Length Data

007 an 16 Current Account Available Balance:

Position 1 – Balance Sign (C or D)

Positions 2-3 – Account Balance, amount

Positions 14-16 – Account Currency (ISO N3 Format)

Could be present in 1110/1130/1430 messages and contains

account available balance.

10. Tag 008 – Amount, Installed Exceed Limit

Tag No Length Data






Tag No Length Data

009 an 12 Available Exceed Limit. This amount used to show available

overdraft or credit limit value assigned to card account.







APPENDIX C (FIELD 61)


Size Data


3 LLL – 3


Tag No Length Data

NNN NNN Ans .. 99

3 3 NNN bytes

3. Tag 001 – Cash-In Counters

Tag No Length Data

001 n 15

or n 30or n 45

or n 60

Counters at each active cassette (from 1 to 4) in format:

n 3 – currency of cassetten 12 - amount in cassette

4. Tag 002 – Recycling Counters

Tag No Length Data

002 n 15

or n 30

or n 45

Counters at each active cassette (from 1 to 3) in format:


n 12 - amount in cassette

5. Tag 003 – Recycling Cash-Out Counters

Tag No Length Data

003 n 15

or n 30

or n 45

Cash-out counters at each active cassette (from 1 to 3) in format:


n 12 - cash-out amount from cassette





APPENDIX D (FIELD 95)


Size Data


3 LLL – 3


Tag No Length Data

NNN NNN Ans .. 99

3 3 NNN bytes

3. Tag 001 – Transaction Amount, Transaction

Currency

Tag No Length Data

001 N12 Transaction Amount, Transaction Currency

4. Tag 002 – Transaction Amount, Account Currency

Tag No Length Data

002 N12 Transaction Amount, Account Currency

5. Tag 003 – Transaction Amount, Cardholder Billing

Currency

Tag No Length Data

003 N12 Transaction Amount, Cardholder Billing Currency

6. Tag 006 – Transaction Currency

Tag No Length Data

006 N3 Transaction Currency






LIST OF REVISIONS

№ Date Name, Surname Modifications

1 2010-10-14 Grigoriev A.S. English version of document created. Revised edition.

2 2010-11-24 Grigoriev A.S. Added operations: Debit account with presentment, Credit

account with presentment.

3 2011-02-04 Sasin S.S. Changes in accordance with the Main Project: transaction

type for P2P_DEBIT (781) and UTILITY_PAYMENT

(508) is being changed to POSP (774), and CBS will never

know original operation type

4 2011-02-21 Ustinchenko A.G. Added tag 002 to field 61

5 2011-05-25 Dudnikov V.M. Added Account Verification transaction. Added tag 14, 15 to

field 48.

6 2011-05-27 Ustinchenko A.G. Added tag 003 to field 61

7 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.

8 2011-08-30 Sasin S.S. New processing codes were added: 26 – Service

Reimbursement, 94 – Change Account Status.

New parameters for status and payments were added: tag

019 – Account status, tag 020 – External code for operation,tag 021 – Customer external account number, tag 022 –

Customer mobile phone number, tags 090-099 – Payment

specific data.

9 2011-09-19 Kondrashin E.K. Changed field 43 format and comment field 62.3

10 2011-09-19 Sasin S.S. New processing code – Predefined Service Payment (50) –

was added.

11 2011-09-28 Dudnikov V.M. Changed description of field 39.

12 2011-10-18 Ustinchenko A.G. Added tag 008, 009 to field 54

Added tag 023 to field 48

Changed name of tag 007 of field 54

13 2011-11-03 Dudnikov V.M. Added tag 24 to field 48.

14 2011-12-16 Dudnikov V.M. Field 22 marked as optional.

15 2011-12-27 Dudnikov V.M. Added SVFE transaction type 781.

Documents

Smartvista CBS Specification