EdgeKit Subscriptions
Turn engaged readers into subscribers who stay
Sell your offers on your own pages, with no redirect, and let subscribers gift single articles. Your billing provider keeps the money. EdgeKit keeps the access of every reader who buys through it in step with their subscription: renewed, past due, paused or ended. Recurly is connected today; Stripe is being connected.
- Provider
- Recurly
- Sold as
- Individual
- Access to
- 3 Mar 2027
- StartedEdgeKit checkoutBought Digital Annual on an article page
- ExtendedRecurlyRenewal paid · access to 3 Mar 2027
- SuspendedRecurlySubscription paused · reason: pause · term end unchanged
- ResumedRecurlyPause ended · access to 3 Mar 2027
Written from the provider's own events
Where it leaks
Three places reader revenue slips between systems
The refund that keeps reading.
Billing ends the subscription. The paywall is never told, so the reader keeps full access until somebody runs a report.
The discount nobody bills.
The paywall promises half off the first year. Billing has no matching coupon. The reader finds out on their statement.
The corporate deal in a spreadsheet.
Forty seats, a list of names and an account manager who has moved on. Nobody can say who should still be reading.
EdgeKit moves all three onto the record your paywall already reads.
What it does
Between the invoice and the article
Your billing provider knows who paid. Your paywall knows who is reading. Subscriptions keeps them the same person.
Access follows billing
Renewals, pauses and endings move access on their own
EdgeKit reads every change from your provider and makes the access change it calls for. A renewal extends access. When your provider ends a subscription early, access ends too, and the reason is recorded.
- By default, readers keep reading while your provider retries the card: its schedule is the grace period
- Whether past due or paused stops reading is one policy, chosen with EdgeKit at setup
- Paid again or back from a pause, access resumes on its own
- Access during dunning
- Keep access
- Access continues through your provider's retry schedule.
- Access during pause
- Suspend
- No access now; the term end is unchanged.
When your provider saysAccess does
Renewal paidExtended to the new period end
Invoice past dueKept by default, or suspended
Subscription pausedSuspended by default, or runs to period end
Invoice paid againResumed
Ended earlyEnded · reason kept: refund, chargeback, non-payment
Ended on its dateRuns out on that date
Checkout
The offer on the paywall is the offer at checkout
Your paywall picks the offer and your page takes payment right there, in your design. Checkout sells the offer the paywall showed: it cannot be swapped, nothing in draft can be bought, and access starts in the same step.
- Card fields belong to your provider, so card numbers never reach EdgeKit
- A reader who isn't signed in gives an email and is subscribed in one step
- Bank challenges (3-D Secure) run in the page and finish the same purchase
£48 the first year
then £96 a year · every title
Emaila.mensah@example.comCard•••• 424212 / 28CVCRecurly secure fieldSubscribeWhat checkout did
- Offer matches what the paywall showed
- Discount billed with coupon INTRO50
- Charged by Recurly · 3-D Secure passed
- Reader record created for a.mensah@example.com
- Access started · All Access · every title
Group licences
Corporate seats the employer's own admin runs
Give a company one account its people read under. Their admin invites colleagues, or you list the company's email domain and verified sign-ups join on their own. The seat limit is enforced on every join.
- Account full? Block the next seat, or let them in and flag it: one policy, set with EdgeKit
- Anyone turned away is listed for the admin, so you can see who is waiting for a seat
- Members, roles and invitations come through EdgeKit's API, for a corporate page in your own design
- Email domain
- examplefreight.com · auto-join on
- When full
- Block the next seat
MemberRoleJoined via
r.ito@examplefreight.comAdminAdded by your team
p.osei@examplefreight.comMemberEmail domain
l.varga@examplefreight.comMemberInvitation
Waiting for a seat · 2
k.lund@examplefreight.comturned away twice
m.reyes@examplefreight.comturned away once
Gift links
Subscribers share a story. You set the limits.
A subscriber makes a link to one article and sends it to anyone. Who may gift, how many a month and how many devices each link opens on are rules you write, and the link is bound to that one article.
- Signed links: a forged or expired one is no gift, and the normal paywall applies
- Lock an article again and its gift links stop opening it
- Seven days by default, set once; your own server can make any link shorter
Inside the port deal, six months on
The rule behind it
IfProduct is All AccessandGifts sent under 5 · rolling 30 days→Allow
Each link1 article10 devices7 days
Also in Subscriptions
Built for the billing edge cases
Your billing history, read in
Accounts, subscriptions, invoices, transactions, coupons and the catalogue are read from Recurly once at the start, then kept current by its webhooks.
Billing screens for your team
Subscriptions by status (trialing, active, past due, paused, ended), plus invoices, transactions, prices, coupons and currencies, with no login to your provider.
Trials taken once
Trial reuse is checked before the card is charged: once per reader by default.
Introductory discounts that actually bill
A percentage, or a fixed amount per currency, billed by your provider's own coupon. Publishing refuses a discount with no coupon behind it.
Stop selling without cutting anyone off
Archive an offer and it stops selling: publishing won't let a paywall rule keep offering it. Everyone who bought it keeps their access.
Know how each reader was sold
Show students a student offer and everyone else the standard one: the audience each reader bought under is something your paywall rules can test.
Offers that know renewal is coming
Days until access runs out is something any rule can test, so a reader 14 days from renewal can see a different offer than one 300 days out.
A purchase that finishes itself
If anything fails between the charge and the access, EdgeKit finds the paid purchase and writes the missing access. The repair only reads your provider; it never charges a card.
Beside, not instead
Your provider keeps billing
Payments stay with your provider, and Recurly is connected end to end today. Upgrades, cancellations and refunds are still made in your provider, as now: EdgeKit follows each one, but has no screen for them yet.
Adoption
From connection to live
White-glove onboarding: we set it up with you, start to finish.
- 01
Connect your billing provider
Add its API key and point its webhooks at EdgeKit. Accounts, subscriptions, invoices and the catalogue are read in, then kept current.
- 02
Say what each price opens
Map your provider's prices to the titles and sections they unlock, then write the offers you sell on top.
- 03
Put the offer in your paywall
A paywall rule returns the offer. Your page renders it in your design and checks out with one call.
- 04
Publish
A published change is live in 60 seconds. From then on, renewals, pauses and endings move access on their own.
Questions
Asked before every demo
Do we have to leave our billing provider?
No. EdgeKit reads your provider and moves access from it; the card, the money and the invoice stay where they are. Stripe, Recurly or Arc XP subscriptions stay as they are.
What happens when a reader's card fails?
One policy decides it, agreed with EdgeKit at setup. By default they keep reading while your provider retries the card: its retry schedule is the grace period. Choose suspend, and a past-due invoice pauses access until it is paid. Paying restores access on its own. If the retries fail and the subscription ends, access ends and the reason is recorded.
Does the reader leave the page to pay?
No. Checkout runs on your page, in your design. The card fields are your provider's, so card numbers go straight to it and never to EdgeKit. Someone who is not signed in gives an email and is subscribed in the same step, and bank challenges run in the page. Hosted payment pages for your billing provider, on your own domain, are coming soon.
Can we sell to companies?
Yes. EdgeKit syncs corporate accounts from your billing and subscription provider.
How do gift links avoid being passed around?
Each link is signed, opens one article, expires after a set number of days (seven by default) and opens on as many devices as you allow. Who can gift and how many a month are rules you write. A forged or expired link counts as no gift, and an article you lock again refuses it.
Who changes offers and prices?
Your commercial team edits offers in the EdgeKit console (name, audience, trial, introductory discount, whether it is on sale) and publishes them like any other change, live in 60 seconds. The price itself is your provider's; EdgeKit records which of its prices each offer sells.
Can we take Subscriptions on its own?
It is built to run with EdgeKit Paywall: the offer a reader buys is one a paywall rule showed them, and access is what the paywall reads. Your own pages can also read a signed-in reader's access through EdgeKit's API.