What is it?

NMI’s EMV Sandbox is a flexible testing platform that allows for validation of credit and debit transactions against predefined test cases, with a specific focus on EMV. It does this by running different checks on the transaction request and then compiles a list of issues it finds which are then returned in the transaction response. This list can then be used to make informed amendments to the integration.

By using this testing platform, it ensures that the integration is in the best possible shape. For example; it could be used before EMV certification begins, saving value time during the formal process. The automated nature of the tool allows integrators to take control of their testing and move at their own pace.

Getting Started

Coming Soon!

Selecting a Test Case

Testing of an integration can be done by selecting specific test cases provided by the EMV Sandbox. This is done by putting the name of the test case in the reference request field, at XPath: Request/TransactionDetails/Reference. For example, to select the Visa Contact 01 test case the XML request might look like this:

<Request type="CardEaseXML" version="1.5.0">
    <TransactionDetails>
        ...
        <Reference>Visa Contact 01</Reference>
        ...
    </TransactionDetails>
    ...
</Request>

Available Test Cases

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: