What are your thoughts on using Google Pay or Apple Pay with your
phones? As a retailer I'm finding an increasing choice by customers to
use the NFC (near field communications) feature on their phones and
using the google or Apple version to make payments.
I've been using my Apple Watch for NFC payments for a few
years. It's already on my wrist and I just need to double
tap a button to bring up my debit card. [...]
What I like about using Apple Pay is when I add my debit
card to my phone or my watch a new virtual card number is
generated for that card/device combination. The card
number on my phone is different than the one on my watch,
so I can pay without exposing my physical card number.
Apple Pay also uses "transaction-specific dynamic security
codes" which can help protect against someone capturing
that information to use again (card skimming).
From what I'm reading about them is that both Gpay and Apay are completely free. What do they get out of offering the ability
for free?
Apple & Google get a small percentage of the Interchange Fee each time Apple/Google Pay is used.
That was my next guess. The retailer takes the hit. I better have a
closer look at my POS statements. There are already different rates
and charges for each variety of dB and cc cards.
I'd be interested to know if there's any extra cost to the
retailer as well.
The amount that Google or Apple receives is paid out of
the bank's portion of the interchange fee, at least from
the articles I've read. Whether the banks pass this fee on
would be interesting to know.
Sysop: | Weed Hopper |
---|---|
Location: | Clearwater, FL |
Users: | 12 |
Nodes: | 6 (0 / 6) |
Uptime: | 11:26:19 |
Calls: | 67 |
Calls today: | 1 |
Files: | 50,165 |
D/L today: |
76 files (8,817K bytes) |
Messages: | 279,578 |