XML Validation Error Messages

Table A-7 provides examples of XML Validation Error Messages. These messages are the value associated with the message attribute of either a cnpResponse or cnpOnlineResponse, when the response=“1” (the response attribute).

If response=“0”, the associated message=“Valid Format”. For information about response values 2 through 5, see Additional Response Header Error Messages.

TABLE A-7 Response Header Error Message Examples

Example Message (message attribute of cnpOnlineResponse)	Description (line numbers will vary according to the location of the error)
Error validating xml data against the schema on line 13. The length of the value is 3, but the required minimum is 4.	The value on line 13 does not meet the minimum length requirement for the element as specified in the schema. For example, if you specified 812 as a value for the `<expDate>` element, which has a minLength of 4, the system returns this error message.
Error validating xml data against the schema on line 18. The length of the value is 6, but the required maximum is 4.	The value on line 18 exceeds the maximum length requirement for the element as specified in the schema. For example, if you specified 082012 as a value for the `<expDate>` element, which has a maxLength of 4, the system returns this error message.
Error validating xml data against the schema on line 11. The value is not a member of the enumeration.	The value on line 11 is not a valid enumeration for the specified element. For example, The `<type>` element allows values of VI, MC, DI, AX, DC, JC, PP and BL. If you submitted a value of VISA, the system returns this error message.
Error validating xml data against the schema on line 8. Content of element "amount" is incomplete.	The `<amount>` element does not contains a valid value. For example, if you submitted a captureGivenAuth request and included the amount element without specifying a value, the system returns this error message.
Error validating xml data against the schema on line 6 tag name "echeckSale" is not allowed. Possible tag names are: <authorization>,<capture>,<credit>, <sale>,<void>	The submitted transaction failed validation against the schema, because an element name was out of sequence or not allowed in the transaction. The error message specifies the invalid element (`<echeckSale>` in the example), as well as the possible valid elements.
System Error - Call Vantiv	Typically, the system returns this error if there was a problem with authentication due to an error in the submitted Merchant Id, user, and/or password. The problem may also be due to the use of single quotes around the attribute (merchantId) value.
Error validating xml data against the schema on line 1. Probably namespace URI of tag "cnpOnlineRequest" is wrong (correct one is "http://www.vantivcnp.com/schema")	The URI named in the `xmlns=` attribute is incorrect. The problem may also be due to the use of single quotes around the attribute value. Note: The URI may differ based upon the version of cnpAPI you are using.
Error validating xml data against the schema on line 12786. The entity name must immediately follow the'& amp;'in the entity reference.	The '&' symbol is used in XML to designate certain special characters. The error indicates that the symbol was submitted without an entity name (for example, " or &). Typically, the error occurs when the name or one of the address lines of the billToAddress element includes the symbol instead of the entity reference. For example, “John & Mary Smith” should be sent as “John & Mary Smith” or “John and Mary Smith”).
Error validating xml data against the schema on line 1. Content is not allowed in prolog.	This error is usually an indication of extraneous characters appearing in front of the first XML element. For example, the “?” before the “<“symbol in the following line would cause this error to be returned: `?<?xml version="1.0" encoding="utf-8">`
Duplicate Batch (Batch ID: 28292109643, session sequence: 1, unique ID:) not processed - 29 duplicate transactions (57 total) in a row found. Duplicate Batch (Batch ID: 23829210964, session sequence: 1, unique ID:) not processed - 96.49% of the transactions (57 total) in the batch are duplicates.	(Batch only) The system has determined that the Batch is a duplicate and therefore not processed. The first part of the message provides the count of the greatest number of consecutive duplicate transaction in the batch (29 in the example). The second part of the message the overall percentage of duplicates in the batch (96.49% in the example). The limits are more than 10 consecutive duplicate transactions detected and/or more than 25% of all transaction in the batch detected as duplicates.