Part C: Appendices

HBCI 

HOMEBANKING COMPUTER INTERFACE 

- Interface Specification - 

Part C: Appendices 

Published by: 

Bundesverband deutscher Banken e.V., Cologne 

Deutscher Sparkassen- und Giroverband e.V., Bonn 

Bundesverband der Deutschen Volksbanken und Raiffeisenbanken e.V., Bonn 

Verband öffentlicher Banken e.V., Bonn 

Version 2.2 

Edition: 2000-05-10

The present interface specification for an automatically usable, multi-bank home banking 

interface (referred to below as ”interface specification”) has been developed on behalf of the 

Federal German Central Banking Committee ("Zentraler Kreditausschuss"). It is herewith 

released for implementation in customer and financial institution (FI) systems. 

The interface specification is protected by copyright. Developers may use it free of charge for 

implementation in customer and financial institution (FI) systems. For this purpose, the 

unmodified interface specification may be copied and distributed on the conditions below. 

Redesign, editing, translation and all other alterations whatsoever of the present interface 

specification are prohibited. Identification marks, copyright notices and statements concerning 

ownership may not be changed under any circumstances. 

Since use of the interface specification is granted at no cost, no warranty or liability may be 

assumed for any errors it may contain or for any malfunction of any products thus developed. 

The Central Banking Committee may modify said specification at any time without prior notice. 

Developers may make the present interface specification in its unchanged form available to third 

parties free of charge, on the conditions stated above. 

This document can be retrieved from the Internet under http://www.hbci.de

Homebanking-Computer-Interface (HBCI) 

Chapter: Appendices 

Section: List of contents 

Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

3 

VIII. APPENDICES 

VIII.1 Overview of segment identifiers................................................................... 7 

VIII.2 Overview of HBCI elements....................................................................... 13 

VIII.2.1 Messages 13 

VIII.2.2 Segment sequences.................................................................... 14 

VIII.2.3 Segments 15 

VIII.2.4 Data element groups................................................................... 21 

VIII.2.5 Data elements............................................................................. 25 

VIII.2.6 HBCI Elements............................................................................ 36 

VIII.3 Overview of message structure.................................................................. 57 

VIII.3.1 Standard session ........................................................................ 58 

VIII.3.2 Anonymous session .................................................................... 61 

VIII.3.3 Synchronisation........................................................................... 62 

VIII.3.4 Communications access ............................................................. 63 

VIII.3.5 Changing customer public key (RDH).......................................... 64 

VIII.3.6 Initial request for financial institution public key (RDH) ................ 65 

VIII.3.7 Initial transmission of customer public key (RDH)........................ 66 

VIII.3.8 Key blocking by the customer (RDH)........................................... 67 

VIII.3.9 Key blocking by the customer (DDV)........................................... 68 

VIII.4 HBCI basic character sets ......................................................................... 69 

VIII.4.1 ISO 8859-1 Subset German........................................................ 69 

VIII.4.2 ISO 8859-1 Subset English ......................................................... 69 

VIII.4.3 ISO 8859-1 Subset French.......................................................... 71 

VIII.5 Example session ....................................................................................... 72 

VIII.5.1 Message "Session initialisation" .................................................. 72 

VIII.5.2 Message "Single remittance"....................................................... 75 

VIII.5.3 Message "Show balance"............................................................ 77 

VIII.5.4 Message "Session end"............................................................... 79 

VIII.6 Principles governing communications media ............................................. 81 

VIII.6.1 T-Online 81 

VIII.6.1.1 ETSI 300 072 ("CEPT") ........................................................ 81 

VIII.6.1.2 EHKP .................................................................................... 85 

VIII.6.1.3 BtxFIF ................................................................................... 85

Chapter: 

VIII 

Page: 

4 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 

Appendices 

List of contents 

VIII.6.2 TCP/IP 88 

VIII.6.2.1 Internet (WWW).................................................................... 88 

VIII.6.2.2 Direct access ........................................................................ 88 

VIII.6.2.2.1 Protocol requests .............................................. 88 

VIII.6.2.2.2 Security requirements ....................................... 89 

VIII.6.3 Other communications services................................................... 89 

VIII.7 Retrieving communications settings........................................................... 90 

VIII.8 Chip application for DDV............................................................................ 96 

VIII.8.1 Data of the application HBCI Banking for the type 0 card ............ 97 

VIII.8.1.1 DF_Banking .......................................................................... 98 

VIII.8.1.2 EF_KEY .............................................................................. 100 

VIII.8.1.3 EF_KEYD ........................................................................... 101 

VIII.8.1.4 EF_AUT .............................................................................. 102 

VIII.8.1.5 EF_AUTD ........................................................................... 103 

VIII.8.1.6 EF_PWD1........................................................................... 104 

VIII.8.1.7 EF_PWDD1 ........................................................................ 105 

VIII.8.1.8 EF_BNK.............................................................................. 106 

VIII.8.1.9 EF_MAC ............................................................................. 108 

VIII.8.1.10 EF_SEQ 109 

VIII.8.2 Data of the application HBCI Banking for the type 1 card .......... 110 

VIII.8.2.1 ADF of the application HBCI-Banking ................................ 112 

VIII.8.2.2 EF_RULE............................................................................ 114 

VIII.8.2.3 EF_KEY .............................................................................. 118 

VIII.8.2.4 EF_KEYD ........................................................................... 120 

VIII.8.2.5 EF_PWD............................................................................. 122 

VIII.8.2.6 EF_PWDD .......................................................................... 124 

VIII.8.2.7 EF_FBZ .............................................................................. 125 

VIII.8.2.8 EF_BNK.............................................................................. 126 

VIII.8.2.9 EF_MAC ............................................................................. 127 

VIII.8.2.10 EF_SEQ 128 

VIII.8.3 Space requirement of the application in the chip ....................... 129 

VIII.8.4 Terminal sequences (Type 0 and Type 1) Chip cards and 

terminal sequences ................................................................... 131 

VIII.8.4.1 Start session ....................................................................... 131 

VIII.8.4.2 Generate message ............................................................. 136 

VIII.8.4.3 Signing message ................................................................ 137 

VIII.8.4.4 Encrypting message ........................................................... 140 

VIII.8.4.5 Transmission session ......................................................... 143 

VIII.8.5 Macros 144 

VIII.8.5.1 MAC calculation / test......................................................... 145 

VIII.8.5.2 Encryption........................................................................... 148



Section: List of contents 

Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

5 

VIII.8.6 Overview of the chip applications parameters (type 1) .............. 149 

VIII.9 Market identifiers ..................................................................................... 150 

VIII.10 Calculation of the check character for internal assignment data (Customer 

reference number) ................................................................................... 152 

VIII.10.1 Calculation procedure ............................................................... 153 

VIII.10.2 Example 154 

VIII.11 Country codes and currency codes.......................................................... 155 

VIII.12 European account addressing ................................................................. 156 

VIII.13 Bibliography............................................................................................. 162

Chapter: 

VIII 

Page: 

6 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 


List of contents 

List of Illustrations 

Fig. 26: Structure of T-Online transfer page 

Fig. 27: Data elements of the application "Banking" 

Fig. 28: Data elements of the application "HBCI", account-related cards 

Fig. 29: Data elements of the application "HBCI", account-independent cards



Section: Overview of segment identifiers 

Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

7 

VIII.1 Overview of segment identifiers 

ID Segment name Type 

1 

HIAOMS 

International remittance without text 

message 

Sender 

Ver- 

Additi Chapter 

2 sion onal 3 

GV I 1 - VII.5.2 

HIAUBS International remittance - parameters GV I 5 4 VII.5.1 

HIAZK Card display GV I 1 - VII.6.2 

HIAZKS Card display parameters GV I 1 - VII.6.2 

HIBPA General bank parameters AD I 2 IV.2 

HIDAA Pending standing order modifications GV I 3 2 VII.1.1.4.5 

HIDAAS Pending standing order modifications - GV I 3 2 VII.1.1.4.5 

parameters 

HIDAB Standing orders GV I 3 2 VII.1.1.4.4 

HIDABS Standing orders - parameters GV I 3 2 VII.1.1.4.4 

HIDAE Confirm standing order set up GV I 4 3 VII.1.1.4.1 

HIDAES Standing order setup - parameters GV I 4 3 VII.1.1.4.1 

HIDALS Cancel standing order - parameters GV I 3 2 VII.1.1.4.6 

HIDAN Confirm modification of standing order GV I 4 3 VII.1.1.4.2 

HIDANS Modify standing order - parameters GV I 4 3 VII.1.1.4.2 

HIDAS Confirmation of standing order interruption GV I 3 2 VII.1.1.4.3 

HIDASS Interrupt standing order - parameters GV I 3 2 VII.1.1.4.3 

HIDVK Return exchange rate GV I 1 - VII.7.1 

HIDVKS Exchange rate parameters GV I 1 - VII.7.1 

HIFDA Return financial data format GV I 1 - VII.9.2.4 

HIFDAS Request financial data format parameters GV I 1 - VII.9.2.4 

HIFDB Return processing status financial data GV I 1 - VII.9.2.2 

format 

HIFDBS Processing status financial data format GV I 1 - VII.9.2.2 

Parameter 

HIFDL Return financial data format list GV I 1 - VII.9.2.3 

HIFDLS Request financial data format list 

GV I 1 - VII.9.2.3 

parameters 

HIFDSS Transmit financial data format 

GV I 1 - VII.9.2.1 

parameters 

HIFGA Confirm fixed-term deposit modification GV I 3 2 VII.3.3 

HIFGAS Modify fixed-term deposit - parameters GV I 3 2 VII.3.3 

HIFGB Fixed-term deposit inventory GV I 3 2 VII.3.5 

HIFGBS Fixed-term deposit inventory - parameters GV I 3 2 VII.3.5 

HIFGK Return fixed-term deposit terms and GV I 2 1 VII.3.1 

conditions 

HIFGKS Fixed-term deposit terms and conditions - GV I 2 1 VII.3.1 

parameters 

HIFGN Confirm new fixed-term deposit GV I 3 2 VII.3.2 

1 

2 

3 

AD: Administration, GV: Business transaction 

K: customer, I: financial institution 

Other segment versions supported under the current HBCI version. (At present, only segments 

defined in the current version are supported.)

Chapter: 

VIII 

Page: 

8 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 


Overview of segment identifiers 

ID Segment name Type Sender 

Ver- 


1 

2 sion onal 3 

HIFGNS New fixed-term deposit - parameters GV I 3 2 VII.3.2 

HIFGP Confirm renewal of fixed-term deposit GV I 3 2 VII.3.4 

HIFGPS Renewal of fixed-term deposit - 

GV I 3 2 VII.3.4 

parameters 

HIFGWS Revoke fixed-term deposit - parameters GV I 3 2 VII.3.6 

HIFPO Confirm fixed-price statement GV I 1 - VII.4.5.1.2 

HIFPOS Fixed-price order parameters GV I 1 - VII.4.5.1.2 

HIFPWS Do not renew fixed-term deposit - GV I 3 2 VII.3.7 

parameters 

HIFRD Return exemption data GV I 1 - VII.9.1.1 

HIFRDS Exemption data parameters GV I 1 - VII.9.1.1 

HIGAMS Guest message - parameters GV I 3 2 VII.8.1.2 

HIINF Requested information GV I 3 2 VII.8.2.2 

HIINFS Information request - parameters GV I 3 2 VII.8.2.2 

HIISA Public key transmission AD I 2 - VI.6.1.3 

HIKAN Return new account movements GV I 4 4 VII.2.1.2 

HIKANS New account movements - parameters GV I 4 4 VII.2.1.2 

HIKASS Exemption data parameters GV I 1 - VII.6.3.1 

HIKAZ Account movements during specified GV I 5 4 VII.2.1.1 

period 

HIKAZS Account movements during specified GV I 5 4 VII.2.1.1 

period - parameters 

HIKDMS Customer message - parameters GV I 4 3 VII.8.1.1 

HIKIA Customer information GV I 3 2 VII.8.2.1 

HIKIAS Customer information - parameters GV I 3 2 VII.8.2.1 

HIKIF Return account details GV I 1 - VII.2.3 

HIKIFS Account details parameters GV I 1 - VII.2.3 

HIKIM Financial institution message AD I 2 - III.3.2.5 

HIKOM Request communications settings GV I 3 - VIII.7 

HIKOMS Communications settings - parameters GV I 3 - VIII.7 

HIKPV Compression procedure AD I 1 - IV.5 

HILASS Direct debit - parameters GV I 4 3 VII.1.1.5 

HINEA List of new issues GV I 1 - VII.4.5.2. 

1 

HINEAS List of new issues parameters GV I 1 - VII.4.5.2. 

1 

HINEZ Confirm subscription submission GV I 1 - VII.4.5.2. 

2 

HINEZS Subscribe for new issue parameters GV I 1 - VII.4.5.2. 

2 

HIOAN Portfolio order information GV I 1 - VII.4.2.1 

HIOANS Portfolio order information parameters GV I 1 - VII.4.2.1 

HIPRO Status log response GV I 3 - III.7 

HIPROS Status log - parameters GV I 3 - III.7 

HIRMG Message-level response AD I 2 - II.8.2 

HIRMS Segment-level response AD I 2 - II.8.3 

HISAL Balance GV I 5 4 VII.2.2 

HISALS Show balance - parameters GV I 5 4 VII.2.2




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

9 


Ver- 


1 

2 sion onal 3 

HISHV Security procedure AD I 2 - IV.4 

HISLAS Multiple direct debit - parameters GV I 5 4 VII.1.2.2 

HISLB Pending post-dated multiple payments GV I 2 1 VII.1.2.4 

HISLBS Pending post-dated multiple payments - GV I 2 1 VII.1.2.4 

parameters 

HISLE Confirm submission of post-dated multiple GV I 2 1 VII.1.2.4 

direct debit 

HISLES Submit post-dated multiple direct debit - GV I 2 1 VII.1.2.4 

parameters 

HISLLS Cancel post-dated multiple payment - GV I 2 - VII.1.2.4 

parameters 

HISRBS Foreign currency and traveller's check GV I 1 - VII.7.3 

order parameters 

HISRK Foreign currency and traveller's check GV I 1 - VII.7.2 

conditions reponse 

HISRKS Foreign currency and traveller's check GV I 1 - VII.7.2 

conditions parameters 

HISSP Confirmation of key blocking AD I 2 - VI.6.1.5 

HISUBS Multiple payment - parameters GV I 5 4 VII.1.2.1 

HISYN Synchronisation reply AD I 3 - III.8.2.2 

HITMVS Financial institution officer appointment - GV I 2 1 VII.7.2.3 

parameters 

HITSB Show all post-dated multiple payments GV I 2 1 VII.1.2.3.2 

HITSBS Show post-dated multiple payments - GV I 2 1 VII.1.2.3.2 

parameters 

HITSE Confirm submission of post-dated multiple GV I 2 1 VII.1.2.3.1 

payment 

HITSES Submit post-dated multiple payment - GV I 2 1 VII.1.2.3.1 

parameters 

HITSLS Cancel post-dated multiple payment - GV I 2 1 VII.1.2.3.3 

parameters 

HITUA Confirm modification of post-dated GV I 3 2 VII.1.1.3.2 

remittance 

HITUAS Modify post-dated remittance - parameters GV I 3 2 VII.1.1.3.2 

HITUB Outstanding post-dated remittances GV I 2 1 VII.1.1.3.3 

HITUBS Show outstanding post-dated remittances GV I 2 1 VII.1.1.3.3 

- parameters 

HITUE Confirm post-dated remittance GV I 3 2 VII.1.1.3.1 

HITUES Post-dated remittance - parameters GV I 3 2 VII.1.1.3.1 

HITULS Cancel post-dated remittance - 

GV I 2 1 VII.1.1.3.4 

parameters 

HIUEBS Single remittance - parameters GV I 4 3 VII.1.1.1 

HIUMBS Reclassification parameters GV I 1 - VII.1.1.3 

HIUPA General user parameters AD I 2 - V.2 

HIUPD Account information AD I 4 1 V.3 

HIVDBS Blank form order - parameters GV I 2 1 VII.6.1.1

Chapter: 

VIII 

Page: 

10 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 




Ver- 


1 

2 sion onal 3 

HIWDU Portfolio statement GV I 4 1,2,3 VII.4.3.2 

HIWDUS Portfolio statement - parameters GV I 4 1,2,3 VII.4.3.2 

HIWFO Confirm fund order submission GV I 1 - VII.4.1.5 

HIWFOS Fund order parameters GV I 1 - VII.4.1.5 

HIWFP Fixed-price offers available GV I 2 1 VII.4.5.1.1 

HIWFPS Fixed-price offers - parameters GV I 2 1 VII.4.5.1.1 

HIWOA Confirm portfolio order modification GV I 2 1 VII.4.1.3 

HIWOAS Portfolio order modification - parameters GV I 2 1 VII.4.1.3 

HIWOH Portfolio order history GV I 2 1 VII.4.2.3 

HIWOHS Portfolio order history - parameters GV I 2 1 VII.4.2.3 

HIWPD Return list of portfolio securities GV I 5 2,3,4 VII.4.3.1 

HIWPDS List of portfolio securities - parameters GV I 5 2,3,4 VII.4.3.1 

HIWPH Return key data GV I 2 1 VII.4.1.1 

HIWPHS Key data - parameters GV I 2 1 VII.4.1.1 

HIWPI Security details GV I 2 1 VII.4.4.4 

HIWPIS Security details - parameters GV I 2 1 VII.4.4.4 

HIWPK Security prices GV I 2 1 VII.4.4.3 

HIWPKS Security prices - parameters GV I 2 1 VII.4.4.3 

HIWPO Confirm submission of portfolio order GV I 2 1 VII.4.1.2 

HIWPOS Portfolio order - parameters GV I 2 1 VII.4.1.2 

HIWPR Security reference number information GV I 2 1 VII.4.4.1 

HIWPRS Security reference information - 

GV I 2 1 VII.4.4.1 

parameters 

HIWPS Confirm portfolio order cancellation GV I 2 1 VII.4.1.4 

HIWPSS Portfolio order cancellation - parameters GV I 2 1 VII.4.1.4 

HIWSD Instrument data GV I 2 1 VII.4.4.2 

HIWSDS Instrument data - parameters GV I 2 1 VII.4.4.2 

HIWSO Portfolio order status information GV I 2 1 VII.4.2.1 

HIWSOS Portfolio order status information – AD I 2 1 VII.4.2.1 

parameters 

HKAOM International remittance without text GV K 1 - VII.5.2 

message parameters 

HKAUB International remittance GV K 5 4 VII.5.1 

HKAZK Request card display GV K 1 - VII.6.2 

HKDAA Show pending standing order 

GV K 3 2 VII.1.1.4.5 

modifications 

HKDAB Show all standing orders GV K 3 2 VII.1.1.4.4 

HKDAE Set up a standing order GV K 4 3 VII.1.1.4.1 

HKDAL Cancel standing order GV K 3 2 VII.1.1.4.6 

HKDAN Modify standing order GV K 4 3 VII.1.1.4.2 

HKDAS Interrupt standing order GV K 3 2 VII.1.1.4.3 

HKDVK Request exchange rate GV K 1 - VII.7.1 

HKEND Session end AD K 1 - III.4.1.2 

HKFDA Request financial data format GV K 1 - VII.9.2.4 

HKFDB Request processing status financial data GV K 1 - VII.9.2.2 

format 

HKFDL Request financial data format list GV K 1 - VII.9.2.3




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

11 

ID Segment name Type 

1 

HKFDS 

Transmit financial data format 

parameters 

Sender 

Ver- 


2 sion onal 3 

GV K 1 - VII.9.2.1 

HKFGA Modify fixed-term deposit GV K 3 2 VII.3.3 

HKFGB Show fixed-term deposits GV K 3 2 VII.3.5 

HKFGK Request fixed-term deposit terms and GV K 2 1 VII.3.1 

conditions 

HKFGN New fixed-term deposit GV K 3 2 VII.3.2 

HKFGP Renew fixed-term deposit GV K 3 2 VII.3.4 

HKFGW Revoke fixed-term deposit GV K 3 2 VII.3.6 

HKFPO Fixed-price order parameters GV K 1 - VII.4.5.1.2 

HKFPW Do not renew fixed-term deposit GV K 2 - VII.3.7 

HKFRD Request exemption date GV K 1 - VII.9.1.1 

HKGAM Guest message GV K 3 2 VII.8.1.2 

HKIDN Identification AD K 2 - III.3.1.2 

HKINF Request information GV K 3 2 VII.8.2.2 

HKISA Request for public key AD K 2 - VI.6.1.2 

HKKAN New account movements GV K 5 4 VII.2.1.2 

HKKAS Apply for card block GV K 1 - VII.6.3.1 

HKKAZ Account movements during specified GV K 5 4 VII.2.1.1 

period 

HKKDM Customer message GV K 4 3 VII.7.1.1 

HKKIA Request customer information GV K 3 2 VII.7.2.1 

HKKIF Request account details GV K 1 - VII.2.3 

HKKOM Request communications settings GV K 3 - VIII.7 

HKLAS Single direct debit GV K 4 3 VII.1.1.5 

HKNEA Request list of new issues GV K 1 - VII.4.5.2. 

1 

HKNEZ Subscribe for new issue GV K 1 - VII.4.5.2. 

2 

HKOAN Request portfolio order information GV K 1 - VII.4.2.1 

HKPRO Request status log GV K 3 - III.7 

HKSAK Change key AD K 2 - VI.6.1.1 

HKSAL Show balance GV K 5 4 VII.2.2 

HKSLA Multiple direct debit GV K 5 4 VII.1.2.2 

HKSLB Show all post-dated multiple payments GV K 2 1 VII.1.2.4 

HKSLE Submit post-dated multiple direct debit GV K 2 1 VII.1.2.4 

HKSLL Cancel post-dated multiple payment GV K 2 1 VII.1.2.4 

HKSRB Foreign currency and traveller's check GV K 1 - VII.7.3 


HKSRK Request foreign currency and traveller's GV K 1 - VII.7.2 

check conditions 

HKSSP Block key AD K 2 - VI.6.1.4 

HKSUB Multiple remittance GV K 5 4 VII.1.2.1 

HKSYN Synchronisation AD K 2 - III.8.1.2 

HKTMV Request appointment with financial GV K 2 1 VII.8.2.3 

institution officer 

HKTSB Show all post-dated multiple payments GV K 2 1 VII.1.2.3.2 

HKTSE Submit post-dated multiple payment GV K 2 1 VII.1.2.3.1

Chapter: 

VIII 

Page: 

12 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 




Ver- 


1 

2 sion onal 3 

HKTSL Cancel post-dated multiple payment GV K 2 1 VII.1.2.3.3 

HKTUA Modify post-dated remittance GV K 3 2 VII.1.1.3.2 

HKTUB Show outstanding post-dated remittances GV K 2 1 VII.1.1.3.3 

HKTUE Submit post-dated remittance GV K 3 2 VII.1.1.3.1 

HKTUL Cancel post-dated remittance GV K 2 1 VII.1.1.3.4 

HKUEB Single remittance GV K 4 3 VII.1.1.1 

HKUMB Reclassification GV K 1 - VII.1.1.3 

HKVDB Blank form order GV K 2 1 VII.6.1.1 

HKVVB General bank parameters AD K 2 - III.3.1.3 

HKWDU Request portfolio account statement GV K 4 1,2,3 VII.4.3.2 

HKWFO Submit fund order GV K 1 - VII.4.1.5 

HKWFP Request for fixed-price offers GV K 2 1 VII.4.5.1.1 

HKWOA Modify portfolio order GV K 2 1 VII.4.1.3 

HKWOH Request portfolio order history GV K 2 1 VII.4.2.3 

HKWPD Request for list of portfolio securities GV K 5 2,3,4 VII.4.3.1 

HKWPH Request key data GV K 2 1 VII.4.1.1 

HKWPI Request security details GV K 2 1 VII.4.4.4 

HKWPK Request security prices GV K 2 1 VII.4.4.3 

HKWPO Present portfolio order GV K 2 1 VII.4.1.2 

HKWPR Request for security reference GV K 2 1 VII.4.4.1 

HKWPS Cancel portfolio order GV K 2 1 VII.4.1.4 

HKWSD Request instrument data GV K 2 1 VII.4.4.2 

HKWSO Portfolio order status request GV K 2 1 VII.4.2.1 

HNHBK Message header AD K/I 3 - II.6.2 

HNHBS Message terminator AD K/I 1 - II.6.3 

HNSHA Signature closer AD K/I 1 - VI.5.3 

HNSHK Signature header AD K/I 3 - VI.5.2 

HNVSD Encrypted data AD K/I 1 - VI.5.5 

HNVSK Encryption header AD K/I 2 - VI.5.4



Section: Overview of HBCI elements 

Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

13 

VIII.2 Overview of HBCI elements 

VIII.2.1 Messages 

No. Name ID Sender 

Chapter 

4 

1 Termination message N21 I II.8.6 

2 Changing of a public key of the customer N1 K VI.6.2.1 

3 Reply to session initialisation N2 I III.3.2.1 

4 Reply to anonymous session initialisation N3 I III.5.1 

5 Reply to communications settings request N4 I VIII.7 

6 Confirmation of key blocking by the financial N5 I VI.6.2.4 

institution 

7 Session initialisation N6 K III.3.1.1 

8 Session initialisation for anonymous access N7 K III.5.1 

9 Session end N8 K III.4.1.1 

10 Anonymous session end N9 K III.5.3 

11 Initial request for key of financial institution N10 K VI.6.2.2 

12 Initial transmission of keys of financial institution N11 I VI.6.2.2 

13 Initial transmission of keys of customer N12 K VI.6.2.3 

14 Communications access N13 K VIII.7 

15 Generic financial institution message N14 I II.8.1 

16 Generic customer message N15 K II.7.1 

17 General anonymous customer message N16 K III.5.2 

18 Blocking of a key by the customer N17 K VI.6.2.4 

19 Synchronisation request message N18 K III.8.1.1 

20 Synchronisation reply message N19 I III.8.2.1 

21 Encrypted message N20 K/I II.9 

4 

K: customer, I: financial institution

Chapter: 

VIII 

Page: 

14 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 


Overview of HBCI elements 

VIII.2.2 

Segment sequences 

No. Name 

Sender 

Chapter 

5 

1 Orders K II.7.2 

2 Financial institution parameter data I IV.1 

3 Data segments I II.8.4 

4 Parameter data I IV.7 

5 User parameter data I V.1 

5 





Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

15 

VIII.2.3 

Segments 

No. Name ID Type Sender 

Chapter 

6 

7 

1 Account details parameters HIKIFS GV I VII.2.3 

2 Account information HIUPD AD I V.3 

3 Account movements during specified period HKKAZ GV K VII.2.1.1 

4 Account movements during specified period HIKAZ GV I VII.2.1.1 

5 Account movements during specified period - HIKAZS GV I VII.2.1.1 

parameters 

6 Apply for card block HKKAS GV K VII.6.3.1 

7 Apply for card block parameters HIKASS GV I VII.6.3.1 

8 Balance HISAL GV I VII.2.2 

9 Blank form order HKVDB GV K VII.6.1.1 

10 Blank form order - parameters HIVDBS GV I VII.6.1.1 

11 Block key HKSSP AD K VI.6.1.4 

12 Cancel portfolio order HKWPS GV K VII.4.1.4 

13 Cancel post-dated multiple payment HKSLL GV K VII.1.2.4 

14 Cancel post-dated multiple payment HKTSL GV K VII.1.2.3.3 

15 Cancel post-dated multiple payment - 

HISLLS GV I VII.1.2.4 

parameters 

16 Cancel post-dated multiple payment - 

HITSLS GV I VII.1.2.3.3 

parameters 

17 Cancel post-dated remittance HKTUL GV K VII.1.1.3.4 

18 Cancel post-dated remittance - parameters HITULS GV I VII.1.1.3.4 

19 Cancel standing order HKDAL GV K VII.1.1.4.6 

20 Cancel standing order - parameters HIDALS GV I VII.1.1.4.6 

21 Card display HIAZK GV I VII.6.2 

22 Card display parameters HIAZKS GV I VII.6.2 

