support@protx.com
 
Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9

VSP Direct Custom Integration: Step 6 (3D Secure Authentication ONLY)

Step 6: 3D-Authentication is carried out and your website called back with the 3D Secure Authentication results

(N.B: ALL code examples and references to integration kit files within this document are related
to the ASP kit ONLY. To download kits in other languages please visit the Downloads page.)










Your shopper completes the 3D-authentication process at their Issuing Bank's web site.

Once complete (either successfully or not), the bank will redirect your shopper back to the page supplied in the TermURL field you sent in Step 5: You redirect your shopper to their Issuing Bank for 3D Secure Authentication.

Along with this redirection, two fields are also sent. The MD value, to uniquely identify the transaction you are being called back about, and the PARes, the encrypted and encoded results of your shopper's 3D-authentication.

At this stage the shopper is back on your site, via your TermURL, and you have completion information for the 3D-Authentication process. You now need to send those through to Protx to decode the results and, where appropriate, obtain a card authorisation from your acquiring bank.




**IMPORTANT**
Like the PAReq value sent to your site by Protx (as discussed in Step 4: VSP Direct replies to your registration POST), you should NOT store the PARes file in your database. Also, because it is strongly encrypted, only the Protx MPI can decode this for you, so you should not attempt to modify it or the authentication process will fail.

 
Back to top