Blog Home

ISO8583 Message Converter JSON and XML interface specification mapping

Posted on 8th Jun 2019 11170 views

Sample ISO8583 conversion to JSON

This article describes how the ISO8583 Converter creates a JSON object from an incoming TCP/IP ISO8583 binary message, and then sends it to a HTTp host as a POST. Go to ISO8583 converter to JSON for more details and download links.

Analysis of a sample ISO8583 to JSON conversion, from the Converter.

Take the following ISO8583 sample message

20-08-19 15:53:38:203:--------------------------------------------------***--------------------------------------------------
20-08-19 15:53:38:203:ACQ: Test case: 001-01-Withrawal
20-08-19 15:53:38:203:ACQ: Card set: CagecfiCard01
20-08-19 15:53:38:203:ACQ: Key set: 1
20-08-19 15:53:38:203:ACQ: MessageType :1100
20-08-19 15:53:38:204:ACQ: Bitmap :F2344101A8E080000100000006000000 bits:11110010001101000100000100000001101010001110000010000000000000000000000100000000000000000000000000000110000000000000000000000000
20-08-19 15:53:38:204:ACQ: F02_PAN :5044439101000000111
20-08-19 15:53:38:204:ACQ: F03_ProcessingCode :010000
20-08-19 15:53:38:204:ACQ: F04_AmountTransaction :000000010000
20-08-19 15:53:38:204:ACQ: F07_TransmissionDateTime :0820155338
20-08-19 15:53:38:204:ACQ: F11_SystemTraceAuditNumber :005345
20-08-19 15:53:38:205:ACQ: F12_DateTimeLocalTransaction :000000155338
20-08-19 15:53:38:205:ACQ: F14_DateExpiration :1807
20-08-19 15:53:38:205:ACQ: F18_MerchantType :6011
20-08-19 15:53:38:205:ACQ: F24_FunctionCode :200
20-08-19 15:53:38:208:ACQ: F32_AcquiringInstitutionIdenti:001504
20-08-19 15:53:38:208:ACQ: F33_ForwardInstitutionIdentifi:001504
20-08-19 15:53:38:208:ACQ: F35_Track2Data :5044439101000000111=180762010397626000
20-08-19 15:53:38:208:ACQ: F37_RetrievalReferenceNumber :533836310001
20-08-19 15:53:38:208:ACQ: F41_CardAcceptorTerminalIdenti:10001009
20-08-19 15:53:38:208:ACQ: F42_CardAcceptorIdentification:0015040011123
20-08-19 15:53:38:208:ACQ: F43_CardAcceptorNameLocation :BPM LOCATION DEFAULT CITY MA
20-08-19 15:53:38:208:ACQ: F49_CurrencyCodeTransaction :504
20-08-19 15:53:38:209:ACQ: F72_DataRecord :02001504 100000927D000000010000504001504 10001C000000010000504
20-08-19 15:53:38:209:ACQ: F102_AccountId1 :100000927
20-08-19 15:53:38:209:ACQ: F103_AccountId2 :10001
20-08-19 15:53:38:209:--------------------------------------------------***--------------------------------------------------
20-08-19 15:53:38:209:ACQ: Finished building the message, sending now
20-08-19 15:53:38:419:SYS:Client listener received:00D4
20-08-19 15:53:38:419:SYS:Read length:212
31323130F2304001AEC0800000000000060000003139353035383233393130313030303030303235393031303030303030303030303031303030303038323031353533333830303533343530303030303031353533333836303131303630303135303430363030313530343338353035383233393130313030303030303235393D3138303736323031303339373632363030303533333833363331303030313633323634383030303130303031303039303031353034303031313132332020353034303931303030303039323730353130303031--END
20-08-19 15:53:38:424:--------------------------------------------------***--------------------------------------------------
20-08-19 15:53:38:425:ACQ: Message Received
20-08-19 15:53:38:425:ACQ: MessageType :1110
20-08-19 15:53:38:425:ACQ: Bitmap :F2304001AEC080000000000006000000 bits:11110010001100000100000000000001101011101100000010000000000000000000000000000000000000000000000000000110000000000000000000000000
20-08-19 15:53:38:425:ACQ: F02_PAN :5044439101000000111
20-08-19 15:53:38:426:ACQ: F03_ProcessingCode :010000
20-08-19 15:53:38:426:ACQ: F04_AmountTransaction :000000010000
20-08-19 15:53:38:427:ACQ: F07_TransmissionDateTime :0820155338
20-08-19 15:53:38:427:ACQ: F11_SystemTraceAuditNumber :005345
20-08-19 15:53:38:427:ACQ: F12_DateTimeLocalTransaction :000000155338
20-08-19 15:53:38:427:ACQ: F18_MerchantType :6011
20-08-19 15:53:38:427:ACQ: F32_AcquiringInstitutionIdenti:001504
20-08-19 15:53:38:428:ACQ: F33_ForwardInstitutionIdentifi:001504
20-08-19 15:53:38:428:ACQ: F35_Track2Data :5044439101000000111=180762010397626000
20-08-19 15:53:38:428:ACQ: F37_RetrievalReferenceNumber :533836310001
20-08-19 15:53:38:428:ACQ: F38_ApprovalCode :632648
20-08-19 15:53:38:428:ACQ: F39_ActionCode :000
20-08-19 15:53:38:428:ACQ: F41_CardAcceptorTerminalIdenti:10001009
20-08-19 15:53:38:428:ACQ: F42_CardAcceptorIdentification:0015040011123
20-08-19 15:53:38:428:ACQ: F49_CurrencyCodeTransaction :504
20-08-19 15:53:38:429:ACQ: F102_AccountId1 :100000927
20-08-19 15:53:38:429:ACQ: F103_AccountId2 :10001
20-08-19 15:53:38:429:--------------------------------------------------***--------------------------------------------------
20-08-19 15:53:38:429:ACQ: ************************** TEST PASS **************************
20-08-19 15:53:38:430:ACQ: RC Received:000 RC Expected:000
20-08-19 15:53:38:430:ACQ: Tests Executed:2
20-08-19 15:53:38:430:ACQ: Tests Passed :1
20-08-19 15:53:38:430:ACQ: Tests Failed :1
20-08-19 15:53:38:431:ANL: RC is new in the graph:000

 

