We currently have limited customer service staffing due to Coronavirus (COVID-19) safety precautions. We encourage you to find quick answers to your questions by searching the community forum, visiting our Help Center, or messaging us (message response times will be delayed). Thank you for your patience.
New to the community? Welcome! Please read our Community Rules and Guidelines
I have had quite a bit of confusing around this as well trying to get it fully supported in our PayPal for WooCommerce plugin. The information we have gotten is that it's not yet ready for PayFlow.
I've been recommending that people switch to Braintree. Using that with the Drop-In UI will help take care of 3DS stuff and will also provide a better checkout experience as it includes PayPal, direct credit cards, Google Pay, Apple Pay, and Venmo all in a single hosted checkout integration.
Basically, Payflow has always supported 3rd Party MPI's as well as having its own Buyer Authentication Service. All the details for sending data via Payflow when using a 3rd party MPI; i.e. Cardinal Commerce, is in the Buyer Authentication guide. However, it's confusing so I am in the process of having the Payflow Gateway Developer Guide updated with a new Appendix related to 3DS support. Should be out soon.
But basically, if you are using Cardinal, you'll do the authorization via Cardinal and send the data received in the Sale or Authorization request.
The cardholder is enrolled:
NOTE: The following two fields will be supported in the future, starting with PayPal in September and other processors to follow. You can send these fields now, but they won’t be effective until support is added.
The cardholder is not enrolled; see descriptions above:
Note: the following field will be supported in the future, starting with PayPal in September and other processors to follow. You can send this field now, but it won’t be effective until support is added.
Let me know if you have any other questions.
Thanks for taking the time to clarify this in such detail @Payflow_Todd, it's super helpful to know these details in advance.
Based on your comment I just had a few questions:
Here is a sample I got from another PayPal rep that he says is working, but I have not yet played with it myself.
1. Payflow supports both BYOB (Bring your own Bank) and PayPal as your bank. Not all fields map to all processors or PayPal. It looks like PayPal doesn't support this parameter, so you can ignore it. However, I believe AUTHENTICATION_ID would map to ProcessorTransactionId as only v1.x was supported and for v2.x support right now only DSTransactionId and the version is supported. Payflow (Buyer Authentication Service) was based on older Cardinal Centinel service and we'll be updating it in the future to support Cardinal Cruise.
2. Correct, 3DS 2.0 is an EU requirement at this time. The US will catch up at some point in the near future.
3. The US card could be registered, so you'd treat these the same regardless of where the merchant is located. However, for US card you won't get full v2 support.
@MTS_Christina @Payflow_Todd - Following on from your assistance last month, is Payflow support for 3DS available yet? We are keen to integrate into our environment so that we can test before 14th September.
If it is, where would be the best place to look for documentation, and if it is not are there any timeframes for when it is expected to be available for merchants?