Payment Processing for US Nonprofit Ticket Sales

Payment processing for nonprofit ticket sales gets compared on one number, the percentage rate, and that is the least important thing about it. Two providers can charge the same 2.9% and give you completely different outcomes.

Everything below is specific to the United States: the card rates, the payout timings, the tax receipting and the compliance obligations. If you are running events elsewhere, the principles carry across but the numbers do not.

What actually matters is whose bank account the funds land in, how long they take to get there, and who absorbs the fee. Get those three right and the rate difference is rounding.

How Payment Processing Works for Ticket Sales

When someone buys a ticket, three parties are involved. The ticketing platform runs the checkout and records the sale. The payment processor moves the funds from the buyer's card. And a merchant account receives what is left after fees. The critical question is who owns that merchant account, because it determines whether the funds are yours from the moment of sale or whether you are waiting for a third party to pass them on.

What You Actually Pay

US card processing has a fairly standard shape. These are Stripe's published US rates for online payments, which most nonprofit ticketing runs on in one form or another.

Standard US online card processing costs

Put real numbers on it. On a $150 ticket you pay $4.65, so you keep $145.35. Across 200 tickets that is $930, which is a meaningful line in an event budget but not the thing that decides your event.

The last row is the one to watch. Processing fees and platform fees are different charges, and a low advertised processing rate paired with a high platform fee costs you more than the reverse. Our guide to free versus paid ticketing platforms covers how those stack up.

Nonprofit Rates Are Available, But You Have to Ask

The published rate is not always the rate you have to pay. Stripe and other major processors do offer discounted pricing to nonprofit organizations, and it is worth contacting them directly to ask.

This will not happen automatically. Discounted nonprofit pricing is not applied because your organization is a 501(c)(3), and it is generally not something your ticketing platform arranges on your behalf. You have to approach the processor yourself, explain what you are, and say roughly what volume you expect to process in a year.

The saving is worth the email. On $200,000 of annual ticket and donation volume, even a 0.5% reduction is $1,000 a year for one conversation you have once.

Two things strengthen the ask: an annual processing volume figure, and evidence of your tax-exempt status. If you already process payments, your last twelve months of volume is the number to lead with.

The Question That Matters More Than the Rate

Here is the difference nobody puts on a pricing page. Some platforms process ticket payments into their own merchant account and pay you afterwards. Others connect to a merchant account in your organization's name, so funds settle directly to you.

The second arrangement is better for you in every way that counts. The funds are yours from the moment of sale rather than sitting on someone else's balance sheet. You are not exposed if the platform has a bad quarter. You control refunds directly. And your reconciliation matches your bank statement instead of a monthly remittance report.

Ask any provider one question before you sign: do the funds land in an account in our name, or in yours? If the answer is theirs, ask when they pay out and what happens to your funds if they stop trading.

When the Funds Actually Arrive

Timing catches nonprofits out more often than fees do, because event budgets have deadlines. Caterers want deposits before the night, not after it.

A new account does not pay out immediately. Stripe notes that after your first live payment, the initial payout typically completes within 7 to 14 days, and can take longer depending on your circumstances. After that, payouts follow a regular schedule.

The practical consequence is simple. If you set up payment processing three weeks before your gala and open ticket sales the same day, your first funds may not reach your bank until close to the event. Set the account up early, run a small test transaction, and get that first payout cycle out of the way before you need the funds.

Who Pays the Processing Fee?

Three options, and the right one depends on your audience more than your budget.

1. Absorb It

You pay the fee out of ticket revenue. Cleanest for the buyer, simplest to explain, and the price on the page is the price they pay. Build the roughly 3% into your ticket price when you set it, which our guide to pricing nonprofit event tickets walks through.

2. Add It to the Price at Checkout

The buyer sees a fee added on top. It protects your revenue exactly, but it is the option most likely to cause complaints, and a fee appearing late in a checkout is a well-known reason people abandon a purchase.

3. Ask the Buyer to Cover It

