How to ask for an optional donation during ticket checkout

Someone has chosen your event, picked their tickets and reached the payment page. You'd like to ask them to support a cause while they're there. That can be a perfectly reasonable request. But the buyer needs to understand what they're buying, what they're giving and whether they can finish their booking without giving anything extra.

Make the donation a separate, clearly labelled choice that starts at zero. Name the beneficiary, explain what happens to the money and show the revised total before payment. Keep the same ticket and booking route available when the buyer declines. Then test the receipts, refunds and financial records as carefully as you test the request itself.

That's the approach this guide takes. It's for operators selling paid event tickets, including businesses working with a charity partner. We'll work through the wording, the checkout experience, the agreement behind it and the numbers you'll need afterwards. The examples use fictional USD amounts. They aren't platform prices, recommended gift levels or evidence of how buyers will behave.

Decide what you're asking the buyer to fund

The first thing you want to do is finish this sentence in ordinary language: the optional donation goes to this organisation for this purpose. If your team can't agree on the answer, the checkout isn't ready for an appeal. A charity logo and an uplifting sentence won't resolve uncertainty about who receives the funds.

There are several arrangements an event business might mean. A buyer could donate directly to a charity through a separate payment service. The event operator could collect gifts and transfer them later under an agreement. Or the operator could promise to donate some of its own ticket income. These arrangements need different descriptions because the buyer is doing something different in each.

An optional donation means the buyer chooses an extra gift. A promise to give part of every ticket sale means the operator allocates money from the sale under its stated terms. Don't combine those promises into a vague claim that every purchase supports the cause. Tell the buyer which money you're talking about and which organisation is responsible for it.

If your event already has a compulsory fundraising payment, describe that requirement before someone starts booking. Calling a required amount optional doesn't make it voluntary. Likewise, a higher-priced ticket with an extra benefit is a ticket offer that needs its own explanation. This guide assumes that giving nothing extra leaves the purchased admission unchanged.

Choose the purpose with the beneficiary. A general appeal can support its approved work without promising a particular outcome for each gift. A restricted appeal, where money is intended only for a defined project, needs a plan for circumstances changing. What happens if the project is fully funded, can't proceed or needs less money than expected?

The Charity Commission's public guidance on raising money for charity advises fundraisers in England and Wales to be clear about the purpose, discuss specific appeals with the charity and explain relevant targets. Use that as a prompt to agree the wording with your partner. Check the applicable requirements wherever you're operating.

For your working brief, record the beneficiary's legal name, the approved purpose, who collects payment and who handles donor questions. Include the person who can approve changes. You want a named contact who can answer a refund or wording question during the sales period, rather than a general assumption that the charity will sort it out.

Agree the money route before designing the request

Work through one gift with the people responsible for finance. Imagine a buyer adds $5. Which account receives it first? Does a payment provider deduct a charge? Does the operator cover that charge or subtract it from the gift? When does the charity receive the money, and what evidence confirms that transfer?

Put those answers in the agreement. The marketing team needs them to write a truthful appeal, and customer support needs them when a buyer asks where the money went. If the charity will receive less than the amount selected, you need to know why before deciding how to explain it.

A promise that the charity receives the full selected donation means someone else must fund any deductions. That could be the operator under a specific arrangement. It doesn't mean payment processing has become free. Budget the cost and make sure the promise still holds for the payment methods, refunds and currencies your checkout actually accepts.

Avoid using an uncertain phrase such as proceeds when you mean a specific amount. Buyers may read it as ticket revenue, donations or the surplus after costs. If the agreement promises the net donation after stated charges, use wording that explains those charges. If the operator promises a fixed amount per sold ticket, state that separately from any optional gift.

The UK's Fundraising Regulator has standards for online fundraising platforms, including clear information about fees before financial details are requested. They distinguish money going directly to an organisation from money collected for onward transfer. The practical lesson is to describe your actual payment arrangement at the point where the buyer decides.

Next, decide what happens during a cancellation. The ticket seller may owe ticket refunds while the charity or fundraising service controls donations. If you collect both, your systems still need to distinguish them. An instruction to refund an order shouldn't accidentally reverse a gift the buyer wanted to keep, or retain one they reasonably expected to recover.

