Content Credits SDK

Content Credits SDK is an article-level payment and access tool for publishers, paired with a shared wallet for readers. It best suits publishers looking to earn from occasional visitors and readers who want selected articles without another subscription. Its appeal is that it can work alongside existing access models; the micropayment fee and limits on credits temper that flexibility.

Overview

The SDK can keep premium articles hidden until a reader pays their credit price, then reveal them without reloading the page. Publishers set prices and access rules while keeping control of their content and audience, so Content Credits can complement an existing subscription or paywall rather than require a full rebuild. That makes it a practical option for testing per-article access with casual readers, though each publisher still needs to weigh whether the micropayment share suits its economics.

Readers use one account and wallet across participating publishers, paying for individual articles instead of committing to a monthly subscription. That is a better fit for occasional reading than for someone who regularly wants broad access: credits have no cash value, cannot be refunded or transferred, and may expire after 12 months of inactivity.

Key features

Publishers can connect through a WordPress plugin, JavaScript SDK, npm package or custom paywall. The npm package supports Next.js, React and Vue, and the SDK checks for the Content Credits Chrome extension before using an API-based purchase flow when it is absent. This gives publishers on those stacks several routes to integration; the product is less compelling for teams whose systems fall outside the named options and custom-paywall route.

Reader payments use credit cards or digital wallets and are processed through PayPal. Content Credits says it does not store payment information, and its privacy policy describes industry-standard security practices while acknowledging that absolute security cannot be guaranteed. Publishers also get analytics on reader behavior and article performance, plus features intended to increase time on site, scroll depth and ad impressions. Those tools may help publishers assess casual-reader engagement, but the stated engagement aims are not a promise of higher revenue.

Publishers receive monthly payouts with a detailed payment report. The library partner program offers libraries a share of revenue from transactions linked to their referral codes or links, with no upfront cost or contract. That is a distinct route for libraries to participate, while the core product remains focused on article purchases and publisher access.

Pricing

Publisher access is free to join at no cost. There is no upfront publisher charge, but Content Credits takes a percentage of micropayments, so the actual return depends in part on transaction volume and the share retained. Monthly payouts and a detailed report provide a regular accounting cycle.

Readers pay for articles as needed, with no subscription fees or hidden costs; the per-article price is set by each publisher. There is no recurring reader plan to compare, but credits are non-refundable and non-transferable and may expire after 12 months without activity. Readers should buy with those limits in mind rather than treat the wallet as cash.

Platforms

Content Credits supports API, extension and web access. Publisher integrations cover WordPress and custom CMSs, with Next.js, React and Vue named for modern frontend use. This range suits both established publication sites and teams integrating through a JavaScript stack.

Who it's for

Choose Content Credits if you publish premium articles and want a per-article option for casual visitors alongside subscriptions or an existing paywall. It is also suited to readers who buy access occasionally across participating publications and prefer that to another monthly bill. Readers seeking unrestricted access or flexibility to cash out unused credits should look elsewhere.

Pros and cons

• Publisher-controlled prices and access: publishers can add article purchases without handing over control of content or replacing their existing paywall.
• Several integration routes: a WordPress plugin, JavaScript SDK, npm package and custom-paywall support accommodate the named CMS and frontend options.
• Free publisher entry: there is no joining cost, though a percentage of micropayments goes to Content Credits.
• Shared reader wallet: one account can serve articles across participating publishers without monthly subscriptions, which favors occasional readers.
• Restrictive credit terms: balances cannot be refunded or transferred, carry no cash value and may expire after 12 months of inactivity.
• Revenue depends on micropayments: publishers give up a percentage of transactions, which can reduce the benefit when article purchases are small.

Alternatives

Pelcro is a better fit for publishers seeking a freemium platform with a free tier for up to 100 customers and a paid Advanced plan for up to 2,000 customers. Content Credits instead centers on per-article micropayments and has no monthly publisher charge.

Cleeng suits publishers who want its free Merchant Basic tier for up to 10,000 subscribers, with global payment processing, local tax calculation, and fraud and chargeback management. Content Credits is more specifically aimed at casual readers paying article by article.

codoc is an alternative for publishers looking at a free content-sales plan with a 15% sales fee, or a paid API plan priced at 9,800 JPY per month. Content Credits offers free publisher entry with a percentage fee but focuses on reader credits for premium articles.

Pay-To-View Lite is a WordPress option for fixed rental prices and durations, with limited features and support on its free Lite plan; its Pro plan costs $29, paid once. Content Credits is the closer match when the goal is per-article micropayments alongside existing access models.

Pigeon offers a WordPress demo mode with no transactions on its free Experiment plan, followed by a Publishers plan at $99 a month. It may suit a publisher seeking that paid monthly option instead of Content Credits' transaction-percentage model.

Steady is a free-to-use alternative with no audience limits; it takes a 10% fee when publishers earn, plus variable payment-provider fees and applicable VAT. Compare its fee structure with Content Credits' percentage of micropayments when choosing a monetization model.

Uix Page Builder is a free WordPress plugin credited to UIUX Lab.

Milkie is a free, open-source option under the MIT license.

For more options, browse Paywall Software.

Verdict

Content Credits SDK is a sensible choice for publishers who want to monetize casual readers with individual article purchases while retaining their existing access setup. Its integration options, publisher controls and shared reader wallet make that model workable across participating sites. Look elsewhere if readers need refundable or transferable balances, or if the publisher's micropayment share makes small article purchases unattractive.