Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

Content Credits SDK

contentcredits.com

  • Free plan
  • Web
  • Browser extension
  • API

What Content Credits SDK is

Content Credits SDK lets readers pay for individual premium articles and gives publishers a way to earn from casual readers alongside existing subscriptions and paywalls. Readers use one account and wallet across participating publishers, buy credits, and pay an article’s credit price to unlock it. The SDK can reveal paid content without reloading the page. Publishers set their own prices and access rules while retaining control of their content and audience. Integration options include a WordPress plugin, JavaScript SDK, npm package, and custom paywalls; named frameworks include Next.js, React, and Vue. Publisher tools include analytics about reader behavior and article performance, plus engagement features intended to encourage longer visits, deeper scrolling, and ad impressions. The publisher plan is free to join, but Content Credits takes a percentage of micropayments; payouts are monthly and include a detailed report. Reader payments are processed by PayPal, and Content Credits says it does not store payment information. Credits have no cash value, are non-refundable and non-transferable, and may expire after 12 months of inactivity.

Who it suits

Content Credits SDK is for publishers seeking revenue from occasional readers and readers who want article-level access without another monthly subscription. It supports WordPress and custom CMSs as well as named JavaScript frameworks.

Good to know, and what to watch

  • Readers can unlock articles without a monthly subscription
  • Publishers set prices and access rules
  • Integrations include a WordPress plugin and JavaScript SDK
  • Publishers receive monthly payouts with detailed reports
  • Content Credits takes a percentage of micropayments
  • Credits are non-refundable and non-transferable
  • Credits may expire after 12 months of inactivity

Reader pay-per-article

—

Publisher

Free

Free plan

Getting started

  1. Open https://contentcredits.com/
  2. Choose a publisher integration route: WordPress plugin, JavaScript SDK, npm package, or custom paywall
  3. Connect the service to WordPress, a custom CMS, Next.js, React, or Vue
  4. Set article prices and access rules
  5. Readers buy credits through PayPal using a credit card or digital wallet

Limits to check

The free Publisher plan is free to join, but Content Credits takes a percentage of micropayments. Reader credits have no cash value, cannot be refunded or transferred, and may expire after 12 months without activity.

The Club's review

Content Credits SDK lets publishers charge readers for individual premium articles, and it suits publications looking to monetize casual visitors alongside subscriptions or existing paywalls. Its strongest case is publisher control over pricing and access; the trade-off is a percentage fee on micropayments and credits that readers cannot reclaim or transfer.

Overview

The SDK puts article-level purchases into a publisher’s existing access setup: premium content stays hidden until a reader pays its credit price, then appears without a page reload. Publishers retain control of their content, audience, prices and access rules, making this a lighter option than replacing a paywall or rebuilding a publication’s site.

Readers use one account and wallet across participating publishers, buying access as needed rather than adding another monthly subscription. That model is most useful for occasional readers; it is less appealing to anyone who wants refundable, transferable cash-like credits.

Key features

Integration routes include a WordPress plugin, JavaScript SDK, npm package and custom paywalls. The npm package supports Next.js, React and Vue, while the publisher page describes use with WordPress, custom CMSs and modern JavaScript frameworks without a full rebuild. The SDK checks for the Content Credits Chrome extension first, then falls back to an API purchase flow if the extension is absent. This gives publishers several ways to fit article purchases into their stack.

Publishers receive analytics about reader behavior and article performance, which can inform content strategy. The platform also describes “sticky” engagement features intended to keep readers on the site longer and increase scroll depth and ad impressions. Those tools complement monetization, though their stated purpose is not a guarantee of improved engagement or revenue.

Readers can pay by credit card or digital wallet. Payments are processed through PayPal, and Content Credits says it does not store payment information. Its privacy policy also says it uses industry-standard security practices while acknowledging that absolute security cannot be guaranteed.

Libraries can participate through referral codes or links and earn a share of linked transaction revenue, with no upfront cost or contracts. That makes the partner program a possible fit for libraries that want to direct patrons to participating publications without taking on an initial fee.

Pricing

The Publisher plan is free to join. Publishers pay no joining fee, but Content Credits takes a percentage of micropayments; payouts arrive monthly with a detailed report. The arrangement keeps the initial cost low, while the fee means publishers should weigh transaction revenue against the share retained by the platform.

Reader pay-per-article has no listed price: readers pay for articles as needed, with no subscription fees or hidden costs. The article price is set by the publisher, so this approach suits readers who want occasional access rather than a recurring subscription. Credits have no cash value, are non-refundable and non-transferable, and may expire after 12 months of inactivity; readers should avoid buying more than they expect to use.

Platforms

Content Credits supports API, extension and web access. Publisher integrations cover WordPress and custom CMSs as well as Next.js, React and Vue, providing options for both established publication sites and modern frontend stacks.

Who it's for

This is a good fit for publishers seeking revenue from casual readers without dismantling subscriptions or an existing paywall, particularly those using the supported CMSs and frameworks. Readers who want occasional access across participating publishers may also prefer one shared wallet to another monthly commitment. It is a weaker fit for readers who need unused balances refunded or transferred, and for publishers unwilling to give up a percentage of micropayment revenue.

