Content Credits SDK

Overview

Content Credits SDK gives publishers an article-level payment option for readers who visit occasionally, and suits publications that want to monetize that audience without rebuilding their existing paywall. Its strongest case is the shared reader wallet across participating publishers; the percentage taken from micropayments and the restrictions on credits are meaningful trade-offs.

Key features

The SDK can keep a premium article hidden until a reader pays its credit price, then reveal it without reloading the page. Publishers set the price and access rules and retain control of their content and audience, so the product can complement existing subscriptions and paywalls rather than replace them. Readers use one account and wallet across participating publications, making one-off access practical without another monthly subscription.

Integration routes include a WordPress plugin, JavaScript SDK, npm package and custom paywall support. The npm package names Next.js, React and Vue, while the SDK checks for the Content Credits Chrome extension before falling back to an API purchase flow. This gives publishers using those tools several ways to add article payments without a full rebuild.

Publishers also get analytics on reader behavior and article performance, plus features intended to increase time on site, engagement and ad impressions. Those tools may help inform content strategy, though the stated purpose of the engagement features is not a substitute for evidence of their effect. Publishers are paid monthly with a detailed report, but Content Credits takes a percentage of micropayments, which matters most for low-priced articles.

Readers can buy credits by card or digital wallet. Payments are processed through PayPal, and Content Credits says it does not store payment details. Credits have no cash value, are non-refundable and non-transferable, and may expire after 12 months of inactivity; occasional users should avoid leaving a balance idle.

Pricing

The Publisher plan is free to join, with monthly payouts; the cost is a percentage of micropayments rather than a stated subscription. That makes it a low-commitment option for publishers testing article purchases, though the fee reduces proceeds from each transaction.

Reader pay-per-article has no listed price: readers pay for articles as needed, with no subscription fees or hidden costs. There are no monthly subscription tiers or stated usage caps to compare. The important limit is the credit policy: unused credits may expire after 12 months of inactivity and cannot be refunded or transferred.

Platforms

Content Credits supports web, API and extension access. Publisher integrations cover WordPress and custom CMSs, as well as Next.js, React and Vue. The extension-first SDK flow falls back to an API purchase flow when the Chrome extension is not present.

Who it's for

This is a good fit for publishers with casual traffic who want to add paid article access alongside subscriptions or an existing paywall, especially those using WordPress or the named JavaScript frameworks. It is less compelling for publishers who need to avoid transaction-based fees or whose business depends on retaining a larger share of every small payment.

Readers who only want occasional access across participating publishers may prefer buying credits to taking on another subscription. It is a weaker fit for anyone who expects to keep unused balances indefinitely or needs payments to be refundable or transferable.

Pros and cons

• Pros: Publishers control article prices and access rules while keeping their existing paywall and audience.
• Pros: A shared account and wallet let readers buy individual articles across participating publishers without monthly subscriptions.
• Pros: WordPress, custom paywall and modern JavaScript integration options avoid requiring a full rebuild.
• Cons: Publishers give up a percentage of micropayments, so transaction economics deserve scrutiny for low-priced articles.
• Cons: Credits are non-refundable and non-transferable, have no cash value, and can expire after 12 months of inactivity.

Alternatives

Paywall Software is a useful category to browse if you want to compare a broader range of approaches.

Choose Pelcro if you want a freemium service with a published Free plan capped at 100 customers or an Advanced plan priced at $450 a month for up to 2,000 customers.

Cleeng is another freemium option, with a free Merchant Basic plan for up to 10k subscribers and global payment processing, local tax calculation, and fraud and chargeback management.

Consider codoc for its free plan with a 15% sales fee and a codoc pro plan at ¥9,800 a month; its platform availability includes API, extension and web.

Milkie is a free, web-based alternative that is open source and MIT licensed.

Paperwall may suit publishers who want a free, open-source protocol that can be forked, audited or self-hosted under GPL-3.0.

Pay-To-View Lite offers a free WordPress plan with fixed rental pricing and duration, while its Pro plan costs 29.00 USD once.

Pigeon provides a free WordPress demo without transactions; its Publishers plan costs $99 a month.

PostGate is free without a monthly subscription and charges a 5% platform fee on successful transactions, with Stripe processing fees separate.

Verdict

Content Credits SDK is a sensible choice for publishers seeking article-level revenue from casual readers while preserving their current paywall and pricing control. Its shared wallet and several integration paths address a clear use case, but publishers should weigh the micropayment percentage against likely transaction sizes, and readers should buy credits with the expiry and non-refund terms in mind. Look elsewhere if those economics or credit restrictions do not fit.