Network-level user validation for network-based exchanges that leverages universally unique ephemeral key to eliminate use of persistent credentials
摘要
說明書
In some examples, the one or more exchange-based attributes may include exchange-specific features. For instance, an exchange-based feature may include a source attribute that is descriptive of a location (e.g., retailer, brick and mortar store, healthcare center, informational source, etc.) from which an object is obtained (e.g., purchased, etc.) through a value-based exchange. The location, for example, may include a virtual and/or physical location. In some examples, the location may depend on the value system. For instance, in a financial value system, the source attribute may identify a retailer, a particular brick and mortar store of a retailer, an online platform, and/or the like. In a healthcare value system, the source attribute may be a virtual and/or physical medical center, and/or the like. In an information value system, the source attribute may be an informational source, and/or the like.
In some examples, a recorded data object and/or a count attribute may be source specific. For instance, a different recorded data object and/or count attribute may be maintained for each source from which an object may be obtained. In addition, or alternatively, a recorded data object and/or a count attribute may be source agnostic.
In some embodiments, the term “restricted object” refers to one or more different types of objects that may be associated with exchange criteria for obtaining through a value-based exchange. A restricted object, for example, may include an object that is subject to one or more obtainment restrictions.
In some embodiments, the term “obtainment restriction” refers to a data entity that defines one or more criteria for validating objects of a value-based exchange. An obtainment restriction may define one or more user-specific, location-specific, and/or other rules for validating a restricted object.
