MicroPayments – Fans Paysite: Paid Creator Subscriptions, Digital Assets, Wallet

Build your own fans paysite with WordPress. MicroPayments – Fans Paysite provides the foundation for a complete creator-content business: sell videos, pictures, audio, documents and posts through individual purchases, site memberships and creator subscriptions. Create a dedicated home for one creator or a platform where multiple creators manage their own work and fans discover whom to support.

Designed for site owners, entrepreneurs and developers, the solution brings the main journeys together: creators publish and offer content, fans join and buy access, and administrators configure accounts, payments and moderation. Connect the optional Video Share VOD and Picture Gallery plugins for dedicated video and picture management; the included catalog, wallets and content workspaces also work independently.

A self-hosted site gives you control of your content, customer data, branding, editorial rules and monetization choices. You operate your own platform rather than depend on a creator platform’s revenue-sharing and editorial model. There is no mandatory VideoWhisper revenue share for using this plugin; hosting, payment processing and any commission you configure for your own site remain separate.

Key features and benefits

• Bring your library together: present posts, videos, pictures, audio and documents in Styled tiles, Cards, List, Creator feed or Justified layouts, with search, filters and ordinary page navigation.
• Choose how to sell access: offer creator subscription tiers, individual purchases or optional one-time site memberships through WooCommerce. Describe the price, access period and purchase terms before checkout.
• Give creators a working studio: manage their own content, drafts, prices, subscription offers and announcements from dedicated frontend workspaces.
• Help fans find their way back: optional creator profiles, approved local avatars, free following and a private Following feed connect discovery with returning visits. Bookmarks and playback memory are separate opt-ins.
• Start solo or grow a community: review Single creator or Multiple creators setup choices before applying them. Keep existing pages, roles, wallets and access settings.
• Welcome each role clearly: optional dedicated fan signup, creator applications, login and password recovery work with native WordPress accounts. Leave them off when another system manages accounts.
• Keep publishing under your control: review creator content, allow selected trusted roles or grant revocable future-publishing approval to a creator. New member content can optionally open on a calendar date or after elapsed days from its own current membership payment.
• Make previews useful: show approved promotional images, independent public audio/video samples, duration and current offers. Add stars, likes or both with Rate Star Review.

Try the interactive content demo | Documentation and shortcodes | WordPress.org support

Popular ways to use MicroPayments

• A single creator’s library: combine public previews, creator membership offers and individual video, picture or document purchases.
• A multi-creator community: give creators their own profiles and studios while fans browse one mixed-media catalog or follow favorite creators.
• A members’ resource library: sell one-time access to explicitly selected resources, with clear duration, purchase terms and private membership history.
• An audio and download collection: present format, verified duration and file size, with separately approved click-to-play samples and optional access-checked full audio.

From first setup to returning fans

1. Choose your creator model. Open Creator setup, review the preview and select the pages and presentation your site needs.
2. Prepare a small library. Add native posts/downloads, or connect Video Share VOD and Picture Gallery for dedicated media management. The optional Media Capture plugin adds uploads, video/audio recording, webcam photos and screenshots.
3. Review the offer and audience. Configure the native price or membership rules, purchase terms and publishing approval. Use the destination editor to confirm the final item.
4. Publish and test as a fan. Check approved previews, discovery, the configured checkout and access with a separate permitted account. Fans can then return through their own purchases, membership history or Following feed.

Native catalog block and reviewed draft releases

In the WordPress editor, insert Fans paysite catalog and choose layout, content type, creator, category and visitor controls in the block sidebar. Its preview uses the existing published catalog; open the page to test filters as a separate fan. Existing [videowhisper_content_list] shortcodes continue to work. Blocks never select private buyer or creator workspaces.

Administrators can open MicroPayments > Draft release calendar from Publication readiness or the VideoWhisper toolbar. Assign site plans in the native editor first, select up to 20 eligible new drafts with no existing delay, choose a calendar or paid-start sequence and review every row. Confirm the exact preview before saving; changed content, permissions, timezone or plan terms require another review. The batch saves member-release rules, not WordPress publication dates. Publish or submit each item separately through its native editor. Existing purchases, approvals, expiry and originals stay native. The first atomic batch adapter requires core wpdb, MySQL/MariaDB with InnoDB content tables and no persistent object-cache drop-in; individual native editors remain available on other setups.

Memberships, wallets and checkout

The included wallet, catalog and content workspaces work independently. Configure creator tiers with labels, descriptions, prices and durations; an item can also have its own purchase price. Donations, goals and supported credit-package workflows are available alongside content access.

Optional WooCommerce integration adds product checkout and one-time fixed-term site memberships. Each purchase retains its own payment start and expiry; overlapping purchases do not stack unused time or renew automatically. Current paid status, ownership, refunds and expiry control access. Existing wallet, role and creator-subscription rules remain separate. WooCommerce sales do not automatically credit a creator’s token wallet.

