Verifier - Revision history

Tom: /* References */

2025-06-03T16:07:01Z

‎References

Tom: /* Payment */

2025-05-30T23:09:15Z

‎Payment

Tom: /* Payment */

2025-05-30T23:08:54Z

‎Payment

Tom: /* Payment */

2025-05-30T23:07:57Z

‎Payment

Tom: /* Payment */

2025-05-30T23:07:05Z

‎Payment

Tom: /* Payment */

2025-05-30T23:06:21Z

‎Payment

Tom: /* Data Hoarders */

2025-05-30T23:05:37Z

‎Data Hoarders

Tom: /* Solutions */

2024-05-09T16:44:12Z

‎Solutions

Tom: /* Solutions */

2024-05-04T00:17:30Z

‎Solutions

Tom: /* Solutions */

2024-05-02T21:27:23Z

‎Solutions

← Older revision		Revision as of 16:07, 3 June 2025
Line 63:		Line 63:

	[[File: PolicyFLows.png]]		[[File: PolicyFLows.png]]
		+
		+	===Amazon===
		+	2025-05 Dock Labs recently had Paul Grassi (Principal Product Manager for Identity Services at Amazon) in our podcast and he mentioned that the ecommerce giant wants to move from verification to acceptance.
		+
		+	Traditionally, Amazon handled all the heavy lifting: scanning physical documents, running credit checks, and matching selfies to confirm a user’s identity. While effective, those steps create extra friction for customers and risk collecting more data than necessary.
		+
		+	Now, Amazon aims to accept digital ID credentials that have already been verified by trusted issuers (like state governments).
		+	Here’s why it’s a game-changer:
		+
		+	> Less Friction for Users: Fewer hurdles during sign-up or checkout, speeding up the purchase of restricted goods (e.g., alcohol or other age-gated items). No more scanning or uploading physical documents. Users simply tap to confirm their identity.
		+
		+	> Improved Privacy: Some Digital ID credentials allow for the use of selective disclosure and zero-knowledge proofs. Prove “Yes, I’m over 21” without handing over your full name and birth-date.
		+
		+	> A Push Towards Broader Industry Adoption: Large-scale acceptance accelerates adoption. Other companies, states, and issuers may follow suit when they see a global retailer leading the charge.
		+
		+	A key part of Amazon’s plan involves integrating mobile driver’s licenses (mDLs), digital versions of your standard license stored on a smartphone.
		+	Several states have already issued mDLs, while others are in various stages of testing or legislation. Despite the fragmented rollout, Amazon sees itself as a perfect fit for the acceptance model.
		+
		+	If Amazon successfully streamlines these technologies, it could reshape how we prove who we are for countless transactions.

	==References==		==References==

@@ Line 31: / Line 31: @@
 One of the biggest concerns from organizations when it comes to issuing digital ID credentials is this: "What's stopping someone else, even our competitors, from verifying the credentials we issue without paying for them?"
-This is what's known as the freeloader problem, and at Dock Labs, we're proud to say we've solved it. With our platform, organizations can issue and manage digital credentials with the confidence that unauthorized third parties won't exploit their work and data.
+This is what's known as the freeloader problem, and at Dock Labs, we're proud to say we've solved it. With our platform, organizations can issue and manage digital credentials with the confidence that unauthorized third parties won't exploit their work and data. Here's how it works:
 * Credential verification can be restricted to authorized ecosystem members, meaning only approved companies (typically the issuer's clients or partners) can verify the credentials.
 *  Membership is controlled by ecosystem administrators, who decide who gets access and under what conditions.

@@ Line 28: / Line 28: @@
 ===Payment===
 There is some discussion about whether the Verifier should pay for every verification. Since the Verifier also has to pay for the equipment that is needed, this might be a killer requirement.
-* 2925-05 Comments in favor of Verifier Pays
+* 2025-05 Comments in favor of Verifier Pays
 One of the biggest concerns from organizations when it comes to issuing digital ID credentials is this: "What's stopping someone else, even our competitors, from verifying the credentials we issue without paying for them?"

@@ Line 31: / Line 31: @@
 One of the biggest concerns from organizations when it comes to issuing digital ID credentials is this: "What's stopping someone else, even our competitors, from verifying the credentials we issue without paying for them?"
-This is what's known as the freeloader problem, and at Dock Labs, we're proud to say we've solved it.
+This is what's known as the freeloader problem, and at Dock Labs, we're proud to say we've solved it. With our platform, organizations can issue and manage digital credentials with the confidence that unauthorized third parties won't exploit their work and data.
 Here's how it works:
@@ Line 40: / Line 38: @@
 * Credential issuers can choose to charge for each verification, creating a clear path for monetization.
-In other words, if you want, credential verification can be gated by ecosystem membership and rules that you define.
+In other words, if you want, credential verification can be gated by ecosystem membership and rules that you define. This ecosystem approach offers a powerful safeguard: anyone trying to verify a credential must first prove they're part of the ecosystem.
 Without that access, they can't even tell whether a credential is valid or not.

@@ Line 36: / Line 36: @@
 Here's how it works:
+* Credential verification can be restricted to authorized ecosystem members, meaning only approved companies (typically the issuer's clients or partners) can verify the credentials.
-> Credential verification can be restricted to authorized ecosystem members, meaning only approved companies (typically the issuer's clients or partners) can verify the credentials.
+*  Membership is controlled by ecosystem administrators, who decide who gets access and under what conditions.
+* Credential issuers can choose to charge for each verification, creating a clear path for monetization.
 In other words, if you want, credential verification can be gated by ecosystem membership and rules that you define.

@@ Line 26: / Line 26: @@
 * Credit Agencies
 * Internal [[Government]] security Agencies, like the US DHS in "The DHS Bought a ‘Shocking Amount’ of Phone-Tracking Data"<ref>Ashley Belanger, ''The DHS Bought a ‘Shocking Amount’ of Phone-Tracking Data'' Wired (2022-07-28) https://www.wired.com/story/dhs-surveillance-phone-tracking-data/</ref><blockquote>FOR YEARS, PEOPLE have wondered not if, but how much, the Department of Homeland Security accesses mobile location data to monitor US citizens. The week of 2022-07-28, the American Civil Liberties Union released thousands of heavily redacted pages of documents that provide a “glimpse” of how DHS agencies came to leverage “a shocking amount” of location data, apparently purchasing data without following proper protocols to ensure they had the authority to do so.</blockquote>
 ==Solutions==

@@ Line 44: / Line 44: @@
 For this wiki we break the [[Verifier]] into two roles from SAML:
 # PDP = policy definition point may act as a [[Credential Aggregation]] process that accepts a collection of sources and produces a ticket for the holder that still needs to be bound to the person presenting the ticket.
-# PEP = policy enforcement point accepts sources of attributes and assures that they presenter is the holder. In some implementations the PEP can be installed in a native app on the device.
+# PEP = policy enforcement point accepts sources of attributes and assures that they presenter is the holder. In some implementations the PEP can be installed in a native app on the client-side device.
 [[File: PolicyFLows.png]]