The Integration Workflow for Connecting Leaky Paywall to a Fulfillment Center

The fulfillment center’s subscriber database becomes the central database we work with. Payments, card updates, etc are handled there. Leaky Paywall is in charge of local WordPress access.

Leaky Paywall’s role is pretty straightforward. For the Leaky Paywall data table we need to know whether a subscriber is allowed access or not. When there is a login we check our table. When a subscriber updates their email address or WordPress password we send the info over to your fulfillment house via the fulfillment center’s API.

When there is a new subscriber or change in subscriber status at the fulfillment house the webhook sends back the info in real time to WordPress so they can log in right away. This keeps the Leaky Paywall user database in sync with the fulfillment center database.

1. User on publication.com clicks on Subscribe. 

2. User goes to fulfillmentcenter.com and purchases a subscription.

3. Fulfillment Center sends a web hook to publication.com with the following data: first_name, last_name, email, subscription_level, subscription_status

4. Leaky Paywall immediately creates a WordPress user on publication.com with the web hook data sent from Fulfillment Center.

5. On the payment confirmation page on Fulfillment Center, a link is added to publication.com/account-setup?email_address=useremail@example.com . When the user clicks on this link it will display a page where they will enter their email address (might be prepopulated from URL if sent) and password to confirm their digital access. 

6. Any welcome email sent by Fulfillment Center should also include the link to the account setup page.

7. Every time the user the logs in, Leaky Paywall checks the Fulfillment Center API to make sure the user with that email address still has an active account. If not, the user is directed to a landing page asking them to subscribe again.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us