Basic functionality

The way the ISO8583 Converter to JSON works in its basic configuration is to map each ISO 8583 field to a JSON field.

Usually customers want that neapay handles all ISO8583-related data and pre-builds the response message to the acquirer.

Therefore, we compose the reponse message and we convert the response to the HTTP host.

  

Converter started creating JSON data
20-08-19 15:53:38:379:ISS: Send HTTP request:
[
{
"name": "MessageType",
"value": "0110"
}, {
"name": "Bitmap",
"value": "F2304001AEC080000000000006000000"
}, {
"name": "F02_PAN",
"value": "5044439101000000111"
}, {
"name": "F03_ProcessingCode",
"value": "010000"
}, {
"name": "F04_AmountTransaction",
"value": "000000010000"
}, {
"name": "F05_AmountReconciliation",
"value": ""
}, {
"name": "F06_AmountCardholderBilling",
"value": ""
}, {
"name": "F07_TransmissionDateTime",
"value": "0820155338"
}, {
"name": "F09_ConvRateReconciliation",
"value": ""
}, {
"name": "F10_ConvRateBill",
"value": ""
}, {
"name": "F11_SystemTraceAuditNumber",
"value": "005345"
}, {
"name": "F12_DateTimeLocalTransaction",
"value": "000000155338"
}, {
"name": "F13_DateLocalTxn",
"value": ""
}, {
"name": "F14_DateExpiration",
"value": ""
}, {
"name": "F15_DateSettlement",
"value": ""
}, {
"name": "F16_DateConversion",
"value": ""
}, {
"name": "F17_DateCapture",
"value": ""
}, {
"name": "F18_MerchantType",
"value": "6011"
}, {
"name": "F19_AcquiringInstitutionCountryCode",
"value": ""
}, {
"name": "F21_CntryCodeFrdInst",
"value": ""
}, {
"name": "F22_POSDataCode",
"value": ""
}, {
"name": "F23_CardSequenceNumber",
"value": ""
}, {
"name": "F24_FunctionCode",
"value": ""
}, {
"name": "F25_MessageReasonCode",
"value": ""
}, {
"name": "F26_CardAcceptorBusinessCode",
"value": ""
}, {
"name": "F27_ApprovalCodeLength",
"value": ""
}, {
"name": "F28_DateReconciliation",
"value": ""
}, {
"name": "F29_ReconciliationIndicator",
"value": ""
}, {
"name": "F30_AmountsOriginal",
"value": ""
}, {
"name": "F32_AcquiringInstitutionIdentificationCode",
"value": "001504"
}, {
"name": "F33_ForwardInstitutionIdentificationCode",
"value": "001504"
}, {
"name": "F34_PANExtended",
"value": ""
}, {
"name": "F35_Track2Data",
"value": "5044439101000000111=180762010397626000"
}, {
"name": "F36_Track3Data",
"value": ""
}, {
"name": "F37_RetrievalReferenceNumber",
"value": "533836310001"
}, {
"name": "F38_ApprovalCode",
"value": "632648"
}, {
"name": "F39_ActionCode",
"value": "000"
}, {
"name": "F40_ServiceCode",
"value": ""
}, {
"name": "F41_CardAcceptorTerminalIdentification",
"value": "10001009"
}, {
"name": "F42_CardAcceptorIdentificationCode",
"value": "0015040011123 "
}, {
"name": "F43_CardAcceptorNameLocation",
"value": ""
}, {
"name": "F44_AdditionalResponseData",
"value": ""
}, {
"name": "F45_Track1Data",
"value": ""
}, {
"name": "F46_AmountFees",
"value": ""
}, {
"name": "F48_AdditionalDataPrivate",
"value": ""
}, {
"name": "F49_CurrencyCodeTransaction",
"value": "504"
}, {
"name": "F50_CurrencyCodeReconciliation",
"value": ""
}, {
"name": "F51_CurrencyCodeCardholderBilling",
"value": ""
}, {
"name": "F52_PINData",
"value": ""
}, {
"name": "F53_Security_CtlInfo",
"value": ""
}, {
"name": "F54_AdditionalAmounts",
"value": ""
}, {
"name": "F55_ICCData",
"value": ""
}, {
"name": "F56_OriginalDataElements",
"value": ""
}, {
"name": "F57_AuthorisationLifeCycleCode",
"value": ""
}, {
"name": "F58_AuthorisingAgentInstitutionIDCode",
"value": ""
}, {
"name": "F59_TransportData",
"value": ""
}, {
"name": "F60_CSMReserved",
"value": ""
}, {
"name": "F62_Reserved",
"value": ""
}, {
"name": "F63_PrivateData",
"value": ""
}, {
"name": "F64_MAC",
"value": ""
}, {
"name": "F67_ExtendedPaymentData",
"value": ""
}, {
"name": "F68_ReceivingInstitutionCountryCode",
"value": ""
}, {
"name": "F70_AuthInstCntryCode",
"value": ""
}, {
"name": "F72_DataRecord",
"value": ""
}, {
"name": "F90_OriginalDataElements",
"value": ""
}, {
"name": "F93_TxnDestInstID",
"value": ""
}, {
"name": "F94_TxnOrgInstId",
"value": ""
}, {
"name": "F95_ReplacementAmounts",
"value": ""
}, {
"name": "F96_KeyManagementData",
"value": ""
}, {
"name": "F100_RecInstIdCode",
"value": ""
}, {
"name": "F102_AccountId1",
"value": "100000111"
}, {
"name": "F103_AccountId2",
"value": "10001"
}, {
"name": "F123_Reserved",
"value": ""
}, {
"name": "F124_NFC",
"value": ""
}, {
"name": "F127_ReservedPrivate",
"value": ""
}, {
"name": "F128_MAC",
"value": ""
}
]
 

