Auto Identification Integration Flow¶
User visits a paid content page on merchant’s website.
- no - proceed to 3
- yes - proceed to 4
Merchant obtains a user ID:
- If the merchant uses LaterPay tokens the user is redirected to /gettoken to be redirected back to the paid content page with an lptoken as a query parameter (flow starts at 1 again).
- If the merchant uses 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).
Merchant checks if the user has access to the paid content.
- no - proceed to 5
- yes - proceed to 6
Merchant denies the user access to paid content and presents them with LaterPay purchase button[s] (links to LaterPay Dialog API).
Merchant presents the paid article to the user.
- Straightforward UX - user either sees the article or a purchase button.