[johndbeatty]

I run a subsidiary of First Data (called Clover). I wrote and published the code for a few reasons:

- so I could answer questions more accurately and thoroughly during press interviews and with current and prospective partners. Nothing beats running code for this.

- My team doesn't trust me to write production code much any more but I need my kicks. ;)

- I'd like for people to understand Apple Pay crypto well -- it's the best I've seen in the payments industry. I'd like to even see something like this standardized for protecting cardholder data (both for card-present/POS transactions and e-commerce), where 3DES/DUKPT is still standard practice.

- There's been some misunderstandings that Apple Pay In-App is a closed system and you need to partner with them to use it. This is an existence proof that this is not the case.

- For people who are their own processor/gateway (e.g. very large companies), this gives them a bit of a head start on understanding what they need to do.

First Data has a commercialized version of Apple Pay in their new e-commerce gateway: http://www.payeezy.com/ (not to mention many gateways which process through First Data and support Apple Pay).