3DS 'unable to verify enrolment'

[davidjgoss87]

I've had a few transactions recently with the above 3DSecure message (usually it would be 'authenticated' or 'not enrolled'. Any ideas of whether this affects the liability shift? Thanks

 

[PayVector]

Yeah the problem is Mastercard directory servers have been up and down over the last week like a yoyo. It is an industry wide issue at present.

Basically your PSPs 3D system is attempting to connect to the directory server and it is failing. What we have actually been seeing is that we are getting a valid response back from the directory server but it is flagged as type 'U' which means 'Unable To Verify'.

Now the tricky bit is wether to proceed with the transaction or not. When there is a failure you can still process and your PSP should submit a code with the transaction saying that the PSP did attempt but could not get a workable response from the directory server. The problem is that the liability shift is not guaranteed so you could be exposed.

What we have had to put in place this week is 2 seperate modes for transaction to run. Strict will fail the transaction with a response code of U. Relaxed will allow it to continue and submit the attempted code with the Tx.

So the short of it is that its Mastercard being Mastercard.

Hope that helps.