Standard behaviour of the converter

 

The HTTP host has the ultimate saying and can alter the fields in any way, even add or remove fields.

Our converter takes care of all the logic, but offers the host the power to change anything, if the host chooses to.

The host can reply with all the fields, no fileds, some fields, or just with an empty 200 HTTP response, and we will resnd the response to the ISO8583 host.

 

A sample run of an ISO8583 acquirer simulator, an ISO8583 to HTTP/JSON converter, and a HTTP Host server

 

A sample decline of the HTTP host

 In this example of an Authorization in ISO8583-87 format, the host, which only receives a JSON of the response data, has decided to decline a transaction that the converter has decided to approve.

Therefore, the converter sends back a decline response to the transaction.

The converter can do all MAC, EMV, key exchnages and PIN verification, and the host can receive only transactions that have passed pre-screeening.


LinkedIn

Top Read Articles


BIN List & Range for MasterCard, Visa, Amex, Diners, Discover, JCB, CUP
108616 views

Read smart card chip data with APDU commands ISO 7816
52574 views

ISO8583 Response Codes for Transaction processing
38564 views

ISO8583 Message Types for Transaction Processing
22772 views

ISO8583 Processing Codes for Transaction Processing
21227 views

Run the neaPay ISO8583 simulator
17652 views

Deploy, run and generate with neaPay Card Data Generator
17520 views

