Digital ticket system and method
By generating and retrieving assertions associated with the target entity with the resource provider, the user privacy and transaction verification issues are solved, and the secure and efficient completion of transactions associated with the resource provider is achieved.
Patent Information
- Application Number
- CN201980061311.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2018-09-20
- Filing Date
- 2019-09-20
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2039-09-20
AI Technical Summary
The prior art is difficult to effectively track and verify whether a user is evaluating goods or services in the physical store of the resource provider, especially due to privacy issues, electronic device tracking methods are not ideal.
Receive assertion requests associated with the resource provider by the target entity through the server computer, generate assertions including the identity attributes of the target entity, retrieve the identity attributes based on the assertion model and domain restrictions, and transmit tickets to the dependent entity computer for completing the transaction.
It enables verification and completion of transactions associated with resource providers, such as issuance and use of digital coupons, ensuring the security and efficiency of transactions without infringing on user privacy.
Smart Images

Figure CN112740249B_ABST
Abstract
Description
[0001] Cross-reference to related applications
[0002] This application claims the benefit of U.S. Provisional Application No. 62 / 733,868, filed September 20, 2018, which is incorporated herein by reference. Background Art
[0003] In some cases, it is difficult to know whether a particular person is using a resource provider's physical store to evaluate goods or services, but is simply purchasing goods or services online or otherwise at a different resource provider. While it is possible to track the location of a particular user's activities through electronic tracking or other means, this approach is not ideal due to privacy issues.
[0004] Embodiments of the invention address these and other problems individually and collectively. Summary of the invention
[0005] One embodiment of the present disclosure relates to a method, comprising: receiving, by a server computer, a first request from a target entity computer to form an assertion of a target entity and a resource provider associated with the target entity computer, the assertion comprising an identity of the target entity and a location of the resource provider, the first request being generated in response to an interaction of the target entity computer with a digital indicator associated with the resource provider; generating, by the server computer, the assertion comprising identity attributes of the target entity based at least in part on the first request, the identity attributes comprising the identity of the target entity and the interaction of the target entity computer with the digital indicator associated with the resource provider; receiving, by the server computer, the assertion from a dependent entity computer, the assertion comprising an identity attribute of the target entity, the identity attribute comprising the identity of the target entity and the interaction of the target entity computer with the digital indicator associated with the resource provider; receiving a second request for the identity attribute associated with the target entity to conduct a transaction associated with a dependent entity associated with the dependent entity computer and the target entity, the second request comprising: a first identifier of the dependent entity; a second identifier associated with the target entity; and an item identifier of an item associated with the transaction; in response to receiving the second request, determining, by the server computer, an assertion model based at least in part on the first identifier and the second identifier; retrieving, by the server computer, the identity attribute based at least in part on the assertion model and one or more domain restrictions on the assertion; and transmitting, by the server computer, a ticket to the dependent entity computer based at least in part on the retrieval of the identity attribute.
[0006] In an embodiment, the ticket is used by the relying entity to complete the transaction. The ticket may include a digital coupon for the item. In an embodiment, the one or more domain restrictions include at least one of: prohibiting the ticket from being used for a specific resource provider, prohibiting the ticket from being used for the specific resource provider and a specific item, limiting the use of the ticket to one or more resource providers specified by an entity, or limiting the use of the ticket to a specific time period. In an embodiment, the method further includes transmitting, by the server computer, a notification of the asserted use to a resource provider computer associated with the resource provider in response to receiving the ticket from the relying computer.
[0007] In an embodiment, the notification includes the resource provider, the location of the resource provider, the item identifier, and the identity of the target entity. In an embodiment, the method further includes transmitting, by the server computer to the relying entity computer, a payment token corresponding to a discount on the item in the transaction in response to receiving the ticket from the relying entity computer. In an embodiment, the second identifier associated with the target entity is maintained by an application of the target entity computer and provided in the second request. In an embodiment, the method further includes transmitting, by the server computer to the target entity computer, a notification of the generation of the assertion identifying the resource provider. In an embodiment, another entity is prohibited from utilizing the assertion.
[0008] Another embodiment of the present disclosure is directed to a computer system, comprising: a processor; and a memory element, which includes instructions that, when executed with the processor, cause the system to perform the method described above.
[0009] In an embodiment, the digital indicator comprises a quick response (QR) code. In an embodiment, the computer system implements an assertion model manager. In an embodiment, the assertion model manager receives the first request and the second request using an application programming interface (API). In an embodiment, the second identifier associated with the target entity comprises the identity of the target entity. In an embodiment, the one or more domain restrictions are specified by the resource provider. In an embodiment, the location of the resource provider comprises a geographic location of the resource provider. In an embodiment, the second identifier associated with the target entity is maintained by an application of the target entity computer and provided in the second request. In an embodiment, the identity attribute is retrieved from a digital identity provider.
[0010] Another embodiment of the present disclosure is directed to a non-transitory computer-readable storage medium having stored thereon instructions which, when executed by a computer system, cause the computer system to perform the method described above. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] Figure 1 is a schematic diagram of a system for providing at least one assertion according to an embodiment;
[0012] Figure 2 is a flow chart of a method of providing at least one assertion according to an embodiment;
[0013] Figure 3 is a flow chart of a method of providing at least one assertion according to an embodiment;
[0014] Figure 4 is a flow chart of a method of providing at least one assertion including a digital coupon according to an embodiment; and
[0015] Figure 5 is a flowchart of a workflow for providing at least one assertion including a digital coupon, according to an embodiment. DETAILED DESCRIPTION
[0016] An "issuing institution," "portable financial device issuer," "issuer," or "issuing bank" may include one or more entities that provide accounts to customers for transactions (e.g., payment transactions), such as initiating credit and / or debit payments. For example, an issuing institution may provide customers with account identifiers, such as a personal account number (PAN), that uniquely identify one or more accounts associated with the customer. The account identifier may be embodied on a portable financial device, such as a physical financial instrument (e.g., a payment card), and / or may be electronic and used for electronic payments. In some embodiments, the issuing institution may be associated with a bank identification number (BIN) that uniquely identifies the issuing institution. An "issuing institution system" may include one or more computer systems operated by or on behalf of the issuing institution, such as a server executing one or more software applications. For example, an issuing institution system may include one or more authorization servers for authorizing transactions.
[0017] An "account identifier" may include one or more types of identifiers associated with a user account (e.g., an account identifier, PAN, card number, payment card number, account token, etc.). In some embodiments, an issuing institution may provide a user with an account identifier (e.g., PAN, account token, etc.) that uniquely identifies one or more accounts associated with the user. An account identifier may be embodied on a physical financial instrument (e.g., a portable financial instrument, a payment card, a credit card, a debit card, etc.), and / or may be electronic information transmitted to a user so that the user can use it for electronic payments. In some embodiments, an account identifier may be an original account identifier, where the original account identifier is provided to the user when the account associated with the account identifier is created. In some embodiments, an account identifier may be an account identifier provided to the user after the original account identifier is provided to the user (e.g., a supplemental account identifier). An account identifier may be any combination of alphanumeric characters, characters, and / or symbols, etc.
[0018] An "account token" may include an identifier used as a replacement or substitute identifier for an account identifier such as a PAN. An account token may be used as a replacement or substitute identifier for an original account identifier such as a PAN. An account token may be associated with a PAN or other original account identifier in one or more data structures (e.g., one or more databases, etc.) so that the account token can be used to conduct transactions without directly using the original account identifier. In some embodiments, an original account identifier such as a PAN may be associated with multiple account tokens for different individuals or purposes. In some embodiments, an account token may be associated with a PAN or other account identifier in one or more data structures so that the account token can be used to conduct transactions without directly using an account identifier such as a PAN. In some instances, an account identifier such as a PAN may be associated with multiple account tokens for different uses or purposes.
[0019] A "resource provider" may include one or more entities (e.g., an operator of a retail business) that provides goods and / or services and / or access to goods and / or services to users (e.g., clients, customers, etc.) based on transactions, such as payment transactions. A "resource provider computer" may include one or more computer systems operated by or on behalf of a resource provider, such as a server executing one or more software applications.
[0020] A "product" may include one or more goods and / or services provided by a resource provider. Examples of resource providers may include merchants.
[0021] A "transaction service provider" may include an entity that receives transaction authorization requests from merchants or other entities and, in some cases, provides payment assurance through an agreement between the transaction service provider and the issuer organization. For example, a transaction service provider may include a payment network, such as or any other entity that processes transactions. As used herein, a "transaction service provider system" may include one or more computer systems operated by or on behalf of a transaction service provider, such as a transaction service provider system that executes one or more software applications. A transaction service provider system may include one or more processors and, in some embodiments, may be operated by or on behalf of a transaction service provider.
[0022] "Client" and "client device" may include devices that can communicate with a server computer. As an example, a "client device" may include one or more POS devices and / or POS systems used by a merchant. It should be understood that a client device may be any electronic device configured to communicate with one or more networks and initiate or facilitate transactions, such as but not limited to one or more computers, portable computers, tablet computers, cellular phones, wearable devices (e.g., watches, glasses, lenses, clothing, etc.), PDAs, and / or other similar devices.
[0023] A "server" may include one or more computing devices, such as processors, storage devices, and / or similar computer components, that communicate with client devices and / or other computing devices over a network, such as the Internet or a private network.
[0024] An "identifier" may include any information that can be used to identify something. In some embodiments, an identifier may be a special value that is randomly generated or generated according to a predetermined algorithm, code, or shared secret. For example, a driver's license number or a cryptographic key may be used to identify an individual. In some embodiments, an identifier may be in the form of one or more graphics, tokens, bar codes, quick response (QR) codes, or any other information that can be used to uniquely identify an entity. In some embodiments, an identifier may be in the form of an alphanumeric string corresponding to a user's name or a resource provider's name.
[0025] An "identity attribute" may include a specific piece of information about an entity (e.g., a person, organization, thing, etc.) Examples of identity attributes include name or other unique identifier associated with a person, social security number, age, phone number, and bank account number.
[0026] A "digital identity" (DI) may include a secure set of information about an entity (e.g., a person, organization, or thing). A DI may include multiple identity attributes, as well as a digital identity identifier that identifies the digital identity. For example, a DI for a user, Joe Smith, may include: identity attributes, such as the user's date of birth, social security number, address, and driver's license number; and an identifier, such as Joe_Smith_1234, that identifies Joe Smith's digital identity or corresponds to an identity of a user such as Joe Smith. The DI may be made available to another entity in a secure manner. A DI may rely on agreements between stakeholders and security measures such as passwords.
[0027] An "assertion" (sometimes called an "assertion value") may include security facts about an entity. Assertions may protect information while being useful in achieving a particular goal. For example, an assertion may specify something about an entity, such as whether the entity should be allowed to purchase alcohol at a particular location. An assertion may be "Jane Doe is old enough to purchase alcohol in California." A bar may use this assertion to decide to serve alcohol to a person without having to show the bar the person's driver's license information. As another example, an assertion may specify whether an entity has an account that can accept deposits (e.g., "Jane Doe has a bank account and can accept deposits."). As another example, an assertion may specify whether an entity has interacted with a digital indicator associated with a resource provider. An assertion may be "Jane Doe has used a mobile phone to scan a QR code provided by a resource provider."
[0028] An "assertion type" can be an assertion category, such as whether an entity has at least $100 in its bank account. An "assertion" or "assertion value" associated with an assertion type can be a corresponding answer to a specific entity, which can be in the form of "yes" or "no", or can be an affirmative statement (e.g., "Jane Doe has $100 or more in her bank account," or "Jane Doe has interacted with a digital indicator provided by a resource provider"). Assertions can be cryptographically protected. Assertions can be digitally signed by an entity of interest and / or a trusted party providing a security fact.
[0029] An "assertion model" may be a set of assertion types that may be associated with a particular entity. An assertion model may specify one or more assertion types. For example, an assertion model may include two assertion types: whether the entity is old enough to rent a car, and whether the entity has a valid driver's license. An assertion model may be tailored for a particular situation. Continuing with the previous example, whether the entity is old enough to rent a car and whether the entity has a valid driver's license may correspond to an assertion model for the context of a potential car renter interacting with a car rental agency. An assertion model may further specify a set of identity attributes. As another example, an assertion model may include a single assertion type, such as "Did the entity interact with a digital indicator provided by a resource provider?" An assertion model may be used in the context of issuing a digital coupon on behalf of an entity for subsequent transactions, which transactions are conducted in response to the entity interacting with a digital indicator provided by a resource provider.
[0030] "Target entity" may include entities corresponding to assertions, DIs and / or identity attributes. For example, the target entity may be Mary Jones. The assertion about Mary Jones may specify whether Mary Jones is old enough to purchase alcohol at a particular location. The relevant identity attribute of Mary Jones may be the exact age of Mary Jones (e.g., 35 years old). To continue the example, the assertion about Mary Jones may be that she interacts with a digital indicator provided by a resource provider at a particular location. The relevant identity attribute of Mary Jones may be an identifier of Mary Jones (e.g., name or other identifiers such as Mary_Jones_1234). As used herein, "target entity computer" may refer to one or more computer systems operated by or on behalf of a target entity, such as a mobile computer device executing one or more software applications. The target entity may be referred to as a user, and the target entity computer may be referred to as a user device.
[0031] A "relying entity" may include an entity that may receive assertions, DIs, and / or identity attributes. For example, a relying entity may be a bar that requests an assertion as to whether the target entity is old enough to serve him alcohol. In some embodiments, a relying entity may be a resource provider or a merchant. A "relying entity computer" may include one or more computer systems operated by or on behalf of a relying entity (e.g., a resource provider).
[0032] A "ticket" may include an element that entitles the holder to obtain an item such as a discount or value. In some embodiments, a ticket may include an element for accessing a digital coupon or prepaid card for use in a payment and settlement process to complete a transaction with a resource provider. A ticket may represent a digital coupon or prepaid card issued to a particular target entity to complete a transaction with a relying entity such as a resource provider in response to the target entity interacting with a digital indicator provided by a resource provider (which may be the same or a different resource provider). In embodiments, the ticket may be transmitted by the relying entity to a payment processing network to receive a monetary payment to complete the transaction.
[0033] A "key" may include a piece of information used in a cryptographic algorithm to transform input data into another representation. A cryptographic algorithm may be an encryption algorithm that transforms original data into an alternative representation, or a decryption algorithm that transforms encrypted information back into the original data. Examples of cryptographic algorithms may include Triple Data Encryption Standard (TDES), Data Encryption Standard (DES), Advanced Encryption Standard (AES), etc.
[0034] Embodiments of the present invention may include systems, methods, and computer program products for providing at least one assertion about an entity, including whether the entity is eligible to obtain any relevant instruments to complete a transaction with a relying entity.
[0035] Reference now Figure 1 , a schematic diagram of an example system and method 100 for providing at least one assertion according to an embodiment is shown. The system 100 may include at least one digital identity (DI) provider 121. For example, the DI provider may be an issuer, an acquirer, a transaction service provider, a government agency, etc. that is capable of creating and storing DIs. The DI provider 121 may communicate with at least one entity 111 to create and store DIs associated with the entity 111, as described herein. The entity 111 may include a user 111a and / or a client device 111b of the entity. As used herein, the term "entity" may include an individual (e.g., a client, a customer, etc.), a business or other legal organization, a government agency, etc. Additionally or alternatively, the term "entity" may include a thing (e.g., an object, a piece of equipment, an electronic component, a computer system, etc.). The entity 111 may include a target entity.
[0036] In some embodiments, the DI providers 121 and / or entities 111 may communicate with an assertion model manager 131. For example, communication with the assertion model manager 131 may be direct, indirect, over a network such as the Internet, and / or through an application programming interface (API), as described herein. The assertion model manager 131 may maintain and store (e.g., in a database, etc.) assertion models for making assertions about entities 111. For example, each assertion model may be standardized and / or typical so that information about different entities 111 from various DI providers 121 may be organized into assertion sets that are consistent regardless of the DI provider 121 or the source of the information, as described herein. Additionally or alternatively, each assertion model may be based on a domain in which the assertion model is expected to be used or the type of dependent entity 161 requesting an assertion about an entity, as described herein. In an embodiment, the assertion model manager 131 may be implemented by a server computer.
[0037] In some embodiments, the assertion model manager 131 may include and / or communicate with the assertion ledger 141 and / or event log 151. The assertion ledger 141 and event log 151 may each be stored in any suitable computer-readable storage medium and / or any suitable combination of computer-readable storage media. For example, the assertion ledger 141 and / or event log 151 may be stored in a database. Additionally or alternatively, the assertion ledger 141 and / or event log 151 may be maintained and stored in a distributed ledger, including but not limited to a blockchain, etc. For purposes of illustration and not limitation, reference is made to Figure 1 , the assertion ledger 141 is depicted as a distributed ledger, and the event log 151 is depicted as a database.
[0038] In some embodiments, the assertion model manager 131 may communicate with a dependent entity 161. For example, communication with the assertion model manager 131 may be direct, indirect, over a network such as the Internet, and / or through an API, as described herein. A dependent entity 161 may be any entity that requests information (e.g., assertions) about an entity 111, as described herein. For example, a dependent entity 161 may be a resource provider that requests information (e.g., assertions) about an entity 111, which entity is referred to as a customer of a merchant in connection with a payment transaction. Additionally or alternatively, a dependent entity 161 may be an entity (e.g., a government agency or a business organization) that requests information (e.g., assertions) about an entity 111 in connection with a non-payment interaction (e.g., granting the entity 111 access to a secure area or event venue).
[0039] Reference now Figure 2 , a flowchart of a method 200 for providing at least one assertion according to an embodiment is shown. Figure 1 The exemplary system 100 may be referred to as Figure 2 . At 210, an assertion model may be received or retrieved. For example, the assertion model manager 131 may retrieve or obtain data associated with the assertion model from a database. Additionally or alternatively, the assertion model manager 131 may retrieve data associated with the assertion model from an external data storage device over a network, the external data storage device including, but not limited to, a database, a distributed ledger, a blockchain, etc. For purposes of illustration and not limitation, the assertion model may be a standardized and / or typical assertion model of a relevant domain, which may be determined based on the entity 111 that will make the assertion, the DI provider 121 from which DI data will be obtained for the assertion, and / or the dependent entity 161 requesting the assertion. For example, before retrieving or receiving the assertion model, the assertion model manager 131 may receive data associated with an identifier of the entity 111, the DI provider 121, and / or the dependent entity 161, and determine the relevant domain / assertion model based on the received identifier. In some embodiments, the identifier may include data associated with a digital signature and / or cryptographic key of entity 111 , DI provider 121 , and / or relying entity 161 .
[0040] In some embodiments, the assertion model may include at least one assertion type. For example, the assertion model may include a set of assertion types sufficient to be considered "well-formed" for the relevant domain. Additionally or alternatively, the assertion model may include data associated with additional identification, including but not limited to the name / identifier and current version number of the assertion model, and the date the assertion model was last updated.
[0041] For each assertion type of the assertion model, at 220, an identity attribute type corresponding to the assertion type may be determined. For example, the assertion model manager 131 may determine which identity attribute type(s) available from the DI provider 121 correspond to each assertion type in the assertion model. For example, if the dependent entity 161 is a merchant that rents cars, one of the assertion types in the assertion model is whether the entity 111 is old enough to rent a car in the country where the dependent entity 161 is located, and the identity attribute type available from the DI provider 121 is the date of birth of the entity 111, then the assertion model manager 131 may determine that the date of birth identity attribute type corresponds to such an assertion type. For example, if the dependent entity 161 is a resource provider or merchant that inquires about the eligibility of a digital coupon on behalf of the entity 111, then the assertion model manager 131 may determine that the identity attribute type of the entity 111's interaction with the digital indicator associated with the resource provider corresponds to such an assertion type. In other words, the assertion model may include assertion types such as "Did the target entity interact with the digital indicator at the resource provider A?" An assertion associated with this assertion type might be "target entity B interacts with a digital indicator at resource provider A."
[0042] For each assertion type of the assertion model, at 230, the source of identity attribute data corresponding to the identity attribute type may be determined. For example, the assertion model may further include a list of valid information sources for the assertion type contained therein. Additionally or alternatively, a list of valid information sources associated with one or more assertion models may be maintained and stored, as described herein. For purposes of illustration and not limitation, referring to the exemplary case of asserting whether the entity 111 is old enough to rent a car as described above, a list of valid sources for date of birth information may include government documents (e.g., driver's license, birth certificate, passport, etc.), government databases, corporate organization records (e.g., of an issuer, transaction service provider, etc.), and the like. Additionally or alternatively, a verification method for verifying the identity attribute type may be included in the list of valid sources and / or communicated by the DI provider 121. For example, the verification method may include checking documents by the DI provider 121, verification by a corporate organization (e.g., a third-party service), and / or verification by a government agency.
[0043] For each assertion type of the assertion model, at 240, identity attribute data associated with the entity corresponding to the identity attribute type may be obtained. For example, the assertion model manager 131 may communicate with the DI provider 121 to obtain identity attribute data associated with the entity 111 corresponding to the identity attribute type in the assertion model. The DI provider 121 may provide identity attribute data, which may include data associated with the entity 111 corresponding to the identity attribute type and / or additional data associated with the identity attribute type, including but not limited to the source of the data, as described herein. For example, referring to the exemplary case of asserting whether the entity 111 is old enough to rent a car as described above, the identity attribute data associated with the date of birth may be a numerical representation of the date of birth of the entity 111, a bit or bit string indicating whether the entity is above a certain age threshold (e.g., the minimum age for renting a car) or is in a certain age category (e.g., under 18, between 18 and 25, over 25), etc. In addition, the identity attribute data may include the source of the date of birth data (e.g., a visual inspection of the driver's license by the DI provider 121). In an embodiment, the assertion model manager 131 may retrieve or otherwise obtain the identity attributes without communicating with the DI provider 121. In the context of a target entity interacting with a digital indicator at a resource provider, the identity attribute data may be a data representation of the interaction between the target entity's computer and the digital indicator at the resource provider (e.g., a data file of a QR code picture, a data logo, etc.).
[0044] For each assertion type of the assertion model, at 250, an assertion value corresponding to the assertion type may be calculated based on identity attribute data associated with the entity. For example, the assertion model manager 131 may calculate the assertion value based on data provided by the DI provider 121. For example, referring to the exemplary case of asserting whether the entity 111 is old enough to rent a car as described above, the value of the assertion of whether the entity 111 is old enough to rent a car may be calculated based on the date of birth information provided by the DI provider 121 using the following algorithm:
[0045] {“OfAgeToRentAutoInUSA”::=“Yes”, if “Current Date” - “Verified Date of Birth” ≥ 25 years old, otherwise “No”}
[0046] Where "OfAgeToRentAutoInUSA" is an assertion of whether the entity 111 is old enough to rent a car in the United States, "Yes" is a value if the entity 111 is old enough, "No" is a value if the entity 111 is not old enough, "Current Date" is the date on which the calculation is performed, and "Verified Date of Birth" is the date of birth of the entity 111 provided by the DI provider 121 after verifying the source of the data. In addition or alternatively, an expiration date for the assertion may also be determined, or the expiration date may be omitted if the assertion will not expire, or the expiration data may have a null value, a "none" value, a 0 value, etc. In the context of a target entity interacting with a digital indicator at a resource provider, identity attribute data, such as a data representation of the interaction between the target entity's computer and the digital indicator at the resource provider (e.g., a data file of a QR code picture, a data flag, etc.), may be used to calculate or determine an assertion value, such as "Yes", the target entity interacted with the digital indicator, or "No", the target entity did not interact with the digital indicator. The value may depend on whether there is data representing the interaction.
[0047] For each assertion type of the assertion model or for a complete set of assertions, at 260, a strength / confidence score associated with the assertion value can be calculated based on the source of the identity attribute data. For example, the confidence score can be calculated based on a series of valid sources. Additionally or alternatively, the confidence score can be calculated based on a standardized or typical method for calculating strength. For example, the confidence score can be calculated according to NIST Special Publication 800-63A, Digital Identity Guidelines: Enrollment and Identity Proofing Requirements, U.S. Department of Commerce (updated November 15, 2017), which can be used to calculate the technology described in https: / / doi.org / 10.6028 / NIST.SP.800-63a, the entire text of which is hereby incorporated herein.
[0048] For each assertion type of the assertion model, at 265, an assertion can be created. Each assertion can include an assertion value and / or additional data associated with the assertion value, including but not limited to the name of the assertion, the strength / confidence score of the assertion, the expiration date of the assertion, etc. In addition, the assertion can be added to a temporary assertion set stored when the complete assertion set corresponding to the assertion model is completed. In an embodiment, the assertion can be generated and associated with an identifier of the entity 111, so that recall of the assertion associated with the entity 111 can be mapped by the identifier. In the context of the target entity interacting with a digital indicator at a resource provider, an assertion "Yes, the target entity interacted with the digital indicator" or "No, the target entity did not interact with the digital indicator" can be created.
[0049] For each assertion type of the assertion model, at 270, it can be determined whether there are remaining assertion types in the assertion model for which assertions have not yet been created. If there is at least one remaining assertion type, the next assertion type can be selected and the process can be repeated starting from 220.
[0050] At 280, assertion data associated with the assertion set may be transmitted. The assertion set may include assertions (e.g., assertion values) corresponding to each assertion type of the assertion model. For example, the assertion data associated with the assertion set may be communicated from the assertion model manager 131 to the dependent entity 161. Additionally or alternatively, the assertion model manager 131 may write the assertion data associated with the assertion set to the assertion ledger 141. For example, the assertion ledger 141 may be a distributed correspondence including a blockchain. Additionally or alternatively, the assertion data associated with the assertion set may be transmitted / written using at least one of the digital signature / cryptographic keys of the entity 111 or the DI provider 121. For example, the assertion data may be written to the distributed ledger using the cryptographic keys of the entity 111 and the DI provider 121 across all assertions.
[0051] At 290, the event log may be updated. For example, the assertion model manager 131 may generate an event in the event log 151, and the event may be associated with the transmission of the assertion set. Illustratively, the data associated with the event in the event log 151 may include an event type (e.g., from a series of standardized and / or typical assertion updates), an event value (e.g., associated with an event type in a series of standardized and / or typical assertion updates), an event date / time, an identifier of the entity 111 (e.g., a cryptographic key of the entity 111), an identifier of the DI provider 121 (e.g., a cryptographic key of the DI provider 121), an identifier of the dependent entity 161 (e.g., a cryptographic key of the DI provider 121), an identifier of a third-party service provider or technology provider (if any), etc. In an embodiment, the entity 111 may provide at least one identity attribute data source 111c to the assertion model manager 131. The assertion model manager 131 may verify the identity attribute data source 111c, and if valid, create a DI for the entity 111 to be stored in a database or event log 151. Additionally or alternatively, the assertion model manager 131 may transmit a ticket to the relying entity 161 that confirms the identity of the identity attribute queried on behalf of the entity 111 to complete a transaction as described herein.
[0052] Reference now Figure 3 , a flowchart of a method 300 for providing at least one assertion according to an embodiment is shown. Figure 1 The exemplary system 100 may be referred to as Figure 3 An exemplary method 300 of Figure 3 The method 300 may be combined with Figure 2The method 200 of , concurrently with, before, after, or as an alternative to the method 200. At 310, a request for an assertion may be received. For example, the assertion model manager 131 may receive a request for an assertion from the dependent entity 161. For example, the request may include first identification data identifying the dependent entity 161 (e.g., a cryptographic key of the dependent entity 161), second identification data identifying the dependent entity 111 (e.g., a cryptographic key of the entity 111), entity type data identifying an entity type associated with the dependent entity 161 (e.g., a merchant category code (MCC) or the like), and assertion request data associated with at least a subset of the assertion types in the assertion model. Additionally or alternatively, prior to communicating the request for the assertion, the dependent entity 161 may present its identifier (e.g., the cryptographic key of the dependent entity 161) and / or its entity type (e.g., MCC) to the assertion model manager 131, and the assertion model manager 131 may communicate the set of assertions that the dependent entity 161 request is granted, for example, based on the entity type of the dependent entity, etc. Such communications used to determine the set of assertions to grant requests from dependent entity 161 may also be logged in event log 151 (e.g., assertion model manager 131 may update the event log as described herein). For example, referring to the example of an assertion type of whether entity 111 is old enough to rent a car as described above, dependent entity 161 may be permitted to request information regarding whether entity 111 is old enough to rent a car, has a valid driver's license, has a valid payment token, etc. Illustratively, if dependent entity 161 is a bar / restaurant, the dependent entity may be permitted to request whether entity 111 is old enough to purchase alcohol, has a valid payment token, etc.
[0053] At 320, it may be determined whether the request is valid. For example, the assertion model manager 131 may verify first identification data identifying the dependent entity 161, entity type data identifying an entity type associated with the dependent entity 161, and a subset of assertion types in the assertion model. For example, the assertion model manager 131 may confirm that the entity type matches a predetermined entity type associated with the first identification data identifying the dependent entity 161. Additionally or alternatively, the assertion model manager 131 may confirm that a subset of assertions requested by the dependent entity 161 is permitted based on the entity type. Additionally or alternatively, the assertion model manager 131 may determine a strength / confidence score associated with the identification data of the dependent entity 161. If the request is invalid, the process may end. Additionally or alternatively, a notification may be sent to the relying party 161, including information about why the request is invalid. The assertion model manager 131 may verify the first identification data identifying the dependent entity 161 to confirm approval of the dependent entity 161 request for the assertion of the entity 111.
[0054] At 330, if the request from the dependent entity is valid, a notification may be transmitted to the entity. In some embodiments, the notification may include data identifying the dependent entity 161, the entity type of the dependent entity 161, the subset of assertion types requested, the strength / confidence score associated with the dependent entity 161, etc. At 340, it may be determined whether the entity 111 approves the request. In some embodiments, the entity 111 may transmit, in accordance with the request, a confirmation that the assertion model manager 131 is approved to transmit response data associated with the subset of the assertion set to the dependent entity 161, and the assertion model manager 131 may receive the confirmation from the entity 111.
[0055] At 380, assertion data associated with the assertion set may be transmitted. For example, the assertion data may be similar to that described above with reference to Figure 2 Transmitted as described at 280 .
[0056] At 390, the event log may be updated. For example, the event log may be updated similar to that described above with reference to Figure 2 The event log is updated as described at 290. Additionally or alternatively, the event generated in the event log can be associated with the request for the assertion subset, which can be the same event, or a different event than the event associated with the assertion transmission. Upon receiving the assertion subset, the relying entity 161 can determine whether to proceed with the interaction (e.g., payment transaction and / or non-payment interaction).
[0057] Figure 4 is a flow chart of a method of providing at least one assertion including a digital coupon according to an embodiment. Figure 4 exist Figure 1 The system 100 is best understood in the context of the example system 100 shown in FIG. 1 , which in some embodiments may be adapted to provide assertions related to digital coupons provided for items in a transaction. Figure 4, entity 111 may be referred to as a target entity. The assertion may be based on the target entity being associated with an identity or account of the target entity, the event utilizing an associated target entity computer to interact with a digital indicator associated with or provided by a resource provider for an item provided by a resource provider. In an embodiment, the digital indicator may include an object that may be scanned, read, communicated, or otherwise interacted with by a target entity computer. Examples of digital indicators may include a quick response (QR) code, a near field communication (NFC) tag, an object with Bluetooth capabilities, or other suitable electronic data objects that may communicate with a target entity computer. The target entity may use the target entity computer to interact with a digital indicator associated with a resource provider and / or an item to generate an assertion associated with the identity or account of the target entity. The assertion may represent an item digital coupon or discount provided by a merchant or a relying entity for an item during a payment and clearing process or when completing a transaction on behalf of a target entity.
[0058] The example system 100 may be adapted for use in a scenario involving a dependent entity 161 attempting to determine whether an assertion of a digital coupon or discount is associated with an entity 111 initiating an item transaction. Traditionally, a user may take advantage of a mail-back rebate to enjoy a discount on an item. However, this traditional method may not be effective for the user to obtain the discount because the user will not or is not willing to mail the rebate back to enjoy the discount; and utilizing the mail-back rebate may provide disconnected information (e.g., location and time) about how to obtain the discount. In addition, traditionally, the results or analysis of the discount activity are difficult to obtain and identify the effectiveness of the discount activity. However, in the embodiments described herein corresponding to digital coupon assertions, information about obtaining and redeeming digital coupons / assertions may be provided to entities other than the dependent entity requesting whether an assertion exists. For example, an entity that provides digital coupons or discounts, such as a merchant, a physical store, or a manufacturer, may receive information from the assertion model manager 131 that identifies the location where the user obtained the assertion, which item is associated with the assertion, and the location where the user ultimately redeemed the assertion. Information associated with the redemption of the assertion (digital coupon or discount) can help the entity determine the effectiveness of the digital discount activity and help identify specific markets or merchants to provide future digital discounts. To further promote the sale of a particular item. In an embodiment, the example system 100 may be adapted to associate an assertion with an account or identity of a user to obtain a discount or digital coupon for an item associated with the assertion. In an embodiment, when a request for an eligibility assertion for a digital coupon is received on behalf of the entity 111, the assertion model manager 131 may generate a notification or message and transmit it to the resource provider that generated the digital indicator and digital coupon pair. As described herein, the notification or message to the resource provider may include the identity of the resource provider utilizing the digital coupon, the location of the resource provider, the identity of the entity 111, and / or item information, such as an item SKU corresponding to the item included in the transaction for which the digital coupon is requested.
[0059] In an embodiment, a dependent entity 161 may request the existence of an assertion of an item and entity 111 on behalf of entity 111 initiating an item transaction. The assertion of the item and entity 111 may include an assertion between entity 111 and a specific resource provider. Entity 111 may provide identification of the entity itself to dependent entity 161, for example, by interacting with dependent entity 161 using a target entity computer (e.g., a user device) or by communicating with dependent entity 161 using an application of the target entity computer. As described herein, entity 111 may have previously interacted with a digital indicator associated with a resource provider using a target entity computer, such as by scanning a QR code in a resource provider location, such as a QR code at a physical store of the resource provider. In an embodiment, the digital indicator may be associated with the location of the resource provider, or the digital indicator may be associated with a specific item provided by the resource provider. The application of the target entity computer may transmit information obtained by the QR code (e.g., a resource provider identifier, an item stock keeping unit (SKU) or other item identifier) and information about the device and entity 111 (e.g., a target entity identifier and device information) to the assertion model manager / API 131. According to at least one embodiment, assertion model manager / API 131 may generate assertions representing interactions of entity 111 and associate them with a digital indicator of entity 111's identity stored by assertion model manager / API 131. In an embodiment, assertions may be used to generate discounts or digital coupons for digital prepaid cards representing items that may only be redeemed or used by entity 111. In an embodiment, entity 111 is prohibited from transmitting or allowing other entities to use digital coupons associated with assertions about entity 111 and maintained by assertion model manager 131.
[0060] Relying entity 161 may submit a request for identity attributes on behalf of entity 111 to determine the eligibility of a digital coupon for an item included in a transaction conducted between relying entity 161 and entity 111. It should be noted that relying entity 161 that submits a request for a digital coupon assertion may be a resource provider that provides a digital indicator, or may be a different resource provider that does not provide a digital indicator and therefore does not provide a digital coupon for an item. By utilizing the systems and methods described herein, a resource provider can incentivize an entity to interact with the provided digital indicator to access digital coupons that can be redeemed at a different resource provider that provides the same item. In exchange for the entity interacting with the provided digital indicator, the resource provider that provides the digital coupon can receive information that can be used to determine the impact of a shift in a marketing program or a specific location of a physical store in a geographic location. The resource provider can receive such information when entity 111 performs a transaction of an item associated with a digital indicator and when relying entity 161 submits a request for an assertion of a digital coupon on behalf of entity 111. Entities such as entity 111 may conduct transactions more efficiently because further interaction by the entity computer (target entity computer) may not be required to notify the resource provider or relying entity 161 of its previous interaction with the digital indicator, which qualified the resource provider or relying entity to obtain a digital coupon or prepaid card for transactions conducted by entity 111. Furthermore, entity 111 does not have to browse or scroll through multiple user interfaces to locate and utilize an assertion indicating that entity 111 is eligible to obtain a digital coupon or prepaid card that can be used for transactions conducted by entity 111. Instead, relying entity 161 and assertion model manager 131 may utilize the identifier of entity 111 to determine that entity 111 is eligible for a discount, and apply the discount to the transaction without further action by entity 111.
[0061] In an embodiment, the request from the relying entity 161 may include an identifier of the relying entity 161, an identifier of the entity 111, and transaction information, such as an item SKU of the item in the transaction. The request may be provided from the relying entity 161 to the assertion model manager 131, which may use the information in the request to look up or identify any assertions associated with the entity 111 and the item and / or the identity of the relying entity 161. In some embodiments, the relying entity 161 may hash or encrypt any information and then transmit the information to the assertion model manager 131. For example, the relying entity 161 may hash or encrypt the identifiers of the relying entity 161 and the entity 111 and send the hashed or encrypted information to the assertion model manager 131. The assertion model manager 131 may take the hashed or encrypted information and compare it to a hash of the identifier on file with the assertion model manager 131, or decrypt the encrypted information using a private key maintained by the assertion model manager 131. A matching comparison will indicate that the identifier is recognized and can be used to identify any assertions associated with the entity 111.
[0062] The assertion model manager 131 may archive or maintain a number of assertions associated with the entity 111. For example, the entity may have used a target entity computer to interact with a number of digital indicators provided by a number of different resource providers. Each interaction between the target entity computer and the digital indicator may form a new assertion corresponding to a digital coupon that may be redeemed during a transaction of an item provided by a system resource provider. The assertion model manager 131 may have information about whether the entity 111 has any assertions associated with itself and a particular resource provider and / or item included in the transaction. The assertion model manager 131 may maintain information identifying whether an assertion has been redeemed (e.g., a prepaid card or a ticket associated with a prepaid card has been provided to the relying entity 161).
[0063] The assertion model manager 131 may return an assertion or a receipt indicating the existence of an assertion for a discount, digital coupon, or prepaid card to the relying entity 161. The assertion may serve as proof of a specific pre-configured fact (e.g., a user device associated with the user has previously interacted with a digital indicator associated with an item included in the transaction information). In an embodiment, the relying entity 161 may provide the receipt to a payment processing network during a clearing and settlement process to complete a transaction corresponding to a payment request to redeem a prepaid card associated with an assertion between the transacting entity 111 and a given resource provider that provided a digital indicator as described herein.
[0064] In a real-world example, a resource provider may be an entity that attempts to provide a discount or digital coupon to a target entity that attempts to purchase an item. For example, a resource provider may be a merchant that provides a pair of basketball shoes. In order to provide a discount on basketball shoes, the resource provider may form a pre-established relationship with an assertion model manager 131 to provide a digital coupon to a specified entity that interacts with a digital indicator provided by the resource provider for basketball shoes. The assertion model manager 131 may form an assertion of an entity 111 that interacts with a digital indicator provided by the resource provider, the digital indicator including an identifier of the entity 111 and a resource provider location or a specific item provided by the resource provider indicated by the digital indicator. This interactive assertion may be used to provide a digital coupon when the entity 111 provides the identity (identifier) of the entity during an item transaction at the resource provider or at a different resource provider (e.g., at a location of a dependent entity 161, a different dependent entity at a different location, or a resource provider at a different location). If an assertion exists, the assertion model manager 131 may provide a ticket to the relying entity 161, which may be redeemed or otherwise provided during the clearing and settlement of a token transaction associated with a prepaid card corresponding to the assertion and associated with the entity 111 when interacting with the digital indicator of the item. By utilizing the token associated with the assertion and any other payment information or payment account provided by the entity 111, a split payment process may be initiated, wherein the entity 111 pays a portion that is less than the original price of the item and the token associated with the assertion is paid by the acquirer that generated the assertion and the corresponding digital indicator.
[0065] In an embodiment, the assertion model manager 131 may use the identifier of the entity 111 included in the request to identify assertions associated with the entity 111 for a transaction in which the assertion request is received from the dependent entity 161. In an embodiment, the assertion model manager 131 may contact a financial entity (e.g., DI provider 121) associated with the entity 111 and provide the identifier of the entity 111 to cause the financial entity (e.g., DI provider 121) to return assertions associated with the interaction of the corresponding target entity computer of the entity 111 with the digital indicator associated with the item and / or resource provider. In an embodiment, the assertion model manager 131 may have previously received assertions about the interaction of the target entity computer with the digital indicator associated with the item from the financial entity (e.g., DI provider 121), and the assertion model manager 131 may retrieve or locate those assertions based on the identifier of the entity and the transaction information included in the request, such as item information (e.g., item SKU) or the identifier of the dependent entity. The assertion may be a set of true / false or yes / no statements.
[0066] In an embodiment, the assertion model manager 131 may collect only assertions related to the entity 111, the dependent entity 161, and / or the items included in the transaction. A specific set of relevant assertions may be defined in advance in the assertion model, which may be based on a specific dependent entity 161 or according to one or more domain restrictions. In an embodiment, a domain restriction may be one or more sets of rules that are associated with potential assertions in response to an entity using a target entity computer to interact with a digital indicator of an item or resource provider. For example, a domain restriction may include assertions that may be used for: a specific item (e.g., a specific item SKU), a specific dependent entity (e.g., a whitelist of white dependent entities that may request and receive assertions), or a date restriction that may indicate a time range in which the assertion may be validly redeemed. Thus, the assertion model manager 131 may provide requested information back to the dependent entity 161 without compromising the privacy rights of the individual, and may initiate provisioning of a discount on an item, a digital coupon, or a prepaid card without requiring any additional action by the entity 111, such as a mail-back discount. Once relying entity 161 receives confirmation of the assertion associated with entity 111 of the item included in the transaction, the digital coupon or discount can be applied to the item and entity 111 can purchase the item at a reduced price due to a previous interaction with a digital indicator associated with the same item at a previous time and at a location, which may be a different location from where relying entity 161 conducted the transaction.
[0067] As described in the previous example, this can be best understood from the perspective of the assertion model manager 131. Figure 4 The assertion model manager 131 may be implemented by a server computer.
[0068] In an embodiment, at block 402, assertion generation is initiated by receiving a first request to form an assertion of a target entity and a resource provider in response to an interaction of a target entity computer with a digital indicator associated with a resource provider. The target entity may utilize the target entity computer to interact with a digital indicator associated with an item (e.g., scanning a QR code of the item) to transmit information including a target entity identifier, the item being interacted with, the resource provider providing the item, and an indication of the interaction to an assertion model manager. If an assertion has not yet been associated for this item and / or resource provider and the target entity, the assertion model manager may associate the assertion with the target entity identifier. In an embodiment, the identifiers of the target entity and the resource provider, the item information, and any other suitable information included in the digital indicator, and the indication of the interaction may be transmitted to the assertion model manager via an application of the target entity computer, such as an application of a mobile device, over a network such as the Internet. The assertion model manager may collect this information, but in some embodiments, this information is not stored in plain text. For example, some or all of the information may be hashed or encrypted. In addition, some or all of the collected information may be tokenized.
[0069] In some embodiments, a copy of a token representing an assertion may be provided to an individual (e.g., for storage on the individual's user device) to allow the individual to use the token when conducting a transaction for an item associated with the assertion. Thus, an individual may attach a token for a payment account to their identity and conduct a transaction for an item associated with the assertion. More specifically, the token may contain information for redemption of a prepaid card.
[0070] In an embodiment, at block 404, the assertion model manager may generate an assertion including an identity attribute of a target entity based at least in part on the first request.
[0071] In some embodiments, a second request for identity attributes associated with the target entity to conduct a transaction associated with the relying entity may be received at block 406. The second request may include a first identifier of the relying entity, a second identifier associated with the target entity, and an item identifier of the transaction item. In embodiments, the target entity may have provided a saved token (e.g., stored when the user established the assertion) from its target entity computer, rather than manually entering information about its identity or identifier to conduct the transaction.
[0072] In an embodiment, at block 408, an assertion model may be determined based at least in part on the first identifier and the second identifier in response to receiving the second request. In an embodiment, the assertion model manager determines the assertion model for the dependent entity based on the received identifier of the dependent entity. The assertion model manager may have a plurality of pre-configured assertion models, one of which may be associated with the particular dependent entity. Thus, the assertion model manager will use the identity of the dependent entity to look up the appropriate assertion model in order to determine the assertions that the dependent entity is authorized to receive. The assertion model manager may also identify and apply appropriate domain restrictions to identify appropriate assertions as described herein based on the identifier of the dependent entity or item information.
[0073] In an embodiment, the assertion model manager may retrieve an identity attribute based at least in part on the assertion model and one or more domain restrictions on the assertion at block 410. If the assertion model manager for the target entity and the transaction item has assertions, the assertion model manager may retrieve an identity attribute indicating eligibility for the digital coupon for the transaction.
[0074] In an embodiment, at block 412, for example, the assertion model manager may provide a ticket indicating that an assertion exists and may be provided by a relying entity to an acquirer or issuer to redeem an associated prepaid card for clearing and settling transactions as described herein.
[0075] Figure 5 is a flowchart of a workflow for providing at least one assertion including a digital coupon, according to an embodiment. Figure 5 The workflow of includes a target entity 502 using a target entity computer 504 to interact with a digital indicator 506 provided by a resource provider 508 to generate an assertion maintained by a server computer 510. In an embodiment, the server computer 510 may implement Figure 1 The assertion model manager 131. The target entity 502 can be Figure 1 According to at least one embodiment, the server computer 510 may store assertions associated with the target entity 502 in a database such as a database 512. Communications between the target entity computer 504, the server computer 510, and the dependent entity computer 514 may be performed via a network 516.
[0076] At step S1, the target entity 502 may utilize the target entity computer 504 to interact 518 with the digital indicator 506 provided by the resource provider 508 to initiate the formation of an assertion by providing a first request as described herein. For example, the target entity 502 may interact with the digital indicator 506 provided by the resource provider 508 to receive a discount on a specific brand of T-shirts. The target entity computer 504 interacting 518 with the digital indicator 506 may include scanning a QR code provided by the resource provider 508. As described herein, the resource provider 508 may provide a digital coupon or prepaid card for purchasing a specific brand of T-shirts at another retail location or at the resource provider.
[0077] At step S2, the target entity computer 504 transmits the identifier of the target entity 502, an indication of the interaction between the target entity computer 504 and the digital indicator 506, and any information included in the digital indicator, such as item information, resource provider, resource provider location, etc., to the server computer 510 in the form of a message via the network 516.
[0078] At step S3, server computer 510 may generate an assertion between target entity 502 and resource provider 508 or an item associated with digital indicator 506, the assertion being mapped or associated with an identifier of target entity 502. The assertion may be stored in database 512.
[0079] At step S4, target entity 502 may utilize target entity computer 504 to trade items with a relying entity via relying entity computer 514. The transaction with the relying entity may be a resource provider different from resource provider 508, which provides digital indicator 506 and digital coupon or prepaid card incentive assertion as described herein.
[0080] At step S5, the dependent entity computer 514 may generate a request (a second request) for the identity attribute of the target entity 502 for the item transaction. The identity attribute may correspond to an assertion of the target entity 502, the assertion being identified by an identifier associated with the target entity 502 and representing an interaction between the target entity computer 504 and the digital indicator 506. In an embodiment, the second request may include a first identifier of the dependent entity, a second identifier associated with the target entity 502, and an item identifier associated with the transaction item.
[0081] At step S6, server computer 510 may determine an assertion model based at least in part on the first identifier and the second identifier in response to receiving the second request. Server computer 510 may retrieve identity attributes from database 512 based at least in part on the assertion model and one or more domain restrictions on the assertion.
[0082] At step S7, server computer 510 may transmit the ticket to relying entity computer 514 over network 516 based at least in part on the retrieved identity attribute. As described herein, the ticket represents the eligibility of a digital coupon or prepaid card for use by a relying entity and associated with target entity 602 to complete a transaction.
[0083] Additional details regarding aspects of the embodiments may be found in U.S. Provisional Patent Application No. 62 / 587,143, filed on November 16, 2017, the disclosure of which is incorporated herein by reference in its entirety for all purposes.
[0084] Although the present invention has been described in detail for illustrative purposes based on what is currently considered to be the most practical and preferred embodiments, it should be understood that such details are only for that purpose and that the present invention is not limited to the disclosed embodiments, but on the contrary, is intended to cover modifications and equivalent arrangements within the spirit and scope of the appended claims. For example, it should be understood that the present invention contemplates that, to the extent possible, one or more features of any embodiment may be combined with one or more features of any other embodiment.
Claims
1. A method comprising: receiving, by a server computer, from a target entity computer a first request to form an assertion of a target entity and a resource provider associated with the target entity computer, the assertion request including an identity of the target entity and a location of the resource provider, the first request being generated in response to interaction of the target entity computer with a digital indicator associated with the resource provider; generating, by the server computer, the assertion including identity attributes of the target entity based at least in part on the first request, the identity attributes including the identity of the target entity and an indication of the interaction of the target entity computer with the digital indicator associated with the resource provider, wherein the assertion is a security fact about the target entity; receiving, by the server computer from a relying entity computer, a second request for the identity attribute associated with the target entity to conduct a transaction associated with a relying entity associated with the relying entity computer and the target entity, the second request comprising: a first identifier of the dependent entity; a second identifier associated with the target entity; and an item identifier of an item associated with the transaction; determining, by the server computer, in response to receiving the second request, an assertion model based at least in part on the first identifier and the second identifier, wherein the assertion model specifies one or more assertion types that the relying entity is authorized to receive; retrieving, by the server computer, the identity attribute based at least in part on the assertion model and one or more domain restrictions on the assertion; and A ticket is transmitted by the server computer to the relying entity computer based at least in part on retrieving the identity attribute.
2. The method of claim 1, wherein the ticket is used by the relying entity to complete the transaction.
3. The method of claim 2, wherein the ticket comprises a digital coupon for the item.
4. The method of claim 1, wherein the one or more domain restrictions include at least one of: prohibiting the use of the ticket for a specific resource provider, prohibiting the use of the ticket for the specific resource provider and specific items, limiting the use of the ticket to one or more resource providers specified by an entity, or limiting the use of the ticket to a specific time period.
5. The method of claim 1, further comprising transmitting, by the server computer, a notification of use of the assertion to a resource provider computer associated with the resource provider in response to receiving the ticket from a relying entity computer. 6 . The method of claim 5 , wherein the notification includes the resource provider, the location of the resource provider, the item identifier, and the identity of the target entity.
7. The method of claim 1, further comprising transmitting, by the server computer to the relying entity computer, a payment token corresponding to a discount on the item in the transaction in response to receiving the ticket from the relying entity computer.
8. The method of claim 1, wherein the second identifier associated with the target entity is maintained by an application of the target entity computer and provided in the second request.
9. The method of claim 1, further comprising transmitting, by the server computer to the target entity computer, a notification of the generation of the assertion identifying the resource provider.
10. The method of claim 1, wherein another entity is prohibited from using the assertion.
11. A computer system comprising: processor; as well as a memory element comprising instructions that, when executed by the processor, cause the system to at least: receiving, from a target entity computer, a first request to form an assertion of a target entity and a resource provider associated with the target entity computer, the assertion request including an identity of the target entity and a location of the resource provider, the first request being generated in response to interaction of the target entity computer with a digital indicator associated with the resource provider; generating the assertion including identity attributes of the target entity based at least in part on the first request, the identity attributes including the identity of the target entity and an indication of the interaction of the target entity computer with the digital indicator associated with the resource provider, wherein the assertion is a security fact about the target entity; receiving, from a relying entity computer, a second request for the identity attribute associated with the target entity to conduct a transaction associated with a relying entity associated with the relying entity computer and the target entity, the second request comprising: a first identifier of the dependent entity; a second identifier associated with the target entity; and an item identifier of an item associated with the transaction; in response to receiving the second request, determining an assertion model based at least in part on the first identifier and the second identifier, wherein the assertion model specifies one or more assertion types that the relying entity is authorized to receive; retrieving the identity attribute based at least in part on the assertion model and one or more domain restrictions on the assertion; and A ticket is transmitted to the relying entity computer based at least in part on retrieving the identity attribute.
12. The computer system of claim 11, wherein the digital indicator comprises a Quick Response (QR) code.
13. The computer system of claim 12, wherein the computer system implements an assertion model manager.
14. The computer system of claim 13, wherein the assertion model manager receives the first request and the second request using an application programming interface.
15. The computer system of claim 11, wherein the second identifier associated with the target entity comprises the identity of the target entity.
16. The computer system of claim 15, wherein the one or more domain restrictions are specified by the resource provider.
17. The computer system of claim 11, wherein the location of the resource provider comprises a geographic location of the resource provider.
18. The computer system of claim 11, wherein the second identifier associated with the target entity is maintained by an application of the target entity computer and provided in the second request.
19. The computer system of claim 11, wherein the identity attributes are retrieved from a digital identity provider.
20. A non-transitory computer-readable storage medium having stored thereon instructions, which when executed by a computer system cause the computer system to perform at least the following operations: receiving, from a target entity computer, a first request to form an assertion of a target entity and a resource provider associated with the target entity computer, the assertion request including an identity of the target entity and a location of the resource provider, the first request being generated in response to interaction of the target entity computer with machine-readable code associated with the resource provider; generating the assertion including identity attributes of the target entity based at least in part on the first request, the identity attributes including the identity of the target entity and an indication of the interaction of the target entity computer with the machine-readable code associated with the resource provider, wherein the assertion is a security fact about the target entity; receiving, from a relying entity computer, a second request for the identity attribute associated with the target entity to conduct a transaction associated with a relying entity associated with the relying entity computer and the target entity, the second request comprising: a first identifier of the dependent entity; a second identifier associated with the target entity; and an item identifier of an item associated with the transaction; in response to receiving the second request, determining an assertion model based at least in part on the first identifier and the second identifier, wherein the assertion model specifies one or more assertion types that the relying entity is authorized to receive; retrieving the identity attribute based at least in part on the assertion model and one or more domain restrictions on the assertion; and A ticket is transmitted to the relying entity computer based at least in part on retrieving the identity attribute.
