Authenticating user requests via interactionless authentication

A method for reducing network traffic associated with authenticating user requests via interactionless authentication, the method comprising:

• in connection with receiving a user request to access a resource transmitted via a user application of a user device of a user, generating an address request for a first address associated with the user device of the user;
• subsequent to transmitting the address request to the user device of the user, receiving, via the user device, the first address associated with the user device, wherein the first address uniquely identifies the user device of the user;
• transmitting the first address to a third-party authentication platform that determines a carrier-specific Uniform-Resource-Locator (URL) indicating an address specific to a mobile carrier of the user device of the user;
• in response to receiving a response indicating the carrier-specific URL from the third-party authentication platform, transmitting a verification token request to an Application Programming Interface (API) associated with the mobile carrier based on the carrier-specific URL;
• receiving a verification token from the API, wherein the verification token verifies that the user device is associated with the mobile carrier;
• transmitting an authentication request to the third-party authentication platform, the authentication request comprising the received verification token;
• receiving, from the third-party authentication platform, an authentication response comprising a user device identifier associated with the user device of the user;
• and
• in response to receiving the authentication response, performing an authentication action associated with the user request based on a matching between the user device identifier and a known user device identifier.

One or more non-transitory computer-readable media storing computer program instructions that, when executed by one or more processors, cause operations comprising:

• in connection with receiving a user request to access a resource transmitted via a user application of a user device of a user, generating an address request for a first address associated with the user device of the user;
• subsequent to transmitting the address request to the user device of the user, receiving, via the user device, the first address associated with the user device;
• transmitting the first address to a third-party authentication platform that determines a carrier-specific Uniform-Resource-Locator (URL) indicating an address specific to a mobile carrier of the user device of the user;
• in response to receiving a response indicating the carrier-specific URL from the third-party authentication platform, transmitting a verification token request to an Application Programming Interface (API) associated with the mobile carrier based on the carrier-specific URL;
• receiving a verification token from the API, wherein the verification token verifies that the user device is associated with the mobile carrier;
• transmitting an authentication request to the third-party authentication platform, the authentication request comprising the received verification token;
• receiving, from the third-party authentication platform, an authentication response comprising a user device identifier associated with the user device of the user;
• and
• in response to receiving the authentication response, performing an authentication action associated with the user request based on the user device identifier and a known user device identifier.