How to build crowdfunding in Bubble

A simple way to build crowdfunding in Bubble is: create a Project data type, allow users to create projects, let supporters make payments with Stripe (via the built‑in Stripe plugin or API Connector), store each payment as a Pledge, and update the project’s funded amount after successful payment. You combine Bubble pages (for displaying projects), database (for tracking funding), backend workflows (for confirming payments), and privacy rules (so users only modify their own data).

Core Data Structure

You need only a few data types to get a working crowdfunding app.

• User (Bubble creates it by default): name, email, etc.
• Project: title, description, goal amount (number), funded amount (number), creator (User), is\_active (yes/no).
• Pledge: amount (number), supporter (User), project (Project), stripe_charge_id (text).

Payments Flow (Stripe)

In Bubble, the simplest approach is using the Stripe plugin. It gives you an action “Charge the current user”. You run this action when the user clicks “Back this project”. After Stripe confirms the charge, the workflow continues.

• On the button click: run Stripe “Charge the current user”.
• Action after charge: create a Pledge with the amount and link it to the Project.
• Update the Project’s funded amount: Project’s funded amount + Pledge amount.

Backend Confirmation (recommended)

If you want stronger reliability, use a Stripe Webhook so Bubble receives a backend event saying “charge.succeeded”. Create an API endpoint in Bubble and parse the charge ID. Then update the Pledge and Project.

// Example JSON Stripe sends to Bubble webhook
{
  "type": "charge.succeeded",
  "data": {
    "object": {
      "id": "ch_12345",
      "amount": 2000 // amount in cents
    }
  }
}

Project Page Logic

Each Project page is a “Page Type: Project”. Bubble automatically loads the project’s data so you can show percent funded, title, and description. A progress bar can simply use “Current Page Project’s funded amount / goal amount”.

• A repeater “Repeating Group” shows all Pledges for transparency.

Privacy Rules

Set rules so only the project creator can edit the Project. Supporters can create Pledges but not change others’ Pledges. Stripe data (like charge IDs) should be readable only by admin.

• Project: “When Current User is This Project’s Creator → can edit”.
• Pledge: “When Current User is This Pledge’s Supporter → can read”.

Essential Safety Checks

Disable the pledge button when the project is no longer active or already fully funded. Also validate the amount > 0 before sending to Stripe.