TicketSignup charges a small processing fee on all purchases made through the platform. These fees are collected by TicketSignup prior to making payments to the event.
You can decide whether the organization absorbs the processing fees, the purchaser pays the processing fees, or if you would like to split the processing fees with the purchaser.
You can set who pays the processing fees for ticket purchases and donations in the Ticket Wizard and/or from your Event Dashboard.
Ticket Wizard Processing Fees
Step 3 of the Ticket Wizard, Payment, allows you to select if you would like to Create New Payment Account, Use an Existing Payment Account or select Other Options, including sending setup instructions, setting up the payment account later or using Test Mode.
If you choose to set up payment for your event in the wizard, by creating a new payment account or using an existing one, you will be given the option to set the ticket purchase processing fee settings. If donations were enabled in Step 1, Basic Info, you will also be able to set up the donation processing fee settings.
You will have two options to select from:
- Processing fee paid by the ticket purchaser: This setting will charge the ticket purchaser the processing fee.
- Processing fee comes out of the charge: This setting will remove the processing fee from the ticket purchase so that the purchaser is not required to pay the processing fee. Instead, the organization will absorb the processing fees collected by TicketSignup.
Note: When you select to take the processing fee out of the charge, you will see the option to Give ticket purchaser the option to pay the processing fee during the ticket purchase. When you select this option, you can add a custom prompt that will appear at checkout to ask the ticket purchasers to pay the processing fee:
By default, this box will be checked, charging the ticket purchaser the processing fee. If they elect not to cover the processing fee, they simply uncheck the box before entering their payment information and completing the transaction. In this case, your organization will absorb the transaction's processing fees.
Note: If you do not input a custom prompt, the default text will say, "To support [Your Event Name], I will pay the processing fee." For example:
Dashboard Processing Fees
You can set up or adjust or processing fee settings, including the who pay the processing fee and if you would like to give the ticket purchasers the option to pay the fee (and edit the custom prompt), from your Event Dashboard under Financial >> Payment Settings.
If you do not already have a payment account set up for the event, you can choose to set up a new payment account, use an existing one, or select from other options (similar to your options in the Ticket Wizard). In this case, you can create a new payment account or choose an existing one, and continue to setup your processing fees. If you already have a payment account set up for the event, you can adjust your processing fees settings that you set in the Ticket Wizard.
The Event Dashboard processing fee settings for ticket purchases and donations are similar to those in the Ticket Wizard, with one additional option: Half is paid by ticket purchaser and half is taken out of the charge. This will charge the ticket purchaser half of TicketSignup's processing fee for the transaction. With this setting you, are also able to Give the ticket purchaser the option to pay the processing fee during the ticket purchase and input a custom prompt:If you select Processing fee comes out of the charge under the Donation settings, donors will automatically be given the option to cover the processing fee when making a standalone donation:
Note: The option to cover the donation processing fee when donating in the ticket purchase path is determined by the Ticket Purchase Processing Fee Settings.
You can customize this checkbox under Donations >> Donation Setup >> Display Settings. There is a text box to input Absorb Processing Fee Text on this page.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article