Pros and cons

  • Pros: Publishers set article prices and access rules while retaining control of their content and audience.
  • Pros: WordPress, JavaScript, npm and custom-paywall integration paths can accommodate a range of publisher setups without requiring a full rebuild.
  • Pros: A shared reader account and wallet enable pay-per-article access across participating publishers without a monthly subscription.
  • Pros: Free publisher joining and monthly payouts lower the barrier to trying the model.
  • Cons: Content Credits takes a percentage of micropayments, reducing publishers’ proceeds from each purchase.
  • Cons: Credits cannot be refunded or transferred and may expire after 12 months of inactivity, which makes unused balances a real reader risk.

Alternatives

Paywall Software is a broader category to explore when comparing paywall approaches.

codoc is worth considering for buyers who want a freemium platform with a free trial and a pro plan at ¥9,800 a month, rather than Content Credits’ percentage-based publisher model.

Pelcro may suit publishers seeking broader customer and subscription tooling: its free plan covers 100 customers, while Advanced costs $450 a month for up to 2,000 customers.

Cleeng is an alternative for subscription businesses: its free Merchant Basic plan supports up to 10k subscribers and includes global payment processing, local tax calculation, and fraud and chargeback management.

Admiral may be a better fit for teams looking for paid subscriptions, paywalls and donations with audience segmentation and customizable calls to action.

Pay-To-View Lite is a WordPress option with a free tier for fixed rental prices and durations, suited to publishers who want that simpler rental model.

Uix Page Builder, Milkie and Paperwall are other alternatives.

Verdict

Choose Content Credits SDK if you publish premium articles and want to sell one-off access while keeping control of pricing and working alongside an existing paywall. The free-to-join publisher plan and multiple integration routes make it a practical option for casual-reader revenue; look elsewhere if the micropayment share or the restrictions on unused credits do not suit your business or audience.

The verdict

Content Credits SDK offers a way to sell individual article access while keeping publisher pricing and access rules in the publisher’s hands. Publishers should account for the micropayment share, and readers should note the restrictions on unused credits.

Questions people ask

Is there a free publisher plan?

Yes. The Publisher plan is free, and publishers can join without an upfront cost.

How do readers pay?

Readers buy credits and can pay with credit cards or digital wallets. PayPal processes the payments.

Which publishing systems are supported?

Supported environments include WordPress, custom CMSs, Next.js, React, and Vue. Integration options include a WordPress plugin, JavaScript SDK, npm package, and custom paywalls.

Are reader subscriptions required?

No. Readers use one account and wallet to pay for articles as needed, without subscription fees.

How are publishers paid?

Publishers receive monthly payouts with a detailed payment report. Content Credits takes a percentage of micropayments.

Can it work with an existing paywall?

Yes. Publishers retain control of access and can use Content Credits alongside an existing paywall or subscription setup.

What the maker publishes

Credit limits
The terms say credits have no cash value, are non-refundable and non-transferable, and may expire after 12 months of inactivity. source
Engagement and analytics
The platform describes tools for reader behavior analytics and features intended to increase time on site, engagement, and ad impressions. source
Engagement features
The site says its “sticky” features encourage readers to stay longer and increase scroll depth and ad impressions. source
Frameworks
The publisher page names Next.js, React, and Vue as supported modern frontend stacks for the npm package. source
Framework support
The publisher page names Next.js, React, and Vue among the supported modern frontend stacks. source
Insights
The platform offers publishers analytics about reader behavior and article performance to inform content strategy. source
Integrations
Integration options include a WordPress plugin, JavaScript SDK, npm package, and support for custom paywalls. source
Intended users
The product is aimed at publishers seeking revenue from casual readers and readers who want occasional access without another subscription. source
Libraries
The library partner program offers libraries a share of revenue from transactions linked to their referral codes or links, with no upfront cost or contracts. source
Maker
The about page identifies Adam Koehler as the originator of the Content Credits idea. source
Payment processor
The privacy policy says payments are processed by PayPal and that Content Credits does not store payment information. source
Payments
The maker says reader payments are processed through PayPal and that payment details are not stored by Content Credits. source
Payouts
The FAQ says publishers are paid monthly and receive a detailed report with the payment. source
Paywall
The SDK can hide premium content until a reader pays the article’s credit price, then reveal it without a page reload. source
Publisher audience
The publisher page describes the product for publications using WordPress, custom CMSs, or modern JavaScript frameworks, without requiring a full rebuild. source
Publisher control
Publishers set their own pricing and retain control over content access while using Content Credits with their existing paywall. source
Publisher controls
Publishers can set their own pricing and retain control of their content, audience, and access rules. source
Publisher fees
The FAQ says joining is free for publishers and that Content Credits takes a small percentage of micropayments. source
Purpose
Content Credits lets readers pay per article to access premium content and helps publishers monetize casual traffic alongside existing subscriptions and paywalls. source
Reader access
Readers can use one account to access articles across a growing network of publishers without a monthly subscription. source
Reader accounts
Readers can use one account and wallet to access articles across participating publishers without a monthly subscription. source
Reader payment
Readers buy credits through the payment system, and the FAQ lists credit cards and digital wallets as payment methods. source
SDK behavior
The SDK checks for the Content Credits Chrome extension first and falls back to an API-based purchase flow when the extension is absent. source
Security
The privacy policy says it uses industry-standard security practices to protect user data but cannot guarantee absolute security. source

Checked against the maker's pages on 8 Oct 2026.