3 ms·
The problem is a lack of "I want to pay you but don't want to give you my credit card" processors out there. That's 99% of the reason I use PayPal (with just on
by smileybarry 3y ago
The problem is a lack of "I want to pay you but don't want to give you my credit card" processors out there. That's 99% of the reason I use PayPal (with just one case of using buyer protection because the vendor just forgot about my order for months and didn't respond).
Google Pay & Apple Pay helps with this now (and the fact they're implemented as a payment type like VISA and not a processor like PayPal helps a lot to prevent lockout cases like this) but they're nowhere near as widespread as PayPal, at least from my experience.
- TheCapeGreek 3y agoI don't understand this "I want to pay without giving my card" thing. Payment gateways process your card, not the app. "Paying without giving my card" is not what that feature is, but rather "card details are saved so you have a lower barrier to spend more".
- smileybarry 3y agoA well-designed app offloads the "enter your payment details" dialog to the processor (e.g.: Stripe), but many shops don't. You're handing off your details to the vendor's website, which then promises to process your payment with Payments R Us. But (A) I can't be sure of that, (B) maybe their forwarding/processing method is insecure and (C) maybe their server is already compromised and a man in the middle will save my card details. Compared to PayPal that are a clear redirection in-browser and result in the vendor getting (at most) a "payment cookie" that can be completed to transfer X USD from Y to Z. Or Apple Pay where your (ephemeral) payment details are E2EE to the payment processor's server, even if they go through the vendor's website/servers.