Batch Transaction Errors

The following errors can be returned in response to a Batch Transaction request.

📘

Format of batch transaction errors

Some batch transaction errors are formatted differently from other error types. They include the processing-info element, which contains the processing-status, processing-error-code, processing-error-name, and processing-error-description elements. For details, see the sample error below.

Code

Name

Description

0

UNEXPECTED_ERROR

An unexpected error has occurred.

2

MISSING_CALLBACK_URL

callback-url element is required

3

MISSING_BATCH_ID

batch-id element is required

4

DUPLICATE_BATCH_ID

Batch ID already exists

6

MISSING_MERCHANT_TRANSACTION_ID

merchant-transaction-id element is required for card transactions

101

INVALID_BATCH_ID

Invalid batchId

10000

INVALID_API_VERSION

The API version passed in the request is invalid.

10001

VALIDATION_GENERAL_FAILURE

The resource passed in the request has violated validation rules. Additional information about the specific issue is provided in the error description.

11001

XSS_EXCEPTION

User input suspected as malicious.

20011

TRANSACTION_TYPE_NOT_ALLOWED

Only AUTH_CAPTURE or CAPTURE card transactions, ECP or recurring PayPal payments are allowed in Batch

80002

BATCH_PROCESSING_IN_PROGRESS

The processing of this batch is not yet complete. Try again later.

{
    "batchId": "PKB0035",
    "callbackUrl": https://pavelk-lap.bluesnap.int:7000/d,
    "processingInfo": {
        "processingStatus": "fail",
        "processingErrors": {
            "processingError": [
                {
                    "processingErrorCode": "4",
                    "processingErrorName": "DUPLICATE_BATCH_ID",
                    "processingErrorDescription": "Batch ID already exists"
                }
            ]
        }
    }
}