<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1094218042721276&amp;ev=PageView&amp;noscript=1">
Skip to content

Donor Management Entry 33

What are HubSpot payment links?

HubSpot payment links are shareable checkout experiences that let a nonprofit collect money without building a separate checkout page for every transaction. A link can be reused for a campaign or created for one person and one specific payment.

Create flexible checkout experiences

A payment link can be distributed through email, chat, a HubSpot form, website, landing page, marketing email, CTA, meeting page, QR code, direct message, or CRM record.

  • One-time and recurring donations
  • Pledge installments
  • Membership dues
  • Event registrations
  • Sponsorships
  • Program and class fees
  • Merchandise and deposits
  • Other nonprofit revenue

Example: send a personalized link after a donor conversation

  1. A donor verbally commits to a $500 contribution.
  2. Staff create the payment link from the donor's Contact, the appropriate Company, or the related Deal.
  3. The link already contains the agreed amount, item, schedule, and terms.
  4. The donor receives the direct URL without searching for a general donation page or re-entering the arrangement.
  5. The resulting payment or subscription associates with the CRM record used to create the link.
  6. The individualized link turns off after its intended purchase.

One-time-use protection should remain enabled when a link contains an individualized amount, discount, schedule, balance, or negotiated arrangement.

Connect payment links with HubSpot forms

A form can collect required constituent or participant information before redirecting the person to checkout. Depending on subscription and form configuration, conditional logic may send different respondents to different payment links.

Form response Possible payment link
Individual registration Individual ticket checkout
Family registration Family ticket checkout
Member Discounted member checkout
Nonmember Standard checkout
Sponsor Sponsorship payment
Monthly donor Recurring donation checkout
One-time donor One-time donation checkout

Test the complete form-to-checkout journey. A submitted form does not prove that the person completed payment.

Add required and optional line items

A link may include donation amounts, membership levels, tickets, sponsorship packages, program fees, workshops, merchandise, meals, guests, fees, optional contributions, deposits, or installments. Some items can be required while others remain optional.

For example, an event checkout might include a required admission ticket plus optional guest tickets, merchandise, and an additional donation. Each item still needs the correct revenue classification. The donation cannot be blended into ticket, merchandise, fee, or tax totals.

Control fixed and selectable quantities

Selectable quantities can support several tickets, workshop seats, guests, products, sponsor units, sessions, or meal packages. Fixed quantities are often safer for a specific pledge, one membership, one installment, a personalized amount, or an agreement the payer should not change.

Quantity is not a substitute for participant data. Buying four tickets does not provide the names, emails, consent, accessibility requirements, and meal choices for four attendees.

Collect one-time, recurring, immediate, or future payments

A payment link can include one-time charges, recurring charges, both types together, amounts due immediately, future start dates, or scheduled installments. Recurring links can support monthly giving, annual memberships, recurring sponsorships, tuition, or payment plans.

When checkout contains a recurring item, a subscription manages the ongoing billing arrangement, while each successful charge creates an individual payment representing money actually collected.

  • Amount due today
  • Amount due later
  • First future billing date
  • Recurring frequency
  • Number of payments
  • Continuation or end date
  • Payment-method update process
  • Cancellation process where permitted
Pledge-management caution

A recurring payment link is not a complete pledge record

A pledge may also require the total promised amount, pledge and start dates, end date, installment schedule, amount received, balance, fund, designation, campaign, conditions, restrictions, agreement, recognition, write-off status, cancellation reason, and payment history.

The recurring checkout can collect installments while a separate commitment or pledge record preserves the complete fundraising agreement.

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.

Associate payments with the correct CRM records

Reusable links created from the payment-links index generally use the checkout email to associate the resulting payment and subscription with a Contact, creating one when no match exists. Individualized links created from a Contact, Company, or Deal instead associate the result with the source record, regardless of the email entered at checkout.

Test shared family emails, organizational payments, assistants and executives, parents and participants, spouses and joint gifts, third-party payers, changed emails, duplicate Contacts, anonymous donors, and foundation payments. The payer, donor, participant, member, and person receiving recognition may be different records.

Choose a reusable or individualized link

Reusable link Individualized link
Public donation campaign Specific pledge
Standard membership level Negotiated sponsorship
General event registration Customized payment plan
Fixed program fee Remaining balance
Standard sponsorship package Major donor commitment
Public recurring-giving option Existing Deal or organizational contribution

Limit links through one-time use, a maximum number of checkouts, expiration, or manual deactivation so old personalized, discounted, or campaign-specific links do not accept unintended payments.

Collect the right information before or during checkout

Checkout may collect supported Contact or Company information such as name, phone, organization, address, and other approved details. A separate form may be better for multiple participants, extensive program questions, uploads, conditional logic, tributes, designations, detailed consent, sensitive information, or custom object data.

Collect only what is necessary for the transaction and permitted by privacy and security policies.

Share or embed the payment experience

A payment link can be copied as a URL, sent through email or chat, added to a marketing email, embedded on a website, placed on a landing page, connected with a CTA or meeting page, or shared through a QR code.

When distributing a reusable link, staff should copy the original shareable URL from HubSpot, not the unique checkout-session URL created after someone opens it.

Automate follow-up based on successful payment

The link used and resulting transaction can support payment confirmation, donation acknowledgment, stewardship, membership onboarding, event communication, internal notifications, tasks, finance review, and failed-payment follow-up.

Any communication that assumes money was received should wait for a successful payment status. A form submission, link view, or incomplete checkout should not trigger a completed-payment acknowledgment.

Test every payment link before publishing

  • Branding, name, line items, and quantities
  • Required and optional items
  • One-time and recurring amounts
  • Frequency, start date, and installments
  • Discounts, taxes, and fees
  • Methods and checkout fields
  • Receipt, confirmation, and redirect
  • Contact, Company, and Deal associations
  • Subscription and workflow creation
  • Reporting, expiration, and checkout limits

Preview the checkout and, where appropriate, complete a low-value transaction. Testing is especially important when one link combines immediate and future charges.

Questions to ask before creating a payment link

  • What is the person paying for?
  • Is the link public or personalized?
  • Should it work once, several times, or until expiration?
  • Are amounts and quantities fixed or selectable?
  • Which items are required or optional?
  • Is billing immediate, future, recurring, or scheduled?
  • Is this a pledge or a subscription?
  • Which fund, designation, and tax treatment apply?
  • Are payer, donor, and participant different?
  • Which records should receive associations?
  • What information and receipt are required?
  • Who owns monitoring and deactivation?

Requirements and limitations

Functionality depends on HubSpot subscription, processor, country, currency, payment method, permissions, form editor, Content Hub or Marketing Hub access, workflows, reporting, products, line items, subscriptions, website setup, CRM architecture, donation and pledge design, accounting, and receipting.

Before launch, confirm processing, methods, billing frequency, future dates, quantities, optional items, Contact matching, Company and Deal associations, revenue classification, funds, receipts, successful-payment automation, personalized-link protection, expiration, testing, and ongoing management.