National nonprofit payment resource
Nonprofits, Donations & Fundraising Payments
A practical framework for organizing donation checkout, recurring gifts, events, campaigns, records, staff access, donor communication, and support responsibilities.
Start with the organization
Map who collects each payment and why
Nonprofits may receive one-time donations, recurring gifts, membership dues, event registrations, sponsorship payments, merchandise orders, program fees, and other funds. Before comparing technology, define the organization, campaign, fund, chapter, event, or program responsible for each transaction and the record that should receive it.
Donation channels
List website forms, hosted pages, payment links, in-person terminals, mobile devices, mail or phone workflows, events, and third-party fundraising platforms.
Transaction purpose
Decide how a donor or payer identifies the campaign, designation, event, membership, product, program, or general fund connected with a payment.
Responsible entity
Document which organization receives the funds, who operates the checkout, who can change settings, and who answers payment questions.
System of record
Define how transactions connect with donor, campaign, event, accounting, membership, order, and bank-deposit records without copying sensitive payment data.
Clear checkout
Help supporters understand the transaction
Identify the recipient
Make the receiving organization and campaign clear before payment. If a platform, chapter, fiscal sponsor, event partner, or campaign organizer participates, explain the roles using accurate, approved language.
Explain one-time and recurring choices
Present the selected amount and frequency clearly. Before a recurring gift begins, show the schedule and the organization’s current instructions for changes or cancellation. Keep the donor’s authorization and communication records in the approved system.
Set expectations for acknowledgments
Explain what confirmation the payer will receive and which team can answer questions. Keep payment confirmation separate from any tax or legal statement unless that language has been approved by a qualified adviser.
Use a recognizable description
Ask the payment provider how the organization name appears during checkout and on account statements. Use consistent donor-facing contact details so unfamiliar charges can be investigated through a trusted channel.
Channel planning
Build a complete donation payment workflow
Online forms
Map who hosts the website and payment page, what information the form collects, where confirmation data goes, and who owns updates, monitoring, and incident response.
Events and in-person giving
Plan device custody, staff sign-in, connectivity, receipts, offline procedures, end-of-event closeout, and the secure return or storage of equipment.
Recurring gifts
Define authorization records, schedule visibility, failed-payment handling, donor-request routing, account updates, cancellation handling, and reporting responsibilities.
Fundraising platforms
Confirm who receives the payment, when funds move, what data the organization can access, how refunds or disputes are handled, and where supporters obtain help.
Records and reconciliation
Connect gifts with deposits and programs
A useful reconciliation process should let the finance and fundraising teams trace a transaction from the donor-facing channel to the processor or platform report, bank deposit, campaign or fund record, and any follow-up action.
Use consistent identifiers
Carry approved campaign, event, location, chapter, fund, or appeal identifiers through forms and reports when the selected systems support them.
Separate gross activity from deposits
Record the transaction total, refunds, reversals, disputes, adjustments, and deposit batches as distinct events. Ask the responsible provider how each appears in reports.
Assign exception ownership
Route unmatched gifts, duplicate payments, donor questions, returned payments, refunds, and disputes to named roles with a documented escalation path.
Protect retained records
Limit access, define retention with qualified guidance, and avoid storing complete card numbers, security codes, passwords, bank credentials, or secret keys in spreadsheets or general notes.
Access and security
Protect accounts, devices, and payment data
Control administrator access
Use individual accounts, least-necessary permissions, provider-supported multifactor authentication, periodic access review, and prompt offboarding for staff and volunteers.
Verify unexpected requests
Train teams to pause when a message requests credentials, changes payout information, introduces urgency, or bypasses a known approval process. Verify through a trusted contact method.
Inventory providers
Record the processor, gateway, platform, website host, application, device, bank, integration, and support contacts involved in every donation channel.
Prepare for incidents
Document who contains access, contacts providers, preserves a timeline, communicates with supporters, and obtains security or legal help if suspicious activity occurs.
Decision path
Questions to answer before selecting a solution
1. What must supporters do?
Define the devices, payment channels, accessibility needs, amounts, frequencies, designations, confirmations, and help options the experience requires.
2. What must staff do?
List setup, campaign creation, user management, reporting, reconciliation, refunds, donor service, event closeout, and escalation tasks.
3. What must systems exchange?
Map the minimum information needed by accounting, fundraising, membership, event, ecommerce, and banking workflows, then confirm supported data flows.
4. What must providers confirm?
Verify current features, availability, eligibility, supported channels, integrations, reporting, implementation, security responsibilities, service terms, and support directly.
Related guidance
Continue your payment research
Common questions
Nonprofit payment FAQ
Is a donation form the same as a payment gateway?
No. A form is the donor-facing experience. The underlying workflow may also involve a website, hosted page, gateway, processor, acquiring provider, bank, fundraising platform, and record system.
What should be documented for recurring gifts?
Document the donor-facing schedule, authorization record, confirmation, failed-payment process, change and cancellation path, account-update method, staff permissions, and responsible providers.
Should a general form collect card or bank details?
No. Use the approved payment workflow. Do not request complete card numbers, security codes, passwords, bank credentials, or secret API keys through a general contact form.
Who should answer a refund or dispute question?
Start with the organization’s documented donor-service and finance workflow, then use the responsible processor, platform, gateway, or bank’s current case instructions when needed.
Last editorial review: August 11, 2026. Sources reviewed: FTC donation and fundraising-platform guidance, PCI SSC small-merchant resources, and CISA multifactor-authentication guidance.
Next step
Map your donation payment workflow
Payments Max can help organize channels, equipment, systems, records, access, reporting, and provider questions before you compare available options.
To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.
CONTACT US