Services News

File Maintenance Error Codes

| Product News

File maintenance error codes?


What is File Maintenance
& List of Error Codes?

There is a file update request 0304 message and 0314 response message. All error codes appear in field 48 of a 0310 or 0312 response message, or in a 0322 file update advice message.

In most cases of file-related error code, the Network Interchange Center (NIC) replies to the file update or file inquiry by sending back a 0310 or 0312 response message, or a 0322 file update discrepancy advice message that contains a response code of 06 (error) in field 39, and an error code in field 48 of the response message.

In the following table, file error codes are listed in numeric order together with the name of the data field or subfield in error and a brief description of the error condition.

Refer to the individual field descriptions for details of field edits file maintenance error codes.



File Maintenance Error Codes

LIST ERROR CODES TABLE
All Error Codes List as of 2019 and 2020
Error Code All Error codes condition
0568 Field 91 - File Update Code, in a 0300 or 0302 request message contains a code other than 1, 2, 3, or 5.
Field 91 - File Update Code, in a 0110 response message contains a code other than 3 or 4 (issued as an Auto-CDB file update error code).
0570 Field 2 - Primary Account Number, has an invalid check digit.
0571 Invalid Account Number. The Account Number does not fall within the range of valid Account Numbers used by any Issuer.
0572 The source authorization centre is not the centre responsible for this Cardholder data.
0574 Field 73 - Date, Action, the purge date month is not 01-12.
0575 Field 73 - Date, Action, the purge date is invalid for one of these reasons:
•   In an add or change, the date is missing
•   Date has expired
•   Date is present in a delete
Field 127.E1 - Action Code contains an invalid code. Valid codes are 01, 04, 05, 07, 11, 41, and 43.
0577 One of the following:
•   Field 127 E.2 - Region Coding contains an invalid code
•   For file name = E2, valid codes are 0 through 9, A through F, and X through Z
•   Region coding includes zero in combination with one or more non-zero codes
0578 Field 127 E.2 - Region Coding is spaces when action code is 04, 07, 41, or 43.
0579 Special processing code and designated action code is specified.
0580 Neither the special processing control code or designated action code is specified.
0582 ield 127 P.1 - PIN Verification Data, positions 1-2 - algorithm identifier is not 01 or 04.
0583 Field 127 P.1 - PIN Verification Data, the PIN verification key index is not a value between 1 and 6.
0584 Field 127 P.1 - PIN Verification Data, the PVV, PIN offset, or PVV/offset is not numeric.
0585 An exception record cannot be updated by the Issuer because the record is from MasterCard.
0586 The country code in field 20 is invalid.
0587 The Issuer exception record cannot be updated.
0588 Field 127 TLV format error.
0590 Field 62.2 -Transaction Identifier (bitmap format), is missing. This field is required in deletions and replacements.
0591 Field 19 - Acquiring Institution Country Code, is missing. This field is required.
0592 The 2-byte tag value 'DF11' is missing. This field is required in additions and replacements.
0650 Field 127 E.1 - Action Code is invalid for one of these reasons.
•   The code is not 01, 04, 05, 07, 11, 41, 43, A1 through A9, XA, or XD
•   The code is 01 in an Electron account record
Action code is inconsistent with data field 39 - Response Code in the Authorization Response (Auto-CDB).
0653 Field 127 R.1 - Risk Level is invalid for one of these reasons:
•   The code is not A, B, C, or D
•   In an add, the field is blank
•   In a change to lower risk, the new risk level is not the next lower code (for example, D cannot be changed to B or A)
0658 Field 127 R.6 - Travel Activity Limit is invalid. (Issuer available).
0659 Field 127 R.7 - Travel Activity Limit is invalid. (Issuer unavailable).
0660 Field 127R.8 - Lodging Activity Limit is invalid. (Issuer available).
0661 Field 127 R.9 - Lodging Activity Limit is invalid. (Issuer unavailable).
0662 Field 127 R.10 - Auto Rental Activity Limit is invalid. (Issuer available).
0663 Field 127 R.10 - Auto Rental Activity Limit is invalid. (Issuer unavailable).
0664 Field 127 R.12 - Restaurant Activity Limit is invalid. (Issuer available).
0665 Field 127 R.13 - Restaurant Activity Limit is invalid. (Issuer unavailable).
0666 Field 127 R.14 - Mail/Telephone Activity Limit is invalid. (Issuer available).
0667 Field 127 R.15 - Mail/Telephone Activity Limit is invalid. (Issuer unavailable).
0668 Field 127 R.16 - Risky Purchase Activity Limit is invalid. (Issuer available).
0669 Field 127 R.17 - Risky Purchase Activity Limit is invalid. (Issuer unavailable).
0670 Field 127 R.18 - Total Purchase Activity Limit is invalid. (Issuer available).
0671 Field 127 R.19 - Total Purchase Activity Limit is invalid. (Issuer unavailable).
0672 Field 127 R.20 - Total Cash Activity Limit is invalid. (Issuer available).
0673 Field 127 R.21 - Total Cash Activity Limit is invalid. (Issuer unavailable).
0674 Field 127 R.22 - ATM Cash Activity Limit is invalid. (Issuer available).
0675 Field 127 R.23 - ATM Cash Activity Limit is invalid. (Issuer unavailable).
0676 Field 127 invalid Issuer available amount 10.
0677 Field 127 invalid Issuer unavailable amount 10.
0678 Field 127 invalid Issuer available limit 11.
0679 Field 127 invalid Issuer unavailable limit 11.
0680 Field 127 invalid Issuer available limit 12.
0681 Field 127 invalid Issuer unavailable limit 12.
0682 Field 101 - File Name, length is not 2.
0683 The BIN for this account does not participate in the Risk-Level File. Participation is a Member parameter setting.
0684 BIN does not participate in the service.
0699 In an update, the length of field 127 is less than the minimum or more than the maximum length allowed, based on the subfield requirements for the file name specified.
0704 Record deleted (escalation update).
0705 No longer a pick-up (escalation update).
0706 No cash or non-cash refresh amount on add.
0707 Effective time error on update.
0708 The Account Number length is not valid for the BIN.
0709 The increment or decrement update is outdated.
0710 Restricted Card List (RCL) update for non-MasterCard account.
0745 Field 62.23 - Product ID, is missing.
0746 Field 62.23 - Product ID, is not alphanumeric.
0747 Field 62.24 - Program Identifier, is missing.
0748 Field 62.24 - Program Identifier, is not alphanumeric.
0749 PAN FM request sent without replacement expiry date.
0750 Field format error.
0751 Account has additional tokens not provided.
0752 Issuer not participating.
0753 Issuer provisions token.
0754 Token must be unique.
0755 Field 2 missing or invalid.
0756 Already in requested status.
0757 Token missing or invalid.
0758 Information mismatch.
0759 Invalid add.
0760 Unavailable for token maintenance.
0761 Token unsupported function.
0762 Token edit reject.
0763 Token invalid source.
0765 Token invalid change.
0766 No token in the token vault.
0767 Field 2 is a token.
0768 Token expiry date invalid.
0769 Token not inactive.
0771 Replacement PAN has invalid account length or invalid check digit.
0772 PAN and replacement PAN match: PAN expiry change request required.
0801 The length of field 127 in a 0300 request is invalid.
0802 Invalid use in a 0300 request message: both field 41 - Card Acceptor Terminal Identification and field 42 - Card Acceptor Identification Code are present.
0806 Invalid field 41 - Card Acceptor Terminal Identification or field 42 - Card Acceptor Identification Code supplied.
0807 In a 0300 request message, field 32 - Acquiring Institution Identification Code, contains an invalid Acquirer BIN (Acquirer BIN is not listed in VEAS).
0809 Field 127 is all spaces in a 0300 request message.
0810 Field 43 - Card Acceptor Name/Location is missing.
0811 Field 43 - Card Acceptor Name/Location, not all subfields in are present.
0812 Invalid country code.
0813 Field 59 - National Point-of-Service Geographic Data, length is missing but field 59 data is supplied.
0814 Field 59 - National Point-of-Service Geographic Data, data is missing but field 59 length is supplied.
0815 Field 59 - National Point-of-Service Geographic Data, length is invalid.
0816 State code is invalid or missing.
0817 Invalid county code.
0818 Postal code is missing.
0819 Province code is invalid or missing.
0820 'V' updated not allowed when BIN keys are set for 'U' service
0821 Invalid or missing data.


