ISO 8583 Tutorial – Introduction for Beginners

本文介绍ISO8583标准的基础知识,包括消息结构、类型标识符、位图及数据元素等内容,帮助读者理解银行及金融交易中ISO8583的使用。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

http://jimmod.com/blog/2011/07/25/jimmys-blog-iso-8583-introduction-beginners-tutorial/


ISO 8583 Tutorial article

Introduction

Lately I’ve handle several financial project that allow me to understand bank and financial transaction better.
All (or most?) financial transaction is using ISO 8583 standard, which at first I thought is a complicated standard. But after learn and see how it implemented it’s not as complex as I thought.
In this post I will try to explain (based on my experience :) before I go deeper on the programming side.

Although it’s a ‘standard’ I see that’s many variant for the detail implementation of ISO 8583.

Financial transaction is communication between 2 system through socket connection.
After connection established, each system can send message in ISO 8583 format which commonly will be request and the other system will response.
From my experience the communication will be start with sign on and then the financial transactions.
Periodically an echo message is send to make sure the other system is still alive.

If I break down the flow:

  1. System A open connection to System B (through specific IP and Port).
  2. Connection established.
  3. System A send Sign-On request message.
  4. System B send Sign-on response message.
  5. System A will start send Echo request message periodically (e.g every 1 minute).
  6. System B will send Echo response message when receive Echo request message.
  7. When financial transaction happen, System A will send Transaction request message.
  8. Then System B will send Transaction response message.
  9. If something wrong happen (usually timeout so System A didn’t get the response), System A will send Reversal request message to cancel the previous transaction.
  10. System B will send Reversal response message.

I hope my explaination give clear basic understanding about the flow.
Next the question will be what’s this ISO 8583 message looks like.
We can separate the message into 3 parts:

  • Message Type Identifier
  • Bitmaps
  • Data Elements

ISO8583 - structure

ISO8583 - structure

Message Type Identifier

Message Type Identifier or MTI is 4 digits numeric that describe the message type. It will explain the message function.
Commonly used:
- 02xx : Financial Message (e.g 0200 for request, 0210 for response)
- 04xx : Reversal Message (e.g 0400 for request, 0410 for response)
- 08xx : Network Management Message (e.g 0800 for request, 0810 for response)
* I found more detail & complete list at wikipedia

Bitmaps

Bitmaps is field that contain information about which data element is presence or absence. Based on the variant it could be 16 hexadecimal characters.
An example will make it clear.

The bitmap is:

B220000000100000

If we break down to binary (I hope you understand how to convert hexadecimal to binary:) :

1011001000100000000000000000000000000000000100000000000000000000

Since I’m nice ;) I create graphical illustration.

Bitmap sample

Bitmap sample

You can see that in this bitmap it explain that data element in the message is 1, 3, 4, 7, 11.
There’s special meaning of first bit of bitmap, if it has value of 1 that mean there’s secondary bitmap.
And what the hell is this secondary bitmap?
Since 16 hexadecimal characters will can only contain info of 64 data element, some transactions contain data element number 64 – 128. That mean the 16 hexadecimal characters is not sufficient.
With set the first bit to ’1′ that will inform there’s additional bitmap, which is another 16 hexadecimal characters.
So in this case the full bitmap example should be:
B2200000001000000000000000800000
Convert to binary:
10110010001000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000100000000000000000000000
From the bitmap, data element presence in the message : 3, 4, 7, 11, 105.

Sample Bitmap complete

Sample Bitmap complete

Data Elements

Data Elements is the essense of the whole ISO message, contain information about the transaction (transaction type, amount, customer id, etc).
Each data element have their on format, attribute and length.
Each data element number also have standard purpose, for example DE #4 is transaction amount.
I will explain based on the example above, since this is only introduction I don’t want to confuse beginner reader. In wikipedia there’s full list.
For our examples, the data element list:

  • #3 – Processing code – n 6
  • #4 – Transaction amount – n 12
  • #7 – Transmission date & time – n 10
  • #11 – Systems trace audit number – n 6
  • #44 – Additional response data – an ..25
  • #105 – Reserved for ISO use – ans …999

To make it practical let’s just use example.
We want to send :

  • DE #3 : 201234
  • DE #4 : 10000
  • DE #7 : 1107221830
  • DE #11 : 123456
  • DE #44 : A5DFGR
  • DE #105 : ABCDEFGHIJ 1234567890

Using above value, the data in data elements :

ISO8583 - de

ISO8583 - de

Based on the type each value will be formatted.

  • a : alpha (including blanks)
  • n : numeric value
  • s : special characters
  • x (no dot) : length is x (fixed)
  • .x (one dot) :  max length is x (1 digit in front as length info)
  • ..xx (two dot) :  max length is xx (2 digit in front as length info)
  • …xxx (three dot) :  max length is xxx (3 digit in front as length info)

ISO Message

From above examples the whole ISO message will be :

0200B2200000001000000000000000800000201234000000010000110722183012345606A5DFGR021ABCDEFGHIJ 1234567890

ISO8583 - full

Conclusion

Ok. This article already long enough :)
Actually I always prefer short article, but on this case it’s cannot be to short.
Anyway, I hope this article is clear enough for you.


资源下载链接为: https://pan.quark.cn/s/1bfadf00ae14 华为移动服务(Huawei Mobile Services,简称 HMS)是一个全面开放的移动服务生态系统,为企业和开发者提供了丰富的工具和 API,助力他们构建、运营和推广应用。其中,HMS Scankit 是华为推出的一款扫描服务 SDK,支持快速集成到安卓应用中,能够提供高效且稳定的二维码和条形码扫描功能,适用于商品扫码、支付验证、信息获取等多种场景。 集成 HMS Scankit SDK 主要包括以下步骤:首先,在项目的 build.gradle 文件中添加 HMS Core 库和 Scankit 依赖;其次,在 AndroidManifest.xml 文件中添加相机访问和互联网访问权限;然后,在应用程序的 onCreate 方法中调用 HmsClient 进行初始化;接着,可以选择自定义扫描界面或使用 Scankit 提供的默认扫描界面;最后,实现 ScanCallback 接口以处理扫描成功和失败的回调。 HMS Scankit 内部集成了开源的 Zxing(Zebra Crossing)库,这是一个功能强大的条码和二维码处理库,提供了解码、生成、解析等多种功能,既可以单独使用,也可以与其他扫描框架结合使用。在 HMS Scankit 中,Zxing 经过优化,以更好地适应华为设备,从而提升扫描性能。 通常,ScanKitDemoGuide 包含了集成 HMS Scankit 的示例代码,涵盖扫描界面的布局、扫描操作的启动和停止以及扫描结果的处理等内容。开发者可以参考这些代码,快速掌握在自己的应用中实现扫码功能的方法。例如,启动扫描的方法如下: 处理扫描结果的回调如下: HMS Scankit 支持所有安卓手机,但在华为设备上能够提供最佳性能和体验,因为它针对华为硬件进行了
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值