Offerlume Offerwall Rewards

Offerlume creates a landing page, dashboard, offerwall directory, history, referrals, withdrawal, terms, privacy, contact, registration, sign-in and password reset pages. Its own responsive template replaces the theme header and footer on these pages. Public pages do not show the member sidebar. WordPress stores the member accounts.

Site administrators can edit landing sections, FAQ, page labels and other portal text under Offerwall Rewards > Page content. Terms, privacy and other page content can be edited in the WordPress page editor. The site operator must replace the starter legal text with their actual policies before launch. No faucet, PTC or shortlinks are included.

A directory lists 19 optional networks, including CPX Research, Prime Earn, TimeWall, TheoremReach, BitLabs, Lootably, Notik, GemiAd, Monlix, ayeT Studios, Easy Surveys, Offerwall, Wannads, Pollfish, AdGate Media, Torox, RevU, inBrain and TapResearch. Names are optional setup choices, not endorsements or promises of approval. All networks start disabled. Administrators must obtain their own publisher agreements and verify that the network permits their incentivized traffic and redemption model.

BitLabs has a built-in signed callback. Other networks require separate server-side adapters that authenticate the actual network callback and send a signed normalized event to the plugin. Merely entering an offerwall URL and adapter secret cannot credit rewards. The provider setup screen links to publisher sites and available documentation. BitLabs signed debug callbacks confirm delivery without crediting points. Test actual conversions and reversals on staging before opening a network to members.

Members earn integer points only from confirmed callbacks and may receive referral bonuses. They can request manual payouts using methods enabled by the site operator, such as PayPal, Stripe Connect, crypto wallet, NOWPayments, bank transfer, FaucetPay, Skrill or Wise. The plugin reserves points and records payout status; it does not send money, call payout APIs or guarantee a cash value. The operator must settle each approved request externally and enter a real transaction reference.

External services and privacy

The plugin makes no external requests merely on activation or when browsing its pages. Opening an enabled offerwall sends the member’s numeric WordPress user ID in the administrator-configured external URL so the provider can attribute the offer. The network may collect additional device, offer, survey and activity data under its own policies. The plugin does not share the member email address with a network. Site administrators choose which networks to enable and must disclose their active providers, policies, retention, user rights and payout arrangements on their site’s own legal pages. Provider publisher signup and documentation links on the admin screen open only when an administrator clicks them.

BitLabs (the built-in integration) provides an offerwall and signed reward/reconciliation callbacks. A member’s numeric ID is sent when that member opens the BitLabs offerwall. BitLabs publisher terms: https://dashboard.bitlabs.ai/termsOfService ; BitLabs user privacy policy: https://bitlabs.ai/offerwall-privacy-policy . Integration documentation: https://developer.bitlabs.ai/docs/general-reward-callbacks . The site owner must read and comply with its current publisher agreement.

For other networks, the plugin supplies optional listings and a generic adapter endpoint only; no native network integration is bundled. The site administrator supplies the external provider URL, must document that provider’s current terms and privacy policy on the site’s pages, and must create or obtain an adapter that verifies the network signature before sending a normalized event. No data is sent to any disabled network. Enabling a network is a deliberate site-administrator setting, and its provider receives a numeric member ID only when the member opens its wall. Payment providers are not called by the plugin; payment destinations and references stay in WordPress until the operator handles a payout externally.

Locally stored data includes account IDs, referral relationships, conversion records, point balances, payout destinations and settlement references. The plugin registers a suggested WordPress privacy policy notice and personal-data export and erase callbacks; financial audit records are retained while completed payout destinations can be cleared. The site owner sets an appropriate retention period and handles legal requests. The plugin does not automatically remove database records when deactivated.

Callback security and testing

For BitLabs, configure the signed GET callback URL and parameter order shown in Offerwall Rewards settings. The plugin verifies the HMAC-SHA1 signature of the exact callback URL before processing a conversion. The BitLabs dashboard Callback Tester sends debug=true: valid signed debug requests are acknowledged and their receipt time shown in Provider setup, without creating points or reversing balances. A real allowed conversion on staging is required to test crediting. Full negative reconciliations with the original reference can reverse points; partial adjustments need manual review.

Other networks must call a trusted adapter, not the generic endpoint. The adapter verifies the native provider signature, maps eligible rewards to whole-number site points, ignores pending/sandbox events and POSTs JSON to /wp-json/offerlume/v1/callback/{provider}. Required fields: user_id (integer), transaction_id (unique ID), amount (positive integer points), status (approved or reversed), signature (hex HMAC-SHA256). Sign provider|user_id|transaction_id|amount|status with that provider’s adapter secret. Reversals use the original transaction ID, member ID and positive amount. The plugin deduplicates events. A URL or generic test POST alone does not prove that a provider integration works.