Include a route for disputed, duplicate or mistaken donations. Identify who investigates, who can authorise a refund and how an already transferred amount is handled. Don't make the buyer contact several organisations without telling them who owns the request. Support staff should be able to start the process from the order reference.

Finally, agree the reporting date. A payment shown as completed in a checkout report might not yet have reached the beneficiary's bank. Your public update should say whether it describes gifts received, amounts awaiting transfer or the final amount delivered. Agreeing those definitions now prevents an awkward correction after you've announced the total.

Write a request people can understand without opening the terms

Keep the main request short enough to read while buying a ticket. Name the gift as optional, identify the recipient and explain the purpose in concrete language. Add the essential money information nearby. A longer policy can explain the details, but the policy shouldn't carry facts that change what a reasonable buyer thinks they're agreeing to.

Here's an illustrative version for an imaginary beneficiary. Replace every detail with approved information before using it: "Optional donation to Community Arts Fund. Help fund its community workshop programme. Choose an amount below, or continue without donating. Your ticket and admission are the same either way."

That example explains the choice without making an unsupported claim about impact. If you want to say that a particular amount pays for a workshop place, ask the charity to substantiate the calculation and approve the wording. Its costs may vary, or the funds may support a broader programme. A pleasing sentence isn't enough evidence.

Now add the payment detail your arrangement requires. For example: "We collect donations and transfer the full selected amount to Community Arts Fund after the event. We cover donation processing charges." That is a sample promise, not a default you can copy. Only use it if the agreement, budget and payment records support every part.

If charges are deducted, explain them in language and detail that match the applicable rules and service. Don't make buyers calculate an unknown deduction from a vague reference to fees. Have the responsible organisation approve a representative example where the exact amount can't be displayed in advance. Keep any additional platform contribution distinct from the charitable gift.

A neutral choice can read "Continue without donating". Avoid a decline label that makes someone defend their character or their commitment to the cause. The person could already support the charity, have a limited budget or be buying on behalf of someone else. You don't need to know their reason to let them complete the purchase.

You can be warm without applying pressure. "Thank you for considering a gift" respects the decision. Claiming that everyone else gives, or implying that declining lets the community down, adds pressure and may make claims you can't substantiate. The event page can tell a richer story about the partnership before the buyer reaches payment.

For a broader campaign, connect the short request to an explanation on your event page. That explanation can introduce the charity's work and the agreement in more detail. Our fundraising event ideas guide can help with the event concept. The checkout's job is narrower: make this particular financial choice understandable.

Make zero the starting amount and keep it easy to leave

Start with no donation added. The buyer should take a deliberate action to add a gift, then see the amount in the order summary. Don't rely on someone noticing a preselected contribution while concentrating on names, ticket quantities and payment details. A voluntary choice needs more than a removable line in the final total.

You can offer suggested amounts and a custom field if your verified service supports them. Choose amounts that make sense for the campaign and test their labels. Don't describe one as typical or most popular unless you have reliable evidence for that exact claim. A suggested amount is a suggestion, not a statement about other buyers.

Keep the no-donation choice visible alongside the giving options. It shouldn't require opening a small menu, entering a special code or explaining a reason. If the buyer can simply leave the amount at zero and continue, make that clear. Ask someone unfamiliar with the setup to finish a booking without donating and watch where they hesitate.

Once a gift is selected, let the buyer change or remove it before payment. The summary should reflect the current choice. If they go backwards to change a ticket, return to checkout or recover from a payment error, check whether the donation stays as they left it. A technical reset shouldn't silently restore an amount they removed.

The US Federal Trade Commission's report on deceptive design practices describes interfaces that hide charges or steer people through misleading choices. Our recommendation is straightforward: use a clear positive choice, readable disclosures and an honest total. Don't make the buyer undo a decision your interface made for them.

Be careful with round-up requests. Rounding a total to the next whole amount still creates an extra payment. Show the precise gift and the new total before confirmation. Explain what the round-up applies to, especially when fees, discounts or multiple tickets make the original amount harder to follow.

Avoid asking again immediately after someone declines. A second modal or repeated question makes the first choice feel temporary. If you offer a separate giving opportunity later, give it a sensible context and a lawful communication route. Respect a completed decision during the booking the person is currently trying to finish.

