Content Credits SDK vs PostGate
Content Credits SDK
contentcredits.comPostGate
qodesphere.comSide by side
| Figure | Content Credits SDK | PostGate |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | Yes |
| API | Yes | — |
| Plans published | 2 | 1 |
| Spec score · Paywall Software | 8.8 (#2) | 7.2 (#25) |
| Integrations | Integration options include a WordPress plugin, JavaScript SDK, npm package, and support for custom paywalls. | PostGate connects to Stripe for payments and supports optional Google Sign-In configured with Google OAuth credentials. |
| Payments | The maker says reader payments are processed through PayPal and that payment details are not stored by Content Credits. | It supports one-time purchases and recurring subscriptions through Stripe-hosted Checkout. |
| Purpose | Content Credits lets readers pay per article to access premium content and helps publishers monetize casual traffic alongside existing subscriptions and paywalls. | PostGate is a WordPress paywall and content monetization plugin for selling access to premium content. |
| Security | The privacy policy says it uses industry-standard security practices to protect user data but cannot guarantee absolute security. | Stripe-hosted Checkout handles payment details, verified webhooks update orders and access, and PostGate says it does not store card details on the WordPress server. |
| Support | The maker says it assists publishers with integration and provides analytics and support; the publisher page invites interested organizations to contact its team. | The product page directs users to PostGate documentation for setup guides, feature details, and troubleshooting help. |
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.
PostGate
PostGate is a WordPress plugin for charging for access to premium content. Publishers can protect an entire site or selected categories, posts, pages, supported custom post types, taxonomies and Gutenberg blocks. Access can require payment or login, and protected material unlocks after successful payment. Stripe-hosted Checkout supports one-time purchases and recurring subscriptions; public previews can be limited by paragraph count or word count. In the WordPress dashboard, publishers can track orders, subscriptions, payment status, revenue and premium-content performance. Subscribers manage billing details, invoices and subscriptions through Stripe Billing Portal. Optional Google Sign-In can be configured with Google OAuth credentials. PostGate says Stripe-hosted Checkout handles payment details, verified webhooks update orders and access, and card details are not stored on the WordPress server. The free plan has no monthly PostGate subscription, but successful transactions incur a 5% platform fee and Stripe processing fees apply separately. The plugin requires WordPress 6.2 or higher and PHP 8.1 or higher. It does not include community profiles or member directories.