Skip to content

Pledgivo

Fundraising that never leaves Salesforce.#

A native AppExchange managed package for donations, recurring giving, campaigns and ticketed events. The donation form, the payment processing and the donor records all run inside your org — no external platform, no sync job, no second permission model.

2GP managed package Namespace: pledgivo API 67.0 Enhanced LWR Stripe payments Person Accounts
0webhooks to secure — Salesforce re-fetches payment status from Stripe
0sync jobs — a gift is queryable the instant it is taken
24scheduled Apex jobs, installed and started for you
90%Apex test coverage, gated on every change

The overview film1:29 · captions included

01

What it does

Four capabilities, one pipeline, one set of records.

Donations & payments

A public, guest-accessible donation form backed by Stripe's Payment Element — card and card-backed wallets, one-time or recurring — landing directly on the standard Opportunity object.

Donations & payments

Recurring giving

Salesforce owns the billing schedule and charges the saved card off-session on its own cadence, with built-in dunning for failed payments — no external subscription system to reconcile.

Recurring giving

Campaigns

Every fundraising ask is a standard Salesforce Campaign, themed with a reusable page design and composed from movable content and field blocks — no page-builder platform bolted on the side.

Campaigns

Events & ticketing

Ticketed events with tiered pricing and seat capacity, built on the same donation pipeline — and the same reporting — as every other gift.

Events & ticketing
02

How a gift travels

Three hops, and none of them leave your org.

Donor gives On your Experience Cloud site. Stripe.js tokenizes the card in the browser — no card number ever reaches Apex.
Salesforce confirms Scheduled Apex asks Stripe what happened, rather than waiting on an inbound webhook you would have to secure.
Records land An Opportunity, a donor Contact or Person Account, a receipt — reportable with standard Salesforce reports, immediately.

Your Stripe secret key lives in a Named Credential you build in Setup. This package never ships, stores, or creates a payment credential of its own.

03

Why native matters

The same five questions, answered two ways.

Typical external platformPledgivo
Donor dataSynced back to Salesforce on a scheduleWritten directly to Salesforce, no sync job
Payment confirmationInbound webhook to a public endpointSalesforce re-fetches status from Stripe — no webhook to secure
ReportingRequires a connector or an exportStandard Salesforce reports and dashboards
Sharing & securityA second permission model to maintainYour org's existing sharing rules and permission sets
Person AccountsUsually unsupported or bolted onDetected at runtime, supported throughout
04

Where to start

Pick the one that matches what you came here for.

New here

Install & connect

Install the package, build the Stripe credentials, and take the setup assistant through record types.

Installation →
Ready to launch

Your first campaign

A guided walkthrough from creating a Campaign to publishing its donation page.

First campaign →
Looking something up

The data model

Every custom object and field, with an interactive relationship diagram.

Data model →
Integrating

Stripe & NPSP

The payment gateway architecture, and the optional NPSP allocation sync.

Integrations →

Everything you raise money with lives in one tab.

Campaigns, events, page designs and donation monitoring, all in the Fundraisers console — and the whole install checklist is graded against your org, live.

Read the install guide

Working title

"Pledgivo" is a working product name. It does not appear in any Salesforce API name, field, or record type — see the data model reference for the actual packaged names.