8. Changelog

The source for this documentation is publicly hosted on Github. The full changes can be found in the revision history.

Pull requests and issues are welcome.

8.1. July 7th, 2025

  1. Added documentation for the v2.3.1 specification.

8.2. September 17th, 2024

Updated preauth response to include two new fields:

  • acsProtocolVersions: Array of objects containing the list of Protocol versions supported by the ACS for the card range, with their associated ACS information indicator, the 3DS method URL, and the list of supported message extensions.

  • dsProtocolVersions: Contains the list of active protocol versions supported by the DS.

8.3. November 11th, 2020

  1. Update list of supported card schemes

  2. Clarify that cardholderName must be ASCII

  3. Mention that browserColorDepth is not always valid by specifiction, provide solution

  4. Update preauth timeout that has been changed from 30, to 80 seconds.

  5. Improve text in threeDSRequestorChallengeInd description in reference.

  6. The sandbox has historically handled Base64-URL encoding wrong, since it has required the CReq values received to include padding, while allowing both with and without padding for the 3DS Method input.

    EMVCo has clarified that Base64-URL encoding must not include padding. Currently for both CReq and 3DS Method, padding is allowed but not required. In January 2021, the sandbox will be changed to disallow padding, requests that include padding will then fail.

    It is suggested that you remove padding the mentioned requests at your leisure, but sooner rather than later.

    The pages described both the challenge flow and 3DS Method has been updated to mention that padding is not allowed.

    Your system should be able to receive messages both with and without padding, until further updates from EMVCo. Currently the sandbox uses padding in the challenge responses (CRes) messages. This will be true until January, to ensure that your systems are compatible and don’t reject messages with padding.

8.4. September 17th, 2020

  1. Fixed error in sandbox, field challengeCompletionInd was incorrectly challengeCompletionIndicator.

8.5. August 21st, 2020

  1. Add proper support for 2.2.0 tests in the sandbox

  2. Ensure that automatic version determination works with sandbox tests

  3. Removed startRange, endRange from preauth response.

  4. Add missing 2.2.0 transStatusReason descriptions

  5. Fix 2.2.0 acsRenderingType difference mention. The change is in RReq, not in ARes.

8.6. August 12th, 2020

  1. Add messageType: CRD to /preauth response

8.7. June 29th, 2020

  1. Clarify that only ASCII characters are allowed.

8.8. June 25th, 2020

  1. Reformat testcase descriptions to be more concise.

  2. Add 3RI example input.

  3. Add scheme to /preauth output.

8.9. June 24th, 2020

  1. Reference for 3-D Secure version 2.2.0 was added (link). This required moving pages around and updating miscellaneous links.

  2. Removed versioning section specifically about Mastercard.

  3. Added New in 2.2.0 page.