Test group orders as well. One buyer purchasing several seats should understand whether the gift applies once to the order or separately to every ticket. A label that says add $5 can produce a nasty surprise if changing the quantity multiplies it. State the basis and check the actual charged amount at each quantity you expect.

Show the full price and separate every kind of extra payment

A buyer should be able to explain the final amount without guessing. In a fictional order, a $40 ticket plus a chosen $5 donation makes $45, assuming there are no other charges. If a mandatory ticket fee applies, show it as part of the required purchase cost under the relevant pricing rules. It isn't another optional donation.

A platform contribution is different again. Some services ask buyers to contribute towards running the service. If your chosen service does that, the buyer needs to know that the money goes to the service rather than the charity. You should also check whether that contribution is optional and how it can be changed or removed.

Don't use the same label for all three. "Support" could describe a charitable gift, a service contribution or an event funding appeal. Spell out the recipient and purpose. The order summary should distinguish the admission purchase, the selected donation and any other charge rather than collecting them under a single generous-sounding heading.

For a family or table booking, show the ticket calculation clearly before adding the gift. Buyers may otherwise interpret an increase as an unexpected charge on each seat. If a promo code changes the admission price, check whether the donation stays unchanged. A discount intended for tickets shouldn't silently change an already selected charitable amount.

There is useful context in Loopyah's Worth It Event Index. In its February 2026 Pollfish survey of 500 US consumers, respondents answered a single-choice question about how clearly they usually understood the event experience before buying. The distribution below concerns general event clarity. It doesn't measure donation requests, checkout design or the effect of changing either.

The survey doesn't tell you an ideal gift amount or prove that one design will sell more tickets. It does remind us that buyers arrive with different levels of understanding. Your appeal adds another decision to that purchase. Explain it without requiring them to reconstruct the event's financial arrangements from several separate pages.

For your final review, read the summary aloud as a customer would: this is my admission cost, this is the optional gift I chose, this is any other charge and this is what I pay now. If a staff member can't do that without supplying missing explanations, fix the labels before opening sales.

Choose a payment route your tools can actually support

Check the service before writing instructions that depend on it. Can it record a voluntary amount separately from ticket income? Can a buyer leave the amount at zero? Can you see the beneficiary and charge information before paying? Can staff trace a refund to the original gift? Ask for a demonstration using the arrangement you intend to run.

A generic donation screen in this guide is an explanation of the choice, not a screenshot of Loopyah. The current Loopyah ticket-selling page describes ticket types and checkout, but it doesn't verify a native optional donation control or charitable tax receipts. Confirm those specific requirements with the responsible service before promising an integrated setup.

If your ticketing setup doesn't support the required donation process, use an approved separate giving route after the ticket purchase. That introduces a second step, which you need to explain honestly. A person buying admission should know that the separate gift doesn't create another ticket or change the booking they've just completed.

An after-purchase request can say that the booking is confirmed and the buyer may separately support the named beneficiary. Link to an official, checked donation page. Make the distinction visible on the destination too. Someone who opens it later shouldn't have to wonder whether their original ticket payment failed or whether another payment is necessary to attend.

When the charity collects directly, ask what aggregate or transaction information it can appropriately share with you. You might be able to report campaign totals without receiving a full donor list. Don't promise attribution to every ticket order if the systems don't connect that information, or try to rebuild it by matching names loosely.

Consider how people reach the giving page. A link in a confirmation email needs a working mobile destination and clear recipient details. A QR code shown at the event needs an official link people can verify. A shortened link shouldn't hide a change of organisation or payment recipient that the buyer needs to understand.

Avoid inventing a workaround by selling a donation ticket that behaves like admission unless the service and responsible charity have explicitly approved that model. It could affect inventory, attendee counts, refunds or tax treatment. What looks like a convenient label in the ticket menu can create inaccurate reports and confusing entry rights.

Choose the route your team can explain and reconcile. An integrated ask can be useful when the required controls work properly. A separate charity page can be more appropriate when it preserves a clear donation relationship and reliable records. The decision depends on your actual tools, rather than an assumption that a single payment is always better.

Work through a fictional budget before deciding what success means