An optional checkbox inviting the buyer to add the processing fee so more of their payment reaches the cause. Framed well, a good share of supporters say yes, and the ones who decline are not penalized. This is usually the best of the three for nonprofit audiences.

One receipting detail if you use option 3: the amount you acknowledge is what the supporter actually paid, including the covered fee. Check the IRS rules on substantiating charitable contributions and confirm your receipt wording with your own adviser, since GalaBid does not provide tax advice.

PCI Compliance and Card Data

The rule here is short: never touch card numbers. Not on a paper form, not in a spreadsheet, not read out over the phone and written down.

Any organization handling card data falls under PCI DSS obligations, and meeting them properly is a serious piece of work. Using a processor with a hosted checkout means card details go straight from the buyer to the processor and never reach your systems, which removes almost all of that burden.

The common failure is not the website. It is the volunteer taking a table booking over the phone and writing the card number on a notepad. Give your team a payment link to send instead.

Refunds, Disputes and Chargebacks

Events generate refund requests, so decide your policy before you sell rather than case by case afterwards. Publish it on the ticket page.

Note that refunding a ticket does not usually return the processing fee to you, so a refunded $150 ticket costs you the $4.65 as well. That is a reason to have a clear policy, not a reason to refuse refunds.

Disputes are different and more expensive, at $15 each whether or not the charge was legitimate. The most common cause at fundraising events is a supporter not recognizing the name on their statement, which is worth checking in your account settings before you open sales.

How GalaBid Handles Payments

GalaBid runs Secure Payment through Stripe, and your organization connects its own Stripe account rather than processing into an account we control. Funds settle to you directly, refunds are yours to issue, and reconciliation matches your own bank records.

GalaBid does not mark up payment processing. You pay Stripe's rates directly, with nothing added on top by us, so if you negotiate a better nonprofit rate with Stripe you keep the whole benefit of it.

Because the checkout is hosted, card details never reach your systems or ours, which keeps your PCI exposure minimal. Free & Paid Tickets and Multiple Ticket Types let you set pricing that accounts for fees however you decide to handle them.

You can run nonprofit ticketing on its own or connect it to your wider fundraising event activity, with payments running through the same account either way.

Frequently Asked Questions

What does it cost a nonprofit to process ticket payments?

In the US, standard online card processing is around 2.9% plus 30 cents per transaction, with additional charges for international cards and currency conversion. Any platform or software fee is separate and charged by the ticketing provider. On a $150 ticket, processing costs roughly $4.65.

Do nonprofits get discounted card processing rates?

Yes, discounted nonprofit pricing is available from Stripe and other major processors, but you have to ask for it directly. It is not applied automatically because you hold tax-exempt status, and your ticketing platform will not usually arrange it for you. Contact the processor with your tax-exempt documentation and your expected annual processing volume.

Should nonprofits pass credit card fees on to ticket buyers?

An optional checkbox asking buyers to cover the fee usually works better than adding it compulsorily. Supporters who want more of their payment to reach the cause can say yes, and the rest are unaffected. A mandatory fee appearing late in checkout is a common reason people abandon a purchase.

How long does it take to receive funds from ticket sales?

The first payout on a new account typically completes within 7 to 14 days of your first live payment, then payouts follow a regular schedule. Set your account up well before you open sales so the first cycle has cleared before you need the funds for deposits.

Is it safe to take card details over the phone for event tickets?

Writing card numbers down or storing them in a spreadsheet creates PCI obligations most nonprofits are not equipped to meet. Send the buyer a payment link instead so the details go directly to the processor. Manually entered cards also carry an extra processing charge.

In Summary

Compare payment processing on three things, in this order: whose account the funds land in, when they arrive, and only then the rate. A direct-settlement account in your own name is worth more than a tenth of a percent on the fee.

Set the account up early so the first payout clears before you need it, give supporters the option to cover the fee rather than forcing it, and keep card details away from your team entirely. And send the email asking your processor about nonprofit rates. It takes ten minutes and it is the only item on this list that pays you every year.

‍