Integration Guide

PayPal Payments Pro Integration Guide April 2012 95
Implementing 3-D Secure Transactions (UK Only)
Testing
B
3. Using HTTP Form POST, redirect the cardholder to the issuer’s URL that was provided in
ACSUrl. Ensure that the PaReq has the data from the field PayLoad, from the
cmpi_lookup response.
4. Send the response (redirect) from the issuer’s HTTP Form POST to Cardinal using the
cmpi_authenticate message to determine how to proceed with the transaction.
5. The cmpi_authenticate response determines how to proceed. In this example, when
authentication fails, the following are true:
– SignatureVerification=Y
– PAResStatus=N
6. Notify the cardholder that the transaction is declined.
Example 3: Card Issuer Not Using 3-D Secure
In this example, the card’s issuer does not use 3-D Secure:
1. Construct message for cmpi_lookup.
2. Review the response from cmpi_lookup. Ensure that:
– ErrorNo=0
– Enrolled=N or U
3. Authoress as normal, with the additional fields described in 3-D Secure Fields for Direct
Payment Transaction Requests.
Example 4: Merchant Not Using 3-D Secure
In this example, the merchant does not authenticate a Maestro transaction using 3-D Secure
before executing a direct-payment transaction request:
 Through 31 December, 2009, a DoDirectPayment request returns
ACK=SuccessWithWarning with error code 12001; PayPal still accepts the transaction.
 Beginning on 1 January, 2010, a DoDirectPayment request will return ACK=Failure
with error code 12000 and PayPal will not accept the transaction.
Testing
For 3-D Secure, you cannot use PayPal’s sandbox for testing. You must use Cardinal’s test
procedures.
Refer to the Cardinal documentation.