We have finished integrating Apple Pay in our app and our payment processor is requiring us to send the 3dSecure version used for apple pay (2.1,2.2,2.3,etc.). I believe this only applies to mastercard but would appreciate if anyone has run into something similar and what you specified. I have not been able to find anything in Apple's documentation specifying the version that is used.
You wrote:
I believe this only applies to mastercard but would appreciate if anyone has run into something similar and what you specified. I have not been able to find anything in Apple's documentation specifying the version that is used.
@by_ptr is correct. Apple Pay doesn't explicitly publish which 3DS sub-version (2.1.0, 2.2.0, 2.3.x) is used in its transactions. This is because:
- Apple Pay's authentication happens at the device/Secure Element level, not through a traditional 3DS requestor flow
- The version can vary by issuer, region, and card network configuration
Because of this, Apple Pay abstracts this away intentionally. Since the sub-version is not exposed, when a processor requires a version string for Mastercard, check your processor's documentation or contact them directly to seek decryption strategies from the cryptogram, or defer to 2.2.0 for testing. Most payment processors have hardcoded mappings for Apple Pay tokens and may not actually need you to supple the version.
Cheers,
Paris X Pinkney | WWDR | DTS Engineer