DEV3 Pledgewell – Crowdfunding & Donations SaaS Laravel Script with Deadline Settlement, Rewards & Monthly Giving

Pledgewell is a crowdfunding and donations platform that you run as a multi-tenant SaaS, built by DEV3 Technologies on Laravel 12 and Filament 4. Each tenant is an organiser: a charity, club, school, maker or community group. They run campaigns, supporters give through public campaign pages with an optional account, and you, the operator, collect the payments, hold the money and pay organisers out after identity and bank checks. You sell plans, and every organiser is isolated from the others.

What it does

• Two kinds of campaign. All-or-nothing campaigns (reward crowdfunding with a deadline) and keep-it-all campaigns (donations). Pledges to an all-or-nothing campaign are charged at once and refunded in full if the goal is missed.
• Deadline settlement that cannot double count. A pledge started before the deadline may be paid for 30 minutes after it, the page shows a Finalising state, and the campaign settles exactly once under a lock: funded or failed. A failed campaign refunds every supporter, fees and tips included, through a durable queue that retries and then flags a manual transfer.
• Rewards with real stock. Reward tiers with limits, claims held while a payment is pending, sold-out pills, shipping rates by country, and a fulfilment list with CSV export.
• Monthly giving. Supporters pick a day, change the amount, pause for up to three months, cancel or update the card. Declined cards are retried on a schedule and cancelled after repeated failures.
• Fundraiser and team pages. Personal and team pages roll up to the campaign, each gift is counted once, and the leaderboard breaks ties fairly.
• Fee maths donors can see. A platform fee by plan, a card fee, optional fee cover by the donor and an optional tip, with a live breakdown before paying and the same maths in a fee calculator on the home page.
• Receipts. Numbered receipts per organiser and year, voided receipts keep their number, annual summaries in January and PDFs for donors.
• Trust and safety. First campaigns are reviewed by a person, payouts wait for an identity check and a verified bank account, risky organisers keep a rolling reserve, card-testing bursts pause the donate button, and disputes, takedowns and a fraud queue are in the operator panel.
• Payouts. A hold period, a minimum, negative balances netted, a reserve, a bank CSV driver and a reversal for chargebacks.
• Goal Thermometer Board. A flat chart on both dashboards that plots every live and recently ended campaign by time used against goal reached.
• SaaS layer. Plans, trials, billing page, invoices, organiser roles (owner, manager, editor, fulfilment), operator roles (super admin, finance, trust, support), audited view-only impersonation, an API with scoped keys, webhooks and an OpenAPI document.
• Embeds and Arabic. An iframe progress widget and a right-to-left layout.

Install and demo data

A web installer checks the server, writes the configuration, migrates and loads either demo data or an empty install, then creates the operator account. The demo has 12 fictional organisers, 48 campaigns in every state, about 1,300 gifts over twelve months, monthly gifts, refunds, disputes, fundraiser and team pages and payouts, and its totals reconcile with a built-in check. Every demo password is password. Node.js is not needed because compiled assets are included.

Good to know before you buy

• All-or-nothing pledges are charged immediately. Card holds (authorise now, capture at the deadline) are not supported in v1. Supporters are told at checkout that they are charged now and refunded in full if the goal is not met.
• You are the merchant of record. Every payment goes through the one gateway you configure; organisers cannot connect their own Stripe account in v1.
• Drivers are simulated until you configure them. Payments run on a simulated gateway (Stripe, Razorpay and PayPal checkout drivers are present). The stored-card recurring chargers for them are not finished: they throw recurring_not_configured, and a real identity provider and bank payout API are your integration work. Identity checks are a manual review by your team.
• Receipts are not tax claims. Pledgewell issues receipts; it does not file Gift Aid or similar claims, and VAT on per-gift platform fees is not applied in v1.
• Run the scheduler every minute. Campaigns settle by the scheduler or on the first read after the deadline window.
• Live updates use Reverb when you run it and fall back to polling.
• Web only. There are no mobile apps.
• No hosted demo. The organisations, campaigns and people in the screenshots are fictional.
• Name: Pledgewell is a working name checked by a web search only, not a trademark clearance.

Quality checks

Pledgewell 1.0.0 passed the seven release gates of the DEV3 Laravel suite on the final code: static analysis (Larastan level 6), the Pest suite, a front-end size budget, migrations and seeding on MySQL 8 and SQLite, a headless-browser pass with donation happy paths and MySQL race checks (last reward unit, pledge against the deadline, parallel settlements, parallel monthly retries, double payout run, refund against payout), an installer test from the package and a secret scan. A financial logic review found twelve issues before release; all were fixed with tests.