Low latency and redundant proof of possession for content subscription with outbound message synchronization
Methods, systems, and apparatus, including computer programs encoded on computer storage media, for mitigating computing latency associated with proving possession of network endpoints across customer domains by leveraging fingerprints associated with user devices. One system includes (i) a user device, e.g., a smartphone or a personal computer, (ii) a proof of possession service running on one or more computers, and (iii) an authorization service running on one or more computers.
1 . A system for content subscription, the system comprising a user device and a server, user device being configured to communicate with the server, the server being implemented on one or more computers, wherein:
the user device has a first network endpoint and is configured with a web browser, wherein the web browser is configured with popup instructions operable to cause the web browser to perform popup operations comprising:
generating a popup from a parent web page, the popup including (i) a call to action to subscribe to content at the first network endpoint and (ii) an end-point input field, wherein the content has an identifier (content ID) and includes SMS messages;
in response to user input indicating acceptance of the call to action, calling a service on the server for content subscription and proof of endpoint possession, wherein one indication of acceptance is receipt of user input specifying the first network endpoint, and wherein the call to the service specifies the first network endpoint;
obtaining a one-time passcode received at the first network endpoint on the user device and sending the passcode to the service;
in response to receiving from the service an indication of successful proof of endpoint possession, deep linking to a messaging application and pre-populating a message addressed to a second network endpoint from which subscribed content is sent; and
sending one or more HTML parameters extracted from the parent web page to the service, wherein the one or more HTML parameters indicate a traffic source of the parent web page; and
the server is configured to implement the service and perform service operations comprising:
in response to the call from the web browser for content subscription and proof of possession, generating a one-time passcode and sending the passcode to the first network endpoint from a third network endpoint that is different from the second network endpoint;
in response to receiving a one-time passcode from the web browser, comparing the received one-time passcode with the generated one-time passcode and, if they match, creating and storing a subscription record that includes the first network endpoint and returning to the browser an indication that proof of possession has been completed; and
appending the record with the one or more HTML parameters.
2 . The system of claim 1 , wherein the service operations further comprise:
queuing and sending a compliance message, from the second network endpoint to the first network endpoint, wherein queuing and sending are synchronized to be responsive to server-side receipt of the pre-populated message, but no later than a duration of time, whereby the second network endpoint is not filtered as being from an unknown sender by the messaging application.
3 . The system of claim 1 , wherein the user device has a fourth network endpoint that is different from and is associated with the first network endpoint, wherein the user input specifying the first network endpoint is a user selection of a submit icon displayed in the popup when the first network endpoint is displayed in the input field, and wherein:
popup instructions operable to cause the web browser to perform popup operations further comprising:
receiving user-input specifying the fourth network endpoint, sending the fourth network endpoint to the service, receiving from the service the first network endpoint, and displaying the first network endpoint in the input field; and
the service operations further comprising:
in response to receiving the fourth network endpoint, using the fourth network endpoint to look up the first network endpoint and sending the first network endpoint to the web browser.
4 . The system of claim 1 , wherein service operations further comprises:
using the fourth network endpoint to look up the first network endpoint in any combination of: records of content subscription, records of content engagement, and records of purchase.
5 . The system of claim 4 , wherein the records are for different merchants.
6 . The system of claim 4 , wherein the records are for different content creators.
7 . The system of claim 1 , wherein:
the popup operations further comprises obtaining state information, HTML parameters, or client-environment information that are needed for the deep linking and using the obtained state information, HTML parameters, or client-environment information for the deep linking.
8 . The system of claim 1 , wherein the deep linking is performed via a deep link that is any combination of: a URI, URN, URL, and a QR code.
9 . The system of claim 8 , wherein the deep link is generated server-side.
10 . The system of claim 8 , wherein the deep link is generated client-side.
11 . The system of claim 1 , wherein the pre-populated message references a reward for sending the pre-populated message, and wherein the service operations further comprises, responsive to receiving an indication that the pre-populated message has been received at the second network endpoint, enabling the reward to be redeemed.
12 . The system of claim 1 , wherein the content ID is one of one or more references to the content subscribed, wherein content subscribed is associated with the popup, and wherein:
the popup operations further comprise receiving the one or more references and including the one or more references in the pre-populated message; and
the service operations further comprise, responsive to receiving the pre-populated message, extracting the one or more references and using them to look up the subscription record to determine that the pre-populated message is associated with the popup.
13 . The system of claim 1 , wherein logic to generate the popup is generated server-side to reduce the number of system calls needed for instantiating the popup.
14 . A computer-program product stored on tangible media, the product comprising:
popup instructions interpretable to cause a web browser running on a user device to perform popup operations, wherein the user device has a first network endpoint, the popup operations comprising:
generating a popup from a parent web page, the popup including (i) a call to action to subscribe to content at the first network endpoint and (ii) an end-point input field, wherein the content has an identifier (content ID) and includes SMS messages;
in response user input indicating acceptance of the call to action, calling a service on the server for content subscription and proof of endpoint possession, wherein one indication of acceptance is receipt of user input specifying the first network endpoint, and wherein the call to the service specifies the first network endpoint;
obtaining a one-time passcode received at the first network endpoint on the user device and sending the passcode to the service;
in response to receiving from the service an indication of successful proof of endpoint possession, deep linking to a messaging application and pre-populating a message addressed to a second network endpoint from which subscribed content is sent; and
sending one or more HTML parameters extracted from the parent web page to the service, wherein the one or more HTML parameters indicate a traffic source of the parent web page; and
instructions executable server side to perform service operations for content subscription and proof of possession, the service operations comprising: in response to the call from the web browser for content subscription and proof of possession, generating a one-time passcode and sending the passcode to the first network endpoint from a third network endpoint that is different from the second network endpoint;
in response to receiving a one-time passcode from the web browser, comparing the received one-time passcode with the generated one-time passcode and, if they match, creating and storing a subscription record that includes the first network endpoint and returning to the browser an indication that proof of possession has been completed; and
appending the record with the one or more HTML parameters.
15 . The computer-program product of claim 14 , wherein the service operations further comprise:
queuing and sending a compliance message, from the second network endpoint to the first network endpoint, wherein queuing and sending are synchronized to be responsive to server-side receipt of the pre-populated message, but no later than a duration of time, whereby the second network endpoint is not filtered as being from an unknown sender by the messaging application.
16 . The computer-program product of claim 14 , wherein the user device has a fourth network endpoint that is different from and is associated with the first network endpoint, wherein the user input specifying the first network endpoint is a user selection of a submit icon displayed in the popup when the first network endpoint is displayed in the input field, and wherein:
popup instructions operable to cause the web browser to perform popup operations further comprising:
receiving user-input specifying the fourth network endpoint, sending the fourth network endpoint to the server, receiving from the server the first network endpoint, and displaying the first network endpoint in the input field; and
the service operations further comprising:
in response to receiving the fourth network endpoint, looking up the first network endpoint with the fourth network endpoint and sending the first network endpoint to the web browser.
17 . The computer-program product of claim 14 , wherein service operations further comprises:
using the fourth network endpoint to look up the first network endpoint in any combination of: records of content subscription, records of content engagement, and records of purchase.
18 . The computer-program product of claim 17 , wherein the records are for different merchants.
19 . The computer-program product of claim 17 , wherein the records are for different content creators.
20 . The computer-program product of claim 14 , wherein:
the popup operations further comprises obtaining state information, HTML parameters, or client-environment information that are needed for the deep linking and using the obtained state information, HTML parameters, or client-environment information for the deep linking.
21 . The computer-program product of claim 14 , wherein the deep linking is performed via a deep link that is one of: a URI, URN, URL, and a QR code.
22 . The computer-program product of claim 21 , wherein the deep link is generated server-side.
23 . The system of claim 21 , wherein the deep link is generated client-side.
24 . The computer-program product of claim 14 , wherein the pre-populate message references a reward for sending the pre-populated message, and wherein the service operations further comprises responsive to receiving an indication that the pre-populated message has been received at the third network endpoint, sending a redeemable code for the reward.
25 . The computer-program product of claim 14 , wherein the content ID is one of one or more references to the content subscribed, wherein content subscribed is associated with the popup, and wherein:
the popup operations further comprise receiving the one or more references and including the one or more references in the pre-populated message; and
the service operations further comprise, responsive to receiving the pre-populated message, extracting the one or more references and using them to look up the subscription record to determine that the pre-populated message is associated with the content subscribed.
26 . The computer-program product of claim 14 , wherein logic to generate the popup is generated server-side to reduce the number of system calls needed for the popup.