User authentication using secure infrastructure

1 . A method comprising:

at a set of one or more third party servers associated with a third party:

determining to require authentication of a second party;

responsive to determining to require authentication of the second party, generating a first code; and

providing the first code to a mobile device of the second party;

at the mobile device of the second party:

receiving the first code; and

providing the first code on a screen of the mobile device;

at a security camera associated with a secure device at a fixed location:

capturing an image of a portion of the screen of the mobile device while the screen of the mobile device is facing the security camera and while the screen of the mobile device is showing the first code generated by the third party; and

providing the image of the first code to a secure device server set as part of a security feed;

at a secure device server set comprising one or more secure device servers of a first party:

receiving the security feed from the security camera;

monitoring the security feed to identify images that may contain a code;

detecting the first code within the provided image, wherein the image includes the portion of the screen of the mobile device while the screen of the mobile device is facing the security camera and while the screen of the mobile device is showing the first code generated by the third party;

responsive to detecting the first code, generating a second code based on the first code; and

transmitting the second code to the third party;

at the set of one or more third party servers:

receiving the second code from the first party; and

determining to authenticate the second party based on the second code.

2 . A method comprising:

at a secure device server set comprising one or more secure device servers of a first party:

receiving a security feed from a security camera associated with a secure device;

monitoring the security feed to identify images that may contain a code;

detecting a first code within an image, wherein the image includes a portion of a screen of a mobile device of a second party that is facing the security camera and wherein the screen is showing a first code generated by a third party responsive to determining to require authentication of the second party;

responsive to detecting the first code:

identifying in the first code at least one of:

indicia of user permission to use authentication:

information of the second party requested to be authenticated by the third party; or

identification of a communication channel to be used for communication with the third party; and

generating a second code based on the first code; and

transmitting the second code to the third party, thereby fulfilling the authentication of the second party, wherein transmitting the second code to the third party includes at least one of:

publishing the second code on a blockchain;

providing the second code in response to an application programming interface call from the third party; or

providing the second code via an application programming interface call to the third party.

3 . The method of claim 2 , wherein the first code is encoded in a dynamic visual code.

4 . The method of claim 3 , wherein the dynamic visual code has colors or brightness that change over time to encode the first code.

5 . The method of claim 2 , wherein the second code includes the first code.

6 . The method of claim 2 , wherein the first code includes an identifier of the second party.

7 . The method of claim 2 , wherein the portion of the screen that is showing the first code is showing the first code within a mobile application associated with the third party running on the mobile device of the second party.

8 . The method of claim 2 , wherein generating the second code includes signing with a private key associated with the secure device.

9 . The method of claim 2 , wherein generating the second code includes:

determining whether a user authenticated with the secure device within a predetermined amount of time of the first code being provided to the secure device; and

including an identifier of the user or a hash of an identifier of the user with the second code.

10 . The method of claim 2 , wherein the first code was generated responsive to determining to require authentication of the second party based on:

detecting a login request from the second party;

detecting a create account request from the second party;

detecting a change to security or privacy settings from the second party;

detecting a change to payment or billing settings;

detecting a password recovery request from the second party;

detecting an account deletion request from the second party;

detecting a request to add another device to an account;

detecting potential fraud in relation to an account of the second party;

detecting potential misuse of an account of the second party;

detecting inauthentic behavior with an account of the second party;

detecting an unusual login location for the second party;

detecting a request requiring a second party be in a particular location; or

determining to verify an age of the second party.

11 . The method of claim 2 , wherein the secure device is an automated teller machine.

12 . A method comprising:

at a third-party server associated with a third party:

determining to require authentication of a second party;

responsive to determining to require authentication of the second party, generating a first code, the first code including at least one of:

indicia of user permission to use authentication;

information of the second party requested to be authenticated by the third party; or

identification of a communication channel to be used for communication with the third party;

providing a displayable representation of the first code to a mobile device of the second party;

receiving a second code from a first party;

determining a location of a device of the first party to which the first code was communicated by the second party;

determining to authenticate the second party based on the second code and the location,

wherein the first code was generated responsive to determining to require authentication of the second party based on:

detecting a login request from the second party;

detecting a create account request from the second party;

detecting a change to security or privacy settings from the second party;

detecting a change to payment or billing settings;

detecting a password recovery request from the second party;

detecting an account deletion request from the second party;

detecting a request to add another device to an account;

detecting potential fraud in relation to an account of the second party;

detecting potential misuse of an account of the second party;

detecting inauthentic behavior with an account of the second party;

detecting an unusual login location for the second party;

detecting a request requiring a second party be in a particular location; or

determining to verify an age of the second party.

13 . The method of claim 12 , wherein receiving the second code from the first party includes:

obtaining the second code from a blockchain to which the first party published the second code:

receiving the second code via an application programming interface call from the first party; or

making an application programming interface call to the third party regarding the second code.

14 . The method of claim 12 , wherein the determining to authenticate the second party is based on a location of a device to which the first code was communicated.

15 . The method of claim 14 , wherein determining to authenticate the second party includes deriving the first code from the second code.

16 . The method of claim 12 , further comprising:

providing the first code via an application of the third party running on the mobile device of the second party.