Taking Payments at Chamber Events: Walk-Ups, Merchandise, and Raffles

"Can we take payments at events?" sounds like one question. It is three, and they have different answers.

A chamber director raised this with us and then, mid-conversation, offered her own resolution: they could handle it in their accounting software. That was a reasonable answer for her situation, and it is worth saying before anyone buys equipment. Sometimes the honest answer is that this does not need a new system.

Work out which problem you actually have first.

Last reviewed August 1, 2026.

The three problems

Walk-up event registration. Someone arrives at the luncheon who did not register. You need to add them to the count and collect payment.

This is the easiest and most common case. It may not need new equipment at all. Register the person in your normal system on a phone or tablet, create the invoice, and send a payment link they can open on their own device. The registration, invoice, and payment remain connected instead of becoming three records someone has to match later.

The mistake is treating a walk-up as an unrelated card transaction that must be reconstructed after the event. If your platform can add a registration and produce a usable payment link quickly, the operational problem is already solved.

Merchandise. Apparel, books, and branded items at a table behave more like retail: multiple products, variable quantities, possible sales tax, inventory, and sometimes a queue.

This is where card-present payment can earn its place. Tap to Pay can let a compatible phone accept contactless cards and digital wallets without a separate reader, but it requires a supported device, region, processor, and app or platform integration. Normal processing fees still apply, and some processors charge an additional Tap to Pay authorization fee.

Use a chamber-managed device with an individual staff login. Do not turn a volunteer's personal phone into the chamber's payment terminal without a deliberate security and access plan.

Raffles and other regulated fundraising. A raffle is not simply a high-volume merchandise sale. It is gaming, and payment acceptance is only one part of the decision.

Before selling tickets, confirm that your organization is eligible under state and local law, obtain any required license or registration, ask your accountant about federal tax treatment, and obtain explicit approval from the payment processor. A lawful raffle is not automatically an approved card-processing use.

Stripe currently treats charity sweepstakes and raffles as a restricted category in the United States and reviews them separately. Do not assume that an existing Stripe account, reader, or Tap to Pay integration authorizes raffle-ticket payments.

The same caution applies to other games of chance. Silent auctions may be treated differently, but the line varies by state. Confirm the current rules with qualified local counsel or the responsible state regulator before the event.

Do not let transaction fees decide the raffle structure

Small card transactions carry a fixed fee as well as a percentage, so they can be relatively expensive. That does not make bundling or changing raffle-ticket prices the first decision.

First establish that the raffle is lawful for your entity, understand the tax and recordkeeping treatment, and receive processor approval. Only then should you compare cash and approved card acceptance, set ticket quantities, and design queue controls.

Cash does not remove gaming, tax, licensing, or reporting requirements. It only changes the payment method.

When Tap to Pay or a reader is worth it

Only add card-present acceptance when the volume and pace justify it. Three questions usually settle the decision.

How often does this happen? If merchandise sales occur at one event a year and there is no queue, an invoice, hosted payment link, or existing accounting workflow may be enough.

What is the annual permitted card volume? If at-event card sales total only a few thousand dollars a year, favor the simplest supported setup. Hardware and a second provider can create more operational cost than they save.

Is there a queue? This is the real differentiator. If people are waiting to buy merchandise, card-present acceptance can make sense. If they are paying a registration invoice, a link on their own phone may be faster and easier to reconcile.

Tap to Pay can avoid a separate reader purchase when your processor or platform supports it and the chamber already has a compatible device. It does not mean payment acceptance is free. Check the processing rate, Tap to Pay authorization fee, device requirements, and supported card types before the event.

Keep reconciliation in mind

The reason to prefer your normal processor and accounting workflow is not just convenience at the event. It is what happens afterward.

A reader or Tap to Pay session connected to the same processor and account can keep transactions in the reporting and reconciliation workflow you already use. A separate provider or separate merchant account creates another stream of charges, fees, refunds, payouts, and deposits that must be recorded and reconciled.

Using one processor does not guarantee every transaction lands in the same payout. Timing, currency, connected-account structure, and processor configuration can split deposits. What it does give you is one reporting system in which the relationship between charge, fee, payout, and deposit can be traced.

If you use a separate provider, reconcile it the same week rather than waiting until month end, while someone still remembers what the transactions represent. Our Stripe and QuickBooks reconciliation guide explains why processor deposits usually differ from gross sales.

Surcharging at an event

Only add a card surcharge where applicable law, card-network rules, your acquirer, and your processor permit it.

Visa and Mastercard prohibit surcharging debit and prepaid cards, including debit cards processed through a credit-card flow. Disclosures, receipt itemization, caps tied to the cost of acceptance, and advance notice requirements can apply. Stripe's current services terms require users to notify Stripe at least sixty days before imposing a surcharge or other fee for accepting a payment method.

In a fast-moving merchandise queue, building ordinary payment costs into the advertised price may be simpler than identifying eligible credit cards and applying a compliant surcharge at checkout. Tax and advertised-price rules still apply, so confirm the treatment with your accountant or counsel.

Our credit-card fee guide covers the network and state-law distinctions in more detail.

Cash

Chambers still take cash and probably always will. Three habits make it manageable.

Count and record it at the event, before anyone leaves, with two people present. Do not wait until the next morning.

Use a starting cash amount, record sales or registrations against the correct event or income category, and document the final count and variance.

Deposit it as one identifiable amount and record it in the books the same way, so the bank deposit matches a documented total rather than becoming an unexplained figure the bookkeeper has to chase.

Cash control is a discipline problem, and the discipline is doing it before everyone goes home. For raffles and other regulated activity, those controls sit alongside the applicable gaming, tax, and recordkeeping duties rather than replacing them.

Common questions

What is Tap to Pay?

It lets a compatible phone accept supported contactless cards and digital wallets without a separate card reader. Availability depends on the device, country or region, payment processor, and the app or platform providing the integration. Processing and any Tap to Pay authorization fees still apply.

Do we need a merchant account?

You need access to merchant-account functionality. Integrated payment providers such as Stripe bundle it into their service, so you generally do not need to open a separate merchant account directly with a bank.

Can we pass the card fee on at an event?

Only where applicable law, card-network rules, and your processor allow it. Visa and Mastercard prohibit surcharging debit and prepaid cards and require specific disclosures. Advance notice may also be required. Check the current requirements with your acquirer and processor before the event.

How should merchandise sales be recorded?

Use an income category separate from dues and event registration. Depending on your state and organization, merchandise sales may also have sales-tax consequences that event admission does not. Ask your accountant before the first sale rather than at year end.

Can we take raffle-ticket payments by card?

Do not assume so. First confirm the raffle is lawful for your organization, understand the federal tax and reporting treatment, and obtain explicit approval from the processor for that activity. If those checks are satisfied, choose cash or an approved card method based on queue, controls, and cost.

Sources

• Stripe Tap to Pay setup requirements
• Stripe pricing and Stripe merchant account overview
• Stripe restricted businesses, including charity raffles
• IRS guidance on exempt-organization gaming and unrelated business income
• Visa merchant surcharge guidance and Mastercard merchant surcharge rules
• Stripe services terms

ChamberHive lets staff add a walk-up registration, create an invoice, and email its payment link from the event record. Start an instant demo to explore the workflow in your browser.