# US 12,764,537 B2 · Password-less login for online access > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,764,537 B2 - Document ID: US12764537B2 - Status: Granted - Kind: B2 - Application number: 18/300,276 - Filed: 2023-04-13 - Published: 2024-09-26 - Granted: 2026-10-13 - Earliest claimed: 2023-03-24 - Assignees: Zumigo, Inc. - Applicants: Zumigo, Inc. - Inventors: Venkatarama S. Parimi; Chirag C. Bakshi; Saravanan Jagadheson - Web page: https://patentgrep.com/patent/US12764537B2 ## CPC - H04W 12/108: Source integrity - H04W 12/06: Authentication - H04W 12/40: Security arrangements using identity modules - H04W 12/69: Identity-dependent - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract A method of authenticating a customer to allow the customer to log in to an account, includes the steps of: in response to a request to authenticate the customer based on a first mobile identifier (ID), generating a code that encodes a uniform resource locator (URL), and then transmitting the generated code to a computer that is managing access to the account; examining a network packet routed according to the URL and determining a second mobile ID using the network packet; comparing the first mobile ID to the second mobile ID; and based on a determination that the first mobile ID matches the second mobile ID, determining that the customer is authenticated, and then transmitting a message to the computer that the customer is permitted to log in to the account. ## Claims ### Claim 1 A method of authenticating a customer to allow the customer to log in to an account of the customer with a vendor that provides goods or a service, the method comprising: in response to a request to authenticate the customer based on a first phone number that is registered with the account, generating a code that encodes a uniform resource locator (URL), and then transmitting the generated code to a computer of the vendor that is managing access to the account; examining network packets transmitted by a computer of the customer to the URL and determining a second phone number using the network packets; comparing the first phone number to the second phone number; and based on a determination that the first phone number matches the second phone number, determining that the customer is authenticated, and then transmitting a message to the computer of the vendor that the customer is permitted to log in to the account. ### Claim 2 (depends on 1) The method of claim 1, wherein the step of determining the second phone number comprises extracting the second phone number from a header portion of the network packets. ### Claim 3 (depends on 1) The method of claim 1, wherein the computer of the customer is a mobile device having the first phone number, and wherein the step of determining the second phone number comprises: (1) transmitting an instruction to the mobile device instructing the mobile device to communicate with a platform of a cellular network provider that provides cellular networking services to the mobile device, and then (2) receiving the second phone number from the platform of the cellular network provider. ### Claim 4 (depends on 1) The method of claim 1, wherein the computer of the customer is a mobile device having the first phone number, and wherein the step of determining the second phone number comprises: (1) extracting a source internet protocol (IP) address from the network packets, then (2) transmitting a request to a platform of a cellular network provider that provides cellular networking services to the mobile device, for a phone number associated with the source IP address, and then (3) receiving the phone number associated with the source IP address from the platform of the cellular network provider as the second phone number. ### Claim 5 (depends on 4) The method of claim 4, wherein the step of determining the second phone number further comprises determining the cellular network provider by extracting metadata from the network packets that identifies the cellular network provider. ### Claim 6 (depends on 1) The method of claim 1, wherein the request to authenticate the customer is received from the computer of the vendor in response to the first phone number being specified as a user input via a login user interface (UI) of the computer of the vendor. ### Claim 7 (depends on 1) The method of claim 1, wherein the request to authenticate the customer is received from the computer of the vendor in response to a user identifier (ID) separate from the first phone number being specified as a user input via a login user interface (UI) of the computer of the vendor. ### Claim 8 (depends on 1) The method of claim 1, wherein the step of determining that the customer is authenticated includes determining that the first phone number has neither been activated on a new mobile device nor been activated on a new subscriber identity module (SIM) card over a previous time period. ### Claim 9 (depends on 1) The method of claim 1, wherein the computer of the customer is a mobile device having the first phone number, the method further comprising: transmitting a session identifier (ID) to the mobile device; after transmitting the session ID, receiving an encrypted response; decrypting the encrypted response by using a cryptographic key associated with the first phone number; and comparing the decrypted response to the session ID, wherein the step of determining that the customer is authenticated includes determining that the decrypted response includes the session ID. ### Claim 10 (depends on 1) The method of claim 1, further comprising: selecting a push notification token associated with the first phone number; routing a one-time passcode (OTP) according to a network address included by the push notification token; and after routing the OTP, receiving a response and determining that the response includes the OTP, wherein the step of determining that the customer is authenticated includes determining that the response includes the OTP. ### Claim 11 An authentication computer configured to execute on a processor of a hardware platform to perform the following steps to allow a customer to log in to an account of the customer with a vendor that provides goods or a service: in response to a request to authenticate the customer based on a first phone number that is registered with the account, generate a code that encodes a uniform resource locator (URL), and then transmit the generated code to a computer of the vendor that is managing access to the account; examine network packets transmitted by a computer of the customer to the URL and determine a second phone number using the network packets; compare the first phone number to the second phone number; and based on a determination that the first phone number matches the second phone number, determine that the customer is authenticated, and then transmit a message to the computer of the vendor that the customer is permitted to log in to the account. ### Claim 12 (depends on 11) The authentication computer of claim 11, further configured to: extract the second phone number from a header portion of the network packets when determining the second phone number. ### Claim 13 (depends on 11) The authentication computer of claim 11, wherein the computer of the customer is a mobile device having the first phone number, and wherein when determining the second phone number, the authentication computer is further configured to: transmit an instruction to the mobile device instructing the mobile device, to communicate with a platform of a cellular network provider that provides cellular networking services to the mobile device, and then receive the second phone number from the platform of the cellular network provider. ### Claim 14 (depends on 11) The authentication computer of claim 11, wherein the computer of the customer is a mobile device having the first phone number, and wherein when determining the second phone number, the authentication computer is further configured to: extract a source internet protocol (IP) address from the network packets, then transmit a request to a platform of a cellular network provider that provides cellular networking services to the mobile device, for a phone number associated with the source IP address, and then receive the phone number associated with the source IP address from the platform of the cellular network provider as the second phone number. ### Claim 15 (depends on 14) The authentication computer of claim 14, wherein when determining the second phone number, the authentication computer is further configured to: determine the cellular network provider by extracting metadata from the network packets that identifies the cellular network provider. ### Claim 16 (depends on 11) The authentication computer of claim 11, wherein the request to authenticate the customer is received from the computer of the vendor in response to the first phone number being specified as a user input via a login user interface (UI) of the computer of the vendor. ### Claim 17 (depends on 11) The authentication computer of claim 11, wherein the request to authenticate the customer is received from the computer of the vendor in response to a user identifier (ID) separate from the first phone number being specified as a user input via a login user interface (UI) of the computer of the vendor. ### Claim 18 (depends on 11) The authentication computer of claim 11, wherein when determining that the customer is authenticated, the authentication computer is further configured to: determine that the first phone number has neither recently been activated on a new mobile device nor been activated on a new subscriber identity module (SIM) card over a previous time period. ### Claim 19 (depends on 11) The authentication computer of claim 11, wherein the computer of the customer is a mobile device having the first phone number, and wherein the authentication computer is further configured to: transmit a session identifier (ID) to the mobile device; after transmitting the session ID, receive an encrypted response; decrypt the encrypted response by using a cryptographic key associated with the first phone number; and when determining that the customer is authenticated, compare the decrypted response to the session ID to determine that the decrypted response includes the session ID. ### Claim 20 (depends on 11) The authentication computer of claim 11, further configured to: select a push notification token associated with the first phone number; route a one-time passcode (OTP) according to a network address included by the push notification token; and after routing the OTP, when determining that the customer is authenticated, receive a response and determine that the response includes the OTP.