Validation Errors

If a request data is not correct, because it has missing/incorrect ICC tags for example, the response will contain further information at XPath:

Response/Result/PaymentProviderError.

An example of this might look like the following:

<Response type="CardEaseXML" version="1.5.0">
    ...
    <Result>
        ...
        <PaymentProviderError code="validation_failure">Tag 4F - Tag missing | Tag 5F30 - Tag missing</PaymentProviderError>
        ...
    </Result>
    ...
</Response>

What validations errors can be returned and what they mean is described below. The output can be interpreted as follows: Tag (tag number) - (List of errors with that ICC tag separated by a semi-colon). For example, if ICC tag 5F30 was the incorrect length and format the output might be something like:

Tag 5F30 - Invalid length: 1, Expected: [2]; Incorrect format, Expected NUM

If there are issues with multiple ICC tags they are separated in the output by a vertical bar character ‘|’. An example of this can be seen above.

The possible validation errors that the testing platform may return are defined in the table below:

Error	Description
Bit 13 (Enciphered PIN for offline verification) does not match terminal configuration	The Terminal Capabilities ICC tag does not match the expected value based on what is provided in the CardholderAuthentication/Offline XML request field.
Bit 14 (Signature (paper)) does not match terminal configuration	The Terminal Capabilities ICC tag does not match the expected value based on what is provided in the CardholderAuthentication/Signature XML request field.
Bit 15 (Enciphered PIN for online verification) does not match terminal configuration	The Terminal Capabilities ICC tag does not match the expected value based on what is provided in the CardholderAuthentication/OnlinePin XML request field.
Bit 16 (Plaintext PIN for offline ICC verification) does not match terminal configuration	The Terminal Capabilities ICC tag does not match the expected value based on what is provided in the CardholderAuthentication/OfflinePin XML request field.
Bit 22 (IC with contacts) does not match terminal configuration	The Terminal Capabilities ICC tag does not match the expected value based on what is provided in the CardInput/ContactEmv XML request field.
Bit 23 (Magnetic stripe) does not match terminal configuration	The Terminal Capabilities ICC tag does not match the expected value based on what is provided in the CardInput/Magstripe XML request field.
Bit 24 (Manual key entry) does not match terminal configuration	The Terminal Capabilities ICC tag does not match the expected value based on what is provided in the CardInput/Keyed XML request field.
Bit at position X incorrect, Expected: Y	The ICC tag had an unexpected bit value at bit position X according to what the selected test case expected.
Does not match boarded country code, Expected: X	The Terminal CountryCode ICC tag does not match the country code boarded for.
Does not match boarded currency code, Expected: X	The Transaction Currency Code ICC tag does not match the currency boarded for.
Does not match expected terminal type	The Terminal Type ICC tag is not the expected value for the request.
Does not match expected value, Expected: X	The ICC tag/value did not match the expected value for the selected test case.
Does not match request value, Expected: X	The ICC tag value does not match the equivalent value in the XML request. For example, the Amount XML field and the Amount Authorized ICC tag.
Failed to verify cryptogram	Either the Application Cryptogram ICC tag is incorrect or a tag it’s computation relies on has a validation error.
Hex character at position X incorrect, Expected: Y	The ICC tag value was partially incorrect at character position X and it was expected to be character Y.
Incorrect format	Service was unable to parse the ICC tag format.
Incorrect format, Expected ALPHANUM	The ICC tag was in an incorrect format. Should have been specifically alphanumeric: [a-zA-Z0-9].
Incorrect format, Expected HEX	The ICC tag was in an incorrect format. Should have been specifically hexadecimal: [a-fA-F0-9].
Incorrect format, Expected NUM	The ICC tag was in an incorrect format. Should have been specifically numeric: [0-9].
Invalid length: X, Expected: [Y, Z]	The ICC tag was the wrong length, in bytes. This message is used when an ICC tag can have a variable length. X = request value length, Y = expected minimum inclusive length, Z = expected maximum inclusive length.
Invalid tag value	The ICC tag had a null value.
No bit at position X (Too short)	The ICC tag value was too short compared to what the selected test case expected.
Online pin CVM used on terminal without reported support	The CVM Results ICC tag indicates an unsupported CVM was used, according to TerminalCapabilities.
Pin CVM used on terminal without reported support	The CVM Results ICC tag indicates an unsupported CVM was used, according to TerminalCapabilities.
Signature CVM used on terminal without reported support	The CVM Results ICC tag indicates an unsupported CVM was used, according to TerminalCapabilities.
Tag missing	A mandatory ICC tag is missing from the request.
Tag should not be present	The ICC tag is not applicable and should be removed.
Unknown format	Service was unable to parse the ICC tag format.
Unknown test case reference	The value in the reference request field is not a valid test case name.
Value length incorrect, Expected: X	The ICC tag was the incorrect length, in bytes, according to what was expected by the test case.