Here's a planning example in USD, with invented assumptions so you can follow the calculation. Suppose an event sells 200 tickets. Each contributes $25 after ticket payment charges and attendee-related delivery costs. Fixed event costs are $4,500. Ticket contribution is therefore $5,000, leaving a $500 event surplus before any extra donation administration.

Now suppose 40 orders include a $5 donation, with one ticket per order throughout this example. Selected gifts total $200. That money follows the charitable agreement. It isn't automatically another $200 of event profit, and you shouldn't use it to make an otherwise unaffordable supplier contract look affordable.

Assume the operator promises to transfer the full selected gift and pays an invented $10 of donation processing charges. It also spends $90 on campaign setup and support. Those are extra event costs of $100. The charity receives $200, while the operator's event surplus falls from $500 to $400. Both outcomes should be visible when evaluating the arrangement.

Now imagine five fewer ticket purchases. At the same $25 contribution per ticket, the operator loses $125 of contribution. If other assumptions stay unchanged, surplus becomes $275 after the $100 donation administration cost. This is a sensitivity calculation. It doesn't claim that the request caused five people to leave, or that every lost order would have donated.

That distinction matters when you measure a real event. A lower booking rate during one week could reflect traffic quality, a price change, a sold-out ticket release or the programme announcement. Don't attribute every movement to the donation prompt. First inspect whether buyers encountered an actual problem and whether the comparison is reasonably like for like.

The example also shows why the donation total alone is a poor decision measure for an event business. The charitable benefit is worthwhile only under an arrangement your organisation deliberately accepts. A successful appeal can coexist with an operator cost that needs funding. Agree who carries the work and charges, and budget them before launch.

Use your own cost structure. If processing is charged per transaction, combined and separate payments may produce different costs. If fees depend on currency or payment method, use the actual quote. Include staff time for donor enquiries and reconciliation. Our event budget guide explains the broader ticket and delivery calculation.

Keep a separate cash forecast. Gifts collected in your account may be due to the beneficiary even while the venue invoice is unpaid. A bank balance containing restricted or payable funds doesn't tell you how much the event can spend. Ask finance to identify the amount owed and the reserve needed for corrections under the agreement.

Decide the refund explanation before someone asks for one

Write down how ticket refunds and donation refunds are handled in your actual arrangement. A buyer might cancel admission while choosing to leave the gift in place. Another might have added a gift accidentally. Event cancellation could raise questions about both payments. These need a clear process, even when different organisations make the decisions.

Don't state that donations are never refundable simply because the label says donation. Check the applicable rules, the purpose of the appeal, the service's terms and the circumstances. Equally, don't promise an automatic donation refund with every ticket cancellation if you lack the authority or technical ability to carry it out.

Give support staff a simple intake procedure. Record the order or donation reference, what the person wants changed and which organisation controls that change. A buyer asking to remove an accidental extra payment shouldn't be forced to explain their financial circumstances. Request only the details needed to investigate through an appropriate private channel.

Test a partial ticket refund with a donation still attached. Suppose the fictional buyer purchases two $40 tickets and chooses one $5 gift for the order, with no other charges. The total is $85. Refunding one $40 ticket while retaining the gift leaves $45, consisting of one ticket and the $5 donation. The surviving ticket must remain valid.

Then test a donation-only correction. Refunding the $5 gift from that original $85 order leaves $80 of ticket purchases before any separate fee treatment. Both tickets should remain valid. These are expected accounting outcomes for the illustrative test, not a claim that every ticketing service supports those actions in one interface.

Check the confirmation the buyer receives after each change. It should explain what was refunded, what remains and who to contact if it is wrong. Update any charitable acknowledgment through the authorised organisation where needed. An old receipt that still shows the original gift can confuse both the donor and the charity's records.

For cancellation of the entire event, publish coordinated instructions. The ticket operator explains admission refunds. The organisation responsible for the appeal explains the donation outcome, including any decision required from donors. Make the relationship clear and avoid sending buyers between help desks that each say the other party owns everything.

Before sales open, make sure your event refund policy and donation explanation don't contradict each other. The practical test is whether a customer can tell which promise applies to which payment. Have the authorised finance and charity contacts approve the wording together, including how to handle money already transferred.

