This page (revision-2) was last changed on 29-Nov-2024 16:16 by -jim

This page was created on 29-Nov-2024 16:16 by unknown

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
2 29-Nov-2024 16:16 7 KB -jim to previous
1 29-Nov-2024 16:16 7 KB unknown to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 2 changed one line
[{$pagename}] is a [Mobile-Digital Wallet] system.
[{$pagename}] is a [Mobile-Digital Wallet] and [Contactless Payment] system.
At line 8 changed one line
[{$pagename}] sends payment data to the contactless terminal when you Tap & Pay utilizing [NFC] and the [EMVCo’s Contactless suite of specifications|http://www.emvco.com/specifications.aspx?id=21 |target='_blank'] to communicate with the contactless reader terminal.
[{$pagename}] sends payment data to the contactless terminal when you Tap & Pay utilizing [NFC] and the [EMVCoS Contactless Suite of Specifications] to communicate with the [Contactless POS].
At line 10 changed one line
[{$pagename}] does not store the real card data inside the [Secure Element]. This is in direct contrast to [Google Wallet] and [Softcard]. [{$pagename}] stores a token that conforms to [EMVCo Tokenization] specification. This token (along with a cryptogram) that gets sent to the contactless terminal. [Apple] refers to the "Device Account Number" (PAN) as the EMVCo token in their documentation.[2]
[{$pagename}] does not store the real card data inside the [Secure Element]. [{$pagename}] stores a token that conforms to [EMVCo Tokenization] specification. This token (along with a cryptogram) that gets sent to [Contactless POS]. [Apple] refers to the "Device Account Number" (DAN) as the [EMVCo token|EMVCo Tokenization] in their documentation.[2]
At line 12 changed one line
During the authorization flow, the card network identifies the token, de-tokenizes them into real [PAN] with the help of a Token Service Provider (TSP) and sends the real [PAN] over to Issuer for authorization.
During the authorization flow, the card network identifies the [Payment Token] and converts them into [Primary Account Number] with the help of a [Token Service Provider] ([TSP]) and sends the real [PAN] over to [Card Issuer] for [authorization].
At line 14 changed one line
Since Apple owns and controls the [Secure Element] embedded inside the device thereby avoiding unnecessary challenges from the [MNO]s.
Since [Apple] owns and controls the [Secure Element] embedded inside the device thereby avoiding unnecessary challenges from the [Mobile Network Operators]. The [Secure Element] ([Secure Enclave]) is typically protected by [Touch ID] or [FACE] ID.
At line 17 changed one line
Each [{$pagename}] transaction is authenticated using [Touch ID] or the user’s passcode. The [Secure Enclave] manages the [Authentication] process and enables a payment transaction to proceed.
Each [{$pagename}] transaction is authenticated using [Touch ID] or the user’s passcode. The [Secure Enclave] manages the [Authentication] process and enables a [Payment Transaction] to proceed.
At line 19 removed 2 lines
As far as we can tell, other than the [Authentication] process, neither the [Secure Enclave] or [Touch ID] are involved in the [{$pagename}] process.
At line 26 changed one line
When a customer adds a [Payment Card] to their wallet, the [PAN] details are submitted to Apple Pay servers.
When a customer adds a [Payment Card] to their wallet, the [Primary Account Number] details are submitted to Apple Pay servers.
At line 28 changed one line
Apple Pay sends the information over to the corresponding [Issuer Bank|Card Issuer] asking for a [Payment Token] in return.
[{$pagename}] sends the information over to the corresponding [Issuer Bank|Card Issuer] asking for a [Payment Token] in return.
At line 30 changed one line
The [Issuer Bank|Card Issuer] calls a Token Service Provider (TSP) and requests for a [Payment Token]. As far as we know, the payment network themselves play the role of TSP at present.
The [Issuer Bank|Card Issuer] calls a [Token Service Provider] ([TSP]) and requests for a [Payment Token]. As far as we know, the [Payment Network] themselves play the role of TSP at present.
At line 36 changed one line
The [Issuer Bank|Card Issuer] returns the [Payment Token], [Payment Token-Key] and [CVV-Key] back to Apple Pay.
The [Issuer Bank|Card Issuer] returns the [Payment Token], [Payment Token-Key] and [CVV-Key] back to [{$pagename}].
At line 38 changed one line
Apple Pay, acting as its own [Trusted Service Manager] ([TSM]) provisions the [Payment Token], [Payment Token-Key] and [CVV-Key] and maybe other data into the [Secure Element]. This combination is the "Token" that Apple calls as "Device Account Number" [DAN] in its press releases.
[{$pagename}], acting as its own [Trusted Service Manager] ([TSM]) provisions the [Payment Token], [Payment Token-Key] and [CVV-Key] and maybe other data into the [Secure Element]. This combination is the "[Token|EMVCo Tokenization]" that [Apple] calls as "Device Account Number" [DAN] in its press releases.
At line 41 changed one line
When a customer taps or waves their iPhone in front of a point of sale terminal, a payment transaction is initiated.
When a customer taps or waves their iPhone in front of a [point of sale terminal|Contactless POS], a payment transaction is initiated.