Network-level user validation for network-based exchanges that leverages universally unique ephemeral key to eliminate use of persistent credentials
摘要
說明書
In the event that an object validation is not required for the object, the process 700 may return to step/operation 704 to identify another object from the exchange request. In some examples, the process 700 may return to step/operation 704 until each object from the exchange request is identified to determine whether each object is a restricted object. In this manner, the exchange platform may identify one or more restricted objects from the plurality of objects of the exchange request.
In the event that an object validation is required (e.g., the object is a restricted object, etc.), the process 700 may proceed to step/operation 708 of
In some embodiments, the process 700 includes, at step/operation 708, determining the validity of the restricted object. For example, the exchange platform may determine whether the restricted object is a validated object or an invalidated object based at least in part on a comparison between the one or more user attributes and an obtainment restriction for the restricted object. In some examples, the process 700 may return to step/operation 704 until each object from the exchange request is identified to determine whether each object is a validated or invalidated object. In this manner, the exchange platform may identify one or more validated objects and/or one or more invalidated objects for the exchange request.
