Donor Management | Entry 32
Yes. HubSpot Payments is HubSpot's built-in payment-processing option and can support donations and other payments for non-physical goods and services. Each completed transaction can create a payment record that staff can review alongside the constituent's other CRM activity.
Bringing payment activity into HubSpot can reduce the need to move among a donation form, processor, spreadsheet, inbox, and CRM simply to confirm whether someone paid.
A payment confirms that money moved. The nonprofit must still define what the payment represents, who the legal donor is, how it should be acknowledged, whether any portion is tax-deductible, where it is designated, how it reaches accounting, and how it contributes to the constituent's giving history.
| Nonprofit need | Possible collection method |
|---|---|
| Simple campaign donation | Payment link or payment-enabled form |
| Monthly giving | Recurring payment link or subscription |
| Membership renewal | Payment link, invoice, or subscription |
| Event sponsorship | Quote, invoice, contract, or payment link |
| Program fee | Payment link or invoice |
| Pledge installment | Invoice or subscription, depending on the commitment |
| Check or external bank transfer | Manually recorded offline payment after receipt is verified |
The best method depends on the donor experience, approvals, revenue type, accounting requirements, and information that must be collected before or after payment.
A subscription should not automatically be treated as a fundraising pledge. Pledges may also need a total promised amount, pledge date, designation, conditional status, recognition rules, write-off treatment, and remaining balance.
Payment methods vary by organization country, bank-account country, processor, currency, checkout, and transaction. HubSpot Payments currently supports eligible organizations in the United States, United Kingdom, and Canada. Supported methods may include cards, Apple Pay, Google Pay, and regional bank-debit options such as ACH, SEPA, PADs, or BACS.
Organizations outside HubSpot Payments' directly supported countries may be able to connect an existing Stripe account, subject to current HubSpot and Stripe availability. Confirm eligibility, currencies, fees, settlement rules, and payment methods during implementation.
Staff can manually create payment records for money received outside HubSpot's online checkout, including approved checks, bank transfers, wire transfers, cash, or external terminals.
Recording an offline payment does not move the money, and HubSpot cannot reverse a transaction it did not process.
Payment records can support review, segmentation, workflows, reporting, receipts, refunds, failed-payment follow-up, subscription management, reconciliation, and constituent service.
Available details may include gross and net amount, currency, date, status, method, processing fees, billing information, processor, transaction ID, invoice, subscription, refund, and dispute information. Payment and subscription records remain separate because one describes an individual transaction and the other describes the recurring arrangement.
Depending on the architecture, payment records may connect with Contacts, Companies, Deals, invoices, subscriptions, orders, carts, quotes, contracts, donation records, campaigns, memberships, events, programs, and households.
This helps staff see whether a payment was completed, which invoice or subscription it belongs to, whether a registration was refunded, how much the constituent has paid, which campaign generated it, and whether it represents a donation, membership, ticket, sponsorship, or another revenue type.
HubSpot does not automatically determine which payments belong in household giving totals. Accurate reporting may require a household Company or custom object, reliable associations and labels, qualifying payment or donation records, rollups, joint-gift rules, soft credits, and protections against double counting.
Legal donor attribution and household recognition may differ. Simply adding every payment associated with every household member can overstate giving.
Supported checkout experiences may allow an added fee through payment links, invoices, quotes, and subscriptions. A nonprofit might invite supporters to help offset processing costs, but it should first review applicable laws, processor and card-network rules, surcharge restrictions, required disclosures, receipt language, accounting treatment, refund handling, and whether the charge is optional.
The nonprofit should not automatically describe the added amount as a tax-deductible donation. Checkout language should clearly explain the charge and align with the organization's donor-experience policies.
Authorized users can issue eligible full or partial refunds from payment records originally processed through HubSpot Payments or the connected Stripe option. Manually recorded offline payments must be returned through their original method and documented.
A refund workflow may also need to cancel an event registration, restore inventory, end a membership, adjust donation and subscription records, reverse recognition, update campaign revenue, notify finance, amend a receipt, and stop stewardship automation. The financial refund alone does not reverse every related record or action.
Disputes and chargebacks require a process that identifies the transaction, payer, related form or agreement, amount, response deadline, evidence, responsible staff member, access or benefit changes, fundraising recognition, finance treatment, and appropriate communication.
A dispute is not an ordinary refund. It follows a different process, timeline, evidence requirement, and financial outcome.
Payments may represent donations, dues, event tickets, sponsorships, auctions, program or training fees, merchandise, rentals, grant or pledge installments, deposits, or mixed transactions. These may have different accounting codes, tax treatment, recognition, receipts, campaigns, restrictions, fair-market values, refunds, stewardship, and reporting.
A gala checkout may combine tickets, a donation, sponsorship, benefits, fees, discounts, tax, and several attendees. Recording the full total as one donation can create inaccurate fundraising, accounting, and receipting results.
Simple fundraising may use a payment record with carefully governed properties. More mature operations may need a separate donation or transaction record containing the donor, legal donor, household, organization, gift and payment amounts, tax-deductible portion, benefit value, fund, designation, appeal, campaign, source, gift type, pledge, installment, soft credits, tribute, anonymity, receipts, acknowledgments, reversals, accounting status, and external finance ID.
This keeps payment processing connected with fundraising without forcing every fundraising concept into the payment record.
Charitable receipts may require the legal organization name, tax or registration information, receipt number, donation date, amount received, eligible amount, benefit description and value, donor's legal name, address, statutory language, authorization, and amendment procedures.
Finance, tax, or legal advisers should confirm whether a HubSpot-generated document meets local requirements. HubSpot may send payment confirmation while another governed system creates the official charitable receipt.
Operational payment visibility does not replace financial reconciliation. Finance may need to account for gross payments, processor and platform fees, taxes, added charges, net payouts, deposit dates, batches, refunds, chargebacks, offline receipts, currencies, restrictions, deferred revenue, memberships, sponsorships, events, and mixed transactions.
A bank deposit may contain the net result of several payments after fees, refunds, and chargebacks. Finance should be able to trace payment records to processor activity, payout batches, bank deposits, revenue classifications, and accounting entries.
Payment credentials are encrypted and tokenized, and full card information should not be stored in ordinary HubSpot records. Staff should never place full card details in notes, forms, emails, tickets, or CRM properties.
Control who configures processing, creates payment links, issues invoices, views transactions, refunds payments, cancels subscriptions, responds to disputes, exports data, changes bank details, records offline payments, reconciles payouts, reviews suspicious activity, owns credentials, and removes departing users.
Functionality depends on country, bank location, HubSpot and Revenue Hub access, processor approval, currency, payment method and channel, checkout, invoices, quotes, subscriptions, contracts, forms, permissions, accounting, donation and household architecture, integrations, tax jurisdiction, receipting, surcharge rules, privacy, staff capacity, and reconciliation.
Before launch, confirm processor eligibility, countries, currencies, payment methods, recurring behavior, revenue classification, funds and designations, household rules, fees, offline verification, refund effects, dispute ownership, receipting, accounting reconciliation, permissions, failed-payment monitoring, and ongoing governance.