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.
I recently built a single-page cart and checkout for a client using Vue.js, and integrated PayPal's Smart Buttons (which seems like it uses the new Checkout REST API).
Everything has been working fine, however, I got a notice from the client today that PayPal told them that they should be using the "PayPal Manager" instead. I dug a little bit deeper and apparently they are being told by PayPal that the site must use Payflow Pro, and that they want to go with checkout "Layout B". As I understand it, this indicates they are being told to use the hosted checkout pages, presumably to maintain PCI compliance and prevent any payment card data from hitting the site (which it doesn't do now either when using the Smart Buttons).
My question is, what is the fundamental difference here? I don't want to push back too much but I am struggling to understand why I am being asked to re-work the checkout process to use an older API when Smart Buttons seem to be the preferred, modern method according to the (horrendous) API documentation. However, using a hosted checkout page in Payflow would require that my Vue.js app be completely re-worked as I would need to create routes for the PayPal checkout page to send the user to to resume and complete their order, rather than keeping it how it is now where everything happens on the same page and the Smart Buttons take place in a pop-up.
Is there a fee difference when using the Payflow service? Do transactions get put into a different account? When I log in to their PayPal account, the transactions coming from the newly-built checkout are showing up identical to the ones from their old checkout.