Money has to be right
A conversion, a streak bonus and a cashout all touch the same balance. If two requests can credit it at once, or a rejection does not claw the money back, the ledger drifts and never recovers.
Release 1.9.26 · Laravel 13 on PHP 8.3
Launch your own get-paid-to rewards platform
A self-hosted rewards business, in full. Members earn one coin balance from offer walls, surveys, daily missions, a spin wheel, login streaks and referrals, then request a cashout that you review and pay. You get the member storefront, the admin panel, the postback plumbing and the money ledger — as source code, with no vendor between you and your own balance.
Why buyers pick this over a starter package
Full unencrypted source
Laravel app, the one theme, admin panel and migrations. No encoder, no lock-in.
16 offer networks wired
Secret-authenticated postbacks on eleven, IP allow-lists on five, chargebacks reversed.
Fraud controls in the box
reCAPTCHA or hCaptcha, login throttles, a replay ledger and referral fraud heuristics.
Reviewed cashout queue
Requests debit inside a row lock, points are held until you approve, refunds are audited.
What ships in the box
24
tables in the shipped schema
16
offer-network postback endpoints
67
automated test methods in the suite
14
PHP extensions the installer verifies
30
pages of documentation
15
admin controllers
89
admin settings keys
4
payout methods seeded, all editable
Counts are of the files and schema in the release you receive. Offer-network accounts, payout accounts and mail credentials are deliberately not included — you supply your own.
Live Demo
Walk it before you buy it
The demo is the product on a public domain with demo mode switched on, so every screen has something in it. Its landing page hands you the member credentials and opens the admin panel in one click.
- The member storefront: the earn page, offer walls, missions, spin wheel, streak and referrals.
- The admin panel, reached without a password from the landing page — as a dedicated demo administrator, never a real one.
- The cashout queue: request a payout as a member and watch it wait for review.
- The demo sandbox: postbacks are refused and restricted admin screens are blocked, so a visitor cannot break anything.
The demo publishes its own member credentials on the landing page —
demo@zapcash.test / Demo@1234 — and the
administrator demo needs no password at all. The demo is a shared
environment: its balances, members and offers are not yours, and nothing
on it is a promise about earnings.
A rewards site is a money system, not a landing page
The members see coins and a spin wheel. You are running a ledger.
Anyone can sign up and claim
Farming is the default failure mode. Registration needs a captcha, a throttle, and enough friction that a scripted signup is not cheaper than a real member.
Every offer network speaks differently
Each network posts conversions back with its own parameter names and its own signature scheme. Each one is a separate parser to write, and an unsigned parser is a way to mint coins from the internet.
Paying out is the part you cannot automate on day one
You need a reviewed queue that holds the points until the money has actually left your account, a refund path for the requests you decline, and a decision about which accounts to pay.
Each of these is solved in the box, with the code in front of you rather than a vendor between you and your own balance.
What the platform actually does
Grouped by the job each part of the system performs. Five tabs, and every card on this page is a shipped screen.
The core loop, and the mechanics that bring a member back tomorrow. Offer walls, surveys, missions, a wheel, streaks, leaderboards and referrals — each with its own admin screen, each credit landing in the same ledger.
One integer coin ledger
Every credit and debit lands in a transaction row, and the earning tracker records what caused it. The member sees their own history on the transactions page; you see every tracked action across all members in the global tracker, which is how you answer “where did this balance come from”.
16 postback endpoints
Eleven networks authenticate with a secret, five by source-IP allow-list, and each provider's own scheme is implemented on top — HMAC-SHA256 with a constant-time compare on AdGem, hash-plus-IP on AdMantum. A chargeback reverses the credit the same way the credit applied it.
The guard fails closed
A callback whose secret is not configured is rejected before any parser runs — not skipped — and a replay ledger refuses the same delivery twice. A provider retrying, or a stranger posting guesses at your endpoint, cannot credit a balance twice.
A postback reference per network
The admin prints the callback URL and the parameters each connected provider needs, ready to paste into that network's dashboard — so connecting wall seven does not mean re-reading documentation you half remember.
A live offer feed
The Torox wall pulls its inventory server-side against your member's ID, with category filtering and a single-offer lookup, so the list is live rather than a snapshot a stale browser cache is showing.
Offer wall configurator
Thirteen walls ship seeded with blank credentials. Paste each network's keys in the admin and the wall URL is rebuilt with the per-member substitution in it. Surveys stay split from standard offers, so CPX Research and BitLabs get their own list.
Daily login streak
A consecutive-day bonus that grows every day it is kept: base plus (streak − 1) × increment, defaulting to 5 coins then 2 a day. Enabled out of the box, both numbers editable in the financial settings.
Daily missions
Four missions ship seeded, from 25 to 1,000 coins, each claimable once and checked server-side against what the member has actually done — a completed offer or a referred friend, not a checkbox they clicked. Game, quiz, offer and refer types are defined.
Spin wheel
Seven weighted segments seeded from 5 to 500 coins, drawn server-side against a daily spin limit (one a day by default) and written to the tracker like every other credit. The live wins feed sits underneath it.
Leaderboards with paid ranks
Lifetime, daily, weekly and monthly boards computed from the earning trackers, with nine rank rewards seeded — three periods, places one to three. The prizes are paid by a scheduled command that keeps an idempotency log, so a re-run cannot pay a place twice.
Referral programme
One link, /r/your-name. Flat join bonuses by default;
switch on tiers and Bronze to Platinum (0, 10, 50, 200 referrals)
raise the share from 5% to 20% plus a flat bonus. Commission pays on
the referred member's join bonus and on the coins they earn from
offer wall postbacks.
Welcome bonus, off by default
A one-time credit for new accounts, disabled until you set an amount. The credit is idempotent — a tracker row marks the account, so re-seeding or a race cannot pay it twice.
Referral commission is single-level.
Tiers change the rate, not the depth: there is no second tier of referrers.
Commission is paid on the referred member's join bonus and their offer wall
earnings — not on streak bonuses, wheel wins or leaderboard prizes. Both
limits are stated here because the product's own referral figure caption calls
the tiers “multi-level”, which the code contradicts.
Everything between a member asking for money and you paying it: methods you define, a debit that cannot double-spend, a queue with explicit states, and a refund path for every request you decline.
Methods you define
Four ship seeded — PayPal, Litecoin and Binance at 500 coins, Gift Card at 1,000 — as editable rows with their own minimum and required member fields. Add your own from the admin; the member's cashout page picks them up as they are.
The debit cannot double-spend
The request runs in a row-locked transaction that re-reads the balance before it moves anything. Two clicks, two tabs or a raced postback all arrive at the same lock, so the account cannot be drawn past its balance.
A five-state queue
Pending, approved, cancelled, returned, completed. Points are held from request to decision, and cancel or return puts them back with a tracker row. A guard makes paying that refund a second time impossible.
Review and action
Each request opens with the member, method, destination and amount together, and the approve, cancel and return controls beside them. The member watches the same request move state on their transactions page.
You set the exchange rate
Coin-to-dollar conversion is one admin number — 1,000 coins to the dollar, seeded — used across the dashboard figures. No live FX feed and no third-party pricing dependency: a quiet market cannot change what your screens say.
Cashout is processed by you, not by the software.
ZapCash has no automated payout adapter for any provider — no Stripe, no
PayPal API. The four seeded methods are manual payouts: the software debits and
holds the balance, queues the request and keeps the audit trail, then an admin
approves and pays out of band. Writing an adapter for your own provider is a
development task.
Registration is where a rewards site is won or lost, and money is where it is stolen. Two captcha providers behind one setting, a throttle on the entry points that matter, fraud heuristics on referrals, and a demo mode that sandboxes itself.
Two captcha providers
reCAPTCHA or hCaptcha, one active at a time, with the token verified server-side against the provider's endpoint — the browser is never taken at its word. Both ship off: add a key in settings to switch one on for registration and login.
Throttles where they matter
Five attempts on member and on admin login, 60 requests a minute on the API, six a minute on the email-verification routes, twenty an IP on demo auto-login — each counted on the user or address the route declares, before any work is done.
Referral fraud heuristics
Same registration IP, same device fingerprint, or a same-fingerprint IPv6 /64 block flags the account for review — each rule behind its own switch, each flag listed on the member record where you can clear it with the context in front of you.
Email verification you can require
A six-character code mailed on signup, and a middleware gate that holds member pages until it is checked — off until you turn it on. Password resets ride the same SMTP settings you configure once.
A locked installer
The six-step installer is session-sequenced, and step six writes a signed installation lock and clears the caches behind it. There is no install route left open after you finish.
Uploads verified before they land
Server-generated filenames, a detected-MIME allow-list and a decoded image check — a renamed executable is rejected by what the bytes are, not by what the extension claims to be.
Demo mode sandboxes itself
With DEMO_MODE on, postbacks are refused, restricted
admin screens are refused rather than merely hidden, and outbound
mail and HTTP are sandboxed. The public demo cannot be used to
credit real balances or reach real inboxes.
The screen you will live in. Fifteen controllers, seven settings screens, a dashboard with the figures that matter, and a CRUD screen for every mechanic on the members' side.
One administrator, fifteen controllers
Dashboard, users, offer walls, withdrawals, withdrawal requests, missions, wheel, leaderboard rewards, referral tiers, referrals, tracker, pages, FAQs, settings and auth — each its own controller. Single-admin by design: no role matrix to misconfigure.
A dashboard with the numbers
Members, joins today, earnings and referrals, a 14-day signup series, sparkline trends, top earners and top referrers — with points shown in dollars at the exchange rate you configured, not at a rate someone else publishes.
Seven settings screens, 89 keys
General, web configuration, financial, SMTP, socials, account and
PWA — captcha keys, referral and streak money, fraud switches,
coin value, mail credentials. All editable from the panel; no
.env surgery required after install.
CRUD for every mechanic
Missions, wheel segments, leaderboard rank rewards, referral tiers, payout methods and offer wall credentials each get their own screen — create, edit, toggle, delete — all database-driven, so next week's idea needs no deploy.
Cashout review with the money handled
The withdrawal requests queue with approve, cancel and return — each state change moving the points for you, refunds written to the tracker — beside the payout-method list and every member's withdrawal history.
Pages and FAQs from the panel
Three content pages and five FAQ rows ship seeded; edit them, add more, and toggle a question off to hide it without deleting it. Five social links come the same way, each enabled on its own.
Scheduled work runs on the Laravel scheduler.
Three
rewards:distribute runs a day — daily, weekly on Monday
and monthly on the 1st — plus a nightly demo reset when demo mode is on.
The host needs the standard schedule:run cron entry, which the
documentation spells out with the exact line to add.
The member side is one server-rendered Blade theme — no JavaScript build, no second application to deploy — with an installable PWA manifest, two social sign-ins and a privacy toggle that actually hides the member.
One theme, rendered on the server
Every member screen — earn, offers, missions, wheel, leaderboard, cashout, transactions, profile, invite — is Blade served by the same Laravel app. Nothing to build, nothing to keep in step with the backend, no separate hosting bill.
Installs as an app
A real manifest and service worker served from admin-managed settings — sixteen keys for name, icons, start URL, display mode and colours — so a member can add the site to their home screen and it opens like an app.
Email plus Google and Facebook
Password auth with remember-me, the optional verification code, and Google and Facebook sign-in through Socialite — each with its own credentials, both off until you configure them.
A profile with a privacy switch
Avatar upload, editable details, and a public-profile toggle that controls whether the member appears in the payout ticker and the leaderboard at all — consent, not a hidden setting.
Proof before sign-up
A public payout ticker, a public leaderboard, the FAQ page and the content pages all render without an account, so a visitor can see the site paying people before they decide to join it.
There is no colour picker and no second theme.
Branding covers the logo, favicon, app icons and the PWA colours; changing the
palette means editing the theme's CSS. Two smaller limits worth knowing: the
release is English-only with no locale switcher, and members have no API —
the only API routes are the sixteen provider postbacks.
The earning loop, end to end
Every step below is a real code path, and every one of them writes to the same ledger.
- 1 A member registers. Email and password, or Google and Facebook. A captcha is available for registration but ships off, a referred member starts with your join bonus, and the optional welcome credit is off until you set an amount.
- 2 You connect offer networks. Thirteen walls ship seeded with blank credentials. Paste each network's keys and the wall URL is rebuilt with the member substitution in it — with that network's callback URL and parameters printed for you to paste back.
- 3 The member browses offers. Surveys keep their own list beside the standard offers, and the Torox wall pulls live inventory server-side, so the page shows what the provider has right now rather than a cached snapshot.
- 4 The network posts the conversion back. The guard checks first — configured secret or IP allow-list, provider scheme verified, replay ledger consulted — and only then does the credit write. A retry or a forged callback is refused.
- 5 The member is credited. The integer balance moves, a transaction row and a tracker row record it, and a referred member's referrer is paid their commission on the same postback, if commission applies to that network.
- 6 Other earnings stack on top. Login streak, missions, the spin wheel, referral flat bonuses and leaderboard placing, each writing its own row in the same ledger.
- 7 The member requests a cashout. Inside a row lock the balance is re-read before anything moves: the points leave the spendable balance, sit held at pending, and cannot be requested twice.
- 8 You review and pay. One screen shows the member, method, destination and amount beside the approve, cancel and return controls. Cancel and return put the points back with a tracker row you can audit.
- 9 The scheduler pays the boards. Daily, weekly and monthly rank rewards are distributed by a scheduled command that keeps an idempotency log — a re-run of the day's job cannot pay a placing twice.
Every screen, as it ships
Captured from the release. Filter by area, then select any image to open it full size.
Public site
Member area
Admin panel
Installer
Demo mode
Names, balances and offer artwork visible in these captures are demo data from a seeded installation. Your installation starts with no members, no offers and no ledger history.
The stack, as shipped
Standard Laravel and MySQL, one server-rendered theme. Nothing exotic to host.
Laravel 13on PHP 8.3 or newer
MySQL24 tables, migrated at install
Blade themeserver-rendered, no Node step
PWA manifestinstallable, service worker
S2S postback API16 provider endpoints
67 testsin the shipped suite
Six-step installerchecks the server, writes the env
Rate limitslogin 5, API 60/min, verify 6/min
From purchase to your first payout
The operator's path, then the member's.
Install it
Point a vhost at the release, make the storage directory writable, and open the site. A six-step installer checks the server, writes the environment file, runs the migrations and seeds, and creates your administrator account.
Brand it
Site name, logo, favicon, meta description, social links and SMTP, all from the admin. Send yourself a test verification code to prove mail works before you invite anyone.
Connect a network
Open the offer walls screen, paste in your credentials for a network, and copy its printed callback URL and parameters into that network's dashboard. The wall URL is rebuilt with the member substitution as soon as you save.
Open the walls you have keys for
Thirteen walls ship seeded with blank credentials. Toggle each one live as its keys go in — surveys keep their own list beside the standard offers — and members see them the moment they are on.
Open registration
Point SMTP at a real server so verification codes send, add Google and Facebook OAuth credentials if you want social sign-in, and let members in. The captcha is there when you want it — it ships off, not on.
Run the scheduler
Add the standard schedule:run cron entry once. Daily,
weekly and monthly leaderboard rewards — and the nightly demo
reset when demo mode is on — all run from it, not from a
request.
What your server needs
Checked automatically by the installer, which will not continue until they pass.
| Requirement | Detail |
|---|---|
| PHP | 8.3.0 or newer |
| Extensions |
ctype, curl, dom,
fileinfo, filter, hash,
json, mbstring, openssl,
pcre, pdo, session,
tokenizer, xml — plus
zip and bcmath, which are warnings only
|
| Image processing | gd or imagick — either one satisfies the check; neither installed blocks the wizard |
| Writable paths | storage, storage/framework, bootstrap/cache, asset/uploads and the directory holding .env — all five are checked, and a failure blocks Step 2 |
| Database | MySQL / MariaDB recommended; PostgreSQL, SQLite and SQL Server also accepted. The installer tests the connection before it writes anything. |
| Web server | Anything that can serve a Laravel application, with .htaccess support if you use Apache. A web.config ships for IIS. |
| Cron | Required — one standard schedule:run entry pays the daily, weekly and monthly leaderboard rewards and runs the nightly demo reset |
| Outbound HTTPS | Required to reach offer network APIs (the live feed), captcha providers and Google / Facebook OAuth |
| SMTP is written at install and editable from the admin's SMTP screen. Verification codes and password resets need a real transport before you open registration. | |
| Node.js | Not required. The member theme is server-rendered Blade; package.json exists only for optional asset tooling. |
Before you buy, worth knowing
- You need a server you control, and a
schedule:runcron entry that actually fires. - You need your own account with at least one offer network, or the offerwall has nothing to show.
- You need to decide how you will pay members out, because the software does not do it for you.
- The captcha, the welcome bonus and the referral tiers all ship off — each is an opt-in switch, not a default you have to undo.
- Configure a real mail transport before you open registration, or verification codes go nowhere.
- Google and Facebook sign-in work only once you add OAuth credentials for each provider.
30 pages, shipped in the box
This is the buyer documentation set, written against this release and versioned with it. It is included in the archive you receive.
Introduction and setup
Product overview, system requirements, version and support, release notes, the installation guide and the initial configuration checklist.
The administrator guide
Eleven pages: dashboard and navigation, users and the global tracker, offer walls, missions, wheel, leaderboard rewards, referral tiers, withdrawals, pages and FAQs, settings, and the offer wall integrations.
The member guide
Eight pages: account and sign-in, earning, missions, spin and win, leaderboard, cashout, referrals, profile and transactions — written for your members, so you can link them straight into your site.
Operations
Maintenance and updates, the demo mode guide, troubleshooting, the FAQ, and the third-party attributions.
Online documentation.
The documentation ships inside the release, so it travels with the code,
and the same set is also published at
https://hansaldev.com/docs/zapcash.
The bundled copy and the published copy are the same pages.
Licence, updates and support
Plain statements, including the parts that are limited.
Licence
You receive the complete source code and the right to run it on a server you control and modify it for your own operation.
The product is sold as a regular licence for a single installation. You cannot resell or redistribute the source as a competing product. The full terms are presented and accepted during installation, so they are recorded on your own instance as well as here.
Updates
You get an upgrade guide and a changelog, and the source is yours to maintain. The release is built from committed source rather than from a vendor's working copy, so the archive you hold matches the documented version.
Future releases are a commercial question for the vendor at the point of purchase. This page does not promise a lifetime update commitment, because none has been contracted.
Support
HansalDev provides support on a commercial basis, and you can raise a request through the contact form before or after purchase.
This page deliberately makes no response-time or 24/7 availability promise. The shipped support page asks for your version and the exact steps that led to a problem, and points at the channel you bought through — it commits to no schedule, so none is quoted here.
Questions a technical buyer asks
Answered from what the release actually does.
Yes, in full. The Laravel application, the member theme, the admin panel and the database migrations. Everything under app/ is plain readable PHP; nothing is encoded or obfuscated.
Point your vhost at the release, make the storage directory writable, and open the site. A six-step installer checks PHP 8.3, the required extensions and the writable paths, writes the environment file, runs the migrations and seed, and creates your administrator account. No command line is needed to complete the install.
PHP 8.3 or newer with fourteen required extensions, image processing via GD or Imagick, a database - MySQL or MariaDB recommended, with PostgreSQL, SQLite and SQL Server also accepted - five writable paths, working outbound HTTPS, and a schedule:run cron entry. Node.js is not required: the theme is server-rendered.
Open the offer walls screen in the admin and paste in the credentials from your account with that network. Saving rebuilds the wall URL with the member substitution in it, and the integrations screen prints that network's callback URL and the parameters it sends, ready to copy into the network's own dashboard.
Each provider posts to its own endpoint - sixteen in total - behind a guard that checks the configured secret or source-IP allow-list first, then that provider's own scheme: HMAC-SHA256 with a constant-time compare on AdGem, hash-plus-IP on AdMantum, and so on. A replay ledger refuses a second delivery of the same callback, and chargebacks reverse the credit through the same path.
Not by guessing. The guard fails closed: a callback for a network whose secret is not configured is rejected before any parser runs, on the credit path and the chargeback path alike. A replay ledger refuses repeated deliveries, and the five networks authenticated by source IP accept nothing from anywhere else.
No, and this page will not imply otherwise. There is no automated payout adapter for any provider, and no fee engine. You define each method with its own minimum and member-facing fields, the software debits the balance and holds the request, and you pay out of band.
By you. The request debits the balance inside a row lock and sits at pending; approve it and it completes, or cancel or return it and the points go back with a tracker row. There is no automated payout for any provider, so paying out is a manual step. The four seeded methods are described in the docs as manual payouts, and that is accurate.
No, and this page will not claim it does. Referral is single-level: flat join bonuses by default, or opt-in tiers - Bronze to Platinum at 0, 10, 50 and 200 referrals - that raise the share of the referred member's join bonus and offer wall earnings, up to 20%. There is no second tier of referrers.
By a scheduled command, not in a request. Daily, weekly and monthly rank rewards - three seeded tiers each, places one to three - are distributed by the scheduler, and every run writes an idempotency log so a re-run of the same period cannot pay a placing twice.
Site name, description, keywords, logo and favicon are admin settings, and so are the five social links and the PWA name, icons and colours used for the installable app version. The theme's own palette is not an admin setting; changing it means editing the theme CSS.
No. The member side is server-rendered Blade - no Node build, no bundle step. The package.json in the release is for optional asset tooling and is not needed at deploy time.
Yes, 30 pages, versioned with the release: overview, requirements, version and support, release notes, installation, configuration, the full eleven-page administrator guide, the eight-page member guide, maintenance and updates, demo mode, troubleshooting, the FAQ and the attributions.
reCAPTCHA or hCaptcha, verified server-side and off until you add a key. Five login attempts on member and admin login, 60 requests a minute on the API, six a minute on the verification routes. Referral fraud heuristics flag the same registration IP, the same device fingerprint or a same-fingerprint IPv6 block - each rule behind its own switch, each flag listed on the member record. Uploads are checked by detected MIME type and a decoded image pass.
No, and that is deliberate. The installer creates your administrator during setup with a minimum eight-character password, and the database seed contains no default admin - installed from the command line instead, a random password is generated and printed once. The live demo runs on dedicated fictional accounts: the member demo credentials are published on its landing page by design, and the demo administrator is a restricted account that no password opens.
You get an upgrade guide and release notes with the release, and the source is yours to maintain. Future releases are a commercial question for the vendor at the point of purchase. This page does not promise free lifetime updates, because no such commitment has been contracted.
Yes. The site-wide Refund Policy (linked in the footer) covers every product sold here: refund requests can be made within 14 days of the transaction date, with clear rules for what qualifies and what does not. Read it before you buy, and ask through the contact page if anything is unclear.
Support is available on a commercial basis and can be arranged before purchase. No response-time or 24/7 commitment is stated here, because none has been contracted. The shipped support page points at the channel that came with your purchase and commits to no schedule either.
That is set by the offers you connect, the rates those networks pay and the traffic you bring. The product does not quote or guarantee a figure, and this page does not invent one. Your dashboard reports the actual figures for your own traffic.
The licence covers one installation. Running several separate public instances is outside it. If you need a multi-site arrangement, raise it with HansalDev before you buy.
The store listing carries version 1.9.26, which is the version the documentation set is written against.
One price, for the source code
A single Regular licence. No per-member fees and no revenue share to us.
Buy this one
In the package
ZapCash — complete source licence
One commercial licence for one installation. The full Laravel application, the member theme, the admin panel, the migrations and 30 pages of documentation.
-25%
Version 1.9.26
$199.00
$
149
USD one-time
Everything in the box
- Full source code — the Laravel app, the member theme and the admin panel.
- 24-table schema with 89 settings keys, 13 offer walls, 4 payout methods, 4 referral tiers, 4 missions, 7 wheel segments, 9 leaderboard rank rewards, 3 content pages and 5 seeded FAQs.
- 16 postback endpoints — eleven secret-authenticated, five IP allow-listed — each implementing that network's own verification scheme.
- A live offer feed, with category filtering and a single-offer lookup, served from your own domain rather than the member's browser.
- The installable PWA — a real manifest and service worker driven by sixteen admin-managed settings.
- The admin panel — dashboard, users, offer walls, postbacks, withdrawals, missions, wheel, leaderboard rewards, referral tiers, tracker, pages, FAQs and seven settings screens.
- Cashout queue and audit — row-locked requests, five explicit states, points held until decision, refunds written to the tracker.
- A six-step web installer that checks the server, writes the environment and runs the migrations and seed.
- 30 pages of documentation covering installation, configuration, every admin and member screen, demo mode, maintenance and troubleshooting.
- Release notes and an upgrade guide, and the release archive delivered against your order.
Buy ZapCash — $149
One-time payment. Taxes, if any, are added at checkout. The archive is delivered against your order, and the licence is presented and accepted again during installation so it is recorded on your own instance.
Prerequisites
What you bring
None of this is held back from you deliberately — it is not yours to resell, and some of it can only be issued to you personally.
Not included in the price
- Offer-network accounts. All thirteen seeded walls ship with blank credentials. You need your own accounts, and eligibility to receive offers from them.
- Payout provider accounts, and an adapter for them. The four payout methods are manual. There is no automated payout integration to configure.
- Social sign-in credentials. Google and Facebook are wired and both ship disabled, with blank client IDs and secrets.
- Captcha keys. reCAPTCHA and hCaptcha are both wired and both ship off. Either one needs your own keys; there is no keyless captcha.
- A hosted instance. You receive the application, not a running server. SSL and a real mail transport are yours to set up.
- A colour or theme editor. Branding covers identity and assets. Palette changes mean editing CSS.
- Custom development. The code is yours to extend; the package does not include bespoke feature work.
- Any revenue, ranking or earnings promise. What members earn depends on the offers you connect, the networks' rates and the traffic you bring.
Open the live demo
No administrator account ships with the release: the seed contains none, and the installer creates yours with a minimum eight-character password (a command-line install generates a random one and prints it once). The seed does contain a starter set — walls with blank credentials, missions, wheel segments, payout methods, pages and FAQs — and no users, no balances and no ledger history.
No recurring fee
You pay once for the source. There is no per-member charge, no revenue share to us, and no subscription to renew.
One installation
The licence covers one site you operate. Running several public instances is outside it, and that question is easier settled before you buy.
Yours to maintain
The source is yours to host, modify and maintain. Future releases are a commercial question with the vendor.
Other products
Best seller
Save $50.00
GPT & Rewards Platform
VibeCash
Launch your own GPT rewards website: offerwalls, surveys, tasks, referrals, cashouts and gamification with a full admin panel.
Popular
Save $49.00
Offerwall & App Monetization Platform
Preads
Monetise your website or app with offerwall and content-locker integrations, postback tracking and monthly payout invoices.
Run your own rewards site
Get the source code, install it, connect a network you already have an account with, and start earning from your own traffic.
Copied