Leaky Paywall – SFS Data

Send your Leaky Paywall subscribers straight to SFS Data. When a reader subscribes, renews, or buys a gift subscription on your site, the order is created in SFS Data automatically, with their name, email, mailing address, and the amount they paid. Your fulfillment team no longer has to key orders in by hand, and your print mailing list stays in sync with your website.

• New subscriptions: each paid signup on a level connected to SFS becomes an order in SFS Data, sent with the source key, edition, and issue term you set for that level.
• Renewals: recurring renewals are sent to SFS as renewal orders, and can use their own renewal source key so you can track new orders and renewals separately.
• Gift subscriptions: gift purchases are sent with the recipient’s name and mailing address and flagged as gifts.
• The price the reader actually paid: trials, coupons, and discounted renewals are reported at the amount charged, not the regular price.
• Order details on every transaction: the SFS Order ID and Order Type are shown on the Leaky Paywall transaction screen.
• Failed orders don’t get lost: if SFS rejects an order or can’t be reached, the reason is shown on the transaction, along with the exact details that were sent, so your team can enter it by hand.

Enter your SFS Data Auth Token and Publication API ID under Leaky Paywall > Settings > Subscriptions > SFS Data. Then, on each subscription level you want sent to SFS, set the Issue Term, Edition, Source Key, and an optional Renewal Source Key. Levels without an Issue Term are not sent to SFS, so digital-only levels can stay out of your fulfillment system.

• Leaky Paywall
• An SFS Data account with API access
• Leaky Paywall Basic Shipping to collect mailing addresses
• Leaky Paywall Recurring Payments to send renewals
• Leaky Paywall Gift Subscriptions to send gifts