23 Change key HKSAK AD K VI.6.1.1 

24 Communications settings - parameters HIKOMS GV I VIII.7 

25 Compression procedure HIKPV AD I IV.5 

26 Confirm fixed-price statement HIFPO GV I VII.4.5.1.2 

27 Confirm fixed-term deposit modification HIFGA GV I VII.3.3 

28 Confirm fund order submission HIWFO GV I VII.4.1.5 

29 Confirm modification of post-dated remittance HITUA GV I VII.1.1.3.2 

30 Confirm modification of standing order HIDAN GV I VII.1.1.4.2 

31 Confirm new fixed-term deposit HIFGN GV I VII.3.2 

32 Confirm portfolio order cancellation HIWPS GV I VII.4.1.4 

33 Confirm portfolio order modification HIWOA GV I VII.4.1.3 

34 Confirm post-dated remittance HITUE GV I VII.1.1.3.1 

35 Confirm renewal of fixed-term deposit HIFGP GV I VII.3.4 

6 

7 

AD: Administration, GV: business transaction 


Chapter: 

VIII 

Page: 

16 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 




Chapter 

6 

7 

36 Confirm standing order set up HIDAE GV I VII.1.1.4.1 

37 Confirm submission of portfolio order HIWPO GV I VII.4.1.2 

38 Confirm submission of post-dated multiple direct HISLE GV I VII.1.2.4 

debit 

39 Confirm submission of post-dated multiple HITSE GV I VII.1.2.3.1 

payment 

40 Confirm subscription submission HINEZ GV I VII.4.5.2 

41 Confirmation of key blocking HISSP AD I VI.6.1.5 

42 Confirmation of standing order interruption HIDAS GV I VII.1.1.4.3 

43 Customer information HIKIA GV I VII.8.2.1 

44 Customer information - parameters HIKIAS GV I VII.8.2.1 

45 Customer message HKKDM GV K VII.8.1.1 

46 Customer message - parameters HIKDMS GV I VII.8.1.1 

47 Direct debit - parameters HILASS GV I VII.1.1.5 

48 Do not renew fixed-term deposit HKFPW GV K VII.3.7 

49 Do not renew fixed-term deposit - parameters HIFPWS GV I VII.3.7 

50 Encrypted data HNVSD AD K/I VI.5.5 

51 Encryption header HNVSK AD K/I VI.5.4 

52 Exchange rate parameters HIDVKS GV I VII.7.1 

53 Exemption data parameters HIFRDS GV I VII.9.1.1 

54 Financial institution message HIKIM AD I III.3.2.5 

55 Financial institution officer appointment - HITMVS GV I VII.8.2.3 

parameters 

56 Fixed-price offers - parameters HIWFPS GV I VII.4.5.1.1 

57 Fixed-price offers available HIWFP GV I VII.4.5.1.1 

58 Fixed-price order HKFPO GV K VII.4.5.1.2 

59 Fixed-price order parameters HIFPOS GV I VII.4.5.1.2 

60 Fixed-term deposit inventory HIFGB GV I VII.3.5 

61 Fixed-term deposit inventory - parameters HIFGBS GV I VII.3.5 

62 Fixed-term deposit terms and conditions - HIFGKS GV I VII.3.1 

parameters 

63 Foreign currency and traveller's check order HKSRB GV K VII.7.3 

parameters 

64 Foreign currency and traveller's check order HISRBS GV I VII.7.3 

parameters 

65 Foreign currency and traveller's check 

HISRKS GV I VII.7.2 


66 Foreign currency and traveller's check 

HISRK GV I VII.7.2 

conditions reponse 

67 Fund order parameters HIWFOS GV I VII.4.1.5 

68 General bank parameters HIBPA AD I IV.2 

69 Customer system preferences HKVVB AD K III.3.1.3 

70 General user parameters HIUPA AD I V.2 

71 Guest message HKGAM GV K VII.8.1.2




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

17 


Chapter 

6 

7 

72 Guest message - parameters HIGAMS GV I VII.8.1.2 

73 Identification HKIDN AD K III.3.1.2 

74 Information request - parameters HIINFS GV I VII.8.2.2 

75 Instrument data HIWSD GV I VII.4.4.2 

76 Instrument data - parameters HIWSDS GV I VII.4.4.2 

77 International funds transfer without text HKAOM GV K VII.5.2 

message 

78 International funds transfer without text HIAOMS GV I VII.5.2 

message parameters 

79 International remittance HKAUB GV K VII.5.1 

80 International remittance - parameters HIAUBS GV I VII.5.1 

81 Interrupt standing order HKDAS GV K VII.1.1.4.3 

82 Interrupt standing order - parameters HIDASS GV I VII.1.1.4.3 

83 Key data - parameters HIWPHS GV I VII.4.1.1 

84 List of new issues HINEA GV I VII.4.5.1. 

1 

85 List of new issues parameters HINEAS GV I VII.4.5.1. 

1 

86 List of portfolio securities HIWPD GV I VII.4.3.1 

87 List of portfolio securities - parameters HIWPDS GV I VII.4.3.1 

88 Message header HNHBK AD K/I II.6.2 

89 Message terminator HNHBS AD K/I II.6.3 

90 Message-level response HIRMG AD I II.8.2 

91 Modify fixed-term deposit HKFGA GV K VII.3.3 

92 Modify fixed-term deposit - parameters HIFGAS GV I VII.3.3 

93 Modify portfolio order HKWOA GV K VII.4.1.3 

94 Modify post-dated remittance HKTUA GV K VII.1.1.3.2 

95 Modify post-dated remittance - parameters HITUAS GV I VII.1.1.3.2 

96 Modify standing order HKDAN GV K VII.1.1.4.2 

97 Modify standing order - parameters HIDANS GV I VII.1.1.4.2 

98 Multiple direct debit HKSLA GV K VII.1.2.2 

99 Multiple direct debit - parameters HISLAS GV I VII.1.2.2 

100 Multiple payment - parameters HISUBS GV I VII.1.2.1 

101 Multiple remittance HKSUB GV K VII.1.2.1 

102 New account movements HKKAN GV K VII.2.1.2 

103 New account movements - parameters HIKANS GV I VII.2.1.2 

104 New fixed-term deposit HKFGN GV K VII.3.2 

105 New fixed-term deposit - parameters HIFGNS GV I VII.3.2 

106 Outstanding post-dated remittances HITUB GV I VII.1.1.3.3 

107 Pending post-dated multiple payments HISLB GV I VII.1.2.4 

108 Pending post-dated multiple payments - HISLBS GV I VII.1.2.4 

parameters 

109 Pending standing order modifications HIDAA GV I VII.1.1.4.5

Chapter: 

VIII 

Page: 

18 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



No. Name ID Type 

6 

110 Pending standing order modifications - 

parameters 

Sender 

Chapter 

7 

HIDAAS GV I VII.1.1.4.5 

111 Portfolio order - parameters HIWPOS GV I VII.4.1.2 

112 Portfolio order cancellation - parameters HIWPSS GV I VII.4.1.4 

113 Portfolio order history HIWOH GV I VII.4.2.2 

114 Portfolio order history - parameters HIWOHS GV I VII.4.2.2 

115 Portfolio order information HIOAN GV I VII.4.2.1 

116 Portfolio order information parameters HIOANS GV I VII.4.2.1 

117 Portfolio order modification - parameters HIWOAS GV I VII.4.1.3 

118 Portfolio order status information HIWSO GV I VII.4.2.2 

119 Portfolio order status information – parameters HIWSOS AD I VII.4.2.2 

120 Portfolio order status request HKWSO GV K VII.4.2.2 

121 Portfolio statement HIWDU GV I VII.4.3.2 

122 Portfolio statement - parameters HIWDUS GV I VII.4.3.2 

123 Post-dated remittance - parameters HITUES GV I VII.1.1.3.1 

124 Present portfolio order HKWPO GV K VII.4.1.2 

125 Processing status financial data format HIFDBS GV I VII.9.2.2 

Parameter 

126 Public key transmission HIISA AD I VI.6.1.3 

127 Reclassification HKUMB GV K VII.1.1.3 

128 Reclassification parameters HIUMBS GV I VII.1.1.3 

129 Renew fixed-term deposit HKFGP GV K VII.3.4 

130 Renewal of fixed-term deposit - parameters HIFGPS GV I VII.3.4 

131 Request account details HKKIF GV K VII.2.3 

132 Request appointment with financial institution HKTMV GV K VII.8.2.3 

officer 

133 Request card display HKAZK GV K VII.6.2 

134 Request communications settings HKKOM GV K VIII.7 

135 Request communications settings HIKOM GV I VIII.7 

136 Request customer information HKKIA GV K VII.8.2.1 

137 Request exchange rate HKDVK GV K VII.7.1 

138 Request exemption date HKFRD GV K VII.9.1.1 

139 Request financial data format HKFDA GV K VII.9.2.4 

140 Request financial data format list HKFDL GV K VII.9.2.3 

141 Request financial data format list parameters HIFDLS GV I VII.9.2.3 

142 Request financial data format parameters HIFDAS GV I VII.9.2.4 

143 Request fixed-term deposit terms and conditions HKFGK GV K VII.3.1 

144 Request for fixed-price offers HKWFP GV K VII.4.5.1.1 

145 Request for list of portfolio securities HKWPD GV K VII.4.3.1 

146 Request for public key HKISA AD K VI.6.1.2 

147 Request for security reference HKWPR GV K VII.4.4.1 

148 Request foreign currency and traveller's check 

conditions 

HKSRK GV K VII.7.2




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

19 


Chapter 

6 

7 

149 Request information HKINF GV K VII.8.2.2 

150 Request instrument data HKWSD GV K VII.4.4.2 

151 Request key data HKWPH GV K VII.4.1.1 

152 Request list of new issues HKNEA GV K VII.4.5.1. 

1 

153 Request portfolio account statement HKWDU GV K VII.4.3.2 

154 Request portfolio order history HKWOH GV K VII.4.2.2 

155 Request portfolio order information HKOAN GV K VII.4.2.1 

156 Request processing status financial data format HKFDB GV K VII.9.2.2 

157 Request security details HKWPI GV K VII.4.4.4 

158 Request security prices HKWPK GV K VII.4.4.3 

159 Request status log HKPRO GV K III.7 

160 Requested information HIINF GV I VII.8.2.2 

161 Return account details HIKIF GV I VII.2.3 

162 Return exchange rate HIDVK GV I VII.7.1 

163 Return exemption data HIFRD GV I VII.9.1.1 

164 Return financial data format HIFDA GV I VII.9.2.4 

165 Return financial data format list HIFDL GV I VII.9.2.3 

166 Return fixed-term deposit terms and conditions HIFGK GV I VII.3.1 

167 Return key data HIWPH GV I VII.4.1.1 

168 Return new account movements HIKAN GV I VII.2.1.2 

169 Return processing status financial data format HIFDB GV I VII.9.2.2 

170 Revoke fixed-term deposit HKFGW GV K VII.3.6 

171 Revoke fixed-term deposit - parameters HIFGWS GV I VII.3.6 

172 Security details HIWPI GV I VII.4.4.4 

173 Security details - parameters HIWPIS GV I VII.4.4.4 

174 Security prices HIWPK GV I VII.4.4.3 

175 Security prices - parameters HIWPKS GV I VII.4.4.3 

176 Security procedure HISHV AD I IV.4 

177 Security reference information - parameters HIWPRS GV I VII.4.4.1 

178 Security reference number information HIWPR GV I VII.4.4.1 

179 Segment-level response HIRMS AD I II.8.3 

180 Session end HKEND AD K III.4.1.2 

181 Set up a standing order HKDAE GV K VII.1.1.4.1 

182 Show all post-dated multiple payments HKSLB GV K VII.1.2.4 

183 Show all post-dated multiple payments HKTSB GV K VII.1.2.3.2 

184 Show all post-dated multiple payments HITSB GV I VII.1.2.3.2 

185 Show all standing orders HKDAB GV K VII.1.1.4.4 

186 Show balance HKSAL GV K VII.2.2 

187 Show balance - parameters HISALS GV I VII.2.2 

188 Show fixed-term deposits HKFGB GV K VII.3.5 

189 Show outstanding post-dated remittances HKTUB GV K VII.1.1.3.3

Chapter: 

VIII 

Page: 

20 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



No. Name ID Type 

6 

190 Show outstanding post-dated remittances - 

parameters 

Sender 

Chapter 

7 

HITUBS GV I VII.1.1.3.3 

191 Show pending standing order modifications HKDAA GV K VII.1.1.4.5 

192 Show post-dated multiple payments - 

HITSBS GV I VII.1.2.3.2 

parameters 

193 Signature closer HNSHA AD K/I VI.5.3 

194 Signature header HNSHK AD K/I VI.5.2 

195 Single direct debit HKLAS GV K VII.1.1.5 

196 Single remittance HKUEB GV K VII.1.1.1 

197 Single remittance - parameters HIUEBS GV I VII.1.1.1 

198 Standing order setup - parameters HIDAES GV I VII.1.1.4.1 

199 Standing orders HIDAB GV I VII.1.1.4.4 

200 Standing orders - parameters HIDABS GV I VII.1.1.4.4 

201 Status log - parameters HIPROS GV I III.7 

202 Status log response HIPRO GV I III.7 

203 Submit fund order HKWFO GV K VII.4.1.5 

204 Submit post-dated multiple direct debit HKSLE GV K VII.1.2.4 

205 Submit post-dated multiple direct debit - HISLES GV I VII.1.2.4 

parameters 

206 Submit post-dated multiple payment HKTSE GV K VII.1.2.3.1 

207 Submit post-dated multiple payment - 

HITSES GV I VII.1.2.3.1 

parameters 

208 Submit post-dated remittance HKTUE GV K VII.1.1.3.1 

209 Subscribe for new issue HKNEZ GV K VII.4.5.1. 

2 

210 Subscribe for new issue parameters HINEZS GV I VII.4.5.1. 

2 

211 Synchronisation HKSYN AD K III.8.1.2 

212 Synchronisation reply HISYN AD I III.8.2.2 

213 Transmit financial data format HKFDS GV K VII.9.2.1 

214 Transmit financial data format parameters HIFDSS GV I VII.9.2.1




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

21 

VIII.2.4 

Data element groups 

No. Name Format Chapter 

1 Alternative delivery address addr 

2 Mailing address addr 

3 Deposit amount amt 

4 Maximum deposit amt 

5 New deposit amount amt 

6 Minimum deposit amt 

7 Deposit account acc 

8 Old deposit account acc 

9 Order filter VII.4.2.1 

10 Maturity account acc 

11 Export limit amt 

12 Issue price VII.4.4.3 

13 Interruption VII.1.1.4 

14 Beneficiary addr 

15 Account to be debited acc 

16 Amount already drawn on amt 

17 Order conditions VII.7.2 

18 Order VII.7.3 

19 Amount of payment amt 

20 Reference message II.6.2 

21 End financial institution ID VIII.7 

22 Exchange information VII.4.4.2 

23 Postal address addr 

24 Standing order details VII.1.1.4 

25 Portfolio account acc 

26 Import limit amt 

27 Issue price amt 

28 Business transactions allowed V.3 

29 Opening price VII.4.4.3 

30 Fixed-term deposit terms VII.3 

31 Format details VII.9.2 

32 Form VII.6.1.1 

33 Exemption amount amt 

34 Optional text information VII.8.2.2 

35 Current balance bal 

36 Validity date VII.4.2.2 

37 Hash algorithm VI.5.2.2

Chapter: 

VIII 

Page: 

22 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 




38 Information VII.8.2.1 

39 Information codes VII.8.2.2 

40 High for the year VII.4.4.3 

41 Low for the year VII.4.4.3 

42 Card limit amt 

43 Spot rate VII.4.4.3 

44 Minimum amount amt 

45 Smallest step amt 

46 Communication parameter VIII.7 

47 Spending limit V.3 

48 Account acc 

49 Customer account acc 

50 Beneficiary account acc 

51 Account to be debited/credited acc 

52 Bank ID bid 

53 Overdraft limit amt 

54 Price data VII.4.4.3 

55 Latest quote VII.4.4.3 

56 Limit amount amt 

57 Minimum order amount amt 

58 Minimum subscription, amount amt 

59 After hours VII.4.4.3 

60 Nominal value amt 

61 Nominal values VII.7.2 

62 Public key VI.5.1.5 

63 Parameters IV.6 

64 International remittance - parameters VII.5.1 

65 International remittance without text message 

VII.5.2 

parameters 

66 Show outstanding post-dated remittances - 

VII.1.1.3.3 

parameters 

67 Modify standing order - parameters VII.1.1.4.2 

68 Interrupt standing order - parameters VII.1.1.4.3 

69 Standing order setup - parameters VII.1.1.4.1 

70 Cancel standing order - parameters VII.1.1.4.6 

71 List of portfolio securities - parameters VI.4.3.1 

72 Portfolio statement - parameters VI.4.3.2 

73 Exchange rate parameters VII.7.1 

74 Single remittance/direct debit parameters VII.1.1.1 

75 Modify fixed-term deposit - parameters VII.3.3 

76 Fixed-term deposit terms and conditions - 

VII.3.1 

parameters




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

23 


77 New fixed-term deposit - parameters VII.3.2 

78 Fixed-price offers - parameters VII.4.5.1.1 

79 Fixed-price order parameters VII.4.5.1.2 

80 Request financial data format parameters VII.9.2.4 

81 Transmit financial data format parameters VII.9.2.1 

82 Fund order parameters VII.4.1.5 

83 Block card parameters VII.6.3.1 

84 Account movements during specified period - 

VII.2.1.2 

parameters 

85 New account movements - parameters VII.2.1.1 

86 Customer/guest message parameters VII.8.1.1 

87 List of new issues parameter VII.4.5.1 

88 Subscribe for new issue parameters VII.4.5.2 

89 Portfolio order information parameters VII.4.2.1 

90 Order status parameters VII.4.2.2 

91 Parameter multiple remittance/direct debit VII.1.2.1 

92 Foreign currency and traveller's checkcheque 

VII.7.3 


93 Foreign currency and traveller's checkcheque 

VII.7.2 


94 Modify post-dated remittance - parameters VII.1.1.3.2 

95 Submit post-dated remittance - parameters VII.1.1.3.1 

96 Blank form order - parameters VII.6.1.1 

97 Security details - parameters VII.4.4.4 

98 Security prices - parameters VII.4.4.3 

99 Portfolio order - parameters VII.4.1.2 

100 Portfolio order modification - parameters VII.4.1.3 

101 Portfolio order history - parameters VII.4.2.3 

102 Portfolio order cancellation - parameters VII.4.1.4 

103 Security reference information - parameters VII.4.4.1 

104 Instrument data - parameters VII.4.4.2 

105 Key data - parameters VII.4.1.1 

106 Price limit amt 

107 Price range to amt 

108 Price range from amt 

109 Renewal VII.3 

110 Reference account acc 

111 Remaining exemption amount amt 

112 Response II.8.5.2 

113 Repurchase price VII.4.4.3 

114 Balance including pending transactions bal 

115 Key name VI.5.1.1 

116 Segment header II.6.1

Chapter: 

VIII 

Page: 

24 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 




117 Security date and time VI.5.1.2 

118 Security identification, Details VI.5.1.3 

119 Signature algorithm VI.5.2.3 

120 Instrument data shares VII.4.4.2 

121 Instrument data fund VII.4.4.2 

122 Instrument data warrants VII.4.4.2 

123 Instrument data pension VII.4.4.2 

124 Denomination possibilities VII7.2 

125 Total sum for all orders amt 

126 HBCI versions supported IV.2 

127 Compression procedures supported IV.5 

128 Security procedures supported IV.4 

129 Languages supported IV.2 

130 Available funds amt 

131 Authorised to draw VII.2.3 

132 Clearing account acc 

133 Encryption algorithm VI.5.4.2 

134 Version of terms and conditions VII.3 

135 Payment purpose VII.1.1 

136 Start bank ID VIII.7 

137 Pre-opening VII.4.4.3 

138 Registration time and date VII.4.2.1 

139 Previous day VII.4.4.3 

140 Securities asset groups VII.4.4.1 

141 Security reference VII.4 

142 Key data VII.4.1.1 

143 Certificate VI.5.1.4 

144 Earned interest expected amt 

145 Earned interest account acc




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

25 

VIII.2.5 

Data elements 

No. Name Format Length 

1 Maturity date dat # 

2 Settlement currency cur # 

3 Settlement currency euro allowed yn # 

4 Settlement currency local currency allowed yn # 

5 Currency of temporary change of amount cur # 

6 Alternative branch office an ..35 

7 Temporary change of amount allowed yn # 

8 Temporary change of amount val # 

9 Different maturity account supported yn # 

10 Different clearing account supported num 1 

11 Different earned interest account supported yn # 

12 Printed address yn # 

13 Printed address possible yn # 

14 All portfolios yn # 

15 All accounts yn # 

16 All accounts allowed yn # 

17 Information on value date of invoice an ..35 

18 Deposit date dat # 

19 Number of payments skipped num ..2 

20 Number of signatures needed num ..2 

21 Number of orders num ..5 

22 Number of business transactions num ..3 

23 Minimum number of signatures num 1 

24 Number of post-dated modifications num 1 

25 Number of post-dated interruptions num 1 

26 Type of key data num 1 

27 Type of export limit num 1 

28 Type of import limit num 1 

29 Type of limit an 4 

30 Limit type modifiable yn # 

31 Type of time limit an 4 

32 Type of time limit modifiable yn # 

33 Scroll reference an ..35 

34 Client name, AZV an ..140 

35 Order comments txt ..2048 

36 Order ID an ..99 

37 Old order ID an ..99 

38 Order ID allowed yn # 

39 Maturity account modifiable yn #

Chapter: 

VIII 

Page: 

26 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 




40 Notice of execution bin .. 

41 Scheduled date dat # 

42 Day of execution num ..2 

43 Scheduled date modifiable yn # 

44 Days of the month available dig ..64 

45 Days of the week available dig ..7 

46 Issue markup val # 

47 Delivery num 1 

48 Delivery type num 1 

49 Interruption end date dat # 

50 Interruption start date dat # 

51 Annual interruption yn # 

52 Annual interruption allowed yn # 

53 Type of interruption possible num 1 

54 Changeover check reference id # 

55 Processing price, currency cur # 

56 Processing price, value val # 

57 Beneficiary possible yn # 

58 Account to be debited modifiable yn # 

59 Remarks txt ..2048 

60 User ID id # 

61 Range of the security application, coded an ..3 

62 Description an ..35 

63 Special instructions txt ..200 

64 Existing deposit account allowed yn # 

65 Order conditions required yn # 

66 Amount modifiable yn # 

67 Subject an ..35 

68 Code for algorithm parameter, IV an ..3 

69 Code for algorithm parameter, key an ..3 

70 Code for exponent an ..3 

71 Code for function type num ..3 

72 Code for hash algorithm parameter an ..3 

73 Code for modulus an ..3 

74 Code for security party an ..3 

75 Reference data element an ..7 

76 Reference segment num ..3 

77 Reference ratio an ..35 

78 End date dat # 

79 Exchange an 4 

80 BPD version num ..3 

81 Branch an ..35 

82 Rate asked/selling rate val #




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

27 


83 Rate asked val # 

84 Balance booking date dat # 

85 Balance booking time tim # 

86 CID bin ..256 

87 Data, encrypted bin .. 

88 Date dat # 

89 Date of transmission dat # 

90 Date and time indicator, coded an ..3 

91 Registration date dat # 

92 Portfolio required yn # 

93 List of portfolio securities bin # 

94 Portfolio securities bank charge val # 

95 Portfolio currency cur # 

96 Session ID id # 

97 Session language num ..3 

98 Dividends val # 

99 DTA data record bin .. 

100 DTAZV data record bin .. 

101 End early order deadline dat # 

102 End early order deadline, remarks txt ..80 

103 End early order deadline, time tim # 

104 Own account yn # 

105 Maximum entries supported yn # 

106 Quote units num 1 

107 Type of payment num 1 

108 Rate of payment val # 

109 Date submitted dat # 

110 E-mail address an ..35 

111 Issue date dat # 

112 Issue price, remarks txt ..80 

113 Issues status num 1 

114 Issues volumes an ..50 

115 Issuing party num 6 

116 Address an ..35 

117 Beneficiary name modifiable yn # 

118 Beneficiary name, AZV an ..140 


120 Order allowed an ..20 

121 Allowed type of denomination num 1 

122 Remarks an ..35 

123 Order to be resubmitted yn # 

124 Opening date dat # 

125 First day of trading dat #

Chapter: 

VIII 

Page: 

28 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 




126 First day of trading, remarksErläuterung txt ..80 

127 First interest due date dat # 

128 First scheduled date modifiable yn # 

129 Execute for the first time on vdat # 


131 Fixed-term deposit status num 1 

132 Fixed-price offer number id # 

133 Filter new issues num 1 

134 Filter function an 3 

135 Financial data format bin .. 

136 Document format an ..3 

137 Format name an ..10 

138 Format details, coded an 10 

139 Format type num 1 

140 Format version an ..10 

141 Form name an ..35 

142 Form code num ..2 

143 Plain text message txt ..2048 

144 Foreign currency cur # 

145 Booked transactions bin .. 

146 Date of birth dat # 

147 Beneficiary's date of birth dat # 

148 Buying rate val # 

149 Buying rate val # 

150 Total amount, currency cur # 

151 Total amount, value val # 

152 Branch office an ..35 

153 Transaction an ..6 

154 Quantity required num ..3 

155 Scheduled date dat # 

156 Scheduled date allowed yn # 

157 Graphics bin .. 

158 Graphics format an ..15 

159 Greenshoe an ..50 

160 Valid from dig 4 

161 Valid to dig 4 

162 Validity duration floor num 1 

163 Validity duration XETRA num ..3 

164 Credit interest val # 

165 Trading type an ..2 

166 Trading type XETRA an ..2 

167 Currency of exchange cur # 

168 Hash algorithm, coded an ..3




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

29 


169 HBCI version num ..3 

170 Registered place of trade an 4 

171 Maximum amount in foreign currency, currency cur # 

172 Maximum amount in foreign currency, value val # 

173 Maximum amount in national currency, currency cur # 

174 Maximum amount in national currency, value val # 

175 Stockholders meeting dat # 

176 IBAN beneficiary an ..34 

177 IBAN specification possible yn # 

178 Identification of the party id # 

179 Document type an 1 

180 Information code an ..10 

181 Name of beneficiary's institution, AZV an ..140 

182 Year of validity num 4 

183 Capital adjustments num 1 

184 Card an ..40 

185 Card type num ..2 

186 Card follow-up number id # 

187 Card number id # 

188 Category of key data an ..30 

189 Minimum order amount val # 

190 Commission val # 

191 Communications address an ..512 

192 Communications address suffix an ..512 

193 Communications service num ..2 

194 Compression function an ..3 

195 Compression version num ..3 

196 Conditions type num 1 

197 Terms name an ..30 

198 Terms ID id # 

199 Terms version an ..10 

200 Terms version an ..10 

201 Consortium leader txt ..200 

202 Contingent information an ..15 

203 Account or portfolio no. id # 

204 Account type num ..2 

205 Account statement code num 1 

206 Account statement code modifiable yn # 

207 Account type an ..30 

208 Account details beneficiary modifiable yn # 

209 Account currency cur # 

210 Contract reference id # 

211 Old contract reference id #

Chapter: 

VIII 

Page: 

30 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 




212 Cost unit num 1 

213 Bank name an ..60 

214 Bank code an ..30 

215 Bank officer name an ..35 

216 Customer ID id # 

217 Customer system ID id # 

218 Customer system status num 1 

219 Price val # 

220 Price information yn # 

221 Price quote type num 1 

222 Share block an ..30 

223 Exchange rate quality num 1 

224 Exchange rate quality available yn # 

225 Exchange rate currency cur # 

226 Quote extension an ..5 

227 Country ctr # 

228 Country information an ..99 

229 Country code ctr # 

230 Information cache expiry num ..3 

231 Last scheduled date modifiable yn # 

232 Execute for the last time on vdat # 

233 Limit type an 1 

234 Limit days num ..3 

