Auto Identification Integration Flow ==================================== 1. User visits a paid content page on merchant's website. 2. Merchant detects if they have an :doc:`lptoken <../identification/user_tokens>` or a :doc:`MUID <../identification/muids>` identifying the user * no - proceed to *3* * yes - proceed to *4* 3. Merchant obtains a user ID: a. If the merchant uses :doc:`LaterPay tokens <../identification/user_tokens>` the user is redirected to :doc:`/gettoken <../identification/gettoken>` to be redirected back to the paid content page with an :doc:`lptoken <../identification/user_tokens>` as a query parameter (flow starts at *1* again). b. If the merchant uses :doc:`MUIDs <../identification/muids>` the merchant identifies the user and reads a MUID assigned to that user or if the user has no MUID yet, the merchant generates a MUID and assigns it to the user's session (or similar mechanism) on the merchant website. (Flow proceeds to *4*). 4. Merchant checks if the user has :doc:`access <../access/index>` to the paid content. * no - proceed to *5* * yes - proceed to *6* 5. Merchant denies the user access to paid content and presents them with LaterPay purchase button[s] (links to LaterPay :doc:`Dialog API <../dialogs/index>`). 6. Merchant presents the paid article to the user. Pros ---- * Straightforward UX - user either sees the article or a purchase button. Cons ---- * If merchant uses LaterPay tokens then every unidentified user is **automatically** (no user interaction initiating the redirect) redirected to :doc:`/gettoken <../identification/gettoken>` and back to the paid content page again.