Batch File Maintenance

Batch file maintenance can be used to change a large number of records in the usermaintained files at the Network Interchange Center (NIC).

Online batch file maintenance is limited to the centre associated with the Account Number to be updated.

For example, a Processing Centre can update an Account Number only if it owns the associated BIN or if it is a Processor of the associated BIN.

File Maintenance Methods

Batch files are maintained by transmitting a tape file to the NIC from an Extended Access Server (EA Server) or by sending a tape to network center Europe.

A tape file is a batch file of update or replacement records that are applied to the user files at the NIC.

The batch file is usually written to a tape, but it may be a disk file that is transferred from a centre host to an EA Server.

If a complete file replacement is required (format 1 only), the centre should co-ordinate the change with NIC. Lack of co-ordination can seriously jeopardise the centre's file.

Each tape transmitted to NIC must contain 500,000 or fewer records. Multiple tapes must be used for update requests involving more than 500,000 records.

Files requiring multiple tapes are accepted as separate tapes with individual header and trailer records or as a multiple reel or concatenated file.

Before the records from a tape file are applied to the files at the NIC, an offline process edits the updates for critical data, such as Account Numbers and purge dates.

Business Services Support will contact the centre if errors are found.

Exception File replace and update options

Host Issuers can perform full file replacement of Exception Files (that is, updating all the Member's records on the NIC Exception File to match those entries listed by the Member on the tape) at the BIN level.

In addition to Processing Centre-level full file replacements, Host Issuers can also submit a tape file with only one update record per Account Number for both NIC and SMS.





















            Contactless Card Home | About Us | Affiliate Agreement | Anti-Spam Policy | Contact Us
            Privacy Policy | Dmca Notice | Terms of Use | Link to Us