This action links a saved cardIdentifier to a new merchantSessionKey with a freshly entered securityCode (CVV) to perform a 3D Secure check when re-using a saved card token, for extra security.
What strikes me as odd if that the examples given show how it would be used from the server side only, which you would want to avoid for PCI reasons. With the right PCI accreditation it can be done, so this library should support it, but in most cases it would be a client-side call only.
This action links a saved
cardIdentifierto a newmerchantSessionKeywith a freshly enteredsecurityCode(CVV) to perform a 3D Secure check when re-using a saved card token, for extra security.What strikes me as odd if that the examples given show how it would be used from the server side only, which you would want to avoid for PCI reasons. With the right PCI accreditation it can be done, so this library should support it, but in most cases it would be a client-side call only.