Fundraising and Donations
Fundraising and donations technology encompasses the platforms, payment systems, and integrations that enable organisations to receive, process, and acknowledge financial contributions from individual supporters. This technology stack handles the complete donation lifecycle from initial gift through receipt generation, while maintaining the payment security standards and data protection requirements that govern financial transactions. The scope here covers individual giving rather than institutional grants, which involve different workflows, compliance requirements, and system architectures.
- Payment Service Provider
- An entity that processes payment card transactions on behalf of merchants. PSPs handle the technical connection to card networks and acquiring banks, abstracting the complexity of payment processing into API calls. Examples include Stripe, PayPal, and Worldpay.
- Payment Gateway
- Software that transmits transaction data between a donation form and the payment processor. The gateway encrypts card details and routes them securely, never storing full card numbers on the organisation’s systems.
- Tokenisation
- The process of replacing sensitive payment card data with a non-sensitive token that has no exploitable value. Tokens can be stored safely and used for recurring transactions without exposing actual card numbers.
- PCI DSS
- Payment Card Industry Data Security Standard. A set of security requirements for organisations that handle payment card data. Compliance levels vary based on transaction volume, with most nonprofits qualifying for simplified Self-Assessment Questionnaire validation.
- Regular Giving
- Recurring donations collected on a scheduled basis, typically monthly. Also called sustainer programmes, monthly giving, or subscription donations. Regular giving provides predictable income and higher lifetime donor value.
- Gift Aid
- A UK tax relief scheme allowing charities to reclaim basic rate income tax on donations from UK taxpayers. Adds 25% to eligible donations at no cost to the donor.
- Soft Credit
- Attribution of a donation to an individual who influenced but did not make the gift. Used in peer-to-peer fundraising to credit the fundraiser while recording the actual donor.
Platform Architecture
Fundraising platforms divide into two architectural categories: integrated suites that combine donation processing with supporter management, and specialised donation tools that focus exclusively on gift collection. The choice between these architectures determines data flow patterns, integration complexity, and operational overhead.
Integrated fundraising suites combine donation forms, payment processing, supporter records, email communications, and reporting in a single platform. Examples include Engaging Networks, Blackbaud Luminate, and Salesforce Nonprofit Cloud with fundraising extensions. These platforms store the complete donor relationship in one system, eliminating synchronisation between separate tools. The trade-off involves vendor lock-in and reduced flexibility for organisations whose needs diverge from the platform’s assumptions.
Specialised donation platforms handle only the collection and processing of gifts, relying on integration with separate CRM and finance systems for relationship management and accounting. Examples include Donorbox, Give Lively, and Fundraise Up. This architecture suits organisations with established CRM investments that need modern donation experiences without replacing core systems. Integration complexity increases, but each component can be optimised or replaced independently.
+--------------------------------------------------------------------+| FUNDRAISING ARCHITECTURE |+--------------------------------------------------------------------+| || +---------------------------+ +----------------------------+ || | INTEGRATED SUITE | | SPECIALISED PLATFORM | || | | | | || | +---------------------+ | | +----------------------+ | || | | Donation Forms | | | | Donation Forms | | || | +----------+----------+ | | +----------+-----------+ | || | | | | | | || | +----------v----------+ | | +----------v-----------+ | || | | Payment Processing | | | | Payment Processing | | || | +----------+----------+ | | +----------+-----------+ | || | | | | | | || | +----------v----------+ | | | API/Webhook | || | | Supporter Records | | | | | || | +----------+----------+ | | +----------v-----------+ | || | | | | | External CRM | | || | +----------v----------+ | | | (Salesforce, CiviCRM)| | || | | Communications | | | +----------+-----------+ | || | +----------+----------+ | | | | || | | | | +----------v-----------+ | || | +----------v----------+ | | | Finance System | | || | | Reporting | | | | (Xero, QuickBooks) | | || | +---------------------+ | | +----------------------+ | || +---------------------------+ +----------------------------+ || || Single vendor, unified data Multi-vendor, integration req. || Higher lock-in Component flexibility |+--------------------------------------------------------------------+The platform’s data model determines how donations connect to supporters. Most platforms distinguish between the transaction record (amount, date, payment method, designation) and the constituent record (name, contact details, giving history, preferences). A single constituent accumulates multiple transactions over time, enabling lifetime value calculations and relationship-based communications. Peer-to-peer fundraising adds complexity through soft credits, where both the fundraiser and the actual donor require constituent records linked to the same transaction.
Donation Processing
When a supporter submits a donation form, the transaction passes through multiple systems before funds reach the organisation’s bank account. Understanding this flow clarifies where fees apply, where failures occur, and where data resides.
The donation form collects gift details and payment information. For card payments, the form must either use a PSP’s hosted payment fields or achieve PCI DSS compliance for handling card data directly. Hosted payment fields (iframes provided by Stripe, PayPal, or similar) shift PCI compliance burden to the PSP while appearing integrated with the organisation’s form. The form submits non-sensitive data (amount, designation, donor details) to the fundraising platform while card details go directly to the PSP.
Donor Form PSP Bank | | | | |---(1) Enter---> | | | | details | | | | | | | | Card data goes directly to PSP via iframe/API | | +---------------+---(2) Card------>| | | | | data | | | | | | | | | Non-card | |--(3) Authorise---->| | | data | | | | | | |<-(4) Approved------| | | | | | | +-------------->|--(5) Token +---->| | | | gift data | | | | | | | |<-(6) Confirm-----| | | | | | |<--(7) Thank you---| | | | + receipt | | | | | | | | | Settlement occurs 1-3 days later | | | |--(8) Transfer----->| | | | funds |Authorisation verifies the card is valid and funds are available, placing a temporary hold. This happens in real-time during form submission. Settlement transfers funds to the organisation’s merchant account, occurring in batches 1-3 business days later. Failed authorisations (declined cards, fraud blocks, insufficient funds) prevent the donation from completing. Failed settlements are rarer but more problematic, as the donor believes their gift succeeded.
Transaction fees compound from multiple sources. A representative breakdown for a £50 online card donation:
| Fee Component | Rate | Amount |
|---|---|---|
| Card network (Visa/Mastercard) | 0.2% + interchange | £0.35 |
| Acquiring bank | 0.3% | £0.15 |
| PSP (Stripe nonprofit rate) | 1.2% + £0.20 | £0.80 |
| Total fees | £1.30 | |
| Net to organisation | £48.70 |
Fee structures vary by card type (credit costs more than debit), card origin (non-UK cards incur higher interchange), and transaction volume (negotiated rates improve with scale). American Express and Discover charge higher fees than Visa/Mastercard. Organisations processing over £100,000 annually should negotiate custom rates.
Alternative payment methods reduce fees and expand donor options. Direct debit (via GoCardless, Rapidata, or bank APIs) costs 1-2% less than cards for regular giving. Digital wallets (Apple Pay, Google Pay) use underlying card rails but increase conversion by reducing form friction. Bank transfers eliminate processing fees entirely but require manual reconciliation. Cryptocurrency acceptance remains niche, with volatility and conversion complexity outweighing benefits for most organisations.
PCI Compliance
Organisations accepting card payments must achieve PCI DSS compliance at the level appropriate to their transaction volume. The standard defines four merchant levels based on annual Visa transaction count:
| Level | Annual Transactions | Validation Requirement |
|---|---|---|
| 4 | Under 20,000 e-commerce | SAQ A (if using hosted fields) |
| 3 | 20,000-1,000,000 | SAQ A or SAQ A-EP |
| 2 | 1,000,000-6,000,000 | SAQ + quarterly network scan |
| 1 | Over 6,000,000 | Annual on-site assessment |
Most mission-driven organisations qualify for Level 4 and can use SAQ A (Self-Assessment Questionnaire A), the simplest compliance path. SAQ A applies when card data never touches the organisation’s systems because hosted payment fields or redirects send data directly to the PSP. This approach requires 22 compliance requirements rather than the 300+ in the full standard.
Organisations that pass card data through their servers, even transiently, must complete SAQ A-EP or more comprehensive questionnaires. This situation arises with certain legacy payment integrations or custom donation forms that handle card data before transmitting to processors. The compliance burden increases substantially, making hosted payment field adoption the preferred approach.
Regular Giving
Regular giving programmes collect recurring donations on fixed schedules, transforming one-time donors into sustained supporters. The mechanics involve storing payment credentials securely and initiating charges on schedule without requiring donor action each time.
Card-based regular giving stores a token representing the donor’s card rather than the card number itself. The PSP maintains the actual card data in their PCI-compliant vault, issuing a token that the fundraising platform stores and submits for each scheduled charge. When cards expire or are replaced, Account Updater services (offered by major PSPs) automatically refresh tokens with new card details, reducing failed payments.
Direct debit regular giving collects bank account details and a mandate authorising the organisation to initiate debits. In the UK, the Direct Debit Guarantee protects donors by requiring advance notice of collection dates and amounts, with full refund rights for disputed charges. Direct debit reduces payment failures compared to cards (bank accounts rarely expire) and costs less per transaction, but requires 3-5 day advance scheduling and carries higher setup friction.
A well-optimised regular giving programme achieves retention rates above 85% annually. Failure management directly impacts this metric. When a scheduled payment fails, the system should:
- Retry automatically after 3-5 days (card failures often resolve when statements clear)
- Notify the donor by email with a simple card update link
- Retry again after 7-10 days
- If still failing, pause the recurring gift and escalate to human outreach
- After 30-60 days without resolution, mark the gift as lapsed
+-------------------------------------------------------------------+| REGULAR GIVING LIFECYCLE |+-------------------------------------------------------------------+| || SIGNUP ACTIVE RECOVERY OUTCOME || || +--------+ +--------+ +--------+ +-------+ || | Donor | | Token | | Retry | | Active| || | signs +-------->| stored +---+------>| after +--->| gift | || | up | | | | | 3 days | | | || +--------+ +---+----+ | +---+----+ +-------+ || | | | || Monthly | | | Still || charge | | | failing || v | v || +----+----+ | +----+----+ +-------+ || | Payment | | | Email | | Card | || | success +---+ | donor +--->| upd. | || | | | + retry | | | || +----+----+ +----+----+ +-------+ || | | || | Fails | 30+ days || v v || +----+----+ +----+----+ +-------+ || | Initiate| | Human | | Lapsed| || | recovery| | outreach| | gift | || +---------+ +---------+ +-------+ || |+-------------------------------------------------------------------+Upgrade and downgrade handling requires smooth processes for donors adjusting their commitment. The platform should allow self-service changes through a donor portal, with modifications taking effect from the next scheduled payment. Backdating changes or issuing partial refunds introduces accounting complexity that most platforms handle poorly.
Peer-to-Peer and Crowdfunding
Peer-to-peer fundraising enables supporters to create personal fundraising pages and solicit donations from their networks on the organisation’s behalf. The fundraiser acts as an intermediary, motivating gifts through personal connection rather than institutional appeal. This model multiplies reach by recruiting supporters as volunteer fundraisers, each accessing networks the organisation could not reach directly.
The technical architecture introduces complexity not present in direct donations. Each campaign spawns multiple fundraising pages, each page accumulates multiple donations, and each donation requires attribution to both the actual donor and the fundraiser who solicited it. The fundraiser receives a soft credit for gifts they influenced while the donor receives the tax receipt and acknowledgement.
+-------------------------------------------------------------+| PEER-TO-PEER DATA MODEL |+-------------------------------------------------------------+| || +-------------------+ || | CAMPAIGN | || | | || | - Goal: £50,000 | || | - End date | || | - Event link | || +--------+----------+ || | || | has many || v || +--------+----------+ +-------------------+ || | FUNDRAISER PAGE | | FUNDRAISER PAGE | || | | | | || | - Personal goal | | - Personal goal | || | - Story/photo | | - Story/photo | || | - URL slug | | - URL slug | || +--------+----------+ +--------+----------+ || | | || | receives | receives || v v || +--------+----------+ +--------+----------+ || | DONATION | | DONATION | || | | | | || | - Amount: £25 | | - Amount: £100 | || | - Donor record | | - Donor record | || | - Soft credit --> | | - Soft credit --> | || | Fundraiser | | Fundraiser | || +-------------------+ +-------------------+ || |+-------------------------------------------------------------+Platform options for peer-to-peer span dedicated tools (JustGiving, GoFundMe Charity, Classy) and modules within integrated suites. JustGiving dominates UK peer-to-peer with high donor recognition and trust, though its fees (5% platform fee plus payment processing) exceed alternatives. GoFundMe Charity (formerly CrowdRise) serves US and international markets. Give Lively offers fee-free peer-to-peer for US nonprofits, relying on optional donor tips rather than mandatory platform fees.
Crowdfunding for specific projects differs from ongoing peer-to-peer in its time-bounded, goal-oriented structure. Campaigns typically run 30-60 days with a specific funding target. Some platforms implement all-or-nothing funding where gifts are not charged unless the goal is met, while others allow keeping whatever is raised. All-or-nothing creates urgency but risks losing momentum-stage contributions if the goal proves unreachable.
Event Fundraising Technology
Fundraising events combine in-person or virtual gatherings with donation collection, ticket sales, auction management, and participant tracking. The technology requirements depend on event type, with galas, sponsored challenges, and auctions each requiring distinct capabilities.
Gala and dinner events require ticket sales with table management, seating assignments, and on-site check-in. Platforms like Greater Giving, OneCause, and GiveSmart provide integrated event management with silent auction, live auction, and fund-a-need functionality. Mobile bidding allows guests to browse auction items and place bids from their phones, eliminating paper bid sheets and enabling real-time competition that drives final prices higher.
Sponsored challenge events (runs, walks, cycles) combine peer-to-peer fundraising with event registration. Participants create fundraising pages, collect sponsorships, and attend the physical event. The platform must track registration status, fundraising progress, and event logistics in parallel. Integration with timing systems for races adds complexity, linking finish times to fundraising pages for social sharing.
Virtual event technology emerged as a primary channel during pandemic restrictions and persists for reach expansion. Livestream fundraising combines video broadcast with real-time donation collection, on-screen donor recognition, and interactive elements. Platforms like Tiltify specialise in livestream fundraising, integrating with Twitch, YouTube, and standalone video players to overlay donation alerts and progress bars on broadcast content.
Auction item management deserves specific attention. Each item requires catalogue details (title, description, photos, value, donor attribution), bidding rules (starting bid, minimum increment, buy-now price), and fulfilment tracking. Consignment items from auction procurement companies add commission structures to the accounting. The platform must calculate net proceeds correctly: gross bid minus item cost minus consignment commission minus payment processing fees.
Tax-Efficient Giving
Tax relief schemes in various jurisdictions allow donors to increase the value of their gifts or reduce their personal tax burden. Technology systems must capture eligibility information, generate required declarations, and produce documentation for claims.
Gift Aid in the UK adds 25% to donations from eligible taxpayers at no cost to the donor. The mechanism works because charities can reclaim the basic rate income tax (20%) that the donor already paid on the income used for the donation. A £100 donation becomes £125 when Gift Aid is claimed. Higher-rate taxpayers can additionally claim the difference between higher rate (40% or 45%) and basic rate (20%) on their personal tax return.
Collection requires a Gift Aid declaration confirming the donor is a UK taxpayer who has paid sufficient tax to cover the Gift Aid claimed. Declarations can cover single donations or all donations within a four-year window (past and future). The declaration must include the donor’s full name and home address. Fundraising platforms capture this information through checkbox and address fields on donation forms.
Claiming Gift Aid involves submitting donation data to HMRC through the Charities Online service. Submissions include donor name, address, donation amount, and date for each eligible gift. Platforms with Gift Aid functionality can generate claim files in the required format (XML for Charities Online or CSV for manual upload). Claims must be submitted within four years of the donation date. Most organisations submit quarterly to balance administrative effort against cash flow timing.
Gift Aid Small Donations Scheme (GASDS) allows claiming a Gift Aid-style payment on small cash donations (up to £30 per donation) without individual declarations. The scheme caps at £8,000 per year, providing up to £2,000 additional income on bucket collections and similar anonymous giving.
US tax deductions operate differently, reducing the donor’s taxable income rather than increasing the gift value. Donors who itemise deductions can deduct charitable contributions up to 60% of adjusted gross income for cash gifts to public charities. The organisation’s responsibility is providing acknowledgement letters with required language (no goods or services received, or fair market value of any benefits) for gifts over $250. Most fundraising platforms generate compliant acknowledgement letters automatically.
Payroll giving (UK) and employer matching (US and elsewhere) enable donations through salary deduction with associated tax benefits. In the UK, Give As You Earn donations are deducted pre-tax, providing immediate relief at the donor’s marginal rate. Technology integration involves connecting with payroll giving agencies (Charities Trust, CAF) who aggregate and distribute funds to recipient charities.
Integration Architecture
Fundraising platforms must integrate with CRM systems, finance systems, and communication tools to avoid data silos and manual reconciliation. The integration architecture determines how donation data flows through organisational systems and where the authoritative record resides.
+------------------------------------------------------------------+| FUNDRAISING INTEGRATION FLOW |+------------------------------------------------------------------+| || +-------------------+ || | DONATION PLATFORM | || | | || | - Forms | || | - Payment | || | - Receipts | || +--------+----------+ || | || +-----------------+-----------------+ || | | | || v v v || +--------+------+ +-------+-------+ +------+--------+ || | | | | | | || | CRM | | FINANCE | | EMAIL | || | | | | | | || | - Constituent | | - GL posting | | - Thank you | || | record | | - Bank rec. | | - Receipts | || | - Gift history| | - Reporting | | - Campaigns | || | - Soft credits| | - Audit trail | | | || | | | | | | || +---------------+ +---------------+ +---------------+ || || Sync frequency: Sync frequency: Sync frequency: || Real-time or Daily batch Real-time || 15-min intervals recommended triggered || |+------------------------------------------------------------------+CRM integration synchronises donor records and transaction history. The key decision involves designating an authoritative source for constituent data. When the fundraising platform and CRM both store supporter records, conflicts arise when data is updated in both systems. Common patterns include making the CRM authoritative (donations push to CRM, CRM changes do not sync back) or using a middleware layer to manage bidirectional sync with conflict resolution rules.
Data mapping between systems requires careful attention to field alignment. Donation designations in the fundraising platform must map to fund codes in the CRM. Campaign and appeal codes should synchronise to enable consistent reporting. Soft credits from peer-to-peer fundraising require CRM support for multiple attributions per transaction.
Finance system integration ensures donations appear correctly in accounting records. The minimum integration posts summary journal entries (daily or per-batch) showing total donations credited to income accounts and debited to the bank clearing account. More sophisticated integration posts individual transactions, enabling donor-level reconciliation. Fund accounting requirements mean donations must post to correct restricted or unrestricted funds based on designation.
Reconciliation between the PSP settlement report, the fundraising platform transaction list, and the bank statement closes the loop. Discrepancies arise from chargebacks (disputed transactions reversed by the card network), refunds, and fee deductions. The finance system must handle gross versus net recording consistently, either recording gross donations with fees as expenses or recording net amounts directly.
Email integration triggers acknowledgements and receipts immediately after successful donations. This integration should fire in real-time rather than batch processing, as donors expect instant confirmation. Additional integration enables campaign-based communication, allowing email platforms to segment donors by giving history, designation, or source for targeted follow-up.
Implementation Considerations
Organisations with Limited IT Capacity
Organisations without dedicated IT staff should prioritise platforms that minimise technical overhead. Fully hosted solutions with built-in payment processing (Donorbox, Give Lively, fundraising modules within Wix or Squarespace) eliminate server management, PCI compliance complexity, and integration maintenance. These platforms sacrifice customisation for simplicity.
The recommended starting configuration for a small organisation processing under £25,000 annually:
- Donation platform: Give Lively (US) or Donorbox (international), both offering free tiers with payment processing fees only
- Payment processor: Platform default (Stripe for most)
- CRM integration: Manual export/import initially, automated sync when volume justifies
- Gift Aid: Platform built-in declaration capture, manual HMRC submission quarterly
This configuration enables online donations within hours of setup. Limitations become apparent as volume grows: manual reconciliation time increases, lack of peer-to-peer capability constrains campaigns, and basic reporting restricts analysis.
Organisations with Established IT Functions
Larger organisations or those with complex fundraising programmes benefit from platforms offering API access, custom workflows, and deep integration capabilities. The architecture decision between integrated suite and best-of-breed depends on existing system investments and change appetite.
Organisations with Salesforce as their CRM should evaluate Salesforce Nonprofit Cloud fundraising capabilities alongside standalone donation platforms with Salesforce connectors. Native Salesforce fundraising eliminates integration but requires Salesforce-specific skills and licensing. Standalone platforms (Classy, Fundraise Up) with connectors provide purpose-built donation experiences while syncing data to Salesforce.
Implementation priorities for established organisations:
- Define authoritative data sources and sync direction before selecting platforms
- Map existing fund codes, campaign structures, and designation hierarchies
- Plan migration of historical giving data to maintain relationship continuity
- Establish reconciliation procedures between donation platform, CRM, and finance system
- Configure automated acknowledgements with appropriate personalisation
Multi-Country Operations
International organisations face additional complexity from currency handling, local payment methods, and varying tax relief schemes. A centralised platform serving all countries simplifies administration but may not support local payment preferences or tax receipt requirements. Country-specific platforms provide better local experience but fragment data and reporting.
Hybrid approaches deploy a global platform with local payment method additions. Stripe and PayPal support most currencies and many local payment methods through single integrations. Local direct debit schemes (SEPA in Europe, BACS in UK, ACH in US) require country-specific setup but dramatically reduce payment costs for regular giving.
Tax receipt requirements vary by jurisdiction. US organisations must provide specific acknowledgement language. UK charities must issue Gift Aid declarations. German nonprofits must issue Zuwendungsbescheinigungen. Platforms serving international donors either support multiple receipt formats or rely on post-donation manual issuance for countries with specific requirements.
Technology Options
Open Source
CiviCRM provides donation processing, constituent management, and event registration in a single open-source package. The CiviContribute component handles one-time and recurring donations, while CiviEvent manages registrations and attendance. Payment processor integration supports Stripe, PayPal, and other providers through extensions. Deployment options include self-hosted (requiring PHP/MySQL administration skills) or managed hosting from CiviCRM partners.
GiveWP operates as a WordPress plugin, adding donation forms to WordPress sites. The free tier handles basic donations while premium add-ons provide recurring giving, peer-to-peer, and additional payment gateways. Suits organisations already invested in WordPress who want integrated donation functionality without a separate platform.
Commercial Platforms with Nonprofit Programmes
| Platform | Nonprofit Terms | Strengths | Considerations |
|---|---|---|---|
| Give Lively | Free platform, payment fees only | US-focused, modern UX | US nonprofits only |
| Donorbox | Reduced platform fee (1.75%) | International, multilingual | Limited customisation |
| Classy | Negotiated pricing | Strong peer-to-peer | Higher cost tier |
| Fundraise Up | Negotiated pricing | AI-driven optimisation | Newer platform |
| JustGiving | Standard fees | UK peer-to-peer dominance | 5% platform fee |
Selection criteria should weight integration capabilities with existing systems, fee structures for expected transaction volumes, and functionality match with fundraising programmes. Platforms offering free trials enable testing with real transactions before commitment.