I haven't seen yet how (or if) recurring payments are supported. Anyone know?
See page 5 of this document for evidence that recurring payments are indeed supported. https://developer.apple.com/apple-pay/Getting-Started-with-A...
How Apple Pay works and why it matters for developers
31–40 of 116 posts
Re: How Apple Pay works and why it matters for developers
#32Maybe 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. Tap cards, stripe cards, chip cards - all the machines have different interfaces, some touch screen, some with pens. Not sure about you guys but I forget my credit card pin compared to my bank card pin half the time. I have a way to many accounts to remember already. What happened to just a signature?
It's like someone needs to come up with an interface for payments. That universally accepted. Think of a wall socket for power, 3 prongs, supports 2 prong interface. Works great.
Lets step back. Oh wait, we have one. It's called CASH. Cash seems to make more and more sense these days. No overage fees for using your own money. Accepted everywhere already. It doesn't get malware and steals your data. It doesn't need charging or have bugs. Doesn't seems as easy to spend when you physically see it leaving your old school wallet.
I for one won't ever use my phone for payments nor will I be looking to work on apps trying to convince others that its fairy land for payments and makes your life better because of revolutionary Apple marketing spiels. Virtual apps on the app stores, fine, I see it makes sense. Brick and mortar, I just don't see it.
Re: How Apple Pay works and why it matters for developers
#33> Apple Pay marks the first time a popular operating system is making payments a platform service for real-world, non-digital-good transactions, in a broad, inclusive manner that is compatible with the mainstream payments processing industry I'm sorry... what? How is this different from Google making Google Wallet back in 2011? They both use the same tech (PayPass, an industry standard), and both are made by an OS co…
Google wallet was unpopular and was impeded by the cell carriers. It was a business failure, not a technical one.
Sure, I totally agree that Google Wallet was basically a business failure.
I'd also say that the only thing that may stop Apple Pay from being a business failure is that it's Apple doing it this time (even tho, frankly, their UI looks significantly worse than Google Wallet, and has far less functionality, and Google Wallet is no longer impeded by the carriers)...
But that's not what the article section i quoted was talking about. It just made an unqualified claim "this is the first time an OS maker has made a payments product for the physical world"
Re: How Apple Pay works and why it matters for developers
#34Maybe 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.
Re: How Apple Pay works and why it matters for developers
#35Earlier quoted context omitted.
Google wallet was unpopular and was impeded by the cell carriers. It was a business failure, not a technical one.
Sure, I totally agree that Google Wallet was basically a business failure. I'd also say that the only thing that may stop Apple Pay from being a business failure is that it's Apple doing it this time (even tho, frankly, their UI looks significantly worse than Google Wallet, and has far less functionality, and Google Wallet is no longer impeded by the carriers)... But that's not what the article section i quoted was t…
I've never used Google wallet- but how could Apple's UI be worse? All you do is tap your device. How did Google Wallet work?
Re: How Apple Pay works and why it matters for developers
#36Maybe 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.…
> 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?
Re: How Apple Pay works and why it matters for developers
#37Earlier quoted context omitted.
That sounds different than Google Wallet. With an NFC Android phone you can pay at any PayPass terminal, without them needing to change their software.
Another interesting question: If a vendor adds support specifically so that they can accept Apple Pay, will my Android phone start working for NFC payments there?
If they implement whatever transaction API is required by your wallet..
Re: How Apple Pay works and why it matters for developers
#38Earlier quoted context omitted.
Sure, I totally agree that Google Wallet was basically a business failure. I'd also say that the only thing that may stop Apple Pay from being a business failure is that it's Apple doing it this time (even tho, frankly, their UI looks significantly worse than Google Wallet, and has far less functionality, and Google Wallet is no longer impeded by the carriers)... But that's not what the article section i quoted was t…
I've never used Google wallet- but how could Apple's UI be worse? All you do is tap your device. How did Google Wallet work?
Yeah I found that to be mildly humorous. Not sure how the UI is terrible, it looks pretty simple and well thought out
Re: How Apple Pay works and why it matters for developers
#39Maybe 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.…
cash wears out easily, it can be hard to have exact change.
I agree with the psychological effect of spending cash compared to a card (digits don't mean as much as handing over a bunch of paper), but things like IC cards are great for people who hate fidgeting with change (this is especially bad in places like Europe/Japan where a handful of change can end up being over $20).
And it's not like cash has disappeared. This is one more option.
Re: How Apple Pay works and why it matters for developers
#40> Apple Pay marks the first time a popular operating system is making payments a platform service for real-world, non-digital-good transactions, in a broad, inclusive manner that is compatible with the mainstream payments processing industry I'm sorry... what? How is this different from Google making Google Wallet back in 2011? They both use the same tech (PayPass, an industry standard), and both are made by an OS co…
I'm always suprised at how Apple and co. can so bluntly deny the existence of prior art for what they do.
Even if they do it better, that doesn't mean they're the first.