Keep tax wording and marketing choices separate from the gift

An optional amount isn't automatically tax-deductible. Eligibility depends on the recipient, the donor, the benefits provided and the relevant jurisdiction. Ask the charity or qualified adviser to approve any tax statement. A payment receipt showing a donation line doesn't by itself establish that the donor can claim relief.

For UK Gift Aid, HMRC's guidance on eligible donations distinguishes gifts from payments for goods or services, including event tickets. A genuinely voluntary extra payment can need a different assessment from the admission charge. Don't copy rules for charitable attraction admissions into an ordinary paid event without checking that they apply.

In the US, the IRS explains payments that combine a contribution and a benefit. The organisation may need a disclosure or acknowledgment, and the value of what the buyer receives matters. Keep the ticket and gift records distinguishable so the responsible charity can apply the appropriate rules to the actual arrangement.

Also distinguish giving from permission to receive fundraising emails. A person may want an acknowledgment while declining future campaigns. Another may buy several tickets without donating. Your records should reflect each choice rather than converting every purchaser or donor into an unrestricted marketing contact for every partner.

For UK communications, use the ICO's current electronic mail marketing guidance. Its rules include a conditional charitable purposes soft opt-in. That exception needs assessment by the relevant charity and doesn't give an event business blanket permission to send fundraising messages or pass a donor list to a partner.

Keep a record of what the person saw and chose where required. Your team should know which organisation collected the details, for which purpose and under which wording. Our ticket checkout email consent guide covers the purchase-side process. Check the donation-side process with the organisation responsible for that relationship.

The same care applies to public thanks. A donation doesn't mean the buyer wants their name on a sponsor slide or a public donor list. Offer the relevant privacy choices and test what a signed-out visitor can see. Reporting an aggregate amount usually doesn't require identifying every person who gave.

Give the team a short operating brief

Your checkout wording can be concise because the team has done the detailed work behind it. Keep an internal brief that staff can use without interpreting the full partnership contract. Start with the exact customer-facing request and a screenshot of the approved summary. Record when that version went live and who authorised it.

Next, write the answer to the questions a buyer is likely to ask. Who gets my donation? Is it required? Can I change my mind before payment? What happens if I cancel my ticket? Can I get a charitable acknowledgment? Each answer should identify the responsible organisation and the approved process, rather than promising a result your support team cannot deliver.

For a mistaken gift, the support response can acknowledge what the buyer is requesting, confirm the reference needed and explain who will investigate. It shouldn't ask them to justify declining the appeal. If the charity controls refunds, tell the buyer how their request reaches the charity and what your team can do to help. Don't promise a resolution time that hasn't been agreed.

Assign the appeal's settings to one responsible person, with a named backup. Someone changing ticket prices shouldn't accidentally change the gift wording or beneficiary. Before updating the request, check whether the payment route, charity permission and financial report still match. Keep a record of the old version so staff can investigate purchases made before the change.

Include a pause procedure. If the donation page becomes unavailable, the beneficiary details are wrong or the totals stop reconciling, decide who can suspend the request while ticket sales continue where appropriate. A checkout issue should have a practical owner. Waiting until the next event meeting can leave the same confusion affecting more buyers.

Handle matching gifts without inflating the promise

A sponsor might offer to match checkout donations. That can strengthen the appeal, but only if the commitment is specific and confirmed. Agree the amount available, eligible gifts, campaign dates, any exclusions and who verifies the final claim. Don't count a possible sponsor conversation as committed matching money.

Suppose a fictional sponsor agrees to match eligible gifts dollar for dollar up to $200. If qualifying gifts total $150, the match is $150. If they total $250, the capped match is $200. Those are invented terms to show the arithmetic. Your request must explain the real cap and qualification rules, including what happens once the cap has been reached.

Show donor gifts and sponsor funds separately in the report. A combined campaign total may include both, but it shouldn't imply that ticket buyers personally donated the sponsor's money. Check refund treatment too. If a matched gift is later returned, the agreement should establish whether the matching contribution changes and how the public figure is corrected.

