We strive to replace our use of Authorize.net. I spent a lot of time looking at the PayPal documentation, but cannot find a clear answer to my question:
Using thousands of dozens of different PayPal APIs is an opportunity to have a verification process that is available on our website, where we collect and process credit card information from a client, without leaving the client, our site and without the client, ever seeing anything related with PayPal (so PayPal is 100% invisible).
I am confused by this PayPal documentation page : "Please note: Direct Payment API is not a standalone product. You must use the Direct Payment API and Express Checkout together as part of the Payments Pro website solution." as Express Checkout requires you to display PayPal logos, etc.
And this page makes it clear that you should offer the branded Express checkout option to use the direct payment API.
I suppose I'm just looking for confirmation that there are people who use SOA who use PayPal in this way and they have no problem making the PayPal client invisible invisible to the client?
source
share