235 Post-dated cancellation possible yn # 

236 Foreign market segment an ..80 

237 Domestic market segment num 1 

238 Maximum buy price val # 

239 Maximum buy price, currency cur # 

240 Maximum number of orders num ..3 

241 Maximum number of C records num ..4 

242 Maximum number of entries num ..4 

243 Maximum number of T records num ..4 

244 Lines available for payment purpose num ..2 

245 Maximum field length for client name num ..3 

246 Maximum field length for beneficiary name num ..3 

247 Maximum field length for institution name of beneficiary num ..3 

248 Maximum field length for purpose num ..3 

249 Maximum length num ..4 

250 Maximum message size num ..4 

251 Maximum lead time num ..4 

252 Minimum commission amount, currency cur # 

253 Minimum commission amount, value val # 

254 Minimum subscription, denomination val ..15




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

31 


255 Minimum lead time num ..4 

256 Mixing permissible yn # 

257 Message reference, coded num 1 

258 Message size dig 12 

259 Message number num ..4 

260 Message reference number num ..4 

261 Name an ..35 

262 Name 1 an ..35 

263 Name 2 an ..35 

264 Account holder 1 dta ..27 

265 Account holder 2 dta ..27 

266 Name of account holder 1 an ..35 

267 Name of account holder 2 an ..35 

268 Nominal value, value val # 

269 New issues allowed yn # 

270 Non-booked transactions bin .. 

271 Nominal value val # 

272 Nominal value modifiable yn # 

273 Nominal value of capital adjustment val # 

274 Nominal interest rate val # 

275 New issues yn # 

276 Present user orders only yn # 

277 Present user restriction available yn # 

278 Standard package yn # 

279 Mode of operation, coded an ..3 

280 Portfolio order modifiable yn # 

281 Portfolio order information bin .. 

282 Ordering possible num 1 

283 Portfolio order number an ..99 

284 Old portfolio order number an ..99 

285 Portfolio order number allowed yn # 

286 Split portfolio order number an ..99 

287 Order split yn # 

288 Place an ..35 

289 Postal code an ..10 

290 Price limit modifiable yn # 

291 Price range, remarks txt ..80 

292 Product type num 1 

293 Product type foreign currency, traveller's checkcheques num 1 

294 Product name an ..25 

295 Product version an ..5 

296 Renewal extension period num ..3

Chapter: 

VIII 

Page: 

32 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 




297 Type of asset num 1 

298 Reference number id # 

299 Region num 1 

300 Region allowed yn # 

301 Yield val # 

302 Risk class of user an ..2 

303 Risk class of security an ..2 

304 Risk class of security, implications an ..38 

305 Role of security supplier, coded an ..3 

306 Response code dig 4 

307 Response parameters an ..35 

308 Response text an ..80 

309 Key type an 1 

310 Key number num ..3 

311 Key version num ..3 

312 Segment identifier an ..6 

313 Segment number num ..3 

314 Segment version num ..3 

315 Unusual currency yn # 

316 Security function code an ..3 

317 Security check reference an ..14 

318 Security reference number num ..16 

319 Security procedure, code an 3 

320 Signature algorithm, coded an ..3 

321 Debit/credit flag an 1 

322 Interest charges val # 

323 Cutoff for account movement data num ..4 

324 Cutoff for account movement data num ..4 

325 Blocking code an ..3 

326 Instrument data available yn # 

327 Standard package allowed yn # 

328 Standard unit num ..4 

329 Default language num ..3 

330 Status num ..2 

331 Street/P.O. Box an ..35 

332 Denominations possibility num 1 

333 Unit nominal value val # 

334 Search term allowed yn # 

335 Synchronisation mode num 1 

336 Telefax number an ..35 

337 Telephone an ..35 

338 Telephone number for confirmation an ..35 

339 Telephone number mandatory yn #




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

33 


340 Text key dig 2 

341 Text key and extension modifiable yn # 

342 Text key extension dig 3 

343 Subject an ..200 

344 Period length num ..2 

345 Period length modifiable yn # 

346 Period length in months dig ..24 

347 Period length in weeks dig ..104 

348 Period length account statement num 1 

349 Overdraft interest val # 

350 Time tim # 

351 Time of transmission tim # 

352 Portfolio movements bin .. 

353 Underlying an ..35 

354 Subsidiary account characteristic id # 

355 HBCI version supported num ..3 

356 Language supported num ..3 

357 UPD version num ..3 

358 Use of UPD num 1 

359 Validation result bin ..512 

360 User procedure an ..3 

361 Authorised to draw num 1 

362 Authorisation to draw num 1 

363 Payout amount, currency cur # 

364 Payout amount, value val # 

365 Clearing account modifiable num 1 

366 Clearing account mandatory yn # 

367 Type of dispatch account statement num 1 

368 Dispatch costs proportion, currency cur # 

369 Dispatch costs proportion, value val # 

370 Encryption algorithm, coded an ..3 

371 Version of filter function num ..3 

372 Document version dat # 

373 Version of security procedure num ..3 

374 Version number num ..3 

375 Administration charge val # 

376 Use of hash algorithm, coded an ..3 

377 Use of the signature algorithm, coded an ..3 

378 Use of encryption algorithm, coded an ..3 

379 Payment purpose modifiable yn # 

380 Purpose of public key an ..3 

381 Purpose, AZV an ..140 

382 Payment purpose line dta ..27

Chapter: 

VIII 

Page: 

34 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 




383 Start date dat # 

384 Currency cur # 

385 Currency of list of portfolio securities cur # 

386 Currency of list of portfolio securities available yn # 

387 Currency of terms and conditions cur # 

388 Currency of price quote cur # 

389 Currency name an ..35 

390 URL an ..256 

391 Other information txt ..2048 

392 Provide additional information yn # 

393 Other subscription information txt ..2048 

394 Value val # 

395 Value of the algorithm parameter, IV bin ..512 

396 Value of the algorithm parameter, key bin ..512 

397 Value of hash algorithm parameter bin ..512 

398 Exponent value bin ..512 

399 Modulus value bin ..512 

400 Security booking bin .. 

401 Type of security num ..3 

402 Type of security, text an ..99 

403 Security name an ..99 

404 Search term for security name an ..99 

405 Securities asset code an ..30 

406 Security group an ..2 

407 Securities group, text an ..35 

408 Notes on securities txt ..2048 

409 Information on security txt ..2048 

410 Detailed security information available yn # 

411 Securities category num 1 

412 Portfolio order bin .. 

413 Securities sales val # 

414 Important details mandatory yn # 

415 Reinvestment code num 1 

416 Reinvestment code modifiable yn # 

417 Reinvestment code on renewal num 1 

418 Reinvestment discount yn # 

419 Start date reinvestment discount dat # 

420 Reinvestment discount possible yn # 

421 Reinvestment discount von dat # 

422 Reinvestment discount, value val # 

423 Subscription possible yn # 

424 Subscription explanation txt ..200 

425 End subscription period dat #




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

35 


426 End subscription period, time tim # 

427 Start date subscription period dat # 

428 Start date subscription period, time tim # 

429 Subscription period, remarks txt ..80 

430 Registration time tim # 

431 Reference period an 1 

432 Time units an 1 

433 Time units modifiable yn # 

434 Time limit dat # 

435 Time limit modifiable yn # 

436 End date dat # 

437 Time period possible yn # 

438 Start date dat # 

439 Content of certificate bin ..2048 

440 Certificate type num 1 

441 Earned interest credit account modifiable yn # 

442 Interest method an 1 

443 Interest period num 1 

444 Rate of interest val # 

445 Queries supported num ..2 

446 Exchanges supported an ..4096 

447 Issue filter supported num 1 

448 Issuing parties supported an ..200 

449 Available categories an ..30 

450 Limit types supported an ..99 

451 Limit steps supported val ..15 

452 Limit limits supported an ..99 

453 Securities groups supported an ..35 

454 Order types supported an ..99 

455 Target country supported ctr # 

456 Additional scheduling alternatives num ..2 

457 Additional scheduling alternatives an ..296 

458 Additional scheduling alternatives, meaning an ..3563

Chapter: 

VIII 

Page: 

36 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



VIII.2.6 

HBCI Elements 

No. Name Type 8 

1 Termination message N 

2 Booked portfolio orders DE 

3 Maturity date DE 

4 Settlement currency DE 

5 euro allowed as settlement currency DE 

6 Local currency allowed as settlement currency DE 

7 Currency of temporary change of amount DE 

8 Alternative branch office DE 

9 Alternative delivery address DEG 

10 Temporary change of amount supported DE 

11 Temporary change of amount DE 

12 Different maturity account supported DE 

13 Different clearing account supported DE 

14 Different earned interest account supported DE 

15 Printed address DE 

16 Printed address possible DE 

17 Mailing address MVE 

18 Mailing address DEG 

19 All portfolios DE 

20 All accounts DE 

21 All accounts allowed DE 

22 Changing of a public key of the customer N 

23 Confirm modification of post-dated remittance SEG 

24 Request for public key SEG 

25 Information on value date of invoice DE 

26 Deposit amount DEG 

27 Maximum deposit DEG 

28 New deposit amount DEG 

29 Minimum deposit DEG 

30 Deposit date DE 

31 Deposit account DEG 

32 Old deposit account DEG 

33 Reply to anonymous session initialisation N 

34 Reply to session initialisation N 

8 

DE: Data Element or Group Data Element 

DEG: Data Element Group or Group Data Element 

MVE: (EMU) Element with multiple uses 

N: Message (German: Nachricht) 

SEG: Segment 

SF: Segment sequence




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

37 


35 Reply to communications settings request N 

36 Number of payments skipped DE 

37 Number of signatures needed DE 

38 Number of orders DE 

39 Number of business transactions DE 

40 Minimum number of signatures DE 

41 Number of post-dated modifications DE 

42 Number of post-dated interruptions DE 

43 Type of key data DE 

44 Type of export limit DE 

45 Type of import limit DE 

46 Type of limit DE 

47 Limit type modifiable DE 

48 Type of time limit DE 

49 Type of time limit modifiable DE 

50 Scroll reference DE 

51 Orders SF 

52 Client name, AZV DE 

53 Order comments DE 

54 Order filter DEG 

55 Order ID DE 

56 Old order ID DE 

57 Order ID supported DE 

58 Maturity account DEG 

59 Maturity account modifiable DE 

60 Export limit DEG 

61 Notice of execution DE 

62 Scheduled date DE 

63 Day of execution DE 

64 Scheduled date modifiable DE 

65 Days of the month available DE 

66 Days of the week available DE 

67 Issue markup DE 

68 Issue price DEG 

69 Executed portfolio orders DE 

70 International remittance SEG 

71 International funds transfer without text message SEG 

72 International funds transfer without text message parameters SEG 

73 International remittance - parameters SEG 

74 Delivery DE 

75 Delivery type DE 

76 Interruption end date DE 

77 Interruption start date DE

Chapter: 

VIII 

Page: 

38 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 




78 Interruption DEG 

79 Annual interruption DE 

80 Annual interruption allowed DE 

81 Type of interruption possible DE 

82 Changeover check reference DE 

83 General bank parameters SEG 

84 Bank parameter data SF 

85 Processing price, currency DE 

86 Processing price, value DE 

87 Request processing status financial data format SEG 

88 Processing status financial data format Parameter SEG 

89 Return processing status financial data format SEG 

90 Beneficiary DEG 

91 Beneficiary possible DE 

92 Account to be debited DEG 

93 Account to be debited modifiable DE 

94 Remarks DE 

95 User ID DE 

96 Range of the security application, coded DE 

97 Amount already drawn on DEG 

98 Description DE 

99 Special instructions DE 

100 Show all post-dated multiple payments SEG 

101 Pending post-dated multiple payments - parameters SEG 

102 Pending post-dated multiple payments SEG 


104 Show post-dated multiple payments - parameters SEG 


106 Show outstanding post-dated remittances SEG 

107 Show outstanding post-dated remittances - parameters SEG 

108 Outstanding post-dated remittances SEG 

109 Confirmation of key blocking SEG 

110 Confirmation of key blocking by the bank N 

111 Existing deposit account supported DE 

112 Order conditions DEG 

113 Order conditions required DE 

114 Order DEG 

115 Amount of payment MVE 

116 Amount of payment DEG 

117 Amount modifiable DE 

118 Subject DE 

119 Code for algorithm parameter, IV DE 

120 Code for algorithm parameter, key DE




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

39 


121 Code for exponent DE 

122 Code for function type DE 

123 Code for hash algorithm parameter DE 

124 Code for modulus DE 

125 Code for security party DE 

126 Reference data element DE 

127 Reference message DEG 

128 Reference segment DE 

129 Reference ratio DE 

130 End date DE 

131 End financial institution ID DEG 

132 Exchange DE 

133 Exchange information DEG 

134 BPD version DE 

135 Branch DE 

136 Rate asked/selling rate DE 

137 Postal address DEG 

138 Rate asked DE 

139 Balance booking date DE 

140 Balance booking time DE 

141 CID DE 

142 Data, encrypted DE 

143 Data segments SF 

144 Date DE 

145 Date of transmission DE 

146 Date and time indicator, coded DE 

147 Registration date DE 

148 Modify standing order SEG 

149 Modify standing order - parameters SEG 

150 Interrupt standing order SEG 

151 Interrupt standing order - parameters SEG 

152 Set up a standing order SEG 

153 Standing order setup - parameters SEG 

154 Cancel standing order SEG 

155 Cancel standing order - parameters SEG 

156 Standing order details DEG 

157 Confirm modification of standing order SEG 

158 Show pending standing order modifications SEG 

159 Pending standing order modifications - parameters SEG 

160 Pending standing order modifications SEG 

161 Confirmation of standing order interruption SEG 

162 Show all standing orders SEG 

163 Standing orders - parameters SEG

Chapter: 

VIII 

Page: 

40 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 




164 Standing orders SEG 

165 Confirm standing order set up SEG 

166 Portfolio account DEG 

167 Portfolio required DE 

168 List of portfolio securities DE 

169 Request for list of portfolio securities SEG 

170 List of portfolio securities - parameters SEG 

171 Return list of portfolio securities SEG 

172 Portfolio securities bank charge DE 

173 Request portfolio account statement SEG 

174 Portfolio statement - parameters SEG 

175 Portfolio statement SEG 

176 Portfolio currency DE 

177 Request exchange rate SEG 

178 Exchange rate parameters SEG 

179 Return exchange rate SEG 

180 Session end N 

181 Anonymous session end N 

182 Session end SEG 

183 Session ID DE 

184 Session initialisation N 

185 Session initialisation for anonymous access N 

186 Session language DE 

187 Dividends DEG 

188 DTA data record DE 

189 DTAZV data record DE 

190 End early order deadline DE 

191 End early order deadline, remarks DE 

192 End early order deadline, time DE 

193 Own account DE 

194 Import limit DEG 

195 Maximum entries supported DE 

196 Quote units DE 

197 Type of payment DE 

198 Rate of payment DE 

199 Confirm submission of post-dated multiple direct debit SEG 

200 Confirm submission of post-dated multiple payment SEG 

201 Confirm post-dated remittance SEG 

202 Confirm subscription submission SEG 

203 Date submitted DE 

204 Single direct debit SEG 

205 Single remittance SEG 

206 Single remittance - parameters SEG




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

41 


207 E-mail address DE 

208 Issue date DE 

209 Issue price DEG 

210 Issue price, remarks DE 

211 Issues status DE 

212 Issues volumes DE 

213 Issuing party DE 

214 Address DE 

215 Beneficiary name modifiable DE 

216 Beneficiary name, AZV DE 


218 Order allowed DE 

219 Business transactions allowed DEG 

220 Allowed type of denomination DE 

221 Remarks DE 

222 Order to be resubmitted DE 

223 Opening date DE 

224 Opening price DEG 

225 First day of trading DE 

226 First day of trading, remarks DE 

227 First interest due date DE 

228 First scheduled date modifiable DE 

229 Initial request for key of bank N 

230 Initial transmission of keys of bank N 

231 Initial transmission of keys of customer N 

232 Execute for the first time on DE 


234 Modify fixed-term deposit - parameters SEG 

235 Confirm fixed-term deposit modification SEG 

236 Modify fixed-term deposit SEG 

237 Renew fixed-term deposit SEG 

238 Show fixed-term deposits SEG 

239 Fixed-term deposit inventory - parameters SEG 

240 Fixed-term deposit inventory SEG 

241 Fixed-term deposit terms DEG 

242 Request fixed-term deposit terms and conditions SEG 

243 Fixed-term deposit terms and conditions - parameters SEG 

244 Return fixed-term deposit terms and conditions SEG 

245 New fixed-term deposit SEG 

246 Confirm new fixed-term deposit SEG 

247 New fixed-term deposit - parameters SEG 

248 Revoke fixed-term deposit SEG 

249 Revoke fixed-term deposit - parameters SEG

Chapter: 

VIII 

Page: 

42 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 




250 Confirm renewal of fixed-term deposit SEG 

251 Renewal of fixed-term deposit - parameters SEG 

252 Do not renew fixed-term deposit SEG 

253 Do not renew fixed-term deposit - parameters SEG 

254 Fixed-term deposit status DE 

255 Request for fixed-price offers SEG 

256 Fixed-price offers - parameters SEG 

257 Fixed-price offers available SEG 

258 Fixed-price offer number DE 

259 Fixed-price order SEG 

260 Confirm fixed-price statement SEG 

261 Fixed-price order parameters SEG 

262 Filter new issues DE 

263 Filter function DE 

264 Financial data format DE 

265 Request financial data format SEG 

266 Request financial data format parameters SEG 

267 Return financial data format SEG 

268 Transmit financial data format SEG 

269 Transmit financial data format parameters SEG 

270 Request financial data format list SEG 

271 Request financial data format list Pparameters SEG 

272 Return financial data format list SEG 

273 Submit fund order SEG 

274 Fund order parameters SEG 

275 Confirm fund order submission SEG 

276 Document format DE 

277 Format name DE 

278 Format details DEG 

279 Format details, coded DE 

280 Format type DE 

281 Format version DE 

282 Form DEG 

283 Form name DE 

284 Form code DE 

285 Exemption amount DEG 

286 Request exemption date SEG 

287 Exemption data parameters SEG 

288 Return exemption data SEG 

289 Plain text details DEG 

290 Plain text message DE 

291 Foreign currency DE 

292 Guest message SEG




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

43 


293 Guest message - parameters SEG 

294 Booked transactions DE 

295 Current balance DEG 

296 Date of birth DE 

297 Beneficiary's date of birth DE 

298 Buying rate DE 

299 Buying rate DE 

300 Total amount, currency DE 

301 Total amount, value DE 

302 Branch office DE 

303 Transaction DE 

304 Cancelled portfolio orders DE 

305 Quantity required DE 

306 Required scheduled date DE 

307 Required scheduled date supported DE 

308 Graphics DE 

309 Graphics format DE 

310 Greenshoe DE 

311 Valid from DE 

312 Valid to DE 

313 Validity duration floor DE 

314 Validity duration XETRA DE 

315 Validity date DEG 

316 Credit interest DE 

317 Trading type DE 

318 Trading type XETRA DE 

319 Currency of exchange DE 

320 Hash algorithm DEG 

321 Hash algorithm, coded DE 

322 HBCI version DE 

323 Registered place of trade DE 

324 Maximum amount in foreign currency, currency DE 

325 Maximum amount in foreign currency, value DE 

326 Maximum amount in national currency, currency DE 

327 Maximum amount in national currency, value DE 

328 Stockholders meeting DE 

329 Beneficiary IBAN DE 

330 IBAN specification possible DE 

331 Identification SEG 

332 Identification of the party DE 

333 Information DEG 

334 Request information SEG 

335 Requested information SEG

Chapter: 

VIII 

Page: 

44 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 




336 Information request - parameters SEG 

337 Document type DE 

338 Information code DE 

339 Information codes DEG 

340 Name of beneficiary's institution, AZV DE 

341 Year of validity DE 

342 High for the year DEG 

343 Low for the year DEG 

344 Capital adjustments DE 

345 Card DE 

346 Card display SEG 

347 Request card display SEG 

348 Card display parameters SEG 

349 Card type DE 

350 Card serial number DE 

351 Card limit DEG 

352 Card number DE 

353 Apply for card block SEG 

354 Apply for card block parameters SEG 

355 Spot rate DEG 

356 Category of key data DE 

357 Minimum order amount DE 

358 Minimum amount DEG 

359 Smallest step DEG 

360 Commission DE 

361 Communications address DE 

362 Communications address suffix DE 

363 Communications service DE 

364 Communications parameter DEG 

365 Communications access N 

366 Request communications settings SEG 

367 Communications settings - parameters SEG 

368 Return Fetch communications settings SEG 

369 Compression function DE 

370 Compression procedure SEG 

371 Compression version DE 

372 Conditions type DE 

373 Terms name DE 

374 Terms ID DE 

375 Terms version DE 

376 Consortium leader DE 

377 Contingent information DE 

378 Account or portfolio no. DE




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

45 


379 Account type DE 

380 Account statement code DE 

381 Account statement code modifiable DE 

382 Account information SEG 

383 Request account details SEG 

384 Account details parameters SEG 

385 Return account details SEG 

386 Spending limit DEG 

387 Account type DE 

388 New account movements SEG 

389 Account movements during specified period SEG 

390 Return new account movements SEG 

391 Account movements during specified period SEG 

392 New account movements - parameters SEG 

393 Account movements during specified period - parameters SEG 

394 Account DEG 

395 Account MVE 

396 Customer account DEG 

397 Beneficiary account DEG 

398 Account details beneficiary modifiable DE 

399 Account to be debited/credited DEG 

400 Account currency DE 

401 Contract reference DE 

402 Old contract reference DE 

403 Cost unit DE 

404 Request customer information SEG 

405 Customer information - parameters SEG 

406 Customer information SEG 

407 Bank name DE 

408 Bank code DE 

409 Bank ID DEG 

410 Bank ID MVE 

411 Bank message SEG 

412 Generic bank message N 

413 Overdraft limit DEG 

414 Bank officer name DE 

415 Customer ID DE 

416 Customer message SEG 

417 Customer message - parameters SEG 

418 Generic customer message N 

419 General anonymous customer message N 

420 Customer system ID DE 

421 Customer system status DE

Chapter: 

VIII 

Page: 

46 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 




422 Price DE 

423 Price data DEG 

424 Price information DE 

425 Price quote type DE 

426 Share block DE 

427 Exchange rate quality DE 

428 Exchange rate quality available DE 

429 Exchange rate currency DE 

430 Quote extension DE 

431 Country DE 

432 Country information DE 

433 Country code DE 

434 Information cache expiry DE 

435 Direct debit - parameters SEG 

436 Latest quote DEG 

437 Last scheduled date modifiable DE 

438 Execute for the last time on DE 

439 Limit type DE 

440 Limit amount DEG 

441 Limit days DE 

442 List of new issues SEG 

443 Request list of new issues SEG 

444 List of new issues parameters SEG 

445 Post-dated cancellation possible DE 

446 Foreign market segment DE 

447 Domestic market segment DE 

448 Maximum buy price DE 

449 Maximum buy price, currency DE 

450 Maximum number of orders DE 

451 Maximum number of C records DE 

452 Maximum number of entries DE 

453 Maximum number of T records DE 

454 Lines available for payment purpose DE 

455 Maximum field length for client name DE 

456 Maximum field length for beneficiary name DE 

457 Maximum field length for institution name of beneficiary DE 

458 Maximum field length for purpose DE 

459 Maximum length DE 

460 Maximum message size DE 

461 Maximum lead time DE 

462 Minimum order amount DEG 

463 Minimum commission amount, currency DE 

464 Minimum commission amount, value DE




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

47 


465 Minimum subscription, amount DEG 

466 Minimum subscription, denomination DE 

467 Minimum lead time DE 

468 Mixing permissible DE 

469 After hours DEG 

470 Message end SEG 

471 Message reference, coded DE 

472 Message size DE 

473 Message header SEG 

474 Message number DE 

475 Message reference number DE 

476 Name DE 

477 Name 1 DE 

478 Name 2 DE 

479 Account holder 1 DE 

480 Account holder 2 DE 

481 Name of account holder 1 DE 

482 Name of account holder 2 DE 

483 Nominal value DEG 

484 Nominal value, value DE 

485 Nominal values DEG 

486 Subscribe for new issue SEG 

487 Subscribe for new issue parameters SEG 

488 New issues allowed DE 

489 Non-booked transactions DE 

490 Nominal value DE 

491 Nominal value modifiable DE 

492 Nominal value of capital adjustment DEG 

493 Nominal interest rate DE 

494 New issues DE 

495 Present user orders only DE 

496 Present user restriction available DE 

497 Standard package DE 

498 Outstanding orders DE 

499 Public key DEG 

500 Mode of operation, coded DE 

501 Portfolio order modifiable DE 

502 Portfolio order information SEG 

503 Request portfolio order information SEG 

504 Portfolio order information parameters SEG 

505 Ordering possible DE 

506 Portfolio order number DE 

507 Old portfolio order number DE

Chapter: 

VIII 

Page: 

48 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 




508 Portfolio order number supported DE 

509 Split portfolio order number DE 

510 Ordersplitt DE 

511 Orderstatus SEG 

512 Request order status SEG 

513 Order status parameters SEG 

514 Place DE 

515 Parameters DEG 

516 International remittance - parameters DEG 

517 International remittance without text message parameters DEG 

518 Show outstanding post-dated remittances - parameters DEG 

519 Modify standing order - parameters DEG 

520 Interrupt standing order - parameters DEG 

521 Standing order setup - parameters DEG 

522 Cancel standing order - parameters DEG 

523 List of portfolio securities - parameters DEG 

524 Portfolio statement - parameters DEG 

525 Exchange rate parameters DEG 

526 Single remittance/direct debit parameters DEG 

527 Modify fixed-term deposit - parameters DEG 

528 Fixed-term deposit terms and conditions - parameters DEG 

529 New fixed-term deposit - parameters DEG 

530 Fixed-price offers - parameters DEG 

531 Fixed-price order parameters DEG 

532 Request financial data format parameters DEG 

533 Transmit financial data format parameters DEG 

534 Fund order parameters DEG 

535 Block card parameters DEG 

536 New account movements - parameters DEG 

537 Account movements during specified period - parameters DEG 

538 Customer/guest message parameters DEG 

539 List of new issues parameter DEG 

540 Subscribe for new issue parameters DEG 

541 Portfolio order information parameters DEG 

542 Order status parameters DEG 

543 Multiple remittance/direct debit parameters DEG 

544 Foreign currency and traveller's checkcheque order parameters DEG 

545 Foreign currency and traveller's checkcheque conditions parameters DEG 

546 Modify post-dated remittance - parameters DEG 

547 Submit post-dated remittance - parameters DEG 

548 Blank form order - parameters DEG 

549 Security details - parameters DEG 

550 Security prices - parameters DEG




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

49 


551 Portfolio order - parameters DEG 

552 Portfolio order modification - parameters DEG 

553 Portfolio order history - parameters DEG 

554 Portfolio order cancellation - parameters DEG 

555 Security referencßßße information - parameters DEG 

556 Instrument data - parameters DEG 

557 Key data - parameters DEG 

558 Parameter data SF 

559 Postal code DE 

560 Price limit DEG 

561 Price limit modifiable DE 

562 Price range to DEG 

563 Price range from DEG 

564 Price range, remarks DE 

565 Product type DE 

566 Product type foreign currency, traveller's checkcheques DE 

567 Product name DE 

568 Product version DE 

569 Renewal DEG 

570 Renewal extension period DE 

571 Type of asset DE 

572 Reference account DEG 

573 Reference number DE 

574 Region DE 

575 Region allowed DE 

576 Yield DE 

577 Remaining exemption amount DEG 

578 Risk class of user DE 

579 Risk class of security DE 

580 Risk class of security, implications DE 

581 Role of security supplier, coded DE 

582 Response DEG 

583 Segment-level response SEG 

584 Message-level response SEG 

585 Response code DE 

586 Response parameters DE 

587 Response text DE 

588 Repurchase price DEG 

589 Show balance SEG 

590 Show balance - parameters SEG 

591 Balance SEG 

