Mobile Payment - Revision history

Tom: /* Compared Designs */

2025-09-23T04:18:05Z

‎Compared Designs

Tom: /* Compared Designs */

2025-09-23T04:15:50Z

‎Compared Designs

Tom: /* Compared Designs */

2025-09-23T04:14:51Z

‎Compared Designs

Tom: /* Compared Designs */

2025-09-23T04:07:53Z

‎Compared Designs

Tom: /* Compared Designs */

2025-09-23T03:57:05Z

‎Compared Designs

Tom: /* KARUNAKARA RAO KARNATI */

2025-09-23T03:55:49Z

‎KARUNAKARA RAO KARNATI

Tom: /* KARUNAKARA RAO KARNATI */

2025-09-23T03:54:53Z

‎KARUNAKARA RAO KARNATI

Tom: /* Compared Designs */

2025-09-23T00:55:25Z

‎Compared Designs

Tom: /* Compared Designs */

2025-09-23T00:43:10Z

‎Compared Designs

Tom: /* Payments on Google */

2025-05-25T18:56:14Z

‎Payments on Google

@@ Line 87: / Line 87: @@
 Apple Pay vs Google Pay: Security Comparison
-{|
+{|  border="1" padding="2" width="888px"
 |-
 |Feature || Apple Pay || Google Pay

@@ Line 103: / Line 103: @@
 |Known Vulnerabilities || Rare; e.g., Express Transit bug allowing payments on locked iPhones || Rare; e.g., bypassing unlock step in older Android builds
 |-
-|Security Philosophy	Hardware-first: Secure Enclave + local-only data	Software-first: Cloud flexibility + fraud detection via data analytics
+|Security Philosophy || Hardware-first: Secure Enclave + local-only data || Software-first: Cloud flexibility + fraud detection via data analytics
 |}

← Older revision		Revision as of 04:14, 23 September 2025
Line 85:		Line 85:

	* [https://undercodetesting.com/apple-pay-vs-google-pay-a-deep-dive-into-security-privacy-and-technical-implementation/ Apple Pay vs Google Pay: A Deep Dive into Security, Privacy, and Technical Implementation] August 17, 2025		* [https://undercodetesting.com/apple-pay-vs-google-pay-a-deep-dive-into-security-privacy-and-technical-implementation/ Apple Pay vs Google Pay: A Deep Dive into Security, Privacy, and Technical Implementation] August 17, 2025
		+
		+	Apple Pay vs Google Pay: Security Comparison
		+	{\|
		+	\|-
		+	\|Feature \|\| Apple Pay \|\| Google Pay
		+	\|-
		+	\|Card Data Storage \|\| Stored locally in a Secure Element chip on the device \|\| Stored on Google’s cloud servers in encrypted form
		+	\|-
		+	\|Tokenization \|\| Uses a Device Account Number (DAN) unique to your device \|\| Uses a Payment Token linked to your card info stored on Google servers
		+	\|-
		+	\|Biometric Authentication \|\| Required for every transaction (Face ID, Touch ID \|\| Also required (Fingerprint, Face Unlock), but implementation varies
		+	\|-
		+	\|Transmission Security \|\| Sends DAN during payment; real card number never leaves device \|\| Sends token during payment; real card number stored remotely
		+	\|-
		+	\|Privacy Model \|\| Apple does not track your purchases or store card data on servers \|\| Google may retain purchase history, device ID, and profile data
		+	\|-
		+	\|Known Vulnerabilities \|\| Rare; e.g., Express Transit bug allowing payments on locked iPhones \|\| Rare; e.g., bypassing unlock step in older Android builds
		+	\|-
		+	\|Security Philosophy Hardware-first: Secure Enclave + local-only data Software-first: Cloud flexibility + fraud detection via data analytics
		+	\|}
		+

	===KARUNAKARA RAO KARNATI===		===KARUNAKARA RAO KARNATI===

← Older revision		Revision as of 04:07, 23 September 2025
Line 83:		Line 83:

	==Compared Designs==		==Compared Designs==
		+
		+	* [https://undercodetesting.com/apple-pay-vs-google-pay-a-deep-dive-into-security-privacy-and-technical-implementation/ Apple Pay vs Google Pay: A Deep Dive into Security, Privacy, and Technical Implementation] August 17, 2025
		+
	===KARUNAKARA RAO KARNATI===		===KARUNAKARA RAO KARNATI===

@@ Line 100: / Line 100: @@
 . Store Info to Google Server – Unlike Apple, Google Pay sends card info to its cloud servers.
 . Payment Token Generated – Google creates a Payment Token that represents your card.
-. Token Sent to Merchant – When you pay, this token is sent to the ecommerce server (merchant).
+. Token Sent to Merchant – When you pay, this token is sent to the eCommerce server (merchant).
 . Token Passed to Bank – The token is validated against the real card info stored in Google’s servers.
 . Bank Approves – The bank checks the actual card info and approves the transaction.
@@ Line 106: / Line 106: @@
 Important Point: Google Pay relies on cloud tokenization, meaning your card info is stored on Google’s servers in the encrypted format.
-* Apple Pay vs Google Pay Main Difference ####
+* Apple Pay vs Google Pay Main Difference
 ** Apple Pay: Card info never leaves your device → stays safe inside a secure chip.
 ** Google Pay: Card info goes to Google’s servers → secure but involves a third party storing your card data.

@@ Line 87: / Line 87: @@
 Apple Pay vs Google Pay Security
-* Apple Pay Security-#
+* Apple Pay Security
 . Credit Card Info – You first add your card details into Apple Wallet.
 . Pass Credit Card Info – The info is securely sent to the bank for verification.
 . Store to Chip. – Apple Pay doesn’t store your real card number. Instead, it creates a Device Account Number (DAN) stored in the phone’s secure chip.
 . DAN Used in Transactions – When you pay, Apple Pay sends this DAN instead of your actual card number.
 . Bank Validates – The bank processes the DAN and approves the transaction.
-Important Point:
+* Google Pay Security
 . Credit Card Info – You add your card into Google Pay.
 . Store Info to Google Server – Unlike Apple, Google Pay sends card info to its cloud servers.
@@ Line 113: / Line 109: @@
 ** Apple Pay: Card info never leaves your device → stays safe inside a secure chip.
 ** Google Pay: Card info goes to Google’s servers → secure but involves a third party storing your card data.
 ===Byte Byte Go===

← Older revision		Revision as of 00:43, 23 September 2025
Line 83:		Line 83:

	==Compared Designs==		==Compared Designs==
		+	===KARUNAKARA RAO KARNATI===
		+
		+	Apple Pay vs Google Pay Security
		+
		+	Apple Pay Security-#
		+	1. Credit Card Info – You first add your card details into Apple Wallet.
		+	2. Pass Credit Card Info – The info is securely sent to the bank for verification.
		+	3. Store to Chip.
		+
		+	– Apple Pay doesn’t store your real card number. Instead, it creates a Device Account Number (DAN) stored in the phone’s secure chip.
		+
		+	4. DAN Used in Transactions – When you pay, Apple Pay sends this DAN instead of your actual card number.
		+
		+	5. Bank Validates – The bank processes the DAN and approves the transaction.
		+
		+
		+	Important Point:
		+	Apple never stores your card number on its servers. The sensitive data stays only on your device in the secure chip.
		+
		+	# Google Pay Security #
		+	1. Credit Card Info – You add your card into Google Pay.
		+	2. Store Info to Google Server – Unlike Apple, Google Pay sends card info to its cloud servers.
		+	3. Payment Token Generated – Google creates a Payment Token that represents your card.
		+	4. Token Sent to Merchant – When you pay, this token is sent to the ecommerce server (merchant).
		+	5. Token Passed to Bank – The token is validated against the real card info stored in Google’s servers.
		+	6. Bank Approves – The bank checks the actual card info and approves the transaction.
		+
		+	Important Point: Google Pay relies on cloud tokenization, meaning your card info is stored on Google’s servers in the encrypted format.
		+
		+
		+	#### Apple Pay vs Google Pay Main Difference ####
		+	• Apple Pay: Card info never leaves your device → stays safe inside a secure chip.
		+
		+	• Google Pay: Card info goes to Google’s servers → secure but involves a third party storing your card data.
		+
		+
		+	===Byte Byte Go===

	[[File:Apple google pay.jpg]]		[[File:Apple google pay.jpg]]

@@ Line 24: / Line 24: @@
 ==Payments on Google==
 * [https://www.customerfutures.com/p/visas-new-pathway-to-empowerment Visa's new pathway to Empowerment Tech, and is Google Wallet the next Google Maps?]
 ==Compared Designs==