Not exactly. These systems generate one-time tokens for each use, sometimes that look like a CC number so it will validate checksums, and transmit that back to the gateway where the actual number (or just the account id at that point) is stored, that way if you get that one id compromised it does not compromise any other transactions.
Think of it as generating a unique CC number, tied to your account, for every transaction. Judah On Wed, Sep 24, 2014 at 2:30 PM, Casey Dougall - Uber Website Solutions < ca...@uberwebsitesolutions.com> wrote: > > So they basically use authorize.net and store the payprofileid as this > unique identifyer? > On Sep 24, 2014 4:04 PM, "Judah McAuley" <ju...@wiredotter.com> wrote: > > > > > Answering part of my own question, it looks like ApplePay does have a > > couple of advantages over Google Wallet that are explained well in this > > article: > > > > > http://www.macworld.com/article/2607181/why-apple-pay-could-be-the-mobile-payment-system-youll-actually-use.html > > > > It's a pretty good use case for some of the things you can do when you > own > > the ecosystem in a way that Google doesn't. Cool stuff. > > > > Judah > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-community/message.cfm/messageid:372665 Subscription: http://www.houseoffusion.com/groups/cf-community/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-community/unsubscribe.cfm