592 Balance MVE 

593 Balance including pending transactions DEG

Chapter: 

VIII 

Page: 

50 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 




594 Multiple direct debit SEG 

595 Multiple direct debit - parameters SEG 

596 Multiple remittance SEG 

597 Multiple payment - parameters SEG 

598 Change key SEG 

599 Key type DE 

600 Key name DEG 

601 Key number DE 

602 Block key SEG 

603 Key version DE 

604 Segment identifier DE 

605 Segment header DEG 

606 Segment number DE 

607 Segment version DE 

608 Unusual currency DE 

609 Security date and time DEG 

610 Security function code DE 

611 Security identification, Details DEG 

612 Security check reference DE 

613 Security reference number DE 

614 Security procedure SEG 

615 Security procedure, code DE 

616 Signature closer SEG 

617 Signature algorithm DEG 

618 Signature algorithm, coded DE 

619 Signature header SEG 

620 Debit/credit flag DE 

621 Interest charges DE 

622 Foreign currency and traveller's checkcheque order SEG 

623 Foreign currency and traveller's checkcheque order parameters SEG 

624 Request foreign curreny and traveller's checkcheque conditions SEG 

625 Foreign curreny and traveller's checkcheque conditions parameters SEG 

626 Foreign curreny and traveller's checkcheque conditions reponse SEG 

627 Cutoff for account movement data DE 

628 Cutoff for account movement data DE 

629 Blocking code DE 

630 Blocking of a key by the customer N




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

51 


631 Instrument data shares DEG 

632 Instrument data fund DEG 

633 Instrument data available DE 

634 Instrument data warrants DEG 

635 Instrument data pension DEG 

636 Standard package allowed DE 

637 Standard unit DE 

638 Default language DE 

639 Status DE 

640 Request status log SEG 

641 Status log - parameters SEG 

642 Status log response SEG 

643 Street/P.O. Box DE 

644 Denomination possibilitiy DE 

645 Denomination possibilities DEG 

646 Unit nominal value DE 

647 Search term allowed DE 

648 Total sum for all orders DEG 

649 Sychronisation SEG 

650 Synchronisation reply SEG 

651 Synchronisation reply message N 

652 Synchronisation mode DE 

653 Synchronisation message N 

654 Telefax number DE 

655 Telephone DE 

656 Telephone number for confirmation DE 

657 Telephone number mandatory DE 

658 Submit post-dated multiple direct debit SEG 

659 Submit post-dated multiple direct debit - parameters SEG 

660 Cancel post-dated multiple payment SEG 

661 Cancel post-dated multiple payment - parameters SEG 

662 Submit post-dated multiple payment SEG 

663 Submit post-dated multiple payment - parameters SEG 

664 Cancel post-dated multiple payment SEG 

665 Cancel post-dated multiple payment - parameters SEG 

666 Modify post-dated remittance SEG 

667 Modify post-dated remittance - parameters SEG 

668 Submit post-dated remittance SEG 

669 Submit post-dated remittance - parameters SEG 

670 Cancel post-dated remittance SEG 

671 Cancel post-dated remittance - parameters SEG 

672 Request appointment with bank officer SEG 

673 Bank officer appointment - parameters SEG

Chapter: 

VIII 

Page: 

52 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 




674 Text key DE 

675 Text key and extension modifiable DE 

676 Text key extension DE 

677 Subject DE 

678 Period length DE 

679 Period length modifiable DE 

680 Period length in months DE 

681 Period length in weeks DE 

682 Turnus account statement DE 

683 Public key transmission SEG 

684 Overdraft interest DE 

685 Time DE 

686 Time of transmission DE 

687 Reclassification SEG 

688 Reclassification parameters SEG 

689 Portfolio movements DE 

690 Underlying DE 

691 Subsidiary account characteristic DE 

692 HBCI version supported DE 

693 HBCI versions supported DEG 

694 Compression procedures supported DEG 

695 Security procedures supported DEG 

696 Language supported DE 

697 Languages supported DEG 

698 UPD version DE 

699 Use of UPD DE 

700 General user parameters SEG 

701 User parameter data SF 

702 Validation result DE 

703 General bank parametersCustomer system preferences SEG 

704 User procedure DE 

705 Available funds DEG 

706 Authorised to draw DEG 

707 Authorised to draw DE 

708 Authorisation to draw DE 

709 Payout amount, currency DE 

710 Payout amount, value DE 

711 Clearing account DEG 

712 Clearing account modifiable DE 

713 Clearing account mandatory DE 

714 Type of dispatch account statement DE 

715 Dispatch costs proportion, currency DE 

716 Dispatch costs proportion, value DE




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

53 


717 Encrypted data SEG 

718 Encrypted message N 

719 Encryption algorithm DEG 

720 Encryption algorithm, coded DE 

721 Encryption header SEG 

722 Version of filter function DE 

723 Document version DE 

724 Version of terms and conditions DEG 

725 Version of security procedure DE 

726 Version number DE 

727 Administration charge DE 

728 Use of hash algorithm, coded DE 

729 Use of the signature algorithm, coded DE 

730 Use of encryption algorithm, coded DE 

731 Payment purpose DEG 

732 Payment purpose modifiable DE 

733 Purpose of public key DE 

734 Purpose, AZV DE 

735 Payment purpose line DE 

736 Start date DE 

737 Start bank ID DEG 

738 Pre-opening DEG 

739 Blank form order SEG 

740 Blank form order - parameters SEG 

741 Registration time and date DEG 

742 Previous day DEG 

743 Currency DE 

744 Currency of list of portfolio securities DE 

745 Currency of list of portfolio securities available DE 

746 Currency of terms and conditions DE 

747 Currency of price quote DE 

748 Currency name DE 

749 URL DE 

750 Other information DE 

751 Provide additional information DE 

752 Other subscription information DE 

753 Value DE 

754 Value of the algorithm parameter, IV DE 

755 Value of the algorithm parameter, key DE 

756 Value of hash algorithm parameter DE 

757 Exponent value DE 

758 Modulus value DE

Chapter: 

VIII 

Page: 

54 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 




759 Security booking DE 

760 Type of security DE 

761 Type of security, text DE 

762 Security name DE 

763 Search term for security name DE 

764 Securities asset code DE 

765 Securities asset groups DEG 

766 Security group DE 

767 Security group, text DE 

768 Notes on securities DE 

769 Information on security DE 

770 Request security details SEG 

771 Detailed security information available DE 

772 Security details - parameters SEG 

773 Security details SEG 

774 Securities category DE 

775 Request security prices SEG 

776 Security prices - parameters SEG 

777 Security prices SEG 

778 Portfolio order DE 

779 Present portfolio order SEG 

780 Portfolio order - parameters SEG 

781 Modify portfolio order SEG 

782 Confirm portfolio order modification SEG 

783 Portfolio order modification - parameters SEG 

784 Confirm submission of portfolio order SEG 

785 Portfolio order history SEG 

786 Request portfolio order history SEG 

787 Portfolio order history - parameters SEG 

788 Cancel portfolio order SEG 

789 Confirm portfolio order cancellation SEG 

790 Portfolio order cancellation - parameters SEG 

791 Security reference DEG 

792 Request for security reference SEG 

793 Security reference information - parameters SEG 

794 Security reference number information SEG 

795 Request instrument data SEG 

796 Instrument data - parameters SEG 

797 Instrument data SEG 

798 Securities sales DE 

799 Value date of invoice DE 

800 Key data DEG 

801 Request key data SEG




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

55 


802 Key data - parameters SEG 

803 Return key data SEG 

804 Important details mandatory DE 

805 Reinvestment code DE 

806 Reinvestment code modifiable DE 

807 Reinvestment code on renewal DE 

808 Reinvestment discount DE 

809 End date reinvestment discount DE 

810 Reinvestment discount possible DE 

811 Start date reinvestment discount DE 

812 Reinvestment discount, value DE 

813 Subscription possible DE 

814 Subscription explanation DE 

815 End subscription period DE 

816 End subscription period, time DE 

817 Start date subscription period DE 

818 Start date subscription period, time DE 

819 Subscription period, remarks DE 

820 Registration time DE 

821 Reference period DE 

822 Time units DE 

823 Time units modifiable DE 

824 Time limit DE 

825 Time limit modifiable DE 

826 End date DE 

827 Time period possible DE 

828 Start date DE 

829 Certificate DEG 

830 Content of certificate DE 

831 Certificate type DE 

832 Earned interest expected DEG 

833 Earned interest account DEG 

834 Earned interest credit account modifiable DE 

835 Interest method DE 

836 Interest period DE 

837 Rate of interest DE 

838 Queries supported DE 

839 Exchanges supported DE 

840 Issue filter supported DE 

841 Issuing parties supported DE 

842 Available categories DE 

843 Limit types supported DE 

844 Limit steps supported DE

Chapter: 

VIII 

Page: 

56 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 




845 Order types supported DE 

846 Securities groups supported DE 

847 Limit limits supported DE 

848 Target country supported DE 

849 Additional scheduling alternatives DE 

850 Additional scheduling alternatives DE 

851 Additional scheduling alternatives, implications DE



Section: Overview of message structure 

Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

57 

VIII.3 Overview of message structure 

The sequence and number of messages that may be exchanged are depicted in the 

tables below for the following types of session: 

• Standard session 

• Anonymous session 

• Synchronisation 

• Retrieval of communications settings 

• Changing customer public key 

• Initial retrieval of financial institution public key 

• Initial transmission of customer public key 

• Key blocking by the customer (RDH) 

• Key blocking by the customer (DDV) 

The presence of the segments HNVSK and HNVSD indicates whether the message is 

encrypted. In this case the encrypted segments are indented.

Chapter: 

VIII 

Page: 

58 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 


Overview of message structure 

VIII.3.1 

Standard session




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

59 

Message 

Segment Session initialisation Order message Session end 

Customer Financial 

institution 


institution 


institution 

N6 N2 N15 N14 N8 N14 

Message 1 1 0-n 0-n 1 1 

HNHBK 1 1 1 1 1 1 

HNVSK 1 1 1 1 1 1 

HNVSD 1 1 1 1 1 1 

HNSHK 1 0-1 0-3 0-1 1 0-1 

HIRMG - 1 - 1 - 1 

HIRMS - 0-m 9 - 0-m - 0-m 

HKIDN 1 - - - - - 

HKVVB 1 - - - - - 

HKISA 0/1-2 10 - - - - - 

HKSYN - - - - - - 

HIBPA - 0-1 - - - - 

HIKOM - 0-1 - - - - 

HISHV - 0-1 - - - - 

HIKPV - 0-1 - - - - 

HIUEBS - 0-n - - - - 

... 11 - 0-n - - - - 

HIUPA - 0-1 - - - - 

HIUPD - 0-n - - - - 

HIISA - 0/0-2 - - - - 

HISYN - - - - - - 

HIKIM - 0-n - - - - 

HKSAL 

12 

- - 1 - - - 

HISAL - - - 0-1 n - - 

... - - - - - - 

HKPRO - - 0-1 - - - 

HIPRO - - - 0- n - - 

HKSAK - - - - - - 

HKSSP - - - - - - 

HISSP - - - - - - 

HKKOM - - - - - - 

HIKOM - - - - - - 

HKEND - - - - 1 - 

9 

10 

11 

12 

m is the total number of segments in the customer message 

The expression ‘n/m’ is used to indicate a difference between symmetrical ("n") and asymmetrical ("m") 

procedure. 

Parameter segments for any other supported business transactions go here. 

From the group of order segments, only one business transaction type per message is allowed at 

present. The example of a ”Show balance” business transaction is used here.

Chapter: 

VIII 

Page: 

60 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



Message 



institution 


institution 


institution 

N6 N2 N15 N14 N8 N14 

HNSHA 1 0-1 1-3 0-1 1 0-1 

HNHBS 1 1 1 1 1 1




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

61 

VIII.3.2 

Anonymous session 

Message 



institution 


institution 


institution 

N7 N3 N16 N14 N9 N14 

Message 1 1 0-n 0-n 1 1 

HNHBK 1 1 1 1 1 1 

HNSHK - - - - - - 

HIRMG - 1 - 1 - 1 

HIRMS - 0-m - 0-m - 0-m 

HKIDN 1 - - - - - 

HKVVB 1 - - - - - 

HKISA - - - - - - 

HKSYN - - - - - - 

HIBPA - 0-1 - - - - 

HIKOM - 0-1 - - - - 

HISHV - 0-1 - - - - 

HIKPV - 0-1 - - - - 

HIUEBS - 0-n - - - - 

... - 0-n - - - - 

HIUPA - 0-1 - - - - 

HIUPD - 0-n - - - - 

HIISA - - - - - - 

HISYN - - - - - - 

HIKIM - 0-n - - - - 

HKSAL 13 - - - - - - 

HISAL - - - - - - 

... - - 0-n 0-n - - 

HKPRO - - - - - - 

HIPRO - - - - - - 

HKSAK - - - - - - 

HKSSP - - - - - - 

HISSP - - - - - - 

HKKOM - - - - - - 

HIKOM - - - - - - 

HKEND - - - - 1 - 

HNSHA - - - - - - 

HNHBS 1 1 1 1 1 1 

13 

Here, the customer can send order segments that do not need to be signed. A list of which business 

transactions do not need to be signed is included in the guest UPD sent by the financial institution.

Chapter: 

VIII 

Page: 

62 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



VIII.3.3 

Synchronisation 

Message 



institution 


institution 


institution 

N18 N19 N8 N14 

Message 1 1 0 0 1 1 

HNHBK 1 1 - - 1 1 

HNVSK 1 1 1 1 1 1 

HNVSD 1 1 1 1 1 1 

HNSHK 1 0-1 - - 1 0-1 

HIRMG - 1 - - - 1 

HIRMS - 0-m - - - 0-m 

HKIDN 1 - - - - - 

HKVVB 1 - - - - - 

HKISA 0/1-2 - - - - - 

HKSYN 1 - - - - - 

HIBPA - 0-1 - - - - 

HIKOM - 0-1 - - - - 

HISHV - 0-1 - - - - 

HIKPV - 0-1 - - - - 

HIUEBS - 0-n - - - - 

... - 0-n - - - - 

HIUPA - 0-1 - - - - 

HIUPD - 0-n - - - - 

HIISA - 0/0-2 - - - - 

HISYN - 1 - - - - 

HIKIM - 0-n - - - - 

HKSAL - - - - - - 

HISAL - - - - - - 

... - - - - - - 

HKPRO - - - - - - 

HIPRO - - - - - - 

HKSAK - - - - - - 

HKSSP - - - - - - 

HISSP - - - - - - 

HKKOM - - - - - - 

HIKOM - - - - - - 

HKEND - - - - 1 - 

HNSHA 1 0-1 - - 1 0-1 

HNHBS 1 1 - - 1 1




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

63 

VIII.3.4 

Communications access 

Message 


Customer 

Financial 

institution 

Customer 

Financial 

institution 

Customer 

Financial 

institution 

N7 N3 N13 N4 N9 N14 

Message 1 1 1 1 1 1 

HNHBK 1 1 1 1 1 1 

HNSHK - - - - - - 

HIRMG - 1 - 1 - 1 

HIRMS - 0-m - 0-m - 0-m 

HKIDN 1 - - - - - 

HKVVB 1 - - - - - 

HKISA - - - - - - 

HKSYN - - - - - - 

HIBPA - 0-1 - - - - 

HIKOM - 0-1 - - - - 

HISHV - 0-1 - - - - 

HIKPV - 0-1 - - - - 

HIUEBS - 0-n - - - - 

... - 0-n - - - - 

HIUPA - 0-1 - - - - 

HIUPD - 0-n - - - - 

HIISA - - - - - - 

HISYN - - - - - - 

HIKIM - - - - - - 

HKSAL - - - - - - 

HISAL - - - - - - 

... - - - - - - 

HKPRO - - - - - - 

HIPRO - - - - - - 

HKSAK - - - - - - 

HKSSP - - - - - - 

HISSP - - - - - - 

HKKOM - - 1 - - - 

HIKOM - - - 0-n - - 

HKEND - - - - 1 - 

HNSHA - - - - - - 

HNHBS 1 1 1 1 1 1

Chapter: 

VIII 

Page: 

64 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



VIII.3.5 

Changing customer public key (RDH) 

Message 



institution 


institution 


institution 

N6 N2 N1 N14 N8 N14 

Message 1 1 1 1 1 1 

HNHBK 1 1 1 1 1 1 

HNVSK 1 1 1 1 1 1 

HNVSD 1 1 1 1 1 1 

HNSHK 1 0-1 1 0-1 1 0-1 

HIRMG - 1 - 1 - 1 

HIRMS - 0-m - 0-m - 0-m 

HKIDN 1 - - - - - 

HKVVB 1 - - - - - 

HKISA 0/1-2 - - - - - 

HKSYN - - - - - - 

HIBPA - 0-1 - - - - 

HIKOM - 0-1 - - - - 

HISHV - 0-1 - - - - 

HIKPV - 0-1 - - - - 

HIUEBS - 0-n - - - - 

... - 0-n - - - - 

HIUPA - 0-1 - - - - 

HIUPD - 0-n - - - - 

HIISA - 0/0-2 - - - - 

HISYN - - - - - - 

HIKIM - 0-n - - - - 

HKSAL - - - - - - 

HISAL - - - - - - 

... - - - - - - 

HKPRO - - - - - - 

HIPRO - - - - - - 

HKSAK - - 1-2 - - - 

HKSSP - - - - - - 

HISSP - - - - - - 

HKKOM - - - - - - 

HIKOM - - - - - - 

HKEND - - - - 1 - 

HNSHA 1 0-1 1 0-1 1 0-1 

HNHBS 1 1 1 1 1 1




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

65 

VIII.3.6 

Initial request for financial institution public key (RDH) 

Message 



institution 


institution 


institution 

N10 N11 N9 N14 

Message 1 1 0 0 1 1 

HNHBK 1 1 - - 1 1 

HNSHK - 0-1 - - - 0-1 

HIRMG - 1 - - - 1 

HIRMS - 0-m - - - 0-m 

HKIDN 1 - - - - - 

HKVVB 1 - - - - - 

HKISA 2 - - - - - 

HKSYN - - - - - - 

HIBPA - 0-1 - - - - 

HIKOM - 0-1 - - - - 

HISHV - 0-1 - - - - 

HIKPV - 0-1 - - - - 

HIUEBS - 0-n - - - - 

... - 0-n - - - - 

HIUPA - - - - - - 

HIUPD - - - - - - 

HIISA - 1-2 - - - - 

HISYN - - - - - - 

HIKIM - - - - - - 

HKSAL - - - - - - 

HISAL - - - - - - 

... - - - - - - 

HKPRO - - - - - - 

HIPRO - - - - - - 

HKSAK - - - - - - 

HKSSP - - - - - - 

HISSP - - - - - - 

HKKOM - - - - - - 

HIKOM - - - - - - 

HKEND - - - - 1 - 

HNSHA - 0-1 - - - 0-1 

HNHBS 1 1 - - 1 1

Chapter: 

VIII 

Page: 

66 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



VIII.3.7 

Initial transmission of customer public key (RDH) 

Message 



institution 


institution 


institution 

N12 N14 N8 N14 

Message 1 1 0 0 1 1 

HNHBK 1 1 - - 1 1 

HNVSK 1 1 - - 1 1 

HNVSD 1 1 - - 1 1 

HNSHK 1 0-1 - - - 0-1 

HIRMG - 1 - - - 1 

HIRMS - 0-m - - - 0-m 

HKIDN 1 - - - - - 

HKVVB - - - - - - 

HKISA - - - - - - 

HKSYN - - - - - - 

HIBPA - - - - - - 

HIKOM - - - - - - 

HISHV - - - - - - 

HIKPV - - - - - - 

HIUEBS - - - - - - 

... - - - - - - 

HIUPA - - - - - - 

HIUPD - - - - - - 

HIISA - - - - - - 

HISYN - - - - - - 

HIKIM - - - - - - 

HKSAL - - - - - - 

HISAL - - - - - - 

... - - - - - - 

HKPRO - - - - - - 

HIPRO - - - - - - 

HKSAK 2 - - - - - 

HKSSP - - - - - - 

HISSP - - - - - - 

HKKOM - - - - - - 

HIKOM - - - - - - 

HKEND - - - - 1 - 

HNSHA 1 0-1 - - - 0-1 

HNHBS 1 1 - - 1 1




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

67 

VIII.3.8 

Key blocking by the customer (RDH) 

Message 



institution 


institution 


institution 

N6, N7 N2, N3 N17 N5 N8, N9 1N14 

Message 1 1 1 1 1 1 

HNHBK 1 1 1 1 1 1 

HNVSK 0-1 0-1 0-1 - 0-1 - 

HNVSD 0-1 0-1 0-1 - 0-1 - 

HNSHK 0-1 0-1 0-1 0-1 - 0-1 

HIRMG - 1 - 1 - 1 

HIRMS - 0-m - 0-m - 0-m 

HKIDN 1 - - - - - 

HKVVB 1 - - - - - 

HKISA 1-2 - - - - - 

HKSYN - - - - - - 

HIBPA - 0-1 - - - - 

HIKOM - 0-1 - - - - 

HISHV - 0-1 - - - - 

HIKPV - 0-1 - - - - 

HIUEBS - 0-n - - - - 

... - 0-n - - - - 

HIUPA - 0-1 - - - - 

HIUPD - 0-n - - - - 

HIISA - 0-2 - - - - 

HISYN - - - - - - 

HIKIM - 0-n - - - - 

HKSAL - - - - - - 

HISAL - - - - - - 

... - - - - - - 

HKPRO - - - - - - 

HIPRO - - - - - - 

HKSAK - - - - - - 

HKSSP - - 1 - - - 

HISSP - - - 1 - - 

HKKOM - - - - - - 

HIKOM - - - - - - 

HKEND - - - - 1 - 

HNSHA 0-1 0-1 0-1 0-1 - 0-1 

HNHBS 1 1 1 1 1 1

Chapter: 

VIII 

Page: 

68 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



VIII.3.9 

Key blocking by the customer (DDV) 

Message 



institution 


institution 


institution 

N6, N7 N2, N3 N17 N5 N8, N9 N14 

Message 1 1 1 1 1 1 

HNHBK 1 1 1 1 1 1 

HNVSK 0-1 0-1 0-1 - - - 

HNVSD 0-1 0-1 0-1 - - - 

HNSHK 0-1 0-1 0-1 - - - 

HIRMG - 1 - 1 - 1 

HIRMS - 0-m - 0-m - 0-m 

HKIDN 1 - - - - - 

HKVVB 1 - - - - - 

HKISA - - - - - - 

HKSYN - - - - - - 

HIBPA - 0-1 - - - - 

HIKOM - 0-1 - - - - 

HISHV - 0-1 - - - - 

HIKPV - 0-1 - - - - 

HIUEBS - 0-n - - - - 

... - 0-n - - - - 

HIUPA - 0-1 - - - - 

HIUPD - 0-n - - - - 

HIISA - - - - - - 

HISYN - - - - - - 

HIKIM - 0-n - - - - 

HKSAL - - - - - - 

HISAL - - - - - - 

... - - - - - - 

HKPRO - - - - - - 

HIPRO - - - - - - 

HKSAK - - - - - - 

HKSSP - - 1 - - - 

HISSP - - - 1 - - 

HKKOM - - - - - - 

HIKOM - - - - - - 

HKEND - - - - 1 - 

HNSHA 0-1 0-1 0-1 - - - 

HNHBS 1 1 1 1 1 1



Section: HBCI basic character sets 

Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

69 

VIII.4 HBCI basic character sets 

The HBCI basic character sets are subsets of ISO 8859. Only printable ISO 8859 

characters are permitted, i.e. from X’20’ to X’7E’ and from X’A1’ to X’FF’, in addition to 

X’0A’ (line feed) and X’0D’ (carriage return). 

VIII.4.1 ISO 8859-1 Subset German 

0 1 2 3 4 5 6 7 8 9 A B C D E F 

0 LF CR 

1 

2 SP ! " # $ % & ' ( ) * + , - . / 

3 0 1 2 3 4 5 6 7 8 9 : ; < = > ? 

4 @ A B C D E F G H I J K L M N O 

5 P Q R S T U V W X Y Z [ \ ] ^ _ 

