How Apple Pay works and why it matters for developers
51–60 of 116 posts
Re: How Apple Pay works and why it matters for developers
#52Maybe it's just me but I'm not drinking the kool aid about Apple Pay in today's announcement. Aside, I really hated the fact that to watch the event you had to use a Safari browser, same with watching Swift tutorial videos on their website, using latest Chrome on a Mac... Maybe I'm old school but I'm actually finding that payment options are getting worse, not better. This is another example of further fragmentation.…
I'm a Canadian who is temporarily in the US, and it seems so backwards to me. A signature? You mean writing on a piece of paper that probably never gets looks at allows someone to take money out of my bank account? Chip+Pin at least has a semblance of technical security. And cash? Don't get me started. Cash can be physically lost. Cash can be stolen. When you pay with cash, you get given coins as well as the thing yo…
Re: How Apple Pay works and why it matters for developers
#53How does Apple pay differ from Google's ecosystem and whatever it provides? There, the smartphone app (Google Wallet vs passbook) and the hardware is not made by the same people (Samsung vs Apple) - so does this pose any problems?
Apple Pay gets a token from your card issuer and uses that to pay. Google Wallet pays with their own card and charges your card the same amount. Only difference I see is that Google knows about every transaction you make. Apple doesn't.
Re: How Apple Pay works and why it matters for developers
#54Earlier quoted context omitted.
> Maybe it's just me but I'm not drinking the kool aid about Apple Pay in today's announcement. What does this actually mean?
Nothing, it's gibberish. Or, rather, a signal you can use to realize that the person who wrote it can't think critically and most likely doesn't have anything useful to say.
edit: getting downvoted like a champ. The Cult is strong with HN.
Re: How Apple Pay works and why it matters for developers
#55Maybe it's just me but I'm not drinking the kool aid about Apple Pay in today's announcement. Aside, I really hated the fact that to watch the event you had to use a Safari browser, same with watching Swift tutorial videos on their website, using latest Chrome on a Mac... Maybe I'm old school but I'm actually finding that payment options are getting worse, not better. This is another example of further fragmentation.…
I'm a Canadian who is temporarily in the US, and it seems so backwards to me. A signature? You mean writing on a piece of paper that probably never gets looks at allows someone to take money out of my bank account? Chip+Pin at least has a semblance of technical security. And cash? Don't get me started. Cash can be physically lost. Cash can be stolen. When you pay with cash, you get given coins as well as the thing yo…
Last time I came to the US, I realized my cards' magnetic bands weren't working. Would have never noticed otherwise, chips don't wear off. Had to prepare for new cards before my next trip. Chips came so long ago in Canada that I can't recall when. My surprise every time I remember they're still not here.
Then cash only places and having to receive coins; the worst. And then what do you do with the coins, hope that one day you'll get the chance to use them? That never happens. You must accumulate coins in your pockets. Accumulate discomfort and never dare throwing them away. And what's up with cents, what do you buy with a cent?
Back in Canada, all I carry is a debit/credit card (wink) and a health insurance card (wink).
Re: How Apple Pay works and why it matters for developers
#56Re: How Apple Pay works and why it matters for developers
#57Earlier quoted context omitted.
I'm a Canadian who is temporarily in the US, and it seems so backwards to me. A signature? You mean writing on a piece of paper that probably never gets looks at allows someone to take money out of my bank account? Chip+Pin at least has a semblance of technical security. And cash? Don't get me started. Cash can be physically lost. Cash can be stolen. When you pay with cash, you get given coins as well as the thing yo…
These conclusions are surprising to me. I grew up in the states and lived in Canada for 4 years. Though I agree with the lack of security offered by a signature, that method of payment is basically offered everywhere in the US. Compared to Canada its uncommon to be asked for a 5 dollar minimum purchase or a 50 cent surcharge for a credit card transaction. Furthermore, the credit limits in Canada seemed downright rest…
Credit limits in Canada start out restrictive, yes, though I've generally found that if you ask for a higher limit, they will generally grant it. I've had good credit though. That probably makes a difference.
I've been lucky enough to never need to do a chargeback in Canada or the US. Maybe it's not easy in Canada.
Re: How Apple Pay works and why it matters for developers
#58Earlier quoted context omitted.
I'm a Canadian who is temporarily in the US, and it seems so backwards to me. A signature? You mean writing on a piece of paper that probably never gets looks at allows someone to take money out of my bank account? Chip+Pin at least has a semblance of technical security. And cash? Don't get me started. Cash can be physically lost. Cash can be stolen. When you pay with cash, you get given coins as well as the thing yo…
This, I'm living exactly the same situation right now. Last time I came to the US, I realized my cards' magnetic bands weren't working. Would have never noticed otherwise, chips don't wear off. Had to prepare for new cards before my next trip. Chips came so long ago in Canada that I can't recall when. My surprise every time I remember they're still not here. Then cash only places and having to receive coins; the wors…
Re: How Apple Pay works and why it matters for developers
#59Maybe it's just me but I'm not drinking the kool aid about Apple Pay in today's announcement. Aside, I really hated the fact that to watch the event you had to use a Safari browser, same with watching Swift tutorial videos on their website, using latest Chrome on a Mac... Maybe I'm old school but I'm actually finding that payment options are getting worse, not better. This is another example of further fragmentation.…
The problem of capitalism is that all agents want (amongst other things) full vendor lock-in. Sadly that's been our general direction for the past 50 years in most aspects of life, and there seems to be little hope for reversing the machine in thr short term.
I'm very hopeful that we will be able to reverse this trend as I see decentralization efforts everywhere (internet to press, 3d printing to manufacturing, bitcoin to currency, blockchain to public ledger, photovoltaics for power, etc).
Re: How Apple Pay works and why it matters for developers
#60Earlier quoted context omitted.
Apple Pay gets a token from your card issuer and uses that to pay. Google Wallet pays with their own card and charges your card the same amount. Only difference I see is that Google knows about every transaction you make. Apple doesn't.
Wow that's creepy and yet completely unsurprising from google..