MCC Codes - Merchant Category Codes to use in ISO8583 Field 18
15827 views

ISO8583 payments message format, programmers guide
15547 views

ISO8583 message: The list of ISO 4217 currency codes for data elements 49 and 52
13673 views

ISO8583 Message Converter JSON and XML interface specification mapping
11171 views

Cards and Banks Training
9257 views

Support for the neaPay products: Authorization, Switch, Converter, Simulator, Issuer
7947 views

Create a new test case in the neaPay ISO8583 simulator Video guide
7722 views

Log Files in BASE24 classic
7626 views

Deploy the neaPay ISO8583 simulator - video guide
7395 views

BASE24 documentation to read
6861 views

BASE24 classic vs BASE24-eps
6715 views

Performance testing at 500, 1000 and 1500 TPS
6657 views

BASE24 classic interview questions
6609 views

EMV explained for programmers
6096 views

ISO8583 converter to JSON XML SQL to HTTP host - message flow - video guide - Part.2
6052 views

Connect the neaPay ISO8583 Acquirer simulator to your own host or Issuer
5709 views

ISO8583 converter to JSON XML SQL to HTTP Host - host unavailable - video guide- Part.3
5640 views

Adding your own card to the Payments simulator to test your system
5532 views

Card readers supported by neaPay payments simulator, CHIP and NFC
5500 views

ISO8583 converter to JSON XML SQL to HTTP host - start& run - video guide - Part.1
5483 views

BASE24 classic screens examples explained
5421 views

Enabling traces in the payments simulator
5376 views

Changing fields definitions in the ISO8583 simulator and message converter
5373 views

Altering test cases in Excel for the ISO8583 simulator
5373 views

Load Test enabling and performance testing at 1TPS and 100TPS
5370 views

Run the neaPay ISO8583 converter to JSON, XML, SQL, in a test environment
5370 views

Sample Recommended design for an Acquirer test cases suite, Scenarios and Regression
5365 views

Deploy the neaPay ISO8583 Payments converter in a test environment
5364 views

ISO8583 ATM POS Crypto API integration with exchanges like Coinbase or Binance
5364 views

Run One, Run Scenario, Run All, Run Load in the neaPay ISO8583 Simulator - Use guide
5359 views

How the fingerprint reader works in the ISO8583 payments simulator
5359 views

Regression Testing in 1 click with instant Analytics and CSV report
5336 views

BASE24-eps interview questions
5099 views

Deploy the Payments Switch Router in a test environment
5061 views

Java version for neapay products Simulator Converter Switch Authorization Cards Issuer
5030 views

Deploy the neaPay HSM simulator in a test environment
5029 views

BASE24 classic ATM configuration Tutorial in ATD and XPNET with examples
4907 views

Add extra custom fields to the ISO8583 simulator
4628 views

BASE24 classic cards configuration tutorial with Examples
4331 views

BASE24-EPS ACI DESKTOP tutorial - Getting started
4078 views

PCI compliant with neapay switch
3759 views

ISO8583 Message Converter to XML SQL CSV interface specification mapping
3656 views

BASE24 classic prefix configuration tutorial CPF with examples
3107 views

BASE24 classic tracing of transactions. Audits, configuration, enabling and opening
3052 views

ACI BASE24 classic automatic extract configuration
3004 views

BASE24 classic Institution configuration Tutorial with example
2730 views

BASE24 classic balance file configuration PBF with example
2720 views

First steps with BASE24 Classic
2483 views

Getting started with using Prognosis for BASE24 and BASE24-eps
2231 views

Trace configuration in neaPay Simulator, Converter, Switch, Authorization and Cards Issuer
2079 views

POS simulator format SPDH HPDH Verifone and custom
1526 views

Iso8583 - articles


Are you ready to start or need help?


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!

Download and Use the software yourself


Download software

Read Documentation and Start guides


Get started