Professional Documents
Culture Documents
Blog Home
Top Read Articles
Read smart card chip data with APDU
commands ISO 7816
Read smart card chip data with
APDU commands ISO 7816
31422 views
Posted on 28th Nov 2019 31421 views
BIN List & Range for MasterCard,
This explanation builds on top of existing information at wiki about
Visa, Amex, Diners, Discover, JCB,
https://en.wikipedia.org/wiki/Smart_card_application_protocol_data_unit CUP
28091 views
A selected list of used commands is available at the end of this page.
Deploy, run and generate with
Any smart card reader will come with a set of drivers an libraries to interface with it. We will assume that you do not neaPay Card Data Generator
need to build communication with the reader, just to use it. 12338 views
The reader comes with an interface to send apdu commands. Run the neaPay ISO8583
simulator
Depending on your Card Brand, different commands need to be used.
11748 views
APDU list
7618 views
+------------+------------------------+------------------------+----------------------+--------------------------------+
| B0 | ISO 7816-48.2.1 | READ BINARY
Deploy the |
Payments Switch
| 00 B0 xx xx xx | GEMPLUS MPCOS-EMV | READ BINARY Router in |a test environment
| A0 B0 xx xx xx | 3GPP TS 11.11 | READ BINARY 2845 views |
| A0 B0 xx xx xx | SAGEM SCT U34 6.4 | READ BINARY |
ISO8583 ATM POS Crypto API
+------------+------------------------+------------------------+----------------------+--------------------------------+
| B2 | ISO 7816-48.3.1 | READ RECORD integration| with exchanges like
| 00 B2 xx 00 | VSDC | READ RECORD Coinbase |or Binance
| A0 B2 xx xx xx | 3GPP TS 11.11 | READ RECORD 2746 views |
| A0 B2 xx xx xx | SAGEM SCT U34 6.6 | READ RECORD |
Add extra custom fields to the
+------------+------------------------+------------------------+----------------------+--------------------------------+
| B4 | | java Component Data ISO8583 simulator
|
+------------+------------------------+------------------------+----------------------+--------------------------------+
2625 views
| B8 | | java Create Applet |
+------------+------------------------+------------------------+----------------------+--------------------------------+
BASE24 classic cards
| BA | | java CAP end |
configuration tutorial with
+------------+------------------------+------------------------+----------------------+--------------------------------+
Examples
| BC | | java Component end |
2520 views
+------------+------------------------+------------------------+----------------------+--------------------------------+
| BE 04 Data | GEMPLUS GemClub-MEMO | READ |
+------------+------------------------+------------------------+----------------------+--------------------------------+ ACI DESKTOP
BASE24-EPS
| C0 | ISO 7816-48.6.1 | GET RESPONSE tutorial - |Getting started
| 00 C0 1C Key Info | GlobalPlatform | GET RESPONSE 2287 views |
| 00 C0 00 00 00 | VSDC | GET RESPONSE |
| 80 C0 00 00 xx | GEMPLUS MPCOS-EMV Getting started
| Get Info on Get Response | with BASE24.
| 80 C0 02 A0 08 Chip SN | GEMPLUS MPCOS-EMV | Get Info Compiling| your first TAL program
| 80 C0 02 A1 08 Card SN | GEMPLUS MPCOS-EMV | Get Info 2094 views |
| 80 C0 02 A2 08 Issuer SN | GEMPLUS MPCOS-EMV | Get Info |
| 80 C0 02 A3 04 Iss.Ref.N | GEMPLUS MPCOS-EMV | Get Info BASE24 classic
| prefix
| 80 C0 02 A4 0D Chip Inf | GEMPLUS MPCOS-EMV | Get Info configuration
| tutorial CPF with
| 80 C0 02 A5 xx Keys | GEMPLUS MPCOS-EMV | Get Info
examples |
| 80 C0 02 A6 02 Last DF/EF | GEMPLUS MPCOS-EMV | Get Info |
1993 views
| A0 C0 00 00 xx | 3GPP TS 11.11 | GET RESPONSE |
| A0 C0 00 00 xx | SAGEM SCT U34 6.3 | GET RESPONSE |
BASE24 classic tracing of
+------------+------------------------+------------------------+----------------------+--------------------------------+
transactions. Audits,
| C2 | ISO 7816-48.6.2 | ENVELOPE |
configuration,
+------------+------------------------+------------------------+----------------------+--------------------------------+
enabling and
| C4 | | java Delete Applets opening |
1888 views
+------------+------------------------+------------------------+----------------------+--------------------------------+
| CA | ISO 7816-48.4.1 | GET DATA |
| 00 CA 00 xx xx MAC, if present | GlobalPlatform | GET DATA Working with| Base24-eps vs
| 80 CA xx xx xx | VSDC | GET DATA BASE24 Classic
|
+------------+------------------------+------------------------+----------------------+--------------------------------+
1826 views
| D0 | ISO 7816-48.2.2 | WRITE BINARY |
| 80 D0 xx xx xx Data to be written in EEPROM | VSDC | LOAD STRUCTURE BASE24 classic
| Institution
configuration Tutorial with
+------------+------------------------+------------------------+----------------------+--------------------------------+
| D2 | ISO 7816-48.3.2 | WRITE RECORD
example |
+------------+------------------------+------------------------+----------------------+--------------------------------+
1803 views
| D6 | ISO 7816-48.2.3 | UPDATE BINARY |
| A0 D6 xx xx xx Data to be written in EEPROM | 3GPP TS 11.11 | UPDATE BINARY |
BASE24 classic interchange
| A0 D6 xx xx xx Data to be written in EEPROM | SAGEM SCT U34 6.5 | UPDATE BINARY |
configuration with examples
+------------+------------------------+------------------------+----------------------+--------------------------------+
1771 views
| 80 D8 xx xx xx KEY Date (and MAC) 00 | GlobalPlatform | PUT KEY |
| D8 | EMV | Set Card Status(personalization|
ACI BASE24 classic automatic
+------------+------------------------+------------------------+----------------------+--------------------------------+
| DA | ISO 7816-48.4.2 | PUT DATA extract configuration
|
| 00 DA xx xx xx Data | VSDC | PUT DATA 1759 views |
+------------+------------------------+------------------------+----------------------+--------------------------------+
| DC | ISO 7816-4 | UPDATE RECORD BASE24 classic
| balance file
| 00 DC xx xx xx Data (and MAC) | VSDC | UPDATE RECORD configuration
| PBF with example
| A0 DC xx xx xx Data to be written in EEPROM | 3GPP TS 11.11 | UPDATE RECORD 1740 views |
| A0 DC xx xx xx Data to be written in EEPROM | SAGEM SCT U34 6.7 | UPDATE RECORD |
BASE24 classic routing in IDF
+------------+------------------------+------------------------+----------------------+--------------------------------+
| DE 04 Data | GEMPLUS GemClub-MEMO | UPDATE 1535 views |
| A0 DE 00 00 03 Data | 3GPP TS 11.11 | LOAD AoC(SICAP) |
Getting started with Base24
+------------+------------------------+------------------------+----------------------+--------------------------------+
| E0 | ISO 7816-96.1 | CREATE FILE development.| TAL tutorial
| 80 E0 02 00 0C Manual | GEMPLUS MPCOS-EMV | CREATE FILE 1501 views |
| 80 E0 xx xx xx FCI length | 3GPP TS 11.11 | CREATE FILE |
| 80 E0 xx xx xx FCI length | SAGEM SCT U34 | CREATE FILE Base24-eps | how to create
+------------+------------------------+------------------------+----------------------+--------------------------------+
journals with esbldjnl
| E2 | ISO 7816-48.3.4 | APPEND RECORD |
1485 views
| 80 E2 00 00 xx Record (and MAC) | GlobalPlatform | APPEND RECORD |
| 00 E2 00 00 xx Record | VSDC | APPEND RECORD |
BASE24 classic External Message
| 00 E2 00 00 xx Record | GEMPLUS MPCOS-EMV | APPEND RECORD |
File configuration EMF with
| 00 E2 00 00 xx Record | 3GPP TS 11.11 | APPEND RECORD |
examples
+------------+------------------------+------------------------+----------------------+--------------------------------+
| E4 | ISO 7816-96.2 | DELETE FILE 1385 views |
| 80 E4 00 00 xx TLV coded name | GlobalPlatform | DELETE FILE |
| A0 E4 00 00 02 xx xx | 3GPP TS 11.11 | DELETE FILE First steps| with BASE24 Classic
1342 views
+------------+------------------------+------------------------+----------------------+--------------------------------+
| E6 | ISO 7816-96.5 | TERMINATE DF |
| 80 E6 xx 00 xx Manual | GlobalPlatform | INSTALL Getting started
| with using
| A0 E6 xx xx 00 | 3GPP TS 11.11 | LOCK RECORD Prognosis|for BASE24 and
BASE24-eps
+------------+------------------------+------------------------+----------------------+--------------------------------+
| E8 | ISO 7816-96.6 | TERMINATE EF 1313 views |
| 80 E8 00 00 xx Record | GlobalPlatform | LOAD |
| A0 E8 00 xx 10 Data | 3GPP TS 11.11 | READ DIRECTORY BASE24 classic
| host configuration
+------------+------------------------+------------------------+----------------------+--------------------------------+
tutorial HCF with examples
| 80 EA 00 00 xx Data | 3GPP TS 11.11 | CREATE BINARY |
1230 views
| 80 EA 00 00 xx Data | SAGEM SCT U34 | CREATE BINARY |
+------------+------------------------+------------------------+----------------------+--------------------------------+
What to expect when installing
| 80 EE 00 xx 00 | VSDC | WRITE LOCK |
Base24-eps
+------------+------------------------+------------------------+----------------------+--------------------------------+
1212 views
| 80 F0 xx xx xx AID of Application (and MAC) | GlobalPlatform | SET STATUS |
+------------+------------------------+------------------------+----------------------+--------------------------------+
Managing BASE24-eps
| A0 F2 00 00 xx | 3GPP TS 11.11 | GET STATUS |
implementation projects
| A0 F2 00 00 xx | SAGEM SCT U34 6.2 | GET STATUS |
| 80 F2 xx xx | GlobalPlatform | GET STATUS 1124 views |
+------------+------------------------+------------------------+----------------------+--------------------------------+
| 80 F8 xx xx xx | SAGEM SCT U34 8.1.1 | DIR ISO8583 Message
| Converter to
XML SQL CSV interface
+------------+------------------------+------------------------+----------------------+--------------------------------+
| A0 FA 00 00 00 | 3GPP TS 11.11 | SLEEP specification
| mapping
| A0 FA 00 00 00 | SAGEM SCT U34 6.18 | SLEEP 687 views |
+------------+------------------------+------------------------+----------------------+--------------------------------+
| 80 FB xx xx xx | SAGEM SCT U34 8.1.1 | DIR PCI compliant
| with neapay switch
+------------+------------------------+------------------------+----------------------+--------------------------------+
686 views
| 80 FC xx xx 10 | SAGEM SCT U34 8.1.3 | READ INFO |
+------------+------------------------+------------------------+----------------------+--------------------------------+
| FE | ISO 7816-96.7 | TERMINATE CARD USAGE |
| 80 FE xx xx 00 | SAGEM SCT U34 | BLOW FUSE |
+------------+------------------------+------------------------+----------------------+--------------------------------+
70 23 -- Record Template (EMV Proprietary) 61 21 -- Application Template 4f 07 -- Application Identifier (AID) - card
a1 23 45 67 89 10 10 (BINARY) 50 04 -- Application Label 56 49 53 41 (=VISA) 9f 12 0c -- Application Preferred
Name 56 49 53 41 20 43 6c 61 73 73 69 63 (=VISA Classic) 87 01 -- Application Priority Indicator 02 (BINARY)
70 25 -- Record Template (EMV Proprietary) 61 23 -- Application Template 4f 07 -- Application Identifier (AID) - card
d5 78 00 00 02 10 10 (BINARY) 50 09 -- Application Label 62 61 6e 6b 61 78 65 70 74 (=bankaxept) 9f 12 09 --
Application Preferred Name 62 61 6e 6b 61 78 65 70 74 (=bankaxept) 87 01 -- Application Priority Indicator 01
(BINARY)
6f 37 -- File Control Information (FCI) Template 84 07 -- Dedicated File (DF) Name a1 23 45 67 89 10 10 (BINARY) a5
2c -- File Control Information (FCI) Proprietary Template 50 04 -- Application Label 56 49 53 41 (=VISA) 87 01 --
Application Priority Indicator 02 (BINARY) 9f 38 06 -- Processing Options Data Object List (PDOL) 9f 1a 02 --
Terminal Country Code 5f 2a 02 -- Transaction Currency Code 5f 2d 04 -- Language Preference 6e 6f 65 6e (=noen)
9f 11 01 -- Issuer Code Table Index 01 (NUMERIC) 9f 12 0c -- Application Preferred Name 56 49 53 41 20 43 6c 61
73 73 69 63 (=VISA Classic)
70 81 c0 -- Record Template (EMV Proprietary) 8f 01 -- Certification Authority Public Key Index - card 07 (BINARY)
90 81 90 -- Issuer Public Key Certificate 04 71 93 ac fb 32 3a bb 95 ac e6 c5 b4 69 27 6d b5 93 16 73 cb a2 e0 ee 23
37 9d 02 79 50 b6 c1 c8 4d 59 e9 aa 7a 54 1b 51 06 0b 0b df 51 4f 44 40 10 2b ee e8 4c 38 3a ce 13 b0 72 84 4e 97
a6 5e 0e 69 b1 c8 c5 dc f3 08 b4 26 b8 b3 3d 72 07 ff 29 a7 7d d5 64 46 ae 8d ba b8 d1 b9 ea 6a 32 ab 11 64 e7 35
2c 14 6d 0a 61 e6 de b1 ec 2f 91 25 27 b9 ce df 72 a9 b0 86 3a 9c 45 b4 9a 81 8a f4 69 8c 71 c9 72 d2 eb 25 41 84
5e 4d f8 a3 49 (BINARY) 9f 32 01 -- Issuer Public Key Exponent 03 (BINARY) 92 24 -- Issuer Public Key Remainder 5b
c8 f7 38 4c 06 dc dc 35 97 51 d1 d4 31 52 0d f5 ff 2d 43 47 4a 88 60 3c 9e fc a0 66 6a 1a 42 bd f0 a4 f5 (BINARY)
[Step 15] Send GET DATA command to find the PIN Try
Counter
80 CA 9F 17 00 response hex : 9f 17 01 03 response SW1SW2 : 90 00 response ascii : .... response parsed :
6f 2e -- File Control Information (FCI) Template 84 07 -- Dedicated File (DF) Name d5 78 00 00 02 10 10 (BINARY) a5
23 -- File Control Information (FCI) Proprietary Template 50 09 -- Application Label 62 61 6e 6b 61 78 65 70 74
(=bankaxept) 87 01 -- Application Priority Indicator 01 (BINARY) 5f 2d 02 -- Language Preference 6e 6f (=no) 9f 11
01 -- Issuer Code Table Index 01 (NUMERIC) 9f 12 09 -- Application Preferred Name 62 61 6e 6b 61 78 65 70 74
(=bankaxept)
[Step 23] Send GET DATA command to find the PIN Try
Counter
80 CA 9F 17 00 response hex : 9f 17 01 03 response SW1SW2 : 90 00 response ascii : .... response parsed :
======================================
[EMVCard]
Answer To Reset (ATR) 3b 67 00 00 a6 40 40 00 09 90 00 Description From Public Database - [Visa card issued by
Norway bank DNBNor, VISA Classic - Landkreditt Bank (Norway), VISA Classic - Nordea Bank (Norway)] ISO
Compliant Answer To Reset (ATR) Convention - DIRECT Protocol - T=0 Historical bytes - a6 40 40 00 09 90 00
Directory Definition File Name: 315041592e5359532e4444463031 (=1PAY.SYS.DDF01) Issuer Code Table Index: 1
(ISO-8859-1) Short File Identifier: 2 (Governed by the EMV specification) Language Preference (in order of
preference): Language: no (Norwegian) Language: en (English)
Applications (2 found):
Application
AID: a1 23 45 67 89 10 10
Label: VISA
Preferred Name: VISA Classic
Application Effective Date: Thu Feb 05 00:00:00 CET 2009
Application Expiration Date: Sat Mar 31 00:00:00 CEST 2012
Application Version Number: 140
Application Currency Code (ISO 4217): 578 (NOK Norwegian Krone)
Application Currency Exponent: 2 (Position of the decimal point from the right)
Issuer Country Code (ISO 3166-1): 578 (Norway)
Application Transaction Counter (ATC): 121
Last Online ATC Register: 103
PIN Try Counter: 3 (Number of PIN tries remaining)
Cardholder Name: SMITH/JOHN
Primary Account Number (PAN) - 5411118888888882
Major Industry Identifier = 5 (Banking and financial)
Issuer Identifier Number: 541111
Account Number: 888888888
Check Digit: 2 (Valid)
PAN Sequence Number: 1
Application Priority Indicator
May be selected without cardholder confirmation
Selection Priority: 2
Application Interchange Profile
Static Data Authentication (SDA) supported
Dynamic Data Authentication (DDA) not supported
Cardholder verification is supported
Terminal risk management is to be performed
Issuer authentication is supported
CDA not supported
Application File Locator
Application Elementary File
Short File Identifier:
1 (Governed by the EMV specification)
Start Record: 1
End Record: 1
Number of Records Involved In Offline Data Authentication: 0
Record: 1
Length: 79
Involved In Offline Data Authentication: false
Application Elementary File
Short File Identifier:
1 (Governed by the EMV specification)
Start Record: 2
End Record: 5
Number of Records Involved In Offline Data Authentication: 1
Record: 2
Length: 82
Involved In Offline Data Authentication: true
Record: 3
Length: 73
Involved In Offline Data Authentication: false
Record: 4
Length: 195
Involved In Offline Data Authentication: false
Record: 5
Length: 150
Involved In Offline Data Authentication: false
Application Usage Control
Valid for domestic cash transactions
Valid for international cash transactions
Valid for domestic goods
Valid for international goods
Valid for domestic services
Valid for international services
Valid at ATMs
Valid at terminals other than ATMs
Domestic cashback not allowed
International cashback not allowed
Processing Options Data Object List
Terminal Country Code (2 bytes)
Transaction Currency Code (2 bytes)
Issuer Public Key Certificate
Issuer Identifier: 492564
CA Public Key Index: 7
Certificate Format: 2
Certificate Expiration Date (MMYY): 1214
Certificate Serial Number: 00e16d (57709)
Hash Algorithm Indicator: 1 (=SHA-1)
Issuer Public Key Algorithm Indicator: 1 (=RSA)
Hash: b6819d8d5af4034214973edbad1bd2866a550dbb
Issuer Public Key
Length: 1152bit
Exponent:
03
Modulus:
ba 53 3e b8 ec c9 f9 b8 b2 a3 5e ed 3b e0 3f 7d
3a cf e2 46 a3 4c 8e 75 f5 c7 4a 64 e6 5c 97 cb
4f 2f ab 97 09 cf 7e 12 89 0e af f1 8a 4f cf b4
fa 98 18 db c3 be 5f dc 65 91 54 46 cb 86 24 ac
2d 1e 07 72 f2 52 49 02 f9 8b a5 5b 4b 4b 11 00
1e 4e cf b7 0f 12 19 a3 97 12 98 e7 ed c5 b9 2b
8d 44 c9 80 e2 f6 8f 90 8f 9d ad 78 5b c8 f7 38
4c 06 dc dc 35 97 51 d1 d4 31 52 0d f5 ff 2d 43
47 4a 88 60 3c 9e fc a0 66 6a 1a 42 bd f0 a4 f5
Card Risk Management Data Object List 1
Amount, Authorised (Numeric) (6 bytes)
Amount, Other (Numeric) (6 bytes)
Terminal Country Code (2 bytes)
Terminal Verification Results (TVR) (5 bytes)
Transaction Currency Code (2 bytes)
Transaction Date (3 bytes)
Transaction Type (1 byte)
Unpredictable Number (4 bytes)
Card Risk Management Data Object List 2
Authorisation Response Code (2 bytes)
Amount, Authorised (Numeric) (6 bytes)
Amount, Other (Numeric) (6 bytes)
Terminal Country Code (2 bytes)
Terminal Verification Results (TVR) (5 bytes)
Transaction Currency Code (2 bytes)
Transaction Date (3 bytes)
Transaction Type (1 byte)
Unpredictable Number (4 bytes)
Signed Static Application Data
Hash Algorithm Indicator: 1 (=SHA-1)
Data Authentication Code: 0123
Hash: 74159900848ab829b9f0318950cdad9351e0bfdf
Cardholder Verification Method (CVM) List:
Cardholder Verification Rule
Rule: Enciphered PIN verified online
Condition Code: If unattended cash
Apply succeeding CV Rule if this CVM is unsuccessful
Cardholder Verification Rule
Rule: Plaintext PIN verification performed by ICC
Condition Code: If terminal supports the CVM
Apply succeeding CV Rule if this CVM is unsuccessful
Cardholder Verification Rule
Rule: If transaction is in the application currency and is under 0.00 value
Condition Code: If terminal supports the CVM
Apply succeeding CV Rule if this CVM is unsuccessful
Cardholder Verification Rule
Rule: Enciphered PIN verified online
Condition Code: If terminal supports the CVM
Apply succeeding CV Rule if this CVM is unsuccessful
Cardholder Verification Rule
Rule: If transaction is in the application currency and is over 0.00 value
Condition Code: Always
Fail cardholder verification if this CVM is unsuccessful
Static Data Authentication Tag List
Application Interchange Profile
Track 1 Discretionary Data:
323439353030303030303030303030313031303030303030 (ASCII: 249500000000000101000000)
Track 2 Equivalent Data:
Primary Account Number (PAN) - 5411118888888882
Major Industry Identifier = 5 (Banking and financial)
Issuer Identifier Number: 541111
Account Number: 888888888
Check Digit: 2 (Valid)
Expiration Date: Wed Feb 29 00:00:00 CET 2012
Service Code: 201
Discretionary Data: 1234567890000
Service Code: 201
Language Preference (in order of preference):
Language: no (Norwegian)
Language: en (English)
Issuer Code Table Index: 1 (ISO-8859-1)
Issuer Action Code - Default:
11110000
00100000
00100100
00101000
00000000
Issuer Action Code - Denial:
00000000
01010000
10000000
00000000
00000000
Issuer Action Code - Online:
11110000
00101000
00111100
11111000
00000000
Application
AID: d5 78 00 00 02 10 10
Label: bankaxept
Preferred Name: bankaxept
Application Expiration Date: Thu Mar 29 00:00:00 CEST 2012
Application Transaction Counter (ATC): 115
Last Online ATC Register: 114
PIN Try Counter: 3 (Number of PIN tries remaining)
Primary Account Number (PAN) - 957852641234567890
Major Industry Identifier = 9 (For assignment by national standards bodies)
Country Code (ISO 3166-1): 578 (=Norway)
Issuer Identifier Number: 957852
Account Number: 64123456789
Check Digit: 0 (Valid)
PAN Sequence Number: 2
Application Priority Indicator
May be selected without cardholder confirmation
Selection Priority: 1
Application Interchange Profile
Static Data Authentication (SDA) not supported
Dynamic Data Authentication (DDA) not supported
Cardholder verification is supported
Terminal risk management is to be performed
Issuer authentication is not supported
CDA not supported
Application File Locator
Application Elementary File
Short File Identifier:
1 (Governed by the EMV specification)
Start Record: 1
End Record: 1
Number of Records Involved In Offline Data Authentication: 0
Record: 1
Length: 112
Involved In Offline Data Authentication: false
Card Risk Management Data Object List 1
Amount, Authorised (Numeric) (6 bytes)
Amount, Other (Numeric) (6 bytes)
Terminal Country Code (2 bytes)
Terminal Verification Results (TVR) (5 bytes)
Transaction Currency Code (2 bytes)
Transaction Date (3 bytes)
Transaction Type (1 byte)
Unpredictable Number (4 bytes)
Card Risk Management Data Object List 2
Authorisation Response Code (2 bytes)
Amount, Authorised (Numeric) (6 bytes)
Amount, Other (Numeric) (6 bytes)
Terminal Country Code (2 bytes)
Terminal Verification Results (TVR) (5 bytes)
Transaction Currency Code (2 bytes)
Transaction Date (3 bytes)
Transaction Type (1 byte)
Unpredictable Number (4 bytes)
Cardholder Verification Method (CVM) List:
Cardholder Verification Rule
Rule: Enciphered PIN verified online
Condition Code: Always
Fail cardholder verification if this CVM is unsuccessful
Track 2 Equivalent Data:
Primary Account Number (PAN) - 957852641234567890
Major Industry Identifier = 9 (For assignment by national standards bodies)
Country Code (ISO 3166-1): 578 (=Norway)
Issuer Identifier Number: 957852
Account Number: 64123456789
Check Digit: 0 (Valid)
Expiration Date: Wed Feb 29 00:00:00 CET 2012
Service Code: 601
Discretionary Data: 12345678900
Language Preference (in order of preference):
Language: no (Norwegian)
Issuer Code Table Index: 1 (ISO-8859-1)
Issuer Action Code - Default:
10110000
01000000
00000100
10001000
00000000
FINISHED
Terminal - Banking Chip Card. How they are talk to each other?
Today was a hard day for me, even if it was Sunday...but anyway I want to start a new very interesting topic about
one standard, which is actually playing very important role in a world of Payment application, its name is EMV.
Everyone today has his own banking card, and this is easy way to get the access to your bank account and as a
consequence to your money. Whatever you do, going to buy something, to get some cash or to pay for your
mobile phone, each time you take your card from your wallet and starting from this moment you oblige to follow
some rules in order make a correct payment. To be precisely, it is not you personally, this is your banking card which
should be complained to EMVco standard. Let's imagine you insert your card to the reader of ATM or POS terminal
and from this moment magic is takes a control on your bank account. Interesting, is not it? Let's see what is going
on between your card and ATM or terminal.
First of all, I will give you some useful links about related topics, which I hope will help you to understand the
process of data exchange between smart card and terminal and also helps to read this topic.
Global Platform general description and full set of documents which can be downloaded from official web
site.
Let’s start to see what is going on between card and terminal. I need to say here, first we will speak about contact
interface.About contactless interface I will describe later on.
When the card inserted in to terminal, it is going to be powered and reset. Card must provide Acknowledge-To-
Reset (ATR) and then will wait for incoming commands.
This is a common part which is not directly related to EMV transaction. More information about ATR you will find
in ISO7816 part 3. So, now let’s have a look from EMV standard point of view.
The next step is to choose and select target application. Depending on what type of card you have (Visa,
MasterCard, etc...), different payment schemes will apply during EMV transaction.
There are two approaches can be used to determine which application is going to be used:
1. Terminal use PSE (Payment System Environment), if the one is exists on card.
2. Terminal build a list of candidates based on list of application stored in terminal.
PSE is Payment System Environment which contains, roughly speaking language preference, list of applications and
their priority in which they must be executed. It is not mandatory for all cards to support PSE.
Terminal select PSE using SELECT command with filename 1PAY.SYS.DDF01. If there is no PSE, card should return
“6A82”, which means “file not found”. If card returns “9000”, terminal proceeds to the next step by processing
response from card. The response on the SELECT command for PSE contains FCI data object, which should looks
according EMV Book 1 like:
6F FCI Template M
84 DF Name M
A5 FCI Proprietary Template M
So now terminal knows the SFI of payment system directory to read. By sendin
Iso8583 - articles
PCI compliant with neapay switch ISO8583 Message Converter to XML SQL Add extra custom fields to the ISO8583
CSV interface specification mapping simulator
ISO8583 ATM POS Crypto API integration Deploy the Payments Switch Router in a Changing fields definitions in the ISO8583
with exchanges like Coinbase or Binance test environment simulator and message converter
The payments converter has the capability Deploy then neaPay Payments switch router In this post we explain how to change
to convert any payment messages to API to easily route transactions based on individual fields settings so they match your
requests to exchanges. ... BIN/prefix, amount, merchant, originating specification. All configurable via GUI or by
or destination insytitution, node. ... altering the configuration files directly. ...
Sample Recommended design for an How the fingerprint reader works in the Altering test cases in Excel for the ISO8583
Acquirer test cases suite, Scenarios and ISO8583 payments simulator simulator
Regression
Ready to start your next project with us? Give us a call or send us an email and we will get back to you
as soon as possible!
Get a free quote, Ask for details, Get guidance Download and Use the software yourself Read Documentation and Start guides
Copyright © 2012-2022 neaPay. The neaPay brand, web site data and content, products, training and material are all reserved, under ownership.
All Rights Reserved. Content cannot be reproduced without written accord from neaPay.