Posted on 29th Jan 2021 1218 views
List of ISO8583 Response Codes, description and use with Video guide of example in the ISO8583 Simulator . Video below
Wikipedia already has a very in-depth description of the ISO 8583 standard.
In this article, we will have a more business-driven approach, focusing on the items that are actually used by banks and Processors in real life.
| Code | Description |
|---|---|
| 00 | Approved or completed successfully |
| 01 | Refer to card issuer |
| 02 | Refer to card issuer's special conditions |
| 03 | Invalid merchant |
| 04 | Pick-up |
| 05 | Do not honor |
| 06 | Error |
| 07 | Pick-up card, special condition |
| 08 | Honour with identification |
| 09 | Request in progress |
| 10 | Approved for partial amount |
| 11 | Approved (VIP) |
| 12 | Invalid transaction |
| 13 | Invalid amount |
| 14 | Invalid card number (no such number) |
| 15 | No such issuer |
| 16 | Approved, update track 3 |
| 17 | Customer cancellation |
| 18 | Customer dispute |
| 19 | Re-enter transaction |
| 20 | Invalid response |
| 21 | No action taken |
| 22 | Suspected malfunction |
| 23 | Unacceptable transaction fee |
| 24 | File update not supported by receiver |
| 25 | Unable to locate record on file |
| 26 | Duplicate file update record, old record replaced |
| 27 | File update field edit error |
| 28 | File update file locked out |
| 29 | File update not successful, contact acquirer |
| 30 | Format error |
| 31 | Bank not supported by switch |
| 32 | Completed partially |
| 33 | Expired card |
| 34 | Suspected fraud |
| 35 | Card acceptor contact acquirer |
| 36 | Restricted card |
| 37 | Card acceptor call acquirer security |
| 38 | Allowable PIN tries exceeded |
| 39 | No credit account |
| 40 | Requested function not supported |
| 41 | Lost card |
| 42 | No universal account |
| 43 | Stolen card, pick-up |
| 44 | No investment account |
| 45-50 | Reserved for ISO use |
| 51 | Not sufficient funds |
| 52 | No checking account |
| 53 | No savings account |
| 54 | Expired card |
| 55 | Incorrect personal identification number |
| 56 | No card record |
| 57 | Transaction not permitted to cardholder |
| 58 | Transaction not permitted to terminal |
| 59 | Suspected fraud |
| 60 | Card acceptor contact acquirer |
| 61 | Exceeds withdrawal amount limit |
| 62 | Restricted card |
| 63 | Security violation |
| 64 | Original amount incorrect |
| 65 | Exceeds withdrawal frequency limit |
| 66 | Card acceptor call acquirer's security department |
| 67 | Hard capture (requires that card be picked up at ATM) |
| 68 | Response received too late |
| 69-74 | Reserved for ISO use |
| 75 | Allowable number of PIN tries exceeded |
| 76-89 | Reserved for private use |
| 76-89 | Reserved for private use |
| 76-89 | Reserved for private use |
| 76-89 | Reserved for private use |
| 90 | Cutoff is in process
(switch ending a day's business and starting the next. Transaction can be sent again in a few minutes) |
| 91 | Issuer or switch is inoperative |
| 92 | Financial institution or intermediate network facility cannot be found for routing |
| 93 | Transaction cannot be completed. Violation of law |
| 94 | Duplicate transmission |
| 95 | Reconcile error |
| 96 | System malfunction |
| 97-99 | Reserved for national use |
| Zero A-9Z | Reserved for ISO use |
| A Zero-MZ | Reserved for national use |
| N Zero-ZZ | Reserved for private use |
| Code | Description |
|---|---|
| 000‑099 | Used in 1110, 1120, 1121, 1140 and 1210, 1220, 1221 and 1240 messages to indicate that the transaction has been approved. |
| 000 | approved |
| 001 | honour with identification |
| 002 | approved for partial amount |
| 003 | approved (VIP) |
| 004 | approved, update track 3 |
| 005 | approved, account type specified by card issuer |
| 006 | approved for partial amount, account type specified by card issuer |
| 007 | approved, update ICC |
| 008‑059 | reserved for ISO use |
| 060‑079 | reserved for national use |
| 080‑099 | reserved for private use |
| 100‑199 | Used in 1110, 1120, 1121, 1140 and 1210, 1220, 1221 and 1240 messages to indicate that the transaction has been processed for authorization by or on behalf of the card issuer and has been denied (not requiring a card pick-up) |
| 100 | do not honour |
| 101 | expired card |
| 102 | suspected fraud |
| 103 | card acceptor contact acquirer |
| 104 | restricted card |
| 105 | card acceptor call acquirer's security department |
| 106 | allowable PIN tries exceeded |
| 107 | refer to card issuer |
| 108 | refer to card issuer's special conditions |
| 109 | invalid merchant |
| 110 | invalid amount |
| 111 | invalid card number |
| 112 | PIN data required |
| 113 | unacceptable fee |
| 114 | no account of type requested |
| 115 | requested function not supported |
| 116 | not sufficient funds |
| 117 | incorrect PIN |
| 118 | no card record |
| 119 | transaction not permitted to cardholder |
| 120 | transaction not permitted to terminal |
| 121 | exceeds withdrawal amount limit |
| 122 | security violation |
| 123 | exceeds withdrawal frequency limit |
| 124 | violation of law |
| 125 | card not effective |
| 126 | invalid PIN block |
| 127 | PIN length error |
| 128 | PIN key synch error |
| 129 | suspected counterfeit card |
| 130‑159 | reserved for ISO use |
| 160‑179 | reserved for national use |
| 180‑199 | reserved for private use |
| 200‑299 | Used in 1110, 1120, 1121, 1140 and 1210, 1220, 1221 and 1240 messages to indicate that the transaction has been processed for authorization by or on behalf of the card issuer and has been denied requiring the card to be picked up. |
| 200 | do not honour |
| 201 | expired card |
| 202 | suspected fraud |
| 203 | card acceptor contact acquirer |
| 204 | restricted card |
| 205 | card acceptor call acquirer's security department |
| 206 | allowable PIN tries exceeded |
| 207 | special conditions |
| 208 | lost card |
| 209 | stolen card |
| 210 | suspected counterfeit card |
| 211‑259 | reserved for ISO use |
| 260‑279 | reserved for national use |
| 280‑299 | reserved for private use |
| 300‑399 | Used in 1314, 1324, 1325 and 1344 messages to indicate the result of the file action. |
| 300 | successful |
| 301 | not supported by receiver |
| 302 | unable to locate record on file |
| 303 | duplicate record, old record replaced |
| 304 | field edit error |
| 305 | file locked out |
| 306 | not successful |
| 307 | format error |
| 308 | duplicate, new record rejected |
| 309 | unknown file |
| 310‑359 | reserved for ISO use |
| 360‑379 | reserved for national use |
| 380‑399 | reserved for private use |
| 400‑499 | Used in 1430, 1432, 1440 and 1442 messages to indicate the result of the reversal or chargeback. |
| 400 | accepted |
| 401‑459 | reserved for ISO use |
| 460‑479 | reserved for national use |
| 480‑499 | reserved for private use |
| 500‑599 | Used in 1510, 1512, 1530 and 1532 messages to indicate the result of a reconciliation. |
| 500 | reconciled, in balance |
| 501 | reconciled, out of balance |
| 502 | amount not reconciled, totals provided |
| 503 | totals not available |
| 504 | not reconciled, totals provided |
| 505‑559 | reserved for ISO use |
| 560‑579 | reserved for national use |
| 580‑599 | reserved for private use |
| 600‑699 | Used in 1614, 1624, 1625, and 1644 messages |
| 600 | accepted |
| 601 | not able to trace back original transaction |
| 602 | invalid reference number |
| 603 | reference number/PAN incompatible |
| 604 | POS photograph is not available |
| 605 | item supplied |
| 606 | request cannot be fulfilled - required/requested documentation is not available |
| 607‑659 | reserved for ISO use |
| 660‑679 | reserved for national use |
| 680‑699 | reserved for private use |
| 700‑799 | Used in 1720, 1721, 1740, 1722, 1723 and 1742 messages. |
| 700 | accepted |
| 701‑749 | reserved for ISO use |
| 750‑769 | reserved for national use |
| 770‑799 | reserved for private use |
| 800‑899 | Used in 1814, 1824, 1825 and 1844 messages. |
| 800 | accepted |
| 801‑859 | reserved for ISO use |
| 860‑879 | reserved for national use |
| 880‑899 | reserved for private use |
| 900 | Advice acknowledged, no financial liability accepted |
| 901 | Advice acknowledged, financial liability accepted |
| 902‑949 | Used in request response and advice response messages to indicate transaction could not be processed. |
| 902 | invalid transaction |
| 903 | re-enter transaction |
| 904 | format error |
| 905 | acquirer not supported by switch |
| 906 | cutover in process |
| 907 | card issuer or switch inoperative |
| 908 | transaction destination cannot be found for routing |
| 909 | system malfunction |
| 910 | card issuer signed off |
| 911 | card issuer timed out |
| 912 | card issuer unavailable |
| 913 | duplicate transmission |
| 914 | not able to trace back to original transaction |
| 915 | reconciliation cutover or checkpoint error |
| 916 | MAC incorrect |
| 917 | MAC key sync error |
| 918 | No communication keys available for use |
| 919 | encryption key sync error |
| 920 | security software/hardware error - try again |
| 921 | security software/hardware error - no action |
| 922 | message number out of sequence |
| 923 | request in progress |
| 924‑929 | reserved for ISO use |
| 930‑939 | reserved for national use |
| 940‑949 | reserved for private use |
| 950‑999 | Used in advice response messages (1x3x) to indicate the reason for rejection of the transfer of financial liability. |
| 950 | violation of business arrangement |
| 951‑983 | reserved for ISO use |
| 984‑991 | reserved for national use |
| 992‑999 | reserved for private use |
Read smart card chip data with APDU commands ISO 7816 16639 views
Deploy, run and generate with neaPay Card Data Generator 8292 views
Run the neaPay ISO8583 simulator 7463 views
ISO8583 payments message format, programmers guide 7105 views
ISO8583 Message Converter JSON and XML interface specification mapping 5251 views
ISO8583 message: The list of ISO 4217 currency codes for data elements 49 and 52 4776 views
Deploy the neaPay ISO8583 simulator - video guide 4433 views
MCC Codes - Merchant Category Codes to use in ISO8583 Field 18 3995 views
Create a new test case in the neaPay ISO8583 simulator Video guide 3520 views
BIN List & Range for MasterCard, Visa, Amex, Diners, Discover, JCB, CUP 3395 views
Log Files in BASE24 classic 2779 views
Asking for defects support for the neaPay products: converter, switch, issuer, simulator 2766 views
Performance testing at 500, 1000 and 1500 TPS 2693 views
Connect the neaPay ISO8583 Acquirer simulator to your own host or Issuer 2542 views
BASE24 documentation to read 2468 views
BASE24 classic vs BASE24-eps 2442 views
Sample Recommended design for an Acquirer test cases suite, Scenarios and Regression 2301 views
BASE24 classic interview questions 2294 views
Regression Testing in 1 click with instant Analytics and CSV report 2292 views
Card readers supported by neaPay payments simulator, CHIP and NFC 2231 views
Load Test enabling and performance testing at 1TPS and 100TPS 2114 views
Run the neaPay ISO8583 converter to JSON, XML, SQL, in a test environment 2032 views
BASE24 classic screens examples explained 2022 views
Adding your own card to the Payments simulator to test your system 1957 views
Changing fields definitions in the ISO8583 simulator and message converter 1926 views
How the fingerprint reader works in the ISO8583 payments simulator 1915 views
Deploy the neaPay ISO8583 Payments converter in a test environment 1843 views
Enabling traces in the payments simulator 1805 views
Altering test cases in Excel for the ISO8583 simulator 1789 views
Run One, Run Scenario, Run All, Run Load in the neaPay ISO8583 Simulator - Use guide 1774 views
BASE24 classic ATM configuration Tutorial in ATD and XPNET with examples 1736 views
EMV explained for programmers 1598 views
Cards and Banks Training 1573 views
Deploy the neaPay HSM simulator in a test environment 1529 views
BASE24-eps interview questions 1472 views
BASE24 classic cards configuration tutorial with Examples 1453 views
Getting started with BASE24. Compiling your first TAL program 1309 views
BASE24-EPS ACI DESKTOP tutorial - Getting started 1289 views
BASE24 classic prefix configuration tutorial CPF with examples 1257 views
ISO8583 Response Codes for Transaction processing 1219 views
ISO8583 converter to JSON XML SQL to HTTP host - message flow - video guide - Part.2 1205 views
ISO8583 converter to JSON XML SQL to HTTP Host - host unavailable - video guide- Part.3 1204 views
BASE24 classic tracing of transactions. Audits, configuration, enabling and opening 1203 views
ISO8583 converter to JSON XML SQL to HTTP host - start& run - video guide - Part.1 1202 views
BASE24 classic Institution configuration Tutorial with example 1093 views
Deploy the Payments Switch Router in a test environment 1043 views
BASE24 classic balance file configuration PBF with example 1039 views
ACI BASE24 classic automatic extract configuration 1031 views
BASE24 classic interchange configuration with examples 1022 views
Base24-eps how to create journals with esbldjnl 983 views
ISO8583 Processing Codes for Transaction Processing 942 views
BASE24 classic routing in IDF 824 views
Getting started with Base24 development. TAL tutorial 816 views
Working with Base24-eps vs BASE24 Classic 799 views
BASE24 classic External Message File configuration EMF with examples 798 views
What to expect when installing Base24-eps 707 views
BASE24 classic host configuration tutorial HCF with examples 707 views
First steps with BASE24 Classic 684 views
Getting started with using Prognosis for BASE24 and BASE24-eps 666 views
ISO8583 Message Types for Transaction Processing 657 views
Ask a question, get advice and 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!
