Content Credits SDK vs InPlayer
Content Credits SDK
contentcredits.comInPlayer
inplayer.comSide by side
| Figure | Content Credits SDK | InPlayer |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | Yes |
| iOS | — | Yes |
| Android | — | Yes |
| API | Yes | Yes |
| Plans published | 2 | 1 |
| Spec score · Paywall Software | 8.8 (#2) | 7.6 (#13) |
| Integrations | Integration options include a WordPress plugin, JavaScript SDK, npm package, and support for custom paywalls. | The dashboard can connect to online video platforms and in-app platforms for in-app payments. |
| Payments | The maker says reader payments are processed through PayPal and that payment details are not stored by Content Credits. | The paywall supports geo-pricing, multiple currencies and languages, and multiple payment and pricing options. |
| Paywall | The SDK can hide premium content until a reader pays the article’s credit price, then reveal it without a page reload. | Its embeddable paywall supports authenticated pay-per-view and subscription access for videos or video collections. |
| Security | The privacy policy says it uses industry-standard security practices to protect user data but cannot guarantee absolute security. | InPlayer says public projects use HTTPS with TLS and that it is PCI DSS compliant, while noting PCI compliance is a shared responsibility. |
| Support | The maker says it assists publishers with integration and provides analytics and support; the publisher page invites interested organizations to contact its team. | InPlayer says clients and end users can receive support before, during, and after events in multiple languages, 24/7/365. |
Plans
Content Credits SDK
- PublisherFree
- Reader pay-per-articlePrice not published
In their own words
Content Credits SDK
Content Credits SDK lets publishers charge for individual premium articles while giving readers a way to pay only when they want access. Readers use one account and wallet across participating publishers, without a monthly subscription. The SDK can keep paid content hidden until a reader pays the article’s credit price, then reveal it without a page reload. Readers buy credits using credit cards or digital wallets; PayPal processes payments, and Content Credits says it does not store payment details. Publishers choose article prices and access rules and can use the service alongside an existing paywall. Integration options include a WordPress plugin, JavaScript SDK, npm package, and custom paywalls; named supported stacks include WordPress, custom CMSs, Next.js, React, and Vue. Publisher tools cover reader behavior and article performance, with features intended to encourage longer visits and deeper scrolling. Publisher participation is free, but Content Credits takes a percentage of micropayments; payouts are monthly with detailed reports. Credits have no cash value, are non-refundable and non-transferable, and may expire after 12 months of inactivity.