Take a donation without it ever leaving your org.
Pledgivo is a managed package that puts the donation form, the payment and the donor record inside Salesforce. A confirmed gift is a standard Opportunity the moment it is taken — there is no external platform and no sync job to keep running.
- Released
- September 2026
- Package
- 2GP managed · namespace pledgivo
- Runs in
- Your Salesforce org
- Price
- $49/mo per admin
How a gift travels.
The card stops at the browser- 01StagingThe gift lands in Donation_Staging__c while the payment is still in flight.
- 02ConfirmA guest-side poll right after the redirect, with a scheduled reconciliation pass behind it.
- 03OpportunityOn confirmation it becomes a standard Opportunity against a standard Campaign.
- 04ReceiptA donor Contact or Person Account, and a receipt — reportable with the reports you already have.
No card number ever reaches your Apex. Stripe.js tokenizes it in the donor’s browser, and the org only ever handles the token.
Pledgivo installs into your Salesforce org and stays there. There is no hosted platform behind it, no connector to license, and no copy of your donor data anywhere else.
Where it is. The package is built and running. The AppExchange listing is with Salesforce for security review, and until that clears an install goes in by package version link, to a sandbox or to production.
How a gift travels. A donor gives on your Experience Cloud site, where Stripe.js tokenizes the card in the browser. Salesforce then asks Stripe what happened — a guest-side poll right after the redirect, and a scheduled reconciliation pass as backup — rather than waiting on an inbound webhook you would have to expose and secure. What lands is an Opportunity, a donor Contact or Person Account, and a receipt, reportable with standard Salesforce reports immediately.
Standard objects used: Opportunity · Campaign · Contact · Account. Package objects carry the rest — Recurring_Donation__c for billing schedules, Payment_Account__c for each connected Stripe account, Campaign_Design__c for page themes, Designation__c for funds.
Works with or without NPSP. The package detects the Nonprofit Success Pack at runtime and behaves identically when it is absent. Nothing to install first, and no separate dependency.
Works with or without Person Accounts. Every donor-facing object carries two lookups — one for Contact, one for Person Account — so there is no org model to declare and no org-specific build to choose between.
What it costs. $49 a month per fundraising admin, or $490 a year, which is twelve months for the price of ten. Donors, event attendees and portal visitors never need a licence, so the count is your staff and nobody else. Three licences is the minimum, putting the whole org at $147 a month. Donations are unlimited at every count, and we never take a percentage of what you raise.
What the package gives you.
Eight capabilities- 01
Standard Objects, Not a Shadow Schema
A confirmed gift is a standard Opportunity. A fundraising ask is a standard Campaign. A donor is a Contact or a Person Account. Every report, list view, flow and sharing rule you already have keeps working — there is no translation layer to maintain.
- 02
Donations & Payments
A public, guest-accessible donation form backed by Stripe's Payment Element — cards and card-backed wallets, one-time or recurring. Stripe.js collects the card in an iframe served by Stripe and tokenizes it in the browser, so no card number ever reaches Apex.
- 03
Recurring Giving Salesforce Owns
The billing schedule lives on a Recurring_Donation__c record rather than in Stripe Subscriptions. A nightly job charges the saved card off-session, and failed payments run the dunning sequence you configure — retry count, retry interval, grace period, donor emails — before the gift is cancelled.
- 04
Campaigns You Compose
Every ask starts from the standard Campaign object, themed with a reusable page design and built from movable content and field blocks. Fund designations, custom questions, FAQs and campaign updates hang off the campaign as related records — no page-builder platform bolted on the side.
- 05
Events & Ticketing
Ticket tiers, seat capacity and named guests, running through the same donation pipeline as every other gift. A ticketed event is a Campaign with ticket types on it, so event revenue lands in the same reports as the rest of your fundraising.
- 06
A Donor Portal With No Passwords
Donors ask for a link and the token in that emailed link is the credential — no sign-up, no password reset queue, and links expire on a window you set. From there donors change, pause, skip or cancel a recurring gift, update a card, reprint tickets and download annual tax statements.
- 07
Several Stripe Accounts, One Org
Route each campaign to exactly one Stripe account — a second entity, a fiscal sponsee, a restricted programme. Every account keeps its own credentials, and its Test or Live badge is read from the publishable key rather than picked from a menu.
- 08
It Tells You What Went Wrong
A Diagnostic Logs tab inside the app shows what the package recorded about its own behaviour — filtered by level, context and date, with stack traces on demand. A health check grades the org's configuration, and a nightly job deletes anything past the retention window you set.
The feature tour.
Two minutes fifty-four, one capability at a timeThe specification.
As built, API 67.0- Package type
- 2GP managed package · namespace pledgivo
- API version
- 67.0
- Donor-facing pages
- Enhanced LWR Experience Cloud site · LWC only
- Payments
- Stripe Payment Element · browser-side tokenization
- Payment confirmation
- Guest-side poll + scheduled reconciliation — no inbound webhook
- Donation record
- Standard Opportunity, with Donation_Staging__c holding pre-confirmation state
- Recurring engine
- Recurring_Donation__c + nightly RecurringDonationScheduler
- Scheduled jobs
- 24, installed and started by the post-install handler
- Secrets
- Named Credential only — never a custom field, never in code
- Testing
- 90% Apex coverage, gated on every change
What it costs, and what it needs.
Five prerequisites, two conditional$49
A month per fundraising admin, or $490 a year, which is twelve months for the price of ten. Donors, event attendees and portal visitors never need a licence, so the count is your staff and nobody else. Three licences is the minimum, putting the org at $147 a month, and we never take a percentage of what you raise.
- Per fundraising admin
- $49/mo · $490/yr
- Minimum, three licences
- $147/mo for the org
- Donor and attendee licences
- None — donors are never billed
- Cut of what you raise
- None
- Salesforce Enterprise, Unlimited, Performance or Developer Edition
- A Stripe account, which you can connect after installing
- API version 67.0 or later
- An Experience Cloud licence, only to take donations from the public
- No Nonprofit Success Pack needed — it is detected at runtime, never required
Where to go next.
Pledgivo · September 2026Pledgivo takes the gift. Getting your org ready to receive it is the other half.
Most fundraising teams arrive with an Opportunity model that grew sideways for a decade. If yours needs straightening before the package lands on it, that is work we do.