Relying party risk-adjusted indicator system and method

A system comprising at least one processor of a user device programmed or configured to:

• receive a request from at least one identity service to approve communicating at least one user proof-of-identity to at least one relying party;
• prompt a user of the user device to request at least one one-time transaction identifier based on the request;
• request the at least one one-time transaction identifier from at least one identity server associated with the at least one identity service based on a first input from the user on the user device;
• in response to the request for the at least one one-time transaction identifier, receive the at least one one-time transaction identifier from the identity server;
• display the at least one one-time transaction identifier on a first user device screen;
• receive a second input from the user on a second user device screen different than the first user device screen, the second input comprising at least one inputted one-time transaction identifier;
• communicate to the at least one identity service the at least one inputted one-time transaction identifier input by the user on the second user device screen;
• and
• at least one processor of the at least one relying party programmed or configured to:
• in response to receiving the at least one inputted one-time transaction identifier, determine whether to approve or deny a transaction based at least partially on the at least one one-time transaction identifier and the at least one inputted one-time transaction identifier.

A computer program product comprising at least one non-transitory computer readable medium including one or more instructions that, when executed by at least one processor, cause the at least one processor to:

• receive a request from at least one identity service to approve communicating at least one user proof-of-identity to at least one relying party;
• prompt a user of a user device to request at least one one-time transaction identifier based on the request;
• request the at least one one-time transaction identifier from at least one identity server associated with the at least one identity service based on a first input from the user on the user device;
• in response to the request for the at least one one-time transaction identifier, receive the at least one one-time transaction identifier from the identity server;
• display the at least one one-time transaction identifier on a first user device screen;
• receive a second input from the user on a second user device screen different than the first user device screen, the second input comprising at least one inputted one-time transaction identifier;
• communicate to the at least one identity service the at least one inputted one-time transaction identifier input by the user on the second user device screen;
• and
• in response to receiving the at least one inputted one-time transaction identifier, determine whether to approve or deny a transaction based at least partially on the at least one one-time transaction identifier and the at least one inputted one-time transaction identifier.