Batch file error handling

This page lists the error codes that can be returned by the D1 batch file processor.

These errors are reported in the batch output file. They can occur either while D1 parses the input batch file or while it processes an individual operation (for example, when decrypting card details).

Error levels

Errors are reported at two different levels:

• Header level (H): Errors that apply to the entire input file. When a header-level error occurs, it is marked as H.

• Record level (R): Errors that apply to a specific operation record. When a record-level error occurs, it is marked as R.

Error handling behavior

Header-level and record-level errors are handled differently:

• Header-level error (H) If a header-level error occurs, D1 does not process any records in the file. The batch output file contains only the header section and the corresponding error.

• Record-level error (R) If there is no header-level error, D1 attempts to process all records in the file. A failure on one record does not prevent other records from being processed. In the batch output file, each record (each end user and card) includes its own status and any associated error.

Error list

The following table describes all error codes that can be returned by the batch file processor.

Error code	Level	Name	Description
100	H	INVALID_HEADER	The header in the batch file does not comply with the expected structure. See Batch file definition.
102	H	FILE_TOO_BIG	The file size exceeds the maximum allowed. See Batch file definition.
103	H	INVALID_JSON_FILE	The file is not valid JSON.
105	H	MANDATORY_PARAMETER_MISSING_HEADER	A required parameter is missing from the header. See Batch file definition.
106	H	FIELD_INVALID_FORMAT	A header parameter is not in the expected format. See Batch file definition.
107	H	DUPLICATE_ROW_ID	Each record must have an incremental rowId value. D1 detected a duplicate rowId. See Batch file definition.
110	H	INVALID_SIGNATURE	Signature verification failed. Check the key that was used and how the signature was computed. See Batch file definition and the signature section on that page.
111	H	MISSING_SIGNATURE	The signature field is mandatory but is missing from the file. See Batch file definition.
112	H	WRONG_CONFIGURATION	For the provided issuerId, no valid configuration was found. Contact your Thales delivery team.
113	H	UNKNOWN_ISSUER	The issuerId in the batch file does not match any issuer onboarded in D1. Contact your Thales delivery team.
116	H	BAD_FILE_EXTENSION	The batch file extension is not recognized. See Batch file overview.
117	H	BAD_FILE_NAME	The batch file name does not follow the expected naming convention. See Batch file overview.
130	H	DUPLICATE_FILE_NAME	A batch file with the same name has already been processed. Ensure that each batch file name is unique.
197	H	UNKNOWN_OPERATION	The operation value in the file header is not supported. See Batch file definition for the list of allowed operations.
199	H	PARSING_ERROR	An unexpected error occurred while parsing the header. Contact your Thales delivery team if the issue persists.
202	H	INVALID_RECORD	The record header is not valid, or the rowId value is invalid. See Batch file definition.
203	H	MANDATORY_PARAMETER_MISSING_RECORD	A required parameter is missing from a record. See Batch file definition.
FIELD_INVALID_FORMAT	R	FIELD_INVALID_FORMAT	The record JSON is not well formatted, or a field in the record is not in the expected format as defined in this documentation. See Batch file definition.
FIELD_INVALID_VALUE	R	FIELD_INVALID_VALUE	A field in the record has a value that is not allowed for that field. See Batch file definition.
CONSUMER_INVALID_STATE	R	CONSUMER_INVALID_STATE	The end user (consumer) already exists in D1 but is in an invalid state (for example, DELETED).
INTERNAL_ERROR	R	INTERNAL_ERROR	An unexpected internal error occurred while processing the record. Additional details may be returned when available.
CRYPTO_ERROR	R	CRYPTO_ERROR	D1 could not decrypt the provided encrypted data in the record.
INVALID_PAN	R	INVALID_PAN	The funding PAN is invalid or does not meet the expected format. See Batch file definition.
INVALID_EXPIRY_DATE	R	INVALID_EXPIRY_DATE	The card expiry date is invalid or does not meet the expected format. See Batch file definition.
CARD_ALREADY_EXISTS	R	CARD_ALREADY_EXISTS	The cardId is already registered in D1 for this end user and differs from the card previously registered under that identifier.
CARD_INVALID_STATE	R	CARD_INVALID_STATE	The cardId is already registered in D1 but the card is in an invalid state (for example, REPLACED or DELETED).
OPERATION_NOT_ALLOWED	R	OPERATION_NOT_ALLOWED	Registration is not allowed for this card product based on the current configuration.
MISSING_C2P_MANDATORY_INFORMATION	R	MISSING_C2P_MANDATORY_INFORMATION	One or more fields required for Click to Pay are missing (for example, firstName, lastName, language, mobilePhoneNumber.countryCode, or mobilePhoneNumber.phoneNumber).