Only describe a deadline as urgent when it actually governs eligibility. If the sponsor extends the offer, update the request and keep the old terms in your records. The useful part of a match is the additional confirmed support. Manufactured scarcity adds another promise for your team to explain when a buyer asks what happened.

Run a booking test that includes people who give nothing

The most useful test isn't simply making one successful donation. Start with a ticket purchase at zero extra gift. Then add a gift, change it and remove it. Complete each route using the devices and payment methods your audience actually uses. Keep the resulting summary and receipt so finance can check what happened.

Use a test environment where the service offers one. If a live transaction is necessary to verify something, agree it with the responsible team, use authorised details and follow the approved correction process. Don't fill a production donor database with invented identities or assume a test payment will automatically disappear from campaign reporting.

Ask a fresh tester to answer what the ticket costs, whether the gift is required and who receives it. Don't coach them before they answer. If they confuse the platform contribution with the charitable donation, the interface needs another explanation. If they think declining changes their admission, the request has failed its central purpose.

Test accessibility as an actual booking task. The W3C guidance on labelling form controls explains that fields and choices need meaningful labels associated with their controls. A custom amount box needs a label, and the selected state must be understandable without relying on colour alone. Ask the service to resolve problems you cannot change yourself.

Check keyboard navigation and the experience with relevant assistive technology. Can a buyer reach the zero option, enter a custom amount, understand an error and continue? A visible label doesn't establish that the underlying control is accessible. Include someone with suitable testing experience when your team can't assess the behaviour confidently.

Try the awkward paths too. Go back after selecting a gift. Change ticket quantity. Apply a discount. Let the payment fail, then retry. Check that a duplicate click doesn't create duplicate gifts and that an unsuccessful payment isn't shown as received. Record any limitations with a named owner and fix them before promoting the appeal.

Finish by tracing the records. Finance should identify ticket income, gift amount, deductions, refund status and settlement reference without matching by name alone. Customer support should retrieve the same transaction from the buyer's reference. If either team needs a manual correction, decide whether it's reliable enough for the expected sales volume.

For a wider investigation into lost bookings, use our checkout abandonment guide. Review observed errors before changing the ask's wording or suggested amounts. Increasing the donation amount won't repair a confusing total, a missing payment method or a broken continue button.

Reconcile the campaign and close the promise you made

Agree a reporting cutoff, then bring together completed gifts, refunds, deductions and transfers. Count the underlying transactions once. A donation appearing in a checkout export and a charity settlement statement is the same gift viewed in two places. The transfer to the beneficiary isn't a second amount raised.

Return to the fictional $200 campaign. If two $5 gifts are refunded, remaining gifts total $190. If the operator still pays the invented $10 processing cost from its own budget, the charity is due $190 under the full-gift promise. Don't subtract the $10 again from the beneficiary amount simply because a settlement report shows the deduction.

The operator must supply the difference if the service has already deducted that charge from the collected funds. Finance should reconcile the net receipt, the operator-funded charge and the final transfer. If the actual cost changes after a refund, replace the example assumption with the service's real statement. The approved promise determines what the charity is owed.

Mark unsettled payments separately. If a donor's payment is pending, it doesn't belong in a received-money total yet. If a completed gift is awaiting transfer, explain that stage accurately in an internal report. Only call the final figure transferred once you have evidence that the agreed recipient received the corresponding amount.

For a public update, use language the evidence supports. You might announce the amount transferred and thank ticket buyers who chose to contribute. Don't announce what that money achieved until the charity can substantiate the result. An approved campaign purpose and a completed programme outcome are different statements.

Review the work alongside the total. How many completed orders included a gift? What was actually transferred? How much staff time did the appeal require? Which questions confused buyers? Use completed order counts for an order-level giving rate, and don't mix tickets with orders when group bookings are common.

If you compare versions next time, define the question before changing the page. You might test whether a clearer recipient explanation reduces support questions while monitoring ticket completion. Keep the no-donation choice and truthful disclosures throughout. A result that depends on hiding the way out isn't a useful improvement to a voluntary appeal.

Before repeating the request, confirm the beneficiary agreement and payment route again. Keep the wording that accurately explains them, fix the issues the test and support records exposed, and make sure finance can still follow one gift all the way to its recipient. Then reopen sales with a choice your team can explain as clearly as the ticket itself.