6 ` a b c d e f g h i j k l m n o 

7 p q r s t u v w x y z { | } ~ 

8 

9 

A ¡ ¢ £ ¤ ¥ ¦ § ¨ © ª « ¬ - ® ¯ 

B ° ± ² ³ ´ µ · ¸ ¹ º » ¼ ½ ¾ ¿ 

C À Á Â Ã Ä Å Æ Ç È É Ê Ë Ì Í Î Ï 

D Ð Ñ Ò Ó Ô Õ Ö × Ø Ù Ú Û Ü Ý Þ ß 

E à á â ã ä å æ ç è é ê ë ì í î ï 

F ð ñ ò ó ô õ ö ÷ ø ù ú û ü ý þ ÿ 

VIII.4.2 ISO 8859-1 Subset English 

0 1 2 3 4 5 6 7 8 9 A B C D E F 

0 LF CR 

1 

2 SP ! " # $ % & ' ( ) * + , - . / 

3 0 1 2 3 4 5 6 7 8 9 : ; < = > ? 


5 P Q R S T U V W X Y Z [ \ ] ^ _ 


7 p q r s t u v w x y z { | } ~ 

8 

9 

A ¡ ¢ £ ¤ ¥ ¦ § ¨ © ª « ¬ - ® ¯ 

B ° ± ² ³ ´ µ · ¸ ¹ º » ¼ ½ ¾ ¿ 




F ð ñ ò ó ô õ ö ÷ ø ù ú û ü ý þ ÿ

Chapter: 

VIII 

Page: 

70 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 


HBCI basic character sets



Section: HBCI basic character sets 

Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

71 

VIII.4.3 

ISO 8859-1 Subset French 

0 1 2 3 4 5 6 7 8 9 A B C D E F 

0 LF CR 

1 

2 SP ! " # $ % & ' ( ) * + , - . / 

3 0 1 2 3 4 5 6 7 8 9 : ; < = > ? 


5 P Q R S T U V W X Y Z [ \ ] ^ _ 


7 p q r s t u v w x y z { | } ~ 

8 

9 

A ¡ ¢ £ ¤ ¥ ¦ § ¨ © ª « ¬ - ® ¯ 

B ° ± ² ³ ´ µ · ¸ ¹ º » ¼ ½ ¾ ¿ 




F ð ñ ò ó ô õ ö ÷ ø ù ú û ü ý þ ÿ

Chapter: 

VIII 

Page: 

72 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 


Example session 

VIII.5 Example session 

In the example, the customer is working with a security data carrier capable of using 

asymmetric security procedure (RDH). 

VIII.5.1 Message "Session initialisation" 

a) Customer message 

The user signs the customer message with the ID ‘12345’. (The unencrypted structure 

is displayed for clarity.) 

Segment: Message header 14 

HNHBK:1:3+000000000323+220+0+1' 

Segment: Signature header 

HNSHK:2:3+1+654321+1+1+1::2+3234+1:19960701:111144 

+1:999:1+6:10:16+280:10020030:12345:S:1:1' 

Segment: Identification 

HKIDN:3:2+280:10020030+12345+2+1' 

Segment: Preparation for processing 

HKVVB:4:2+2+3+1+HomeBanking Plus+3.0' 

Segment: Request for a public key (Signature key) 

HKISA:5:2+2+124+280:10020030:11111:S:1:1' 

Segment: Request for a public key (Encryption key) 

HKISA:6:2+2+124+280:10020030:11111:V:1:1' 

Segment: Signature closer 

HNSHA:7:1+654321+@96@' 

Segment: Message terminator 

HNHBS:8:1+1' 

14 

To make them easier to read, the segments in this example each begin on a new line. In practice, of 

course, segments are not required to end with a carriage return.



Section: Example session 

b) Financial institution message 

Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

73 

Financial institution messages are not signed in this example. The current financial 

institution parameter data, user parameter data, and the current signature key are also 

sent. 

Segment: Message header 

HNHBK:1:3+000000000932+220+4711+1+4711:1' 


HNSHK:2:3+1+123456+1+1+1::2+3234+1:19960701:111145 

+1:999:1+6:10:16+280:10020030:1:S:1:1' 

Segment: Message-level response 

HIRMG:3:2+0010::Message received' 

Segment: Segment-level response 

Segment sequence: Financial institution parameter data 

HIBPA:4:2:4+3+280:10020030+Any Financial 

institution, Anytown+1+1:2:3+1+100' 

HIKOM:5:2:4+280:10020030+1+1:12345678:00+2:1234567 

9:00+3:123.123.123.123::UUE:1' 

HISHV:6:2:4+N+RDH:3:2:1' 

HIUEBS:7:1:4+1+2+7:51:53:54:67:69' 

HIUEBS:8:2:4+1+2+14:51:53:54:67:69' 

HILASS:9:2:4+1+2+14:04:05' 

HISUBS:10:2:4+1+2+999:14:51:53:54' 

HISLAS:11:2:4+1+2+99:14:04:05' 

HIKAZS:12:2:4+1+2+60:Y' 

HIKANS:13:2:4+1+2+60:Y' 

HISALS:14:3:4+1+2' 

Segment sequence: User parameter data 

HIUPA:15:2:4+12345+4+0' 

HIUPD:16:4:4+1234567:280:10020030+12345+DEM+Ernst 

Miller++Giro Spezial+T:2000,:DEM+HKPRO:1+HKSAK:1+H

Chapter: 

VIII 

Page: 

74 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



KISA:1+HKSSP:1+HKUEB:1+HKLAS:1+HKKAN:1+HKKAZ:1+HKS 

AL:1' 

HIUPD:17:4:4+1234568:280:10020030+12345+DEM+Ernst 

Miller++Sparkonto 2000++HKPRO:1+HKSAK:0+HKISA:1+HK 

SSP:0+HKUEB:2:Z:1000,:DEM:7+HKKAN:1+HKKAZ:1+HKSAL: 

2' 

Segment: Public key transmission (signature key) 

HIISA:18:2:5+1+333+1+224+280:10020030:11111:S:1:1+ 

6:16:10:@96@:12:@5@:13' 

Segment: Public key transmission (encryption key) 15 

Segment: Financial institution message 

HIKIM:19:2+Homeowner savings+Find out about the ne 

w homeowner savings plan.' 

Segment: Signature terminator 

HNSHA:20:1+123456+@96@' 


HNHBS:21:1+1' 

15 

It is assumed that the public encryption key is still current, and does not therefore need to be updated.




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

75 

VIII.5.2 

Message "Single remittance" 


This message is signed jointly by user ‘12345’ and user ‘76543’. 


HNHBK:1:3+000000000523+220+4711+2' 

Segment: Signature header for user ‘76543’ 

HNSHK:2:3+1+765432+1+1+1::2+3234+1:19960701:111144 

+1:999:1+6:10:16+280:10020030:76543:S:1:1' 

Segment: Signature header for user ‘12345’ 

HNSHK:3:2+1+654321+1+1+1::2+3234+1:19960701:111144 

+1:999:1+6:10:16+280:10020030:12345:S:1:1' 

Segment: Single remittance 

HKUEB:4:2+1234567::280:10020030+7654321::280:20030 

040+MEIER FRANZ++1000,:DEM+51+000+RE-NR.1234:KD- 

NR.9876' 

Segment: Signature closer for user ‘12345’ 

HNSHA:5:1+654321+@96@' 

Segment: Signature closer for user ‘76543’ 

HNSHA:6:1+765432+@96@' 


HNHBS:7:1+2' 



HNHBK:1:3+000000000140+220+4711+2+4711:2' 

Segment: signature header 

HNSHK:2:3+1+123457+1+1+1::2+3234+1:19960701:111148 

+1:999:1+6:10:16+280:10020030:1:S:1:1'

Chapter: 

VIII 

Page: 

76 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 




HIRMG:3:2+0010::Message received 


HIRMS:4:2:4+0010::Order received' 

Segment: Data segments 


HNSHA:5:1+123457+@96@' 


HNHBS:6:1+2'




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

77 

VIII.5.3 

Message "Show balance" 


The customer message is signed by user ‘12345’ alone. 


HNHBK:1:3+000000000257+220+4711+3' 


HNSHK:2:3+1+654321+1+1+1::2+3234+1:19960701:111144 

+1:999:1+6:10:16+280:10020030:12345:S:1:1' 

Segment: Show balance 

HKSAL:3:3+1234567::280:10020030+N' 


HNSHA:4:1+654321+@96@' 


HNHBS:5:1+3' 



HNHBK:1:3+000000000213+220+4711+3+4711:3' 


HNSHK:2:3+1+123458+1+1+1::2+3234+1:19960701:111150 

+1:999:1+6:10:16+280:10020030:1:S:1:1' 


HIRMG:3:2+0010::Message received' 


HIRMS:4:2:3+0020::Order executed'

Chapter: 

VIII 

Page: 

78 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 




HISAL:5:3:3+1234567::280:10020030+Giro Spezial+DEM 

+C:1000,:DEM:19960701+D:500,:DEM:19960701+5000,:DE 

M+7138,35:DEM+1476,98:DEM' 


HNSHA:6:1+123458+@96@' 


HNHBS:7:1+3'




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

79 

VIII.5.4 

Message "Session end" 



HNHBK:1:3+0000000000475+220+4711+4' 


HNSHK:2:3+1+654321+1+1+1::2+3234+1:19960701:111144 

+1:999:1+6:10:16+280:10020030:12345:S:1:1' 

Segment: Session end 

HKEND:3:1+4711' 


HNSHA:4:1+654321+@96@' 


HNHBS:5:1+4' 



HNHBK:1:3+000000000385+220+4711+4+4711:4' 


HNSHK:2:3+1+123459+1+1+1::2+3234+1:19960701:111151 

+1:999:1+6:10:16+280:10020030:1:S:1:1' 


HIRMG:3:2+0100::Session end' 


HIRMS:4:2:3+0020::Order executed' 


Segment: Signature terminator

Chapter: 

VIII 

Page: 

80 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



HNSHA:5:1+123459+@96@' 


HNHBS:6:1+4'



Section: Principles governing communications media 

Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

81 

VIII.6 Principles governing communications media 

Although HBCI is independent of the underlying communications levels, certain basic 

principles must be observed to preserve multi-financial institution capability and 

standardisation. 

The principles are: 

• Limiting the possible combinations of protocols approved for secure transmission of 

HBCI data streams. 

• Defining the parameters used. 

• Mapping HBCI session procedures into the underlying structures. 

They have been elaborated for the two following types of communication: 

• T-Online under CEPT/EHKP/BtxFIF 

• TCP/IP 

VIII.6.1 T-Online 

As part of its requirements for external computer links, T-Online assumes a protocol 

structure which fits onto X.25 (Datex-P) and allows two possible connections: EHKP or 

X.29. The X.29 alternative is not specified here. For transmission of HBCI messages 

the following definitions are made, depending on the kind of connection used. 

Financial institution system: conditionally mandatory (either the T-Online or the TCP/IP 

access must be implemented 

Customer system: mandatory (so long as no technical restrictions exist 

concerning the hardware) 

VIII.6.1.1 ETSI 300 072 ("CEPT") 

ETSI 300 072 specifies a display and data transmission standard. HBCI data are 

transmitted in the "Transparent Mode of the Line Protocol" within the CEPT data 

stream. 

The data flow control specified in ETSI 300 072 permits also the use of terminals which 

do not allow error correction according to V.42 or MNP4 by the modem. 

Session initialisation and session end are treated as follows in the T-Online session 

protocol: 

a) Session initialisation 

In order to avoid separate decoder macros having to be created in spite of the same 

structure of the T-Online transfer page for each group of financial institutions, the 

following requirements are made for the design of the transfer page.

Chapter: 

VIII 

Page: 

82 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 


Principles governing communications media 

Column 6 

Line 10 

Imprint 

BSC: 

BSC 

Length: 8 

Space for 

free design 

by the 

bank 

HNHBK:1:1+0+1+N‘ 

HNSHK:2:1+1+654321+1+1+1::2+3234+1:19960701:111144+1:999:1+ 

:10:16+280:10020030:12345:S:1:1‘ 

HKIDN:3:1+280:10020030+12345+2+1‘ 

Transparent 

HKVSW:4:1+N+N‘ 

Transport frame 

HKVVB:5:1+1+2+3+1+Homebanking 

Length: 1024 

HNSHA:6:1+654321+‘ 

l 

HNHBS:7:1+1' 

BTX: 

Subscriber ID 

(System variable) 

Length: 12 

Co-user suffix 

(System variable) 

Length: 4 

Figure 26: Structure of T-Online transfer page 

What cannot be changed here are the position of the field "Financial institution" in line 

10, column 6, and the text string "BSC" in Line 10, Column 1. The letters "BSC" stand 

for financial institution code. 

In addition the T-Online transfer page must contain the following session fields in the 

order specified (this is not an HBCI format specification): 

Name 

Lengt 

h 

Format 

Status 

Nu 

mbe 

r 

Entry 

under HBCI 

Financial institution num 8 M 1 Identification of the financial 

institution, e.g. via the financial 

institution code 

Transparent 

bin 1024 M 1 for BtxFIF data blocks 

transport framework 

Subscriber ID an 12 M 1 System variable: Subscriber ID 

Co-user suffix an 4 M 1 System variable: Co-user suffix 

Financial institution 

By this means the financial institution concerned is determined at the financial 

institution end. The 8-digit financial institution code is inserted. 

Transparent transport framework 

The transport framework on the receiving end must be able to accept the 

session initialisation message. The size of this message depends on many 

parameters, such as for example the security procedure used. If one uses




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

83 

maximum values as a basis, then a value of 1024 bytes is sufficient with the 

specified procedures. This takes account also of the necessary space for the Btx 

header data and the CEPT structure code. 

The BtxFIF parameter "Length of the data" should be inserted for this 1st data 

block to "1024". 

Subscriber ID 

Via T-Online the subscriber ID is made available as a system variable. The 

subscriber ID must be entered as a system variable in every case, since its 

presence affects the T-Online session procedure (sending of personal data with 

"19"). 

Co-user suffix 

Via T-Online the co-user suffix is made available as a system variable. Even if 

the transmission of the co-user suffix should not be desired by a financial 

institution, this field must be edited on the page, since otherwise the size of the 

transport framework cannot be standardised. 

b) Transmission mode 

After receipt of the session initialisation message the HBCI session can be carried out 

with a transparent transport page for accepting the BtxFIF data blocks. This is a CEPT 

data collection page without structure code, data entry screen fields and prompt texts 

and with only one transparent session field of a maximum size of 1616 bytes. This size 

must be adjusted for smaller messages and reconciled with the BtxFIF parameter 

"Length of the data". 

The transparent session fields for the transmission of the BtxFIF blocks must absolutely 

possess the attribute "protected". An exception is the last block of any financial 

institution message. Here the session field must allow the entry of transparent data 

(attribute: "unprotected"), so that the customer system can send the next HBCI 

message. The last block of the last financial institution message must on the other hand 

be sent as a protected session field, since otherwise the customer system cannot 

separate the transport connection. (see under c below) "Session end, caused by 

customer"). 

T-Online session control functions, such as for example direct page selection, are not 

used. The session procedure is prescribed by HBCI. 

An HBCI session must be processed without interruptions by user input, since the time 

for transmission of transparent data by the T-Online access computer is monitored. 

c) Session end, caused by the customer 

The customer system marks the last HBCI message by sending the session end 

message. The last BtxFIF block of the associated reply message also ends the logical 

HBCI session. The transparent session field for transmission of the last BtxFIF block of 

the last financial institution message receives the attribute "protected". 

The customer system must now leave the external computer via *0# in order to bring 

about a logical end to the session. Following this, after possibly changing the security 

data carrier, a new logical session can be set up by sending a new session initialisation

Chapter: 

VIII 

Page: 

84 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



or the T-Online connection can be terminated completely. (*9#, Modem command ATH, 

or similar) 

d) Session end, caused by the financial institution 

The financial institution sends synchronously an HBCI reply message with confirmation 

of the session end in the last BtxFIF block. No CEPT farewell page is output.




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

85 

VIII.6.1.2 EHKP 

The EHKP protocols (German initials for "Uniform Higher Communications Protocols") 

of levels 4 and 6 make sure of a secure communication between T-Online network 

nodes and external computer. With this there exists through EHKP6 the restriction to a 

maximum session field length of 1616 bytes while using a single session field on a 

transport page without structure code, entry screen fields and prompt texts. To remove 

this restriction BtxFIF is used for the fragmentation of the HBCI messages. 

VIII.6.1.3 BtxFIF 

BtxFIF ("Btx File Interchange Format") allows transmission on both sides of any 8-bit 

coded transparent data streams in a block-oriented protocol. Two different message 

structures are used. 

♦ Structure of the 1st data block 

Header 

label 

Length 

Header 

Length 

Data 

Block 

Header 

File 

Header 

Data 

♦ Structure of the following data blocks 

Header 

label 

Length 

Header 

Length 

Data 

Block 

Header 

Data 

♦ Definitions 

Apart from the rules for entries listed below, the definitions of the BtxFIF-specification of 

Deutsche Telekom apply, especially the syntax for the data structure (Tag-Length- 

Value). 

Building on this protocol structure the following definitions are made: 

Length of the data 

The length of the data which are transmitted in a block must conform to the size 

of the transparent transport framework, which interprets as a maximum of 1616 

bytes (see chapter VIII.6.1.1.1 and VIII.6.1.1.2). 

♦ Parameters in the block header 

(This is not an HBCI format specification) 

Name 

Format 

Length Status 

Entries 

under HBCI 

Transfer ID an 4 M any 4-digit value 

Block number bin 2 M 16-bit counter 

Number of blocks bin 2 M 16-bit counter 

Restart code 

O 

Continue code O empty or ETSI 300 072 ‘#’ 

♦ Explanations on the block header 

The BtxFIF field "Restart code" is not to be filled-in, since no restart is carried out at 

transport level. The BtxFIF field "Block check sum" is not to be filled-in, since the check

Chapter: 

VIII 

Page: 

86 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



as to whether the data are intact is achieved with HBCI by the formation of the hash 

value. 

Transfer ID 

Here any 4-digit alphanumeric value can be inserted as reference for the current 

message to be transmitted. This goes into the formation of the filename (see File 

Header). 

Block number 

Number of the current block to be transmitted, consistently increasing in 

ascending order without gaps and beginning with 1. 

Number of blocks 

Number of blocks to be transmitted in the whole HBCI message. 

Continue code 

With only one transmission block the field is not to be filled-in, with several fields 

ETSI 300 072 ‘#’ is to be entered. 

♦ Parameters in the file header 

(This is not an HBCI format specification) 

Name 

Format 

Length Status 

Entries 

under HBCI 

Filename an 12 M DOS-compatible name without path 

Date/time an 12 M YYMMDDhhmmss or 00 ... 00 

File length bin 8 M 64-bit length of the HBCI data 

File type num 1 M ‘0’ for binary data 

File check total bin 4 M 32-bit Frame Check Sequence 

(FCS) 

♦ Explanations on the file header 

The BtxFIF fields ‘Destination name, ‘User field’ and ‘Compression’ may not be filled in. 

Filename 

DOS-compatible filename in the format hbci####.hbc, where #### is the 4-digit 

transfer ID (see Block Header). 

Date/time 

Date and time of the transmission in accordance with the format given above. The 

content of this time stamp is not tested for plausibility and must be replaced on 

terminals without date installation by the figure sequence 00 ... 00. 

File length 

Length of the whole HBCI message in accordance with BtxFIF in 64-bit coded. 

File type 

For transmission of binary data, file type ‘0’ is to be inserted.




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

87 

File check total 

Frame Check Sequence (FCS) in accordance with CCITT recommendation 

V.42. This check total is an absolute requirement with BtxFIF.

Chapter: 

VIII 

Page: 

88 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



VIII.6.2 

TCP/IP 

Financial institution system: conditionally mandatory (either the T-Online or the TCP/IP 

access must be implemented) 

Customer system: mandatory (if there are no technical restrictions) 

Transmission Control Protocol (TCP) provides an interface that applications can use to 

securely transmit HBCI messages between customer and financial institution. Since 

TCP/IP itself cannot provide the required session references between the individual 

HBCI messages, this must be done by a session protocol superimposed on TCP/IP. 

It should be made sure that only the minimum extent of protocol commands described 

in RFC793 should be used, so as to achieve the highest possible compatibility. 

As the port number to be used, the address 3000 has been registered with the "Internet 

Assigned Numbers Authority" (IANA). As an interface between the TCP/IP protocol as 

communications path and the HBCI FINANCIAL INSTITUTION system on the application 

side only the use of stream sockets 16 or a network interface which is 100% compatible 

to the socket interface is permitted. This requirement is necessary with respect to the 

basic conditions already described at the beginning of the chapter concerning the 

uniformity and multi-financial institution capability of HBCI on the communications 

interface side of the customer. 

The TCP/IP access can be used to allow an HBCI access to the Internet or a direct 

financial institution access. 

VIII.6.2.1 Internet (WWW) 

HBCI is independent of the components used from the list of Internet applications (e.g. 

World Wide Web, FTP, Telnet). What is important, however, is the transparency of the 

Internet service used, i.e. a filter function may be required. 

Because of the security mechanisms integrated into HBCI, the use of Internet-specific 

security protocols (e.g. SSL) is avoided. 

VIII.6.2.2 Direct access 

VIII.6.2.2.1 Protocol requests 

If a financial institution would like to use direct access, it can implement this with the aid 

of the TCP/IP and PPP protocol stack. The configuration of the customer access cannot 

be done here, however, because of the extent of the necessary parameters. Bilateral 

discussions between customer and financial institution are therefore necessary. At a 

later date, if a PPP variant has developed to become a standard, direct access can 

possibly be described more specifically. 

16 

The implementation of the socket interface is based on the TCP/IP protocol stack and offers a 

communications interface which is almost completely platform-independent on the basis of the TCP/IP 

protocol. Sockets - as a medium for inter-network process communications - are originally a medium of 

interprocess communications interfaces of the UNIX operating system and have established 

themselves in this field as a manufacturing standard. Corresponding portings of the socket interface 

exist today on all usual operating system platforms (Windows 3.1/ 95/ NT, OS/2, Macintosh etc.).




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

89 

VIII.6.2.2.2 Security requirements 

Mandatory security requirements will be added in the next release of the interface 

specification. 

VIII.6.3 Other communications services 

If communications are intended through a communications service which has not yet 

been recorded, all applicable specifications must be defined by the financial institutions 

to assure multi-financial institution capability. 

As with the previously mentioned communications services it must also be ensured with 

the communications relationships to be newly defined, that these can track the session 

references between the individual HBCI messages.

Chapter: 

VIII 

Page: 

90 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 


Retrieving communications settings 

VIII.7 Retrieving communications settings 

For making a connection to the financial institution certain access data specific to the 

network and the service are necessary. These data must be present on the customer 

system, before it can make the connection. The present transaction allows the 

customer to order or update the necessary access data. 

Financial institution system: optional 

Customer system: optional 

a) Customer order 

♦ Description 

An anonymous session initialisation is required, and may be followed by a single 

message with the segment "Request communications settings". As soon as the reply 

message is received the session is ended. Attempting to request the communications 

accesses during any other HBCI session will result in an error message. 

♦ Format 

Name: 

Type: 

Originator: 

Communications access 

Message 

Customer 

No. Name Type ID Status 

Num Remarks 

ber 

1 Message header SEG HNHBK M 1 

2 Request communications SEG HKKOM M 1 

settings 

3 Message SEG HNHBS M 1 

Name: 

Request communications settings 

Type: 

Segment 

Segment type: 

Business transaction 

ID: 

HKKOM 

Reference segment: - 

Segment version: 3 

Originator: 

Customer



Section: Retrieving communications settings 

Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

91 

No. Name 

Type Format 

Leng Sta- 

Num Restrictions 

th tus ber 

1 Segment header DEG M 1 

2 Start financial institution DEG bid 8 O 1 

ID 

3 End financial institution ID DEG bid 8 O 1 

4 Maximum number of DE num ..4 O 1 >0 

entries 

5 Scroll reference DE an ..35 O 1 

♦ Explanations 

No. 2,3: Start financial institution ID, End financial institution ID 

The DEGs "Start financial institution ID" and "End financial institution ID" are 

used to specify a range of financial institutions for which the communications 

settings are desired. If no financial institution code range is inserted then all 

available communications settings will be returned. Note that a range can only 

be specified for financial institutions in the same country. 

No. 4: Maximum number of entries 

The number of communications accesses to be returned can be restricted (see 

Chapter II.7.3). 

No. 5: Scroll reference 

To be used only if a scroll reference has been assigned by the financial 

institution (see Chapter II.7.3). 

♦ Example 

All communications accesses: 

HKKOM:2:3' 

Request communications settings for German financial institution having sort code 

(BLZ) 100 200 30: 

HKKOM:2:3+280:10020030+280:10020030' 

b) Financial institution response 


For each financial institution specified by the customer, one segment of the format 

"Communications settings" will be inserted in the financial institution message. 

Note that no provision is made for indicating the opening hours of the communications 

service, to avoid the need for frequent updates. In general, around-the-clock availability 

is to be aimed for. 

♦ Format 

Name: 

Type: 

Originator: 

Reply to communications settings request 

Message 

Financial institution

Chapter: 

VIII 

Page: 

92 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



No. Name Type ID Status 

Num Remarks 

ber 

1 Message header SEG HNHBK M 1 

2 Message-level response SEG HIRMG M 1 

3 Segment-level response SEG HIRMS O 1 

4 Communications settings SEG HIKOM O n 

5 Message SEG HNHBS M 1 

Name: 

Communications settings 

Type: 

Segment 

Segment type: 


ID: 

HIKOM 

Reference segment: HKKOM 


Originator: 


No. Name 

Type Format 

Leng Sta- 


th tus ber 

1 Segment header DEG M 1 

2 Financial institution ID DEG bid # M 1 

3 Default language DE num ..3 M 1 1,2,3 

4 Communications parameters 

DEG M 1..9 


No. 3: Default language 

The language code as per Chapter III.3.1.3 is to be given, defining the financial 

institution's default language and character set. This must be used for the 

session initialisation message. After that message, the language can be 

changed by the customer specifying the session language during session 

initialisation. 

No. 4: Communications parameters 

Up to nine communication settings per financial institution can be specified. 

 

If the financial institution offers more than one setting for a 

communication service and no connection can be 

established via the setting selected by the customer 

system, the customer system should also try the other 

settings.




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

93 

No. Name 

Type Format 

Leng Sta- 


th tus ber 

1 Communications service GD num ..2 M 1 1,2 

2 Communications address GD an ..512 M 1 

3 Communications address GD an ..512 O 1 

suffix 

4 Filter function GD an 3 O 1 MIM, UUE 

5 Version of filter function GD num ..3 O 1 

No. 1: Communications service 

Communications process supported (protocol stack), to which the following 

refers (see the Chapter on "Restrictions governing communications media"). 

Communications processes supported at present: 

Code Access Protocol stack 

1 T-Online ETSI 300 072 (CEPT), EHKP, BtxFIF 

2 TCP/IP SLIP/PPP 

No. 2: Communications address 

Depending on the communications process the following information is to be 

given: 

Access Address Remarks 

T-Online Gateway page Enter as a number (without entering the 

control characters * and #). 

TCP/IP IP address Enter as an alphanumeric string, (e.g. 

123.123.123.123) 

No. 3: Communications address suffix 

Depending on the communications process the following information is to be 

given: 

Access Address extension Remarks 

T-Online Geographical region For nation-wide access use ‘00’. 

TCP/IP N/A 

No. 4: Filter function 

If the communications process requires conversion of the message into a 7-bit 

character representation (e.g. for the internet), then the filter process to be used 

should be given here. The message is always filtered completely, even if it does 

not contain any binary data. 

Each financial institution may only support one filter function. 

Filter functions available:

Chapter: 

VIII 

Page: 

94 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



Code 

Meaning 

MIM MIME Base 64 

UUE Uuencode/Uudecode 

No. 5: Version of filter function 

To be used only if a filter function has been given. 

♦ Example 

HIKOM:3:3:2+280:10020030+1+1:12345678:00+2:123.123 

.123.123::UUE:1+2:www.financialinstitutionname.de: 

:UUE:1' 

HIKOM:4:3:2+280:20030040+1+1:54321:00' 

HIKOM:5:3:2+280:30040050+2+1:12345:22' 

♦ Some typical return message codes 

Code Example of return message code 

0020 Order executed 

3010 No data found 

3040 Order only partially executed 

9210 Start of range must come before end of range 

c) Financial institution parameter data 

♦ Format 

Name: 

Communications settings - parameters 

Type: 

Segment 

Segment type: 


ID: 

HIKOMS 

Reference segment: HKVVB 


Originator: 


Format: 

Business transaction parameters 


No. 4: Parameters 

This DEG left blank. 

♦ Example 

HIKOMS:11:3:5+1+2' 

 

The communications settings must be requested upon initial 

access, and for anonymous access (as a guest user). They are 

not subject to frequent changes and therefore will seldom need 

updating. Updating can be performed automatically if a 

connection cannot be established due to outdated settings.




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

95 

The customer product must store the settings locally for future 

use. This access database can be linked in the customer product 

with a local financial institution code file to facilitate access. 

It should be borne in mind that the communications address 

under which the access data are called up will not, as a rule, be 

identical to the address of the financial institution for which 

access is desired. Once the settings have been updated, the 

physical connection will probably have to be ended and then reestablished 

with the new settings. 

Each Banking association updates the access data of the 

financial institutions belonging to it and makes them available at 

a central location (available through the contact addresses given 

in the introduction to this document).

Chapter: 

VIII 

Page: 

96 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 


Chip application for DDV 

VIII.8 Chip application for DDV 

In the following, a chip-based application named "Banking", synonym "HBCI-Banking", 

is specified that is the equivalent of the DDV procedure described in Chapter VI. As a 

prerequisite, in addition to the data elements described below, there must be the data 

element EF_ID and the crypto-algorithm Triple DES as per the ZKA interface 

specification for chip-based ec-cards. This section deals only with the data elements 

required for HBCI. 

The application "Banking" can be implemented on a dedicated chip card (an "HBCI 

card") or on some other multi-functional chip card that uses the operating system of the 

chip-based ec-card. For HBCI applications no executable code is required apart from 

what is specified in ISO 7816-4 or the chip-based ec-card. 

This chapter specifies the data structures and access rules of the chip application "DF 

BANKING" for type 0 ("old Central Banking Committee system") and type 1 ("new 

Central Banking Committee system"). The command sequences in the terminal are 

jointly specified for type 0 and type 1 chip cards. 

In VIII.8. and VIII.8.2 there is a explicit description for type 0. In the further course of this 

document "HBCI chip card" means a chip card in accordance with [LIT 1'] and [LIT 1A], 

which contains the HBCI application. Further applications, such as the electronic wallet, 

are not of necessity contained on the chip card. The card can also be account-related 

or account-independent. 

The ADF of the HBCI Banking application for the new Central Banking Committee is 

designated as DF_BANKING_20. In the existing specification it is directly contained in 

the MF. The DF-specific keys relevant for the application are stored in the EF KEY, 

which is directly contained in DF_BANKING_20. 

In the current specification two security environments are used in the context of type 1 

cards: 

1 The security environment with the number 1 (SE #1) as standard SE stipulates the 

access rules for the files of the application HBCI Banking for the event of it being 

used, i.e. for access in the field on HBCI-capable terminals. 

2 As Administrations-SE, the security environment with the number 2 (SE #2) 

stipulates the access rules for the files and the application directory of the HBCI 

Banking application for the case of administration procedures, e.g. monitoring, 

amendments or expansions. 

As described in [LIT 1'], the selection of SEs takes place with the MANAGE SECURITY 

ENVIRONMENT command – i.e. selection of the SE is not necessary on HBCI-capable 

terminals, since the SE #1 is implicitly activated when an application is selected.



Section: Chip application for DDV 

Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

97 

VIII.8.1 

Data of the application HBCI Banking for the type 0 card 

The figure below gives an overview of the data elements (EFs) of the application 

"Banking" for the type 0 card. 

MF 

EF_KEY 

EF_ID 

EF_KEYD 

EF_INFO 

EF_PWD 

EF_LOG 

EF_PWDD 

EF_RAND 

EF_FBZ 

EF_ 

VERSION 

DF_Bankin 

EF_KEY 

EF_KEYD 

EF_AUT 

EF_AUTD 

EF_PWD 

EF_PWDD 

EF_BNK 

EF_MAC 

EF_SE 

Fig. 27: Data elements of the application "Banking" 17 

17 Elementary files EF_PWD0, EF_PWDD0, EF_FBZ and EF_INFO are not used at any card type.

Chapter: 

VIII 

Page: 

98 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



VIII.8.1.1 

DF_Banking 


4 data fields are assigned to the application DF_Banking as AEFs, which are accessible 

to the HBCI terminal via read-and-write access: 

SFI '19' EF_ID in MF 

SFI '1A' EF_BNK in DF_Banking 

SFI '1B' EF_MAC in DF_Banking 

SFI '1C' EF_SEQ in DF_Banking 

If DF_Banking is selected by means of SELECT FILE and a relevant option is set in the 

parameter P2 of the command, the following FMD are output with the paths of the AEFs 

(here it is assumed that DF_Banking is located directly in the MF). 

♦ Format 

Tag Lengt Value Explanation 

h 

'64' '1A' Tag and length for FMD 

'85' '03' '19 00 03' Path for the AEF with SFI '19' (EF_ID in MF) 

'85' '05' '1A A6 00 03 01' Path for the AEF with SFI '1A' (EF_BNK in DF_Banking) 

'85' '05' '1B A6 00 03 02' Path for the AEF with SFI '1B' (EF_MAC in DF_Banking) 

'85' '05' '1C A6 00 03 03' Path for the AEF with SFI '1C' (EF_SEQ in DF_Banking) 

The following FCI can also be output by way of the parameter P2 with the SELECT 

FILE with the ACs of the AEFs in the composite data object with Tag 'A5'. 

Tag Lengt Value Explanations 

h 

'6F' '40' Tag and length for FCI 

'81' '02' 'xxxx' Free memory area in the ec card 

'82' '01' '38' File describer for DF 

'83' '02' ‘A600’ File ID of the application Banking 

'84' '09' ‘D27600002548420100’ DF name (AID) of the DF_Banking 

'86' '02' '0040' AC for DF_Banking 

'A5' '24' Tag and length of the ACs of the AEFs 

'86' '07' '19 0040 0000 00F0' SFI and ACs of the EF_ID 

'86' '07' '1A 0040 0000 0031' SFI and ACs of the EF_BNK 

'86' '07' '1B 0040 3150 0031' SFI and ACs of the EF_MAC 

'86' '07' '1C 0040 0000 0031' SFI and ACs of the EF_SEQ 


Tag '83': 

The file ID of the application ‘Banking’ is A600. 

Tag '84': 

Application Identifier (AID) for HomeBanking with chip card




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

99 

Tag '86': 

Command group ADMIN: AC '0040' (PRO_G with key number '00')

Chapter: 

VIII 

Page: 

100 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



VIII.8.1.2 

EF_KEY 


In this EF is stored the individual customer signature key. 

♦ Format 

File Control Parameter (FCP): 

Tag Lengt Value Explanation 

h 

'62' '15' Tag and length for FCP 

'81' '02' '00 11' Allocated memory area in bytes 

'82' '03' '02 41 11' File describer for linear EF 

'83' '02' '00 10' File ID of the EF_KEY 

'86' '06' '0060 00F0 0060' ACs for the EF_KEY 


Tag '81': 

The EF_KEY contains a maximum of one record of length 17 bytes, so that 17 

bytes are needed. 

Tag '82': 

The record length is 17 bytes (X'11'). 

Tag '83': 

The file ID must be '00 10' with an EF_KEY. 

Tag '86': 

APPEND RECORD: AC '00 60' (ENC_G with key number '00') 

READ RECORD: AC '00 F0' (NEV) with key number '00') 

UPDATE RECORD: AC '00 60' (ENC_G with key number '00') 

Data: 

The EF_KEY of the DF_Banking contains one record. The record contains the 

logical key number with the signature key. 

Logical key no. 

'00' 

Key 

16 bytes long K DSG




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

101 

VIII.8.1.3 

EF_KEYD 


This EF is used for the description of the characteristics of the signature key. 

♦ Format 


Tag Length Value Explanation 


'81' '02' '00 05' allocated memory area in bytes 


'83' '02' '00 13' File ID of the EF_KEYD 

'86' '06' '0040 0000 0040' ACs for the EF_KEYD 


Tag '81': 

The EF_KEYD contains a maximum of one record of length 5 bytes, so that 5 


Tag '82': 

The record length is 5 bytes. 

Tag '83': 

The file ID must be '00 13' with an EF_KEYD. 

Tag '86': 

APPEND RECORD: AC '00 40' (PRO_G with key number '00') 

READ RECORD: AC '00 00' (ALW) 

UPDATE RECORD: AC '00 40' (PRO_G with key number '00') 

Data: 

For each key stored in EF_KEY a record must be contained in EF_KEYD which 

contains the logical key number concerned and further parameters. 

Log. Key No. Key length Algorithm-ID FBZ Key version 

'00' '10' '07' 'FF' '00'

Chapter: 

VIII 

Page: 

102 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



VIII.8.1.4 

EF_AUT 


In this EF is stored the individual customer encryption key. 

♦ Format 






'83' '02' '00 11' File ID of the EF_AUT 

'86' '06' '0060 00F0 0060' ACs for the EF_AUT 


Tag '81': 

The EF_AUT contains a maximum of one record of length 17 bytes, so that 17 


Tag '82': 


Tag '83': 

The file ID must be ‘00 11' with an EF_AUT. 

Tag '86': 


READ RECORD: AC '00 F0' (NEV) 


Data: 

The EF_AUT of the DF_Banking contains one record. The record contains the 

logical key number with the key. 

Logical key no.. 

'00' 

Key 

16 bytes long K ENC




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

103 

VIII.8.1.5 

EF_AUTD 


This EF is used for the description of the characteristics of the encryption key. 

♦ Format 






'83' '02' '00 14' File ID of the EF_AUTD 

'86' '06' '0040 0000 0040' ACs for the EF_AUTD 


Tag '81': 

The EF_AUTD contains a maximum of one record of length 4 bytes, so that 4 


Tag '82': 


Tag '83': 

The file ID must be '00 14' with an EF_AUTD. 

Tag '86': 




Data: 

For each key stored in EF_AUT a record must be contained in EF_AUTD which 

contains the logical key number concerned and further parameters. 

Log. Key No. Key Length Algorithm ID Key version 

'00' '10' '07' '00'

Chapter: 

VIII 

Page: 

104 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



VIII.8.1.6 

EF_PWD1 


In this EF is stored the application-specific Banking PIN. 

♦ Format 






'83' '02' '00 22' File ID of the EF_PWD0 

'86' '08' '0060 00F0 0060 00 00' ACs for the EF_PWD0 


Tag '81': 

The EF_PWD0 contains a maximum of one record of length 8 bytes, so that 8 


Tag '82': 


Tag '83': 

The file ID must be '00 12' with an EF_PWD0. 

Tag '86': 


READ RECORD: AC '00 F0' (NEV) 


VERIFY 

AC '00 00' (ALW) 

Data: 

The Banking PIN is stored in the 'Format 2 PIN Block' in the record '01' of the 

EF_PWD0. The Format 2 PIN Block is formed from the PIN in accordance with 

Appendix A of ISO 10202-6 (ISO 13). It has a minimum length of 5 digits and 

may be a maximum of 12 digits long. The 8 bytes of the records are filled as 

follows: 

C L P P P P P P/F P/F P/F P/F P/F P/F P/F F F 

Each field represents a half-byte: 

C: Check field, binary coded always has the value '2' 

L: PIN length, binary coded possible values from '5' to 'C' 

P: PIN digit, BCD coded 

F: Filler, binary coded always has the value 'F' 

P/F: PIN/Filler 

depending on the PIN length




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

105 

VIII.8.1.7 

EF_PWDD1 


This EF is used for the description of the characteristics of the Banking PIN. 

♦ Format 






'83' '02' '00 25' File ID of the EF_PWDD0 

'86' '06' '0040 0000 0040' ACs for the EF_PWDD0 


Tag '81': 

The EF_PWDD1 contains a maximum of one record of length 5 bytes, so that 5 


Tag '82': 


Tag '83': 

The file ID must be '00 25' with an EF_PWDD1. 

Tag '86': 




Data: 

In the 5 bytes-long record of the EF_PWDD1 is stored additional information on 

the Banking PIN: 

Byte 1 Byte 2 Byte 3 Byte 4 Byte 5 

'01' '21' ‘05’ ‘03’ '03' 

Byte 1: Kind of cardholder authentication. At present only the password 

verification is possible which is coded with the value ‘01’. 

Byte 2: The PIN is stored in the format 'Format 2 PIN Block' in BCD. 

Byte 3: The PIN must be at least 5 digits long. 

Byte 4: Initialisation value of the PIN operator error counter in Byte 5. 

Byte 5: PIN operator error counter.

Chapter: 

VIII 

Page: 

106 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



VIII.8.1.8 

EF_BNK 


The EF_BNK is a linear EF with 5 records in which financial institution connections are 

stored. The financial institution connection can be made via T-Online, Internet or further 

future online services. 

The record comprises a financial institution short name, the financial institution code, 

the communications service, the address and the address extension for the 

communications access, the country code and the user ID. 

♦ Format 




'81' '02' '01 B8' Allocated memory area in bytes 


'83' '02' '03 01' File ID of the EF_BNK 

'86' '06' '0040 0000 0031' ACs for the EF_BNK 


Tag '81': 

The EF_BNK contains a maximum of 5 records of length 88 bytes, so that 440 


Tag '82': 


Tag '83': 

As file ID '03 01' was defined for the EF_BNK. 

Tag '86': 



UPDATE RECORD: AC '00 30' (PWD_D)




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

107 

Data: 

The EF_BNK has 5 records with the following record structure: 

Bytes Length Value Explanation Reference 

1-20 20 'aa .. aa' Short name of financial 

institution 

21-24 4 'nn nn nn nn' Financial institution code see II.5.3.2 No. 2 

of financial institution 

where the account is kept 

25-25 1 'n' Communications service see VIII.7 b) No. 1 

26-53 28 'aa .. aa' Communications address see VIII.7 b) No. 2 

54-55 2 ‘aa aa’ Communications address see VIII.7 b) No. 3 

extension 

56-58 3 'aa aa aa' Country code of financial see II.5.3.2 No. 1 

institution where the 

account is kept 

59-88 30 'aa .. aa' User ID IDs. VI.5.1.1 No. 2 

Contents of alphanumeric fields (‘a’) are in all cases ASCII coded, entered leftjustified 

and padded out with blanks (X’30’) to the required length. 

Contents of numeric fields (‘n’) are in all cases BCD coded.

Chapter: 

VIII 

Page: 

108 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



VIII.8.1.9 

EF_MAC 


The EF_MAC is used for forming the MAC via the hash value of a message. 

It consists of a record 12 bytes long whose ACs must be so set that the MAC is 

produced while the record is read in. 

♦ Format 




'81' '02' '00 0C' Allocated memory area in bytes 

'82' '03' '02 41 0C' File describer for linear EF 

'83' '02' '03 02' File ID of the EF_MAC 

'86' '06' '0040 3150 0031' ACs for the EF_MAC 


Tag '81': 

The EF_MAC contains a maximum of one record 12 bytes long, so that 12 bytes 

are needed. 

Tag '82': 

The record length is 12 bytes (X'0C'). 

Tag '83': 

As file ID '03 02' was defined for the EF_MAC. 

Tag '86': 


READ RECORD: AC '31 50' (PWD_D and PRO_D with key number '00') 

UPDATE RECORD: AC '00 31' (PWD_D) 

Data: 

The EF_MAC possesses a record 12 bytes long which is modified by UPDATE 

RECORD.




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

109 

VIII.8.1.10 

EF_SEQ 


The EF_SEQ is a linear data file, whose record contains a 2 bytes long binary defined 

element. 

This binary ascending counter flows as a security reference number (signature ID) for 

protecting the data against duplicate submission. (see Chapter VI.5.2.1). 

The starting value of the counter is 1. If an overrun occurs there is no restart. 

♦ Format 






'83' '02' '03 03' File ID of the EF_SEQ 

'86' '06' '0040 0000 0031' ACs for the EF_SEQ 


Tag '81': 

The EF_SEQ contains a maximum of one record of length 2 bytes, so that 2 


Tag '82': 


Tag '83': 

As file ID '03 03' has been defined for the EF_SEQ. 

Tag '86': 



UPDATE RECORD: AC '00 31' (PWD_D) 

Data: 

The EF_SEQ possesses a record 2 bytes long which is modified by UPDATE 

RECORD.

Chapter: 

VIII 

Page: 

110 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



VIII.8.2 

Data of the application HBCI Banking for the type 1 card 

The figure below gives an overview of the files of an HBCI card with the application 

HBCI Banking for the type 1 card. 

MF 

EF_KEY 

EF_FBZ 

EF_SIG 

EF_KEYD 

EF_ID 

EF_SIGD 

EF_PWD 

EF_INFO 

EF_PWDD 

EF_RULE 

DF_BANKING_20 

EF_KEY 

EF_KEYD 

EF_RULE 

EF_BNK 

EF_MAC 

EF_SEQ 

EF_PWD 

EF_PWDD 

EF_FBZ 

Fig. 28: Data elements of the application "HBCI", account-related card




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

111 

MF 

EF_KEY 

EF_KEYD 

EF_ID 

EF_RULE 

EF_SIG 

EF_SIGD 

DF_BANKING_20 

EF_KEY 

EF_KEYD 

EF_RULE 

EF_BNK 

EF_MAC 

EF_SEQ 

EF_PWD 

EF_PWDD 

EF_FBZ 

Fig. 29: Data elements of the application "HBCI", account-independent card

Chapter: 

VIII 

Page: 

112 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



VIII.8.2.1 

ADF of the application HBCI-Banking 

When the ADF of the application HBCI-Banking (DF_BANKING_20) is created the 

following FCP should be stipulated: 


'62' '1A' Tag and length for FCP 

'82' '01' '38' File describer for DF 

'83' '02' 'A6 00' File ID of the DF_BANKING_20 

'84' '09' 'D2 76 00 00 25 48 42 02 00' DF name (AID) of the DF_BANKING_20 

'A1' '06' '8B 04 00 30 02 01' Access rule references 

The DF name (the AID) of the DF_BANKING_20 consisting of the national RID of the 

ZKA ('D2 76 00 00 25'), the ASCII-coded ID "HB" ('48 42') and the version of the 

application 2.0 ('02 00'). 

The access rules for the DF_BANKING_20 are contained in the allocated rule file 

EF_RULE. The following stipulations are made through the access rules for the DFspecific 

command: 

If the DF_BANKING_20 is selected, a CREATE FILE (EF), DELETE FILE (self), 

INCLUDE or EXCLUDE may only be executed if the command message is executed 

with secure messaging and has a correct MAC which is created through using the key 

K HBCI_Admin from the EF_KEY of the DF_BANKING_20. For each of these commands 

the return code has a MAC with the key K HBCI_Admin. The commands CREATE FILE 

(DF) and DELETE FILE (child DF) is never allowed to be used. All authorised 

administration commands are only allowed to be executed in SE #2 (access rules in 

Record 1 of the EF_RULE). 

10 files are to be assigned as AEF to the application HBCI Banking: 

SFI '01': 

SFI '02': 

SFI '03': 

SFI '04': 

SFI '05': 

SFI '19': 

SFI '1A': 

SFI '1B': 

SFI '1C': 

SFI '1E': 

EF_RULE in DF_BANKING_20 

EF_KEY in DF_BANKING_20, 

EF_PWD in DF_BANKING_20, 

EF_PWDD in DF_BANKING_20, 

EF_FBZ in DF_BANKING_20, 

EF_ID in MF, 

EF_BNK in DF_BANKING_20, 

EF_MAC in DF_BANKING_20, 

EF_SEQ in DF_BANKING_20, 

EF_KEYD in DF_BANKING_20. 

If DF_BANKING_20 is selected using SELECT FILE and the corresponding option in 

parameter byte P2 of the command is set, the following FCI will be output:




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

113 


'6F' '0D' Tag and length for FCI 

'84' '09' 'D2 76 00 00 25 48 42 02 00' DF name (AID) of the DF_BANKING_20 

'A5' '00' No proprietary information 

If DF_BANKING_20 is selected by means of SELECT FILE and the relevant option is 

set in the parameter byte P2 of the command, the following FMD are output with the 

paths of the AEFs (here it is assumed that DF_BANKING_20 is located directly in the 

MF): 


'64' '44' Tag and length for FMD 

'85' '03' 'C8 00 03' Path for AEF with SFI '19' (EF_ID in MF) 

'85' '05' '08 A6 00 00 30' Path for AEF with SFI '01' (EF_RULE in 

DF_BANKING_20) 

'85' '05' '10 A6 00 00 10' Path for AEF with SFI '02' (EF_KEY in 


'85' '05' '18 A6 00 00 12' Path for AEF with SFI '03' (EF_PWD in 


'85' '05' '20 A6 00 00 15' Path for AEF with SFI '04' (EF_PWDD in 


'85' '05' '28 A6 00 00 16' Path for AEF with SFI '05' (EF_FBZ in 


'85' '05' 'D0 A6 00 03 01' Path for AEF with SFI '1A' (EF_BNK in 


'85' '05' 'D8 A6 00 03 02' Path for AEF with SFI '1B' (EF_MAC in 


'85' '05' 'E0 A6 00 03 03' Path for AEF with SFI '1C' (EF_SEQ in 


'85' '05' 'F0 A6 00 00 13' Path for AEF with SFI '1E' (EF_KEYD in 

DF_BANKING_20)

Chapter: 

VIII 

Page: 

114 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



VIII.8.2.2 

EF_RULE 


The file EF_RULE contains the access rules for the application DF_BANKING_20. In 

the FCP of files and directories these access rules are referenced. 

♦ Format 

For the EF_RULE of the DF_BANKING_20 the following FCP must be stipulated: 


'62' '1C' Tag and length for FCP 

'82' '05' '14 41 00 24 08' File describer for linear EF with variable 

record length (max. 36 bytes), 8 Records 

'83' '02' '00 30' File ID of the EF_RULE 

'85' '02' '00 7D' for storage space allocated to utilisation 

data in byte 

'88' '01' '08' SFI '01' for the EF_RULE 

'A1' '08' '8B 06 00 30 01 02 02 03' Access rule references 

In SE #1 only the commands READ / SEARCH RECORD with unprotected command 

and answer message are allowed to be executed (access rule in Record 2 of the 

EF_RULE). 

In SE #2 APPEND RECORD is only allowed to be executed, if it is executed with 

secure messaging. The MAC is formed for the command and reply message with the 

K HBCI_Admin . UPDATE RECORD is never allowed to be executed (access rule in Record 

3 of the EF_RULE). 

♦ Data 

The EF_RULE in DF_BANKING_20 contains 8 Records with the access rules for the 

directory and the data fields of the directories. 

The following table shows the entries in this record for an HBCI chip card: 

Rec.No Record content 

Bytes 

. 

1 '80 01 DA B4 05 83 03 80 01 FF' 10 

2 '80 01 81 90 00' 5 

3 '80 01 84 B4 05 83 03 80 01 FF' 10 

4 '80 01 86 AF 11 B4 05 83 03 80 01 FF B8 08 95 01 10 83 03 80 01 22 

FF' 

5 '80 01 86 B4 05 83 03 80 01 FF' 10 

6 '80 01 82 A4 07 95 01 08 93 02 80 01 80 01 81 90 00' 17 

7 '80 01 82 A4 07 95 01 08 93 02 80 01 

80 01 81 AF 13 B4 08 95 01 20 83 03 80 02 FF 

A4 07 95 01 08 93 02 80 01' 36 

8 '80 01 83 90 00 80 01 84 B4 05 83 03 80 01 FF' 15




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

115 

The records 1 to 5 each contain one access rule, and the records 6 to 8 each contain 

two access rules. 

The individual records of the EF_RULE are described in more detail below. 

Record 1 is referenced as an access rule by DF_BANKING_20 in SE #2. 

CREATE FILE (EF), DELETE FILE (self), INCLUDE, EXCLUDE: MAC-SM-AC for 

command and reply message with K HBCI_Admin: 


'80' '01' 'DA' Access type for CREATE FILE (EF), DELETE FILE (self), 

INCLUDE, EXCLUDE 

'B4' '05' CCT - tag and length 

'83' '03' '80 01 FF' Key reference for K HBCI_Admin 

Record 2 is referenced as access rule by EF_RULE, EF_KEYD, EF_PWDD and 

EF_FBZ in SE #1. 

READ / SEARCH RECORD: ALW 


'80' '01' '81' Access type for READ / SEARCH RECORD 

'90' '00' Access condition ALW 

Record 3 is referenced as access rule by EF_RULE, EF_BNK and EF_MAC in SE #2. 

APPEND RECORD: MAC-SM-AC for command and reply message with the key 

K HBCI_Admin. 


'80' '01' '84' Access type for APPEND RECORD 



Record 4 is referenced as access rule by EF_KEY and EF_PWD in SE #2. 

APPEND RECORD, UPDATE RECORD: MAC-ENC-SM-AC for command message 

and MAC-SM-AC for reply message with K HBCI_Admin. 


'80' '01' '86' Access type for APPEND RECORD, UPDATE RECORD 

'AF' '11' AND- Template, tag and length 



'B8' '08' CT - tag and length 

'95' '01' '10' Usage qualifier: only for command message 


Record 5 is referenced as access rule by EF_KEYD, EF_SEQ, EF_PWDD and 

EF_FBZ in SE #2. 

APPEND RECORD, UPDATE RECORD: MAC-SM-AC for command and reply 

message with the key K HBCI_Admin.

Chapter: 

VIII 

Page: 

116 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 




'80' '01' '86' Access type for APPEND RECORD, UPDATE RECORD 



Record 6 is referenced as access rule by EF_BNK and EF_SEQ in SE #1. 

UPDATE RECORD: card owner authentication (PWD) with local password 1. 

READ / SEARCH RECORD: ALW 


'80' '01' '82' Access type for UPDATE RECORD 

'A4' '07' AT - tag and length 

'95' '01' '08' Usage qualifier for card owner authentication 

'93' '02' '80 01' Password reference, local password with the number 1 


'90' '00' ALW 

Record 7 is referenced as access rule by EF_MAC in SE #1. 

UPDATE RECORD: card owner authentication (PWD) with local password 1. 

READ / SEARCH RECORD: card owner authentication (PWD) with local password 1 

and MAC-SM-AC for the reply message with the key K DAK. 


'80' '01' '82' Access type for UPDATE RECORD 





'AF' '13' AND - Template, tag and length 


'95' '01' '20' Usage qualifier: Only reply message 

'83' '03' '80 02 FF' Key reference for K DAK 




Record 8 is referenced as access rule in EF_PWDD. 

VERIFY, CHANGE REFERENCE DATA: ALW 

RESET RETRY COUNTER: MAC-SM-AC for command and reply message with 

K HBCI_Admin




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

117 

Tag Length Value Description 

'80' '01' '83' Access type for VERIFY, CHANGE REFERENCE DATA 

'90' '00' ALW 

'80' '01' '84' Access type for command: RESET RETRY COUNTER 


'83' '03' '80 01 FF' Key reference for K HBCI_Admin

Chapter: 

VIII 

Page: 

118 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



VIII.8.2.3 

EF_KEY 


The application-specific keys of the application HBCI-Banking are stored in the EF_KEY 

of the application directory DF_BANKING_20. These are 

• a 16-byte long card-specific key K HBCI_Admin with the key number '01' for administration 

of the application DF_BANKING_20, 

• a 16-byte long card-specific key K DAK with the key number '02' as customer-specific 

authentication key (DAK = Data Authentication Key) 18 , and 

• a 16-byte long card-specific key K ENC with the key number '03' as customer-specific 

encryption key. 

The keys KHBCI_Admin, KDAK and KENC are recognised by the HBCI chip card and 

its responsible background system. They are each derived from a KGK (Key 

Generating Key), using the card identification data in the EF_ID of the MF (see chapter 

8.4.1 of [LIT 1']). The responsible background system recognises the KGK and derives 

the card-specific key as required. 

Different KGKs can be used for each logical key number. A KGK, as well as all keys 

derived from it, is derived on the basis of the key version. The key version for the 

respective logical key number in the related EF_KEYD indicates from which KGK the 

respective card-specific key is derived. 

♦ Format 

For the EF_KEY of the DF_BANKING_20 the following FCP must be stipulated: 



'82' '05' '12 41 00 12 03' File describer for linear EF with fixed record 

length (18 bytes), 3 records 

'83' '02' '00 10' File ID of the EF_KEY 

'88' '01' '10' SFI '02' for the EF_KEY 

'A1' '06' '8B 04 00 30 02 04' Access rule references 

The EF_KEY is only allowed to be accessed in SE #2. 

The commands APPEND RECORD and UPDATE RECORD are only allowed to be 

executed if they are implemented with secure messaging, the record content is 

encoded (ENC) and the command message is protected with a MAC. Encryption and 

the forming of the MAC takes place with the K HBCI_Admin. The return code of an 

APPEND RECORD or UPDATE RECORD is MAC-protected with the K HBCI_Admin. The 

command READ RECORD is never allowed to be implemented. (access rule in Record 

4 of the EF_RULE) 

18 In order to reserve the term "Signature key" in accordance with EU Directive, the term "Data 

authentication key" was used here. In the further course of the text, however, it will be said that a 

message is signed with this key.




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

119 

♦ Data 

The EF_KEY in DF_BANKING_20 contains 3 Records with the DF-specific keys of the 

DF_BANKING_20. 

Logical key Key version 

Key 

number 

'01' 'XX' 16-byte long K HBCI_Admin 

'02' 'XX' 16-byte long K DAK 

'03' 'XX' 16-byte long K ENC 

The key versions 1 to 127 are used.

Chapter: 

VIII 

Page: 

120 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



VIII.8.2.4 

EF_KEYD 


The EF_KEYD in the DF_BANKING_20 contains the additional information on the DFspecific 

keys of the DF_BANKING_20. 

♦ Format 

For the EF_KEYD the following FCP must be stipulated: 


'62' '1C' Tag and length for FCP 

'82' '05' '14 41 00 1C 03' File describer for linear EF with variable 

record length (max. 28 bytes) and 3 

Records 

'83' '02' '00 13' File ID of the EF_KEYD 

'85' '02' '00 48' Storage space allocated for utilisation data 

in bytes 

'88' '01' 'F0' SFI '1E' for the EF_KEYD 



and reply message are allowed to be executed (access rule in Record 2 of the 

EF_RULE). 

In SE #2 APPEND RECORD and UPDATE RECORD is only allowed to be executed, if 

it is carried out with secure messaging. The MAC is formed for the command and reply 

message with the K HBCI_Admin (access rule in Record 5 of the EF_RULE). 

♦ Data 

The EF_KEYD contains 3 records, which contain the additional information on the DFspecific 

keys of the DF_BANKING_20. 

The data object with Tag '93' contains as a second byte in the value field the version of 

the respective key. 

The following shows the structure of the key additional information: 

Entry 1 (K HBCI_Admin):




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

121 


'93' '02' '01 XX' Key number and key version 

'C0' '02' '81 10' Symmetrical key of the length 16 bytes 

'90' '01' 'FF' Operator error counter 

'7B' '0F' SE data object 

'80' '01' '02' Definition for SE #2 

'B4' '04' CCT - tag and length (usage qualifier '30' is default 

value) 

'89' '02' '12 22' Algorithm ID: key may be used for creating a retail 

MAC in CFB mode 

'B8' '04' CT - tag and length (usage qualifier '10' is default 

value) 

'89' '02' '11 23' Algorithm ID: key may only be used for encryption as 

Triple-DES key in CBC mode with ICV ≠ 0 and ICV 

variant 

Entry 2 (K DAK): 




'7B' '0C' SE data object 



'95' '01' '20' Usage qualifier: only SM reply message 

'89' '02' '12 22' Algorithm ID: key may be used for creating a retail 

MAC in CFB mode 

Entry 3 (KENC): 




'7B' '0C' SE data object 



'95' '01' '40' Usage qualifier: only internal authentication 

'89' '02' '21 12' Algorithm ID: key only allowed to be used for 

authentication of the chip card with Triple-DES

Chapter: 

VIII 

Page: 

122 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



VIII.8.2.5 

EF_PWD 


The local EF_PWD in the DF_BANKING_20 contains the length of the HBCI PIN and a 

reference value of the HBCI PIN of the ZKA chip card in the 9-bytes-long Record '01'. 

The HBCI PIN has a minimum length of 5 digits and is allowed to be a maximum of 12 

digits long. 

♦ Format 

For the EF_PWD of the DF_BANKING_20 the following FCP are to be defined: 


'62' '16' 

'82' '05' '12 41 00 09 01' File describer for linear EF with fixed record length of 

9 bytes 

'83' '02' '00 12' File ID of the EF_PWD 

'88' '01' '18' SFI '03' for the EF_PWD 

'A1' '06' '8B 04 00 30 02 

04' 

Access rule reference 

On the EF_PWD is only allowed to take place in SE #2: the commands APPEND 

RECORD and UPDATE RECORD are only allowed to be executed if they are 

implemented with secure messaging, the record content is encoded (ENC) and the 

command message is protected with a MAC. Encoding and the formation of the MAC 

are carried out by means of the K HBCI_Ad min. The return code of an APPEND RECORD 

or UPDATE RECORD is MAC-protected. The formation of the MAC is carried out for 

the reply message by means of the K HBCI_Admin. The command READ RECORD is 

never allowed to be executed (access rule in Record 4 of the EF_RULE). 

♦ Data 

The record '01' of the EF_PWD contains a reference value of the HBCI PIN. 

Bytes Content Description 

1 '05' Length of the PIN 

2 - 9 'XX..XX' Reference value of the 

PIN 

For the generation of the reference value the 8-bytes-long 'Format 2 PIN Block' is first 

created in accordance with [ISO PIN1] from the HBCI PIN as follows: 

Explanation: 

C L P P P P P P/F P/F P/F P/F P/F P/F P/F F F 

Each field represents a half-byte. 

Each field represents a half-byte: 

C: Check field, binary coded always has the value '2' 

L: PIN length, binary coded possible values from '5' to 'C'




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

123 

P: PIN digit, BCD coded 

F: Filler, binary coded always has the value 'F' 

P/F: PIN/Filler 

depending on the PIN length 

The generated format 2 PIN Block is given the code PB. From this PIN Block the 

reference value which is to be stored is generated by means of the DES encryption with 

itself: 

PIN reference value: 

ePB(PB) 

If necessary, a parity adjustment is carried out before using PB as a DES key. PB is 

used unchanged as plain text.

Chapter: 

VIII 

Page: 

124 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



VIII.8.2.6 

EF_PWDD 


The EF_PWDD in the DF_BANKING_20 contains in Record '01' the additional 

information on the HBCI PIN stored in the EF_PWD of the DF_BANKING_20. 

♦ Format 

For the EF_PWDD the following FCPs must be defined: 


'62' '1C' 

'82' '05' '14 41 00 15 01' File describer for linear EF with variable 

record length (max. 21 bytes) and 1 record 

'83' '02' '00 15' File ID of the EF_PWDD 

'85' '02' '00 15' Bytes of storage space allocated for 

utilisation data 

'88' '01' '20' SFI '04' for the EF_PWDD 




EF_RULE). 

In SE #2 APPEND RECORD and UPDATE RECORD only are allowed to be executed, 

if they are implemented with secure messaging and the command message is 

protected with a MAC. The return code is MAC-protected. The MAC is formed for the 

command and reply message by means of the K HBCI_Admin (access rule in Record 5 of 

the EF_RULE). 

♦ Data 

The local EF_PWDD contains in Record '01' a 21-byte-long record which contains the 

additional information on the HBCI PIN. 

Tag Length Value Description 

'93' '02' '01 01' Password reference: Password '01' in 

Record '01' of the EF_PWD 

'89' '02' '11 50' Storage format of the password (minimum of 

5 digits) 

'7B' '0B' SE-DO, tag and length 

'80' '01' '00' SE reference DO: for all SEs 

'A1' '03' '8B 01 08' Access rule reference 

'89' '01' '12' Transmission format of the authentication 

data: PIN Format 2 Block




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

125 

VIII.8.2.7 

EF_FBZ 


EF_FBZ indicates the linear EF, which in Record '01' contains the operator error 

counter and the related initial value for the HBCI PIN stored in the DF-specific 

EF_PWD. 

♦ Format 

For the EF_FBZ in the DF_BANKING_20 the following FCPs must be defined: 



'82' '05' '12 41 00 02 01' File describer for linear EF fixed record 

length 

'83' '02' '00 16' File ID of the EF_FBZ 

'88' '01' '28' SFI '05' for the EF_FBZ 


In SE # 1 only the commands READ / SEARCH RECORD with unprotected command 


EF_RULE). 

In SE #2 the commands APPEND RECORD and UPDATE RECORD are only allowed 

to be executed, if they with are implemented with secure messaging and the command 

message is protected with a MAC. The return code is MAC-protected. The MAC is 

formed for the command and reply message by means of the K HBCI_Admin (access rule 

in Record 5 of the EF_RULE). 

♦ Data 

The EF_FBZ contains in Record '01' a 2-byte-long record, which contains the operator 

error counter and the related initial value '03' for the HBCI PIN. 

Initial value of the 

FBZ 

'03' 

FBZ 

'03'

Chapter: 

VIII 

Page: 

126 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



VIII.8.2.8 

EF_BNK 


The EF_BNK is a linear EF with 5 records in which 5 financial institution connections 

are stored. 

♦ Format 

For the EF_BNK in an HBCI chip card the following FCP must be defined: 



'82' '05' '12 41 00 58 05' File describer for linear EF with fixed record 

length 88 Byte and 5 Records 

'83' '02' '03 01' File ID of the EF_BNK 

'88' '01' 'D0' SFI '1A' for the EF_BNK 


In SE #1 READ / SEARCH RECORD are always allowed to be executed. The reply 

message is not protected. UPDATE RECORD is only allowed to be executed, if a card 

owner-authentication by means of the local password 1 (HBCI PIN) has been carried 

out beforehand. The return code is not MAC-protected (access rules in Record 6 of the 

EF_RULE). 

In SE #2 the command APPEND RECORD is only allowed to be executed, if it is 

implemented with secure messaging. The MAC is formed for the command and reply 

message by means of the K HBCI_Admin (access rule in Record 3 of the EF_RULE). 

♦ Data 

The record comprises a financial institution short name, the financial institution code, 

the communications service, the address and the address extension for the 

communications access, the country code and the user ID.. 

Bytes Length Value Explanation 

1-20 20 'aa .. aa' Short name of the financial institution 

21-24 4 'nn nn nn nn' Financial institution code of the financial institution where 

the account is kept 

25-25 1 'n' Communications service 

26-53 28 'aa .. aa' Communications address 

54-55 2 ‘aa aa’ Communications address extension 

56-58 3 'aa aa aa' Country code of the financial institution where the account 

is kept 

59-88 30 'aa .. aa' User ID 

Contents of alphanumeric fields (‘a’) are in all cases ASCII coded, entered left-justified 

and padded out with blanks (X’30’) to the required length. Contents of numeric fields 

(‘n’) are in all cases BCD coded.




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

127 

VIII.8.2.9 

EF_MAC 


The EF_MAC is used for forming the MAC via the hash value of a message. It consists 

of a record 12 bytes long whose access rules must be so set that the MAC is produced 

while the record is read in. 

♦ Format 

For the EF_MAC the following FCPs must be defined: 



'82' '05' '12 41 00 0C 01' File describer for linear EF with a record 

which 12 bytes long 

'83' '02' '03 02' File ID of the EF_MAC 

'88' '01' 'D8' SFI '1B' for the EF_MAC 


In SE #1 READ / SEARCH RECORD are allowed to be executed after card ownerauthentication. 

The reply message has a K DAK-MAC. UPDATE RECORD is only 

allowed to be executed, if card owner-authentication by means of the local password 1 

(HBCI PIN) has been carried out beforehand. The return code of an UPDATE RECORD 

is not MAC-protected (access rules in Record 7 of the EF_RULE). 

In SE #2 the command APPEND RECORD is allowed to be executed, if it is 

implemented with secure messaging. The MAC is formed for the command and reply 

message by means of the K HBCI_Admin (access rule in Record 3 of the EF_RULE). 

♦ Data 

The EF_MAC contains a record with the following structure: 

Bytes Value Explanation 

1-12 'XX..XX' Hash value

Chapter: 

VIII 

Page: 

128 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



VIII.8.2.10 

EF_SEQ 


The EF_SEQ is a linear data file, whose record contains a 2 bytes long binary defined 

element. This binary ascending counter flows in as a security reference number 

(signature ID) for protecting the data against duplicate submission. The starting value of 

the counter is 1. If an overrun occurs there is no restart. 

For the EF_SEQ the following FCP must be defined: 



'82' '05' '12 41 00 02 01' File describer for linear EF with 1 record 2 

bytes long 

'83' '02' '03 03' File ID of the EF_SEQ 

'88' '01' 'E0' SFI '1C' for the EF_SEQ 


In SE #1 READ / SEARCH RECORD are always allowed to be executed. The reply 

message is not protected. UPDATE RECORD is only allowed to be executed, if 

beforehand card owner-authentication by means of the local password 1 (HBCI PIN) 

has been carried out. The return code is not MAC-protected (access rules in Record 6 

of the EF_RULE). 

In SE #2 the commands APPEND RECORD and UPDATE RECORD only are allowed 

to be executed, if they are implemented with secure messaging. In each case the MAC 

is formed for the command and reply messages by means of the K HBCI_Admin (access rule 

in Record 5 of the EF_RULE). 

♦ Data 

The EF_SEQ contains 1 record with the following structure: 


1-2 'XX XX' Sequence number




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

129 

VIII.8.3 

Space requirement of the application in the chip 

The calculation of space requirement is very heavily dependent on the thickness of the 

ROM entry screen. The necessary space for the EF management, e.g. record numbers 

and address administration, is directly connected to the management of the E 2 -PROM. 

This management is a component of the ROM entry screen. The actual precise space 

requirement can only be determined by the ROM entry screen developers. It is different 

from chip to chip and from ROM entry screen to ROM entry screen. 

♦ Type 0 

The following table therefore contains only the net data size of the "Banking" 

application. 

Filename Header size Data size 

DF_Banking 28 26 

EF_KEY 23 17 

EF_KEYD 23 5 

EF_AUT 23 17 

EF_AUTD 23 4 

EF_PWD1 25 8 

EF_PWDD1 23 5 

EF_BNK 23 440 

EF_MAC 23 12 

EF_SEQ 23 2 

237 536 

Consequently the application "Banking" has a minimum space requirement of 773 

bytes. 

♦ Type 1 

The following table therefore only contains a rough estimation of the net data size (in 

bytes) of the application. Therefore the size of the respective FCP was used as the 

basis for the overhead. In addition the FMD of the DF_BANKING_20 (contains the 

assigned SFIs and their paths) was interpreted as ”utilisation data ” of the DF. 

File name Overhead Utilisation data 

DF_BANKING_20 28 68 

EF_KEY 24 54 

EF_KEYD 30 72 

EF_PWD 24 9 

EF_PWDD 30 21 

EF_FBZ 26 2 

EF_RULE 30 125 

EF_BNK 26 440 

EF_MAC 26 12 

EF_SEQ 26 2

Chapter: 

VIII 

Page: 

130 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



270 805 

Accordingly the HBCI application has a space requirement of approximately 1075 

bytes.




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

131 

VIII.8.4 

sequences 

Terminal sequences (Type 0 and Type 1) Chip cards and terminal 

The following specifies the application sequences from the point of view of the terminal 

equipment. Here the chip card-related aspects are taken into consideration. Applicationrelated 

details are not part of this specification. 

If an error occurs during the execution of a command, the terminal terminates the 

process, unless a deviating behaviour is specified. 

VIII.8.4.1 

Start session 

HBCI chip card 

Terminal/Gateway 

R1 ATR of the HBCI chip card 

R2 OK 

R3 Card identification data (CID) 

R4 OK 

R4 Sequence number (SEQ) 

R5 Financial institution connection 

 

 

 

 

 

 

 

 

 

 

 

 

A1 

C1 

C2 

C3 

A3 

A4 

C4 

C5 

A5 

C6 

A6 

Display: ‘Please enter card’ 

Reset HBCI chip card 

SELECT FILE DF_BANKING(_20) 

READ RECORD EF_ID 

Check and store CID 

HBCI PIN entry and formatting 

VERIFY HBCI PIN 

READ RECORD EF_SEQ 

Store SEQ 

READ RECORD EF_BNK 

Check and store data 

♦ Explanation 

1. After the HBCI chip card has been entered the card is reset (communications protocol 

T = 1). The correct ATR and its handling are, for instance, specified in [LT]. 

2. The application HBCI Banking is opened through the ADF of the application 

DF_BANKING_20 for HBCI cards of type 1 or DF_BANKING for HBCI cards of type 0 

being selected by the terminal using the command SELECT FILE. In the course of this 

process initially there is an attempt to select the new application DF_BANKING_20. If 

the return code is '6A 82' the application is not available. The "old" application 

DF_BANKING will then be selected.

Chapter: 

VIII 

Page: 

132 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



Command APDU: 


1-2 '00 A4' CLA, INS 

3 '04' P1, selection with DF name 

4 '0C' P2, no answer data 

5 '09' L c 

6-14 'D2 76 00 00 25 48 42 0X 00' AID of the HBCI application (X=1.2) 

After the application context has been opened, the AEFs of the application can be 

referenced by means of SFI. The terminal holds the information on which type of card it 

is 

3. The terminal uses READ RECORD to read the card identification data in Record '01' of 

the EF_ID in the MF of the HBCI card (SFI '19'). 

Command APDU: 


1-2 '00 B2' CLA, INS 

3 '01' P1, record number 

4 'CC' P2, reference control byte 

5 '00' L e 

If the READ RECORD is successfully implemented the HBCI card returns a reply 

message with the following structure. 


1 '67' Branch main key 

2-4 '2n nn nn' Short routing number of institution issuing card 

5-9 'nn..nn' Individual card number 

10 'nD' Check character for bytes 1 - 9 

11-12 'YY MM' Expiry date of the card 

13-15 'YY MM TT' Activation date of the card 

16-17 '0280' Country code 

18-20 '44 45 4D' or '45 55 52' Currency code "DEM" or "EUR" 

21 '01' Value of the currency 

22 'XX' Chip type 

23 '00' Filler 

24 'XX' Operating system version 

23-24 

or 25- 

26 

'XX XX' 

Positive return code SW1 SW2 

The answer data are at least 22 bytes long and can be longer than 24 bytes for cards of 

type 1. 

The coding of the received data is checked: 

If a card of type 0 issue more than 22 bytes of answer data, or if a card of type 1 issues 

less than 24 bytes of answer data, or if the currency code in bytes 18-20 or the value of




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

133 

the currency in byte 21 are not correctly coded, or if a card of type 0 issues the currency 

code "EUR" or a card of type 1 issues the currency code "DEM", or if byte 24 of a card 

of type 1 has the value '00' and in every other case of an error the process will be 

terminated with an error message. 

4. The terminal requests the card owner to enter the PIN and then formats the entered 

PIN to format 2 PIN-Block FPIN2. The terminal builds a command message for the 

command VERIFY. 

Command APDU: 


1 '00 20' CLA, INS 

3 '00' P1, fixed value 

4 '81' P2, search for PIN in the EF_PWD1 of the DF 

(and has PWDID ´01´) 

5 '08' L c 

6-13 'XX..XX' FPIN2 

The chip card carries out the PIN check and sets the flag of the appropriate security 

condition if the PIN check was successful. If this is not the case, the PIN operator error 

counter is decremented. 

By means of the return code of the command VERIFY the chip card informs the 

terminal whether the check was successful and how many attempts are still possible. 

5. The terminal uses READ RECORD to read the sequence number in Record '01' of the 

EF_SEQ (SFI '1C'). 

Command APDU: 


1-2 '00 B2' CLA, INS 


4 'E4' P2, reference control byte 

5 '00' L e 

If the READ RECORD is successfully implemented, the HBCI card returns a reply 

message with the following structure. 


1-2 'XX XX' Sequence counter 

3-4 'XX XX' Positive return code SW1 SW2 

The terminal stores the value of the sequence counter. 

6. The terminal uses READ RECORD to successively read the financial institution 

connections data in the records of the EF_BNK (SFI '1A'), until the ”fitting” entry is 

found.

Chapter: 

VIII 

Page: 

134 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



Command APDU: 


1-2 '00 B2' CLA, INS 

3 '0X' P1, record number X 

4 'D4' P2, reference control byte 

5 '00' L e 

If the READ RECORD is successfully implemented the HBCI card returns a reply 

message with the following structure: 

Bytes Length Value Explanation 

1-20 20 'aa .. aa' Short name of the financial institution 

21-24 4 'nn nn nn nn' Financial institution code of the financial institution 

where the account is kept 

25-25 1 'n' Communications service 

26-53 28 'aa .. aa' Communications address 

54-55 2 ‘aa aa’ Communications address extension 

56-58 3 'aa aa aa' Country code of the financial institution where the 

account is kept 

59-88 30 'aa .. aa' User ID 

89-90 2 'XX XX' Positive return code SW1 SW2 

Alternatively for chip cards of Type 1 the command SEARCH RECORD can be used, in 

order to find the ”fitting” entry in one step by means of a transferred search model 

Example: the first entry on a stipulated routing number of the financial institution where 

the account is kept is to be found (byte positions 21-24): 

Command APDU: 


1-2 '00 A2' CLA, INS 

3 '01' P1, record number where the search starts 

4 'D7' P2, reference control byte (SFI + specific search) 

5 '07' L C 

6 '04' Control byte 

7 '14' Offset 20 = Byte 21 

8 '0E' Configurations byte: search at this position until 

first successful record with return of the content 

9-12 'nn nn nn nn' Financial institution code search model 

13 '00' L e 

In the case of successful command execution the command SEARCH RECORD issues 

the following message:




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

135 


1 'XX' Record number 

2-89 'XX..XX' Record content 

90-91 'XX XX' Status bytes 

Further, more comprehensive search options are also possible (e.g. locate all fitting 

entries or interval search), see [LIT 1´].

Chapter: 

VIII 

Page: 

136 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



VIII.8.4.2 

Generate message 

This part of the overall sequence is only relevant to chip cards, insofar as financial 

institution connections data which are required for the order generation are taken from 

the chip card. For the following sequence description it is assumed that the application 

has also generated HBCI messages. If necessary, these messages have to be also 

protected cryptographically, i.e. segments are entered for the electronic signatures and 

for the encryption in accordance with HBCI specifications.




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

137 

VIII.8.4.3 

Signing message 

The following sequences can be carried out offline, i.e. outside the transmission 

session. This applies to all messages with the exception of the session initialisation. 

The reason for this is that key of the sender of the session message is necessary for 

the protection of all financial institution messages. Therefore the chip card of the sender 

must also remain inserted in the terminal during the entire session. 

The sequences for the signature of the session initialisation message are always 

identical with the sequences for the signature of order messages, as described below. 

However, since further chip cards are required by the application for the session 

initialisation (User ID, Session ID, communications setting, etc.), the complete 

sequence, including the signature of the session initialisation, is described again in 

Chapter VIII.8.4.5 "Transmission Session". 


R1a KV 

R1b OK 

R1c Data record 

R6 OK 

 

 

 

 

 

 

 

 

 

 

C1a 


GET KEYINFO (only type 1) 

A1a Store key version KV 

C1b SELECT EF_KEYD (only type 0) 

C1c 

A1c 

A2 

A3 

A4 

M5 

C6 

A7 

A8 

A9 

A10 

READ RECORD EF_KEYD (only type 0) 

Store key version KV 

Increment sequence counter (Signature 

ID) SEQ 

Build signature header and insert in HBCI 

message 

Provide data (signature header, HBCI 

utilisation data) for MAC calculation 

Use data for MAC calculation (see section 

VIII 8.5.1) 

UPDATE RECORD EF_SEQ with SEQ 

Build signature closer and insert in HBCI 

message 

If necessary, repeat A2 to A7 for further 

messages 

Store signed HBCI messages for further 

processing 

If necessary, repeat start session and A1 

to A9 for multiple signatures 


1. In this step the terminal ascertains which data authentication key KGK DAK and K DAK 

must be used as a signature of the message. Here step 1a is only implemented for 

cards of Type 1, and step 1b and 1c is only implemented for cards of type 0.

Chapter: 

VIII 

Page: 

138 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



1a. If its is a HBCI card of type 1, the command GET KEYINFO is used for this purpose. 

Command APDU: 


1-2 ‘B0 EE’ CLA,INS 

3 '80' P1 for "DF-specific" 

4 ‘02’ P2, key number 

5 ‘00’ L e 

If GET KEYINFO is successfully implemented, the HBCI card returns a reply message 

with the following structure: 


1 'XX' 1 existing key version KV 

2-3 ‘XX XX’ Positive return code SW1 SW2 

The key version is stored. 

1b. If it is an HBCI card of type 0, the EF_KEYD in the DF_BANKING is selected by means 

of SELECT FILE EF_KEYD. 

Command APDU: 


1-2 '00 A4' CLA, INS 

3 '02' P1, Selection of an EF in the current DF 

4 '0C' P2, no answer data 

5 '02' L c 

6-7 '00 13' File ID of EF_KEYD 

1c. The terminal uses READ RECORD to read the additional information for the key K DAK 

from Record ‘02’. 

Command APDU: 


1-2 '00 B2' CLA, INS 

3 '02' P1, record number for logical key no. ‘02’ 

4 ‘04' P2, reference control byte 

5 '00' L e 

If READ RECORD was successfully executed, the HBCI card returns the following reply 

message: 


1 '02' Logical key number 

2 '10' Key length 

3 '07' Algorithm ID 

4 'XX' Operator error counter 

5 'XX' Key version 

6-7 ‘XX XX’ Positive return code SW1 SW2




The key version is stored. 

Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

139 

2. The previously read and stored sequence counter SEQ is incremented. 

3. The signature header is generated and inserted in the HBCI message. 

4. The data (signature header, HBCI utilisation data) for the MAC calculation are provided. 

5. The MAC on the data is calculated (see section VIII 8.5.1). 

6. The terminal overwrites the sequence counter in EF_SEQ with the incremented value. 

This takes place by means of UPDATE RECORD EF_SEQ without Secure Messaging. 

Due to the access conditions for the EF_SEQ, the command can only be executed if 

the HBCI PIN was successfully verified beforehand. 

Command APDU: 


1-2 '00 DC' CLA, INS 


4 'E4' P2, reference control byte (SFI ‘1C‘) 

5 '02' L c 

6-7 'XX XX' New sequence counter SEQ 

7. The signature closer is generated and inserted in the HBCI message. 

8. If necessary, the steps 2 to 7 can be repeated for further messages. Step 1 does not 

have to be repeated, since the key version to be used is already stored. 

9. The signed HBCI messages can be stored for further processing. 

10. If necessary, the start session and the steps 1 to 9 can be repeated for multiple 

signatures.

Chapter: 

VIII 

Page: 

140 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



VIII.8.4.4 Encrypting message 


R1a KV 

R1b OK 

R1c Data record 

R3 RND 

R4 e* K ENC(KS L) 

R5 RND 

R6 e* K ENC(KS R) 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

C1a 


GET KEYINFO (only type 1) 

A1a Store key version KV 

C1b SELECT EF_AUTD (only type 0) 

C1c 

READ RECORD EF_AUTD (only type 0) 

A1c Store key version KV 

A2 Provide data (HBCI utilisation data and, if 

necessary, signature header/signature 

closer) for the encryption 

C3 GET CHALLENGE 

A3 

C4 

A4 

C5 

A5 

C6 

Store RND as message key half KS L 

INTERNAL AUTHENTICATE with KS L 

Store e* K ENC(KS L) 

GET CHALLENGE 

Store RND as message key half KS R 

INTERNAL AUTHENTICATE with KS R 

A6 Store e* K ENC(KS R) 

A7 Concatenate e* K ENC(KS L) with e* 

K ENC(KS R) to e* K ENC(KS) and store 

A8 Concatenate KS L with KS R to KS and 

encrypt data with KS (triple DES CBC 

mode, IV=0, X9.23 padding) 

A9 Construct signature header and insert in 

HBCI message 

A10 Insert encrypted data as binary data in 

HBCI message 

A11 If necessary, repeat A2 to A10 for further 

messages 

A12 Store encrypted and signed HBCI 

messages for further processing 


1. In this step the terminal establishes which version of the encryption key KGK ENC or 

K ENC must be used for encrypting the message. In doing so step 1a is only carried out 

for cards of type 1, and step 1b and 1c is only carried out for cards of type 0. 

1a. If it is an HBCI card of type 1, the command GET KEYINFO is used for this. 

Command APDU:

Chapter: 

VIII 

Page: 

142 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



3. The GET CHALLENGE command can be used to give the terminal a random number 

from the HBCI card. 

Command APDU: 


1-2 '00 84' CLA, INS 

3 '00' P1 

4 '00' P2 

5 '00' L e 

If the command was successfully implemented the HBCI card issues a random number 

8 bytes long as an answer date, which is stored as message key half KS L . 

4. The INTERNAL AUTHENTICATE command is used for encrypting the value KS L from 

the HBCI card with the key K ENC encrypted and transmitted in the answer message as 

e* K ENC (KS L ). 

Command APDU: 


1-2 '00 88' CLA, INS 

3 '00' P1 

4 '80' '83' P2, type 0: '80' (log. key number '00'), 

Type 1: '83' (log. key number '03') 

5 '08' L c 

6-13 'XX .. XX' Random number KS L 

14 '00' L e 

The command INTERNAL AUTHENTICATE returns the following answer message: 


1-8 'XX .. XX' Encrypted value e* K ENC(KS L) 


5. With the command GET CHALLENGE the terminal can be given a further random 

number from the HBCI card, which is stored as message key half KS R . 

6. Analogue to step 4 an INTERNAL AUTHENTICATE is carried out with KS R . 

7. e* K ENC (KS L ) is concatenated with e* K ENC (KS R ) to e* K ENC (KS) and stored. 

8. KS L is concatenated with KS R to KS and the data are encrypted with KS (triple DES 

CBC mode, IV=0, X9.23 padding). 

9. The encryption header is built up and inserted in the HBCI message. 

10. The encrypted data is inserted in the HBCI message as binary data. 

11. If necessary, steps 2 to 10 are repeated for further messages (it is not necessary to 

repeat step 1). 

12. The encrypted and signed HBCI messages are stored for further processing.




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

143 

VIII.8.4.5 

Transmission session 

HBCI chip card Terminal/Gateway Financial 

Institution 

A1 Increment sequence counter 

(signature ID) SEQ 

A2 Locate user ID from the FI 

connection which has already been 

read (EF_BNK) 

A3 Construct dialogue initialising 

message 

A4 Construct signature header and 

insert in HBCI message 

A5 Provide data (signature header, 

HBCI utilisation data) for MAC 

calculation 

 

 

M6 Calculate MAC from data (see 

section VIII 8.5.1) 

R7 

OK 

 

 

 

 

 

 

C7 UPDATE RECORD EF_SEQ with 

SEQ 

A8 Construct signature closer and insert 

in HBCI message 

A9 

C10 Transmit message (beginning with 

dialogue initialisation message) 

If answer message encrypted: 

provide data (binary data after the 

A11 signature header) and d*K ENC(KS) 

from the signature header for the 

decoding 

M12 Decode data (see section VIII 8.5.2) 

A13 If financial institution message 

signed: 

provide data (signature header, 

utilisation data) and reference MAC 

for MAC testing 

M14 Test MAC via data and reference 

MAC (see VIII.8.5.1) 

A15 Repeat C10 to M14 for all further 

HBCI messages 

 

R10 Transmit 

answer 

message

Chapter: 

VIII 

Page: 

144 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



VIII.8.5 

Macros




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

145 

VIII.8.5.1 

R3 OK 

R4 OK 

MAC calculation / test 


R5 Data from EF_MAC with 

CFB-64 MAC over HASH R 

(identical to CBC-MAC over 

HASH) 

 

 

 

 

 

 


A1 Calculate hash value HASH over data 

(RIPEMD160) 

A2 Dissect HASH into HASH_L (the left 8 

bytes of HASH) and HASH R (the 

remaining 12 bytes) 

C3 UPDATE RECORD EF_MAC with 

HASH R 

C4 PUT DATA with HASH L (only type 0) 

C5 

A5 

READ RECORD EF_MAC with secure 

messaging 

(for type 1 here HASH L is also 

transmitted) 

When calculating MAC: Save MAC 

When making MAC test: compare 

MAC from financial institution with 

MAC of chip card 


1. The hash value HASH is calculated over the data (RIPEMD160). 

2. The hash value HASH is dissected into HASH L (the left 8 bytes of HASH) and HASH R 

(the remaining 12 bytes). 

3. HASH R is entered in the first record of the EF_MAC. The access condition for the 

EF_MAC ensures that the UPDATE command can only be executed if the HBCI PIN 

has been verified beforehand. 

Command APDU: 


1-2 '00 DC' CLA, INS 


4 'DC' P2, reference control byte (SFI ‘1B‘) 

5 '0C' L c 

6-17 'XX .. XX' Record content HASH R 

4. The terminal transmits HASH L to the HBCI card by means of PUT DATA. This step is 

only carried out for cards of type 0, since for cards of type 1 the random value is 

transmitted in the next step as part of the command. 

Command APDU:

Chapter: 

VIII 

Page: 

146 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 




1-2 '00 DA' CLA, INS 

3-4 '01 00' P1, P2 

5 '08' L c 

6-13 'XX..XX' HASH L 

5. The terminal uses READ RECORD to read the hash value with secure messaging 

which has just been entered in EF_MAC. 

Command APDU for chip cards of type 0: 


1-2 '04 B2' CLA, INS 


4 'DC' P2, reference control byte 

5 '00' L e 

If the READ RECORD is successfully executed, the HBCI card returns an answer 



1-12 'XX ... XX' Record content HASH R 

13-20 'XX ... XX' CFB-MAC with KENC over the 16 bytes 1-12|’00 

00 00 00‘ with ICV= HASH L 


Command APDU for chip cards of type 1: 19 


1-2 '08 B2' CLA, INS with secure messaging 


4 ‘DC' P2, reference control byte 

5 '11' L C 

6-7 'BA 0C' Day and length for response descriptor 

8-9 'B4 0A' Day and length for CCT 

10-11 '87 08' Day and length for random number 

12-19 'XX..XX' Random number HASH L 

20-22 '96 01 00' Day, length and value of the L e data object 

23 '00' L e 

If the READ RECORD is successfully executed, the HBCI card returns an answer 


19 With regard to the transfer of ICVs on Response Descriptors see chapter 8.6.1.1 of [LIT 1'].




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

147 


1-2 '81 0C' Day and length of the plain text data object 

3-14 'XX ... XX' Record content HASH R 

15-16 '8E 08' Day and length of the MAC data object 

17-24 'XX ... XX' CFB-MAC with KENC over bytes 1-12|’80 00 00 

00‘with ICV HASH L 


The terminal stores the MAC value.

Chapter: 

VIII 

Page: 

148 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



VIII.8.5.2 Encryption 


R2 KS L 

R3 KS R 

 

 

 

 


A1 Dissect d* K ENC(KS) into the two halves d* 

K ENC(KS L) and d* K ENC(KS R) 

C2 INTERNAL AUTHENTICATE with d* 

K ENC(KS L) 

A2 Store KS L 

C3 INTERNAL AUTHENTICATE with d* 

K ENC(KS R) 

A3 Store KS R 

A4 Concatenate KS L with KS R to KS 

concatenate and encrypt data with KS (triple 

DES CBC mode, IV=0, X9.23 padding) 


1. d* K ENC (KS) is dissected into the two halves d* K ENC (KS L ) and d* K ENC (KS R ). 

2. With the command INTERNAL AUTHENTICATE the value d* K ENC (KS L ) is encrypted 

from the HBCI card with the key K ENC and transmitted in the answer message as KS L . 

Command APDU: 


1-2 '00 88' CLA, INS 

3 '00' P1 

4 '80' or '83' P2, type 0: '80' (log. key number '00'), 

type 1: '83' (log. key number '03') 

5 '08' L c 

6-13 'XX .. XX' Parameter value d* K ENC(KS L) 

14 '08' L e 

The command INTERNAL AUTHENTICATE returns the following answer message: 


1-8 'XX .. XX' Decoded value KS L 


KS L is stored. 

3. Analogous to step 2 an INTERNAL AUTHENTICATE is executed with d* K ENC (KS R ). 

The result is stored as KS R . 

4. KS L is concatenated with KS R to KS and the data are encrypted with KS (triple DES 

CBC mode, IV=0, X9.23 padding).




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

149 

VIII.8.6 Overview of the chip applications parameters (type 1) 

♦ File structure 

Location File ID Name SFI Access rule 

SE #1 

(standard) 

Access rule 

SE #2 

(admin) 

MF '00 03' EF_ID '19' 

'A6 00' DF_BANKING_20 1 

DF_BANKING_20 '00 30' EF_RULE '01' 2 3 

'00 10' EF_KEY '02' -- 4 

'00 12' EF_PWD '03' -- 4 

'00 13' EF_KEYD '1E' 2 5 

'00 15' EF_PWDD '04' 2 5 

'00 16' EF_FBZ '05' 2 5 

'03 01' EF_BNK '1A' 6 3 

'03 02' EF_MAC '1B' 7 3 

'03 03' EF_SEQ '1C' 6 5 

♦ Access rules 

# READ / 

SEARCH 

RECORD 

APPEND 

RECORD 

UPDATE 

RECORD 

IN-/EXCLUDE 

CREATE EF 

DELETE self 

VERIFY 

CHANGE 

REF DATA 

RESET 

RETRY 

COUNTER 

1 K HBCI_Admin-MAC 

2 ALW 

3 K HBCI_Admin- NEV 

MAC 

4 K HBCI_Admin-ENC-MAC (K) 

K HBCI_Admin-MAC (A) 

5 K HBCI_Admin-MAC 

6 ALW HBCI PIN 

7 HBCI PIN 

HBCI PIN 

K DAK-MAC 

(A) 

8 ALW K HBCI_Admin- 

MAC 

The specified access conditions apply not only to command (K) but also answer 

messages (A), except where otherwise indicated by means of brackets. 

♦ Keys of the application 

Logical key 

number 

Allowed 

SE # 

Key 

Who knows the master key 

'01' 2 K HBCI_Admin Responsible background system 

'02' 1 K DAK Responsible background system 

'03' 1 K ENC Responsible background system

Chapter: 

VIII 

Page: 

150 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 


Market identifiers 

VIII.9 Market identifiers 

The tables below give a list of selected stock markets with the market identifier codes 

(MIC) as per ISO 10383. Where several markets with different MICs exist in one 

location, the specific market is identified by name in brackets. 

German markets 

Berlin 

Bremen 

Düsseldorf 

Frankfurt 

Hamburg 

Hanover 

Munich 

Stuttgart 

XETRA 

EUREX 

European markets 

Amsterdam (Amsterdam Exchanges) 

Antwerp 

Athens 

Barcelona 

Bern 

Bilbao 

Bordeaux 

Bratislava 

Budapest 

Brussels (Société de la Bourse des Valeurs) 

Brussels (EASDAQ) 

Dublin (Irish Stock Exchange) 

Helsinki (Helsinki Stock Exchange) 

Istanbul 

Copenhagen (Kobenhavns Fondsbors) 

Lille 

Lisbon 

Ljubliana 

London (London Stock Exchange) 

London (London International Financial Futures and 

Options Exchange) 

Luxembourg 

Lyon 

Madrid (Bolsa de Madrid) 

Milan 

Code 

XBER 

XBRE 

XDUS 

XFRA 

XHAM 

XHAN 

XMUN 

XSTU 

XETR 

XEUR 

Code 

XAMS 

XANT 

XATH 

XBAR 

XBRN 

XBIL 

XBOR 

XBRA 

XBUD 

XBRU 

XEAS 

XDUB 

XHEL 

XIST 

XCSE 

XLIL 

XLIS 

XLJU 

XISE 

XLIF 

XLUX 

XLYO 

XMAD 

XMIL



Section: Market identifiers 

Marseilles 

Nancy 

Nantes 

Nicosia 

Oslo 

Paris (Société des Bourses Francaises) 

Prague 

Reykjavik 

Rome (Mercato Italiano Futures) 

Sofia 

Stockholm 

Valencia 

Warsaw 

Valletta 

Vienna (Wiener Wertpapierbörse) 

Vienna (Österreichische Termin- und Optionsbörse) 

Zagreb 

Zurich (Schweizer Börse) 

Zurich (ISMA) 

Version: 

2.2 

Edition: 

2000-05-10 

XMAR 

XNAY 

XNAN 

XCYS 

XOSL 

XPAR 

XPRA 

XICE 

XMIF 

XBUL 

XSSE 

XVAL 

XWAR 

XMAL 

XVIE 

XOTB 

XZAG 

XSWX 

XISM 

Chapter: 

VIII 

Page: 

151 

International markets (non-exhaustive list) 

Bangkok 

Boston 

Buenos Aires 

Chicago (Chicago Stock Exchange) 

Hong Kong (Stock Exchange of Hong Kong) 

Johannesburg (Johannesburg Stock Exchange) 

Kuala Lumpur (Kuala Lumpur Stock Exchange) 

Mexico 

Montreal (Montreal Exchange) 

Moscow 

New York (American Stock Exchange) 

New York (New York Stock Exchange) 

New York (New York Futures Exchange) 

Rio de Janeiro 

San Francisco (Pacific Stock Exchange) 

São Paulo (Bolsa de Valores de São Paulo) 

Shanghai (Shanghai Stock Exchange) 

Singapore (Stock Exchange of Singapore) 

Sydney (Australian Stock Exchange) 

Tokyo (Tokyo Stock Exchange) 

Toronto (Toronto Stock Exchange) 

Code 

XBKK 

XBOS 

XBUE 

XCHI 

XHKG 

XJSE 

XKLS 

XMEX 

XMON 

XMOS 

XASE 

XNYS 

XNYF 

XRIO 

XPSE 

XBSP 

XSHG 

XSES 

XASX 

XTKS 

XTSE

Chapter: 

VIII 

Page: 

152 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 


Calculation of the check character for internal 

VIII.10 Calculation of the check character for internal assignment 

data (Customer reference number) 20 

(Based on DIN ISO 7064, MOD 11,10) 

20 

Taken from "Guidelines for uniform payment transaction forms and leaflets for neutral payment 

transactions forms".



Section: Calculation of the check character for internal 

Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

153 

VIII.10.1 

Calculation procedure 

The internal assignment data (customer reference number) consists of 12 digits plus a 

single-digit check character, giving a 13-character string together. This string is 

processed from left to right, one character at a time. 

Using the index j = 1 to n (where n is the number of characters in the string, including 

the check character) and the starting value P 1 = M for j = 1, one calculates as follows: 

S j = P j I (M+1) + a (n-j+1) 

P (j+1) = S j II M x 2 

where 

II M is the remainder following division by M; if the remainder is zero, then it is 

made equal to M instead 

I (M+1) is the remainder following division by (M+1); this remainder will never be equal 

to zero 

a (n-j+1) is the value of that character digit 

The check is considered to be positive if S n = 1 (mod M). 

To generate the check character, a 1 is chosen so that 

P n I (M+1) + a 1 = 1 (mod M) 

The value found for a 1 is added to the internal assignment data (customer reference 

number).

Chapter: 

VIII 

Page: 

154 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 


Calculation of the check character for internal 

VIII.10.2 

Example 

The internal assignment data (customer reference number) proper consist of the string 

100845456115. The check character is appended to the string on the trailing end, as 

per DIN ISO 7064, MOD 11,10. 

Generation of check character 

Step 

Product 

brought 

forward 

next digit 

value 

Subtotal 

Subtotal 

(mod 10) x 2 

= Product 

Product 

(mod 11) 

carried forward 

j P j I 11 + a (n-j+1) = S j S j II x 2=P (j+1) P (j+1) I 11 

1 2 3 4 

1 10 + 1 = 11 1 x 2 = 2 2 

2 2 + 0 = 2 2 x 2 = 4 4 

3 4 + 0 = 4 4 x 2 = 8 8 

4 8 + 8 = 16 6 x 2 = 12 1 

5 1 + 4 = 5 5 x 2 = 10 10 

6 10 + 5 = 15 5 x 2 = 10 10 

7 10 + 4 = 14 4 x 2 = 8 8 

8 8 + 5 = 13 3 x 2 = 6 6 

9 6 + 6 = 12 2 x 2 = 4 4 

10 4 + 1 = 5 5 x 2 = 10 10 

11 10 + 1 = 11 1 x 2 = 2 2 

12 2 + 5 = 7 7 x 2 = 14 3 

13 3 + 8 = 1 

(mod 10) 

The check character is 8. 

Explanations 

The starting value, to which in the first step the 1st digit value is added, is always 10. 

Subtotal (mod 10): The result of the calculation in column 2 is divided by 10, 

and the integer remainder gives the subtotal S j II 10 . 

If this remainder is 0, then the value 10 is to be assigned 

instead. 

Product (mod 11): The product in column 3 is divided by 11; the remainder 

yields the next step of the calculation. 

Check digit: 

In the final calculation step, the amount carried forward is 

subtracted from 11, i.e. 1 (mod 10). The result of the 

subtraction will be the check character. If the amount 

carried forward from Step 12 is 1, then the check 

character is 0.



Section: Country codes and currency codes 

Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

155 

VIII.11 

Country codes and currency codes 

The following table provides, for a limited number of countries, the country code as per 

ISO 3166-1, the currency code and the number of decimal places for the national 

currency, as per ISO 4217. 

Name of country 

Country 

code 

(numeric) 

Country 

code (Alpha- 

2) 

Currency 

code 

Decimal 

places 

Austria 040 AT ATS 2 

Belgium 056 BE BEF 0 

Bulgaria 100 BG BGL 2 

Canada 124 CA CAD 2 

Croatia 191 HR HRK 2 

Czech Republic 203 CZ CZK 2 

Denmark 208 DK DKK 2 

Finland 246 FI FIM 2 

France 250 FR FRF 2 

Germany 280 21 DE DEM 2 

Great Britain 826 GB GBP 2 

Greece 300 GR GRD 0 

Hungary 348 HU HUF 2 

Iceland 352 IS ISK 2 

Ireland 372 IE IEP 2 

Italy 380 IT ITL 0 

Japan 392 JP JPY 0 

Liechtenstein 438 LI CHF 2 

Luxembourg 442 LU LUF 0 

Netherlands 528 NL NLG 2 

Norway 578 NO NOK 2 

Poland 616 PL PLN 2 

Portugal 620 PT PTE 0 

Rumania 642 RO ROL 2 

Russian Federation 643 RU RUR 2 

Slovakia 703 SK SKK 2 

Slovenia 705 SI SIT 2 

Spain 724 ES ESP 0 

Sweden 752 SE SEK 2 

Switzerland 756 CH CHF 2 

Turkey 792 TR TRL 2 

USA 840 US USD 2 

Euro 978 EU EUR 2 

21 

The new Code 276 is not yet used at present, since Code 280 is more usual in the banking business.

Chapter: 

VIII 

Page: 

156 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 


European account addressing 

VIII.12 


The DEG "Account addressing“ (see chapter II.5.3.3) should be filled in the following 

way for target countries: 22 

Belgium: 

Country code: 056 

Bank code: 

Account/portfolio no.: 

The field is not occupied (the bank code is a fixed part 

of the account number). 

The entire character sequence (exactly 12 characters) 

must be entered. 

3 n 23 7 n 2 n 

Bank-Code No. Compte or Rekeningnr. Check digit 

Denmark: 


Bank code: 

The field is filled with the S.W.I.F.T. code. 

8 or 11 an 

S.W.I.F.T. code 


The bank code is a fixed part of the account number. 



4 n max. 9 n 1 

Bank code Account Check digit 

Germany: 


Bank code: 

The field is filled with the account number. 

8 n 

Bank code 

22 

23 

See „Register of European Account Numbers“, ECBS Technical Report TR 201, Version 2.1, 

September 1999 (http://www.ecbs.org/download/tr201v2.1.pdf) 

The format information indicates length and data type of the respective field/sub-field (n = numerical; an 

= alphanumerical)



Section: European account addressing 

Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

157 


The bank code is not a fixed part of the account 

number. The account number must be entered. 

10 n 

Account number 

Finland: 


Bank code: 






6 n max. 7 n 1 

Bank code Account number Check digit 

France: 


Bank code: 


The field is not occupied. 

The RIB code is a combination of bank code and 

account number. The entire character sequence must 

be entered (exactly 23 places). 

5 n 5 n 11 an 2 n 

Code banque Code guichet No. de Compte Cié RIB 

Greece: 


Bank code: 


8 or 11 an 



The bank code is a fixed part of the account number. 

The entire character sequence must be entered 

(exactly 19 characters). 

3 n 3n 12 n 1 n 

Bank code Branch code Account number Check digit 

Great Britain: 


Bank code: 

The field is filled with the sort code.

Chapter: 

VIII 

Page: 

158 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



6 n 

Sort code 


The account number must be entered. 

8 n 


Ireland: 


Bank code: 

The field is filled with the sort code. 

6 n 

Sort code 



8 n 


Iceland: 


Bank code: 

The field is filled with the bank code. Alternatively the 

S.W.I.F.T. code can also be specified. 

4 n 

Bankanúmer 



18 n 

Reikningsnúmer 

Italy: 


Bank code: 


8 or 11 an 



1 a 5 n 5 n max. 12 x 

The Coordinata Bancaria is a combination of bank code 

and account number. The entire character sequence 

must be entered (exactly 23 places). 

CIN ABI code CAB code Numero di Conto




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

159 

Liechtenstein: 


Bank code: 

The field is filled with the bank code (SIC code). 

Alternatively the S.W.I.F.T. can also be entered. 

Max. 5 an 

SIC code 



Max. 16 an 

Kontonummer 

Luxembourg: 


Bank code: 


8 or 11 an 



The bank code is a fixed part of the account number 

(max. 14 characters). 

2 n 6 n 2 n 4 an 

Bank- Numeró de Compte Check bankinterne 

Code Digit Kennziffer 

Netherlands: 


Bank code: 


8 or. 11 an 



The bank code is a fixed part of the account number 

(altogether max. 9 characters, of these bank code 2 to 

3 characters and account number max. 7 characters). 

10 n 

Rekeningnummer 

Norway: 


Bank code: 


of the account number).

Chapter: 

VIII 

Page: 

160 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 



Account/portfolio no.: The account number should be entered (max. 11 

characters). 

4 n 7 n 1 n 

Registernummer Konto 

Check digit 

Austria: 


Bank code: 

The field is filled with the bank code. Alternatively the 

S.W.I.F.T. code can be entered. 

5 n 

Bankleitzahl 



11 n 

Kontonummer 

Portugal: 


Bank code: 




The entire character sequence must be entered (a total 

of max. 21 places). 

4 n 4 n 11 n 2 n 

National Bank Bank Branch Account number Check 

Code Code Digit 

Sweden: 


Bank code: 




The account number must be specified (a total of max. 

15 characters, usually 11 characters). 

4 n 6 n 1 n 

Bank code Account number Check digit 

Switzerland: 

Country code: 756




Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

161 

Bank code: 

The bank code is not a fixed part of the account 

number. Alternatively the S.W.I.F.T. code can also be 

specified. 

max. 5 n 

Clearingnummer 



max. 16 an 


Spain: 


Bank code: 


4 n 4 n 2 n 10 n 



The entire character sequence must be entered 

(exactly 20 characters). 

Código de Código de Dígitos Número de cuenta 

entidad oficina de control

Chapter: 

VIII 

Page: 

162 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 


Bibliography 

VIII.13 

Bibliography 

The specification makes use of a variety of different documents which have been 

classified by topic below. 

♦ General 

• ISO 639:1988: Code for the representation of names of languages 

• ISO 3166-1:1996: Code for the representation of names of countries and their 

subdivisions - Part 1: Country code 

• ISO 4217:1995: Codes for the representation of currencies and funds 

• ISO 8859-1:1987: Information processing - 8 bit single-byte coded graphic character 

sets - Part 1: Latin alphabet No. 1 

• ISO 13616: Banking and related services - International Bank Account Number 

(IBAN) 

• IBAN: International Bank Account Number (EBS 204), published by European 

Committee for Banking Standards, November 1996 (www.ecbs.org/download.html) 

• IBAN: Standard Implementation Guidelines (SIG 203), published by European 

Committee for Banking Standards, November 1996 (www.ecbs.org/download.html) 

♦ Security 

• Kryptographische Verfahren des deutschen Kreditgewerbes für die Elektronische 

Unterschrift und für die Verschlüsselung im Rahmen der Kunde-Financial institution- 

Kommunikation (Cryptographic Procedures of the German Banking Industry for Electronic 

Signature and for Encryption in the Framework of Customer-Financial institution- 

Communication) in: ZKA-Abkommen über die Datenfernübertragung zwischen 

Kunden und Kreditinstituten (DFÜ-Abkommen) v. 15.03.1995, Anlage 2 (ZKA- 

Agreement on Data Transmission between Customers and Financial institutions dated 

15.03.1995, Appendix 2) 

• ISO CD 9735-5: Electronic data interchange for administration, commerce and 

transport - (EDIFACT) - Application level syntax rules; Part 5: Security rules for batch 

EDI (Authenticity; Integrity and Non-repudiation of origin), SJWG, Release 1 1995- 

12-14 (not yet published) 

• ISO WD 9735-7: Electronic data interchange for administration, commerce and 

transport - (EDIFACT) - Application level syntax rules; Part 7: Security rules for batch 

EDI (Confidentiality), SJWG, Release 1.1 1995-10-18 (not yet published) 

• ISO CD 9735-9: Electronic data interchange for administration, commerce and 

transport - (EDIFACT) - Application level syntax rules; Part 9: Security key and 

certificate management (Message type - KEYMAN), SJWG, Release 1 1996-01-12 

(not yet published) 

• ISO 9796:1991: Information technology - Security techniques - Digital signature 

scheme giving message recovery



Section: Bibliography 

Version: 

2.2 

Edition: 

2000-05-10 

Chapter: 

VIII 

Page: 

163 

• ISO 10116: Information technology - Modes of operation for an n-bit block cipher 

algorithm 

• ISO 10118-2: Information technology - Security techniques - Hash functions Part 2: 

Hash functions using an n-bit block cipher algorithm 

• ISO 10118-3: Information technology - Security techniques - Hash functions Part 3: 

Dedicated hash functions, Draft, 1997 

• ISO 10126: Banking - Procedures for message encipherment (wholesale) 

• ANSI X3.92-1981 (R1987): Data Encryption Algorithm 

• ANSI X3.106-1983 (R1996): Data Encryption Algorithm, Modes of operation for the 

• ANSI X9.19-1996: Financial Institution Retail Message Authentication 

• ANSI X9.23-1995 (R1995): Financial Institution Encryption of Wholesale Financial 

Messages 

• EDIFACT Message Implementation Guidelines: Ciphered Text Message. CIPHER, 

SJWG; Working Draft Version, Paris September 16th 1994 

• EDIFACT Security Implementation Guidelines, Trade/WP.4/R.1026/Add.2, 22 

February 

• MIG Handbook UN/EDIFACT Message KEYMAN (proposed draft), June 30, 1995 

• R. Rivest, A. Shamir, L. Adleman: A method for obtaining digital signatures and 

public key cryptosystems, Communications of the ACM, vol. 21 no. 2, 1978. 

• H. Dobbertin, A. Bosselaers, B. Preneel: "RIPEMD-160, a strengthened version of 

RIPEMD", Fast Software Encryption - Cambridge Workshop 1996, LNCS, Band 

1039, D. Gollmann, Ed., Springer-Verlag, 1996, S. 71-82 (ftp://ftp.esat.kuleuven.ac.be/pub/COSIC/bosselae/ripemd/) 

♦ Descriptions of communications media 

• Datex-J Rechnerverbund - EHKP Protokollhandbuch, Version 4.3 vom 18.10.1995, 

Deutsche Telekom AG, Zentrum MIV Darmstadt (Datex-J Computer Link - EHKP 

Protocol Manual, Version 4.3 dated 18.10.1995 ) 

• Datex-J - X.29 Protokollhandbuch, 3. Ausgabe vom September 1993, Deutsche 

Telekom AG, Zentrum MIV Darmstadt (Datex-J - X.29 Protocol Manual, 3rd edition dated 

September 1993) 

• Functional Specifications for Videotext Terminals, Deutsche Telekom AG, Zentrum 

MIV Darmstadt 

• Funktionserweiterungen im Datex-J-Dienst - Technische Beschreibung der Datex-J 

Release 4.2/4.3, dated 26.6.1995, Deutsche Telekom AG, FTZ Darmstadt, Referat 

T24 (Functional extensions in the Datex-J-Service - Technical Specification of Datex-J 

Release 4.2/4.3) 

• Btx File Interchange Format (BtxFIF) for Transparent Mode, Deutsche Telekom AG, 

FTZ Darmstadt, Referat T25, Version 1.1, August 1992 

• Request for Comment (RFC) 791: Internet Protocol (IP), September 1981

Chapter: 

VIII 

Page: 

164 

Version: 

2.2 

Edition: 

2000-05-10 


Chapter: 

Section: 


Bibliography 

• Request for Comment (RFC) 793: Transmission Control Protocol (TCP), September 

1981 

• Request for Comment (RFC) 1700: Assigned Numbers, Oktober 1994 

Source for RFC documents: e.g. ftp://ftp.eunet.de/pub 

♦ Business transactions 

• Richtlinien für einheitliche Zahlungsverkehrsvordrucke und Merkblätter für neutrale 

Zahlungsverkehrsvordrucke (Guidelines for uniform payment forms and leaflets for 

neutral payment forms) 

• S.W.I.F.T. User Handbook, October 1998 Standards Release (see also 

http://www.iso15022-org) 

• ISO 6166: International Securities Numbering System 

• ISO 9362: Financial institution Identifier Code (BIC) 

• ISO 10383: Market Identifier Code (MIC) 

• Register of European Account Numbers, Technical Report TR 201, Version 2.1, 

published by European Committee for Banking Standards, September 1999 

(http://www.ecbs.org/download/tr201v2.1.pdf) 

• International Payment Instruction (IPI), Electronic Banking Standard EBS 206, 

Version 1.4, published by European Committee for Banking Standards, November 

1999 (www.ecbs.org/download/ebs206v1.4.pdf) 

♦ Chip card specification 

[ISO PIN1] ISO 9564-1, Banking – Personal Identification Number Management and 

Security, Part 1: PIN protection principles and techniques, DIS 1999 

[LIT 1'] 

[LIT 1A] 

[LT] 

Schnittstellenspezifikation für die ZKA-Chipkarte, Datenstrukturen und 

Kommandos (Interface specification for the ZKA chip card, data structures 

and commands), Version 4.1, 01.07.1999 

Schnittstellenspezifikation für die ec-Karte mit Chip, Dateien des MF 

(Interface specification for the ec card with chip, files of the MF, Version 

4.2, 01.12.1999 

Schnittstellenspezifikation für die ec-Karte mit Chip, Ladeterminal 

(Interface specification for the ec card with chip, charging terminal), 

Version 3.0, 02.04.1998

Part C: Appendices

Create successful ePaper yourself

Delete template?

Save as template?