Also I've seen Amex offer login/auth verification, where you a service can verify you as the actual Amex user, and possibly trust you more that way.
Never seen it in the US but it would be nice. I feel more comfortable going directly to AMEX first. Some website payment systems are shady feeling.
The only people I've ever met that recommend Stripe are developers.
The only people I'd recommend Square to are merchants whose avg ticket is less than $5 or are borderline hobbyists.
The number of hardcore PP users has dropped significantly in the last 5 years, in my experience, to less than 10%.
Switching to Stripe, they got a two-tier one layer fee scheme. One tier for AMEX and a lower tier for MC/VISA.
The fee burden was noticeably lower with Stripe, too. the business I mention requested a fee discount and got it based on annual volume. But it was cheaper even without the discount.
So, where are the lower fees?
s/tokenization/lockin/ # devil's advocate
Tokenization is vital in this age of cybermiscreants. Ya don't want customer payment card data in your dbms.
The stripe.com API offers tokenization, and it offers the ability to send and validate data like zip/postcode, cvv and street address to cut fraud. They have an api for chargeback disputes, too. (The business I serve doesn't use it, instead we use the forms on their web site. We have dozens of disputes per decade, not worth programming.)
Squareup.com (Square) does a good job with card-present transactions.
And these service providers offer predictable processing fees.
I wonder what's special about the AMEX APIs? Maybe somebody from AMEX can explain? Some of us are always looking for better ways to serve customers and handle payments efficiently.