For new member content, optional calendar or elapsed-day availability affects only the site-membership route. It does not schedule WordPress publication, approve content or extend a purchase’s expiry. Existing content is not migrated. Review and explicitly save member access before publishing; after publication, release rules can move earlier or be disabled, but cannot become more restrictive. Detailed setup and access cases are in the FAQ.

Brief purchase wording, expandable details and a selectable complete-terms page help buyers understand an offer. Native WooCommerce checkout acceptance remains authoritative. Available gateways, supported countries, fees and merchant eligibility depend on the selected extensions and provider. Qualify your site’s checkout before opening sales.

Creator profiles and content presentation

Choose eligible public-profile roles separately from publishing permissions. Opted-in profiles can show an introduction, biography, creative focus, website, approved promotional cover/avatar, collections, native content and current offers. Initials remain the default avatar. Following is free and grants neither paid access nor an email subscription.

Separate buyer views explain recorded purchases, completed WooCommerce orders and supported content currently included with creator subscriptions. Private membership history shows each source’s original term and own order link. The optional FansPaysite theme supports live light/dark/system presentation; other compatible themes remain usable.

Public previews use separately approved promotional media. Full content keeps its native audience, approval, channel, purchase and delivery checks. A hidden page does not make an ordinary public file URL private; configure protected delivery at the storage origin when needed.

Reviewed editorial suggestions

Use Agent assistance to preview a clearer title and excerpt. With Site Manager 1.27.0 or later and the separately enabled content review/write tools, choose Create private WordPress review, open its before/after comparison and approve the exact fields there. The proposal expires after ten minutes and does not itself update content. Changed items and revoked permissions require a fresh review. Read-only agent advice never grants saving or publishing authority; each plugin remains usable without Site Manager. SEO uses the active provider and its separate Site Manager review workflow.

Optional integrations

• Video Share VOD and Picture Gallery: dedicated video and picture management, including explicit site-membership adapters.
• Media Capture: a shared upload/record/review workflow. Each destination keeps its own permissions and originals.
• WooCommerce: optional product checkout, one-time memberships, credit-package products and completed-order history.
• TeraWallet and myCRED: optional wallet/points integrations with their own configuration and applicable extensions.
• Rate Star Review: optional stars, likes and rating-based sorting.
• Broadcast Live Video and Paid Videochat: optional live-content integrations with their own streaming requirements. BuddyPress/BuddyBoss and PeepSo integrations remain optional.

External services and privacy

Google reCAPTCHA is optional and is configured with the site’s reCAPTCHA keys for the guest content-upload form. When enabled and that form is rendered, the visitor’s browser loads Google’s reCAPTCHA JavaScript from https://www.google.com/recaptcha/api.js . Google receives the browser connection information, including IP address, and processes browser/device and interaction information under its policies to assess abuse. When the visitor submits the form, this plugin sends the generated response token and the site’s verification secret to Google’s verification service at https://www.google.com/recaptcha/api/siteverify . The upload’s content file, title, description and email fields are not included in that verification request. With no reCAPTCHA site key configured, the guest form does not load this Google integration.

Service information: https://developers.google.com/recaptcha/ . Privacy policy: https://policies.google.com/privacy . Terms: https://policies.google.com/terms . Site owners should explain this optional service in their own privacy/consent notices before enabling it.

Frontend account forms have their own disabled-by-default reCAPTCHA switch and keys under Accounts and creators. When enabled, the visitor explicitly checks the Google verification notice and submits before this integration loads Google. Verification sends the response token and server-held secret to the same fixed service; account passwords, email fields and profile text are not included in that verification request. The browser still sends connection and interaction information to Google. Configure keys for the site’s hostname and review current Google service terms/limits. The plugin does not create a Google account automatically.

Frontend forms use an essential, short-lived HttpOnly guest-session cookie to bind security nonces; native WordPress cookies maintain authenticated sessions. Temporary request limits use site-salted hashes and expire after fifteen minutes rather than storing raw addresses in plugin records. Creator applications retain a minimal current status/request/review timestamp. Public profile fields and private follows are scoped to the current WordPress site. Native privacy export/erasure includes these profile, application and follow records; erasure removes that presentation/community data without deleting original media, accounts, native roles, purchases, subscriptions or wallets. Deactivation retains data. WordPress controls password storage, account deletion and shared network users.

Optional payment/wallet extensions communicate with the processors the administrator configures when their checkout, funding or billing features are used. Those extensions control the payment-data requests; review their documentation and privacy/terms for the actual provider. MicroPayments stores site content, user, wallet, subscription, purchase and transaction records in WordPress; third-party extensions may retain additional records.

The included catalog and workspaces run on the WordPress site. Media storage and streaming integrations retain their own configuration requirements. Application paywalls and preview cards do not make an ordinary public media URL private; private media needs independently protected delivery at its storage/streaming origin.

Build and review with less guesswork

Use native editor blocks with presentation presets and category search. Choose a mixed-content library, creator feed or visual gallery while retaining your selected audience and category filters. Optional Site Manager tools read permitted publication guidance or prepare plain-text editorial suggestions for review. They cannot save, publish, approve or change access. Each plugin remains independently usable.