With Payment Method Actions, you can automate changes to your ticketing page based on how someone chooses to pay. Whether you're hiding certain fields for pre-registrants or offering exclusive add-ons for credit card payments, these actions give you flexibility to customize the experience based on the payment method.

For example, you can automatically require an additional checkbox to be selected when someone pays by offline payments, or hide donation fields when an attendee pre-registers for your event. These actions help streamline your process, provide clarity to attendees, and keep your page tailored and accurate.

Example Use Cases

Hide your Sessions field for attendees who pre-register
Apply a 10% discount to attendees who pay via offline payments

Getting Started

From the Pages screen, click the pencil icon under the page you want to edit
Go to the Actions tab
Click Create Your First Action, or click the + icon on your action if you already have actions on your page

Add Your Trigger

On the left-hand side, select the payment method you want to target
Select your desired option
- The Is Selected option will trigger your action when a specific payment method is selected
- The Is Not Selected option will trigger your action when a specific payment method is not selected
Click the + button if you would like to add multiple triggers
- If you click this button, click the All of these must be true checkbox if you would like all of the conditions to be met to trigger your action
- If this checkbox is not selected, the action will occur if any one of the conditions is met

Add Your Action

You can create a variety of actions in TicketSpice that are triggered by the selected payment method. Below are some of the action types you can set up to customize the ticketing experience.

Pro Tip: It is important to know that actions run from top to bottom. So if you have multiple actions in your TicketSpice page, actions towards the bottom can override actions above them. You have full control over the order of your actions and can reorder as needed. Because the order of actions can impact how your page behaves, we highly recommend previewing and testing your page before publishing it live. This helps ensure that all your actions work together the way you intend.

Show-Hide Actions

In TicketSpice, you can dynamically show or hide fields based on the selected payment method. For example, you can automatically show a specific merchandise field when someone pre-registers for your event.

Pro Tip: Our actions automatically assume the opposite is true. For example, if a field is set to only show based on a certain condition, it will be hidden by default until that condition is met. Once the condition is met, the field will show.

Likewise, if a field is set to hide until a condition is met, it will by default show. For instance, if a merchandise field is set to hide when an attendee pays by credit card, this field will by default show until that payment method is selected.

By default, TicketSpice fields show all of the time, so if you would like to show your field at all times, no action is needed.

On the right-hand side, find and select Show or Hide
Choose the Field(s) or Function(s) that you would like to show or hide when the condition is met
Click the + button if you would like to add another action that occurs when the condition is met
Click Save Action
Click Save Now in the upper-right corner of your page to save your changes. Click Publish to publish these changes to your live page

Require/Don't Require Field Actions

In TicketSpice, you can dynamically require or not require fields based on the selected payment method. For example, you can automatically require a specific merchandise field to be completed when someone pre-registers for your event.

Pro Tip: Actions will override the default requirement settings you set on the page builder. Actions also automatically assume the inverse is true. For example, if you create an action to require a field based on a certain condition, this field will not be required by default, even if it is marked as required in the Page Builder settings. This field will only become required once the condition is met.

For example, if your meal choice field is required in the page builder, but you create an action to require this field when someone pays by offline payment, our system will automatically make the meal choice field not required until that payment method is selected. Even though the Page Builder has marked this field as required, the action takes precedence. When an attendee chooses the offline payment method, the field will then become required.

If you want a field to always be required (or not required), no action is necessary. In this case, we recommend adjusting the Required setting within the Page Builder itself.

On the right-hand side, find and select Require or Not Require
Choose the Field(s) or Function(s) that you would like to require/not require when the condition is met
Click the + button if you would like to add another action that occurs when the condition is met
Click Save Action
Click Save Now in the upper-right corner of your page to save your changes. Click Publish to publish these changes to your live page

Select an Option Actions

In TicketSpice, you can dynamically select an option based on the selected payment method. For example, you can automatically select a specific multiple choice option when someone pre-registers for your event.

Pro Tip: Select an Option actions will only take place when the condition event is met. If the condition event is not met, the Select an Option action will not take place. For example, if you create an action to select two specific sessions when an attendee pays by credit card, the session field will remain unselected by default until that condition is met. Once the credit card payment method is selected, the required sessions will then be automatically checked.

On the right-hand side, find and select Select Option
Choose the Field(s) that you would like to target when the condition is met
Click Lock Selection if you would like to prevent attendees from changing their option
Click the + button if you would like to add another action that occurs when the condition is met
Click Save Action
Click Save Now in the upper-right corner of your page to save your changes. Click Publish to publish these changes to your live page

Note: Select an Option actions works with time slots (on date-based pages), Sessions, and Multiple Choice actions. This action does not work with checkboxes and merchandise fields. If you do not have a date-based page with time slots, a Sessions field, or a Multiple Choice field on your TicketSpice page, the Select an Option action will not appear in your list of events.

Set Value Actions

In TicketSpice, you can dynamically set a value in a text field based on the selected payment method. For example, you can automatically set the value of a text field to “N/A” when someone pre-registers for your event.

Pro Tip: Set a Value actions will only take place when the condition event is met. If the condition event is not met, the Set a Value action will not take place. For example, if you create an action to set the value of your text field to "N/A" for attendees who pay by offline payments, the text field will be blank until that condition is met. Once the attendee chooses to pay by offline payments, the text field will automatically be filled in with the text "N/A."

On the right-hand side, find and select Set Value
Enter the value you would like to enter in the text field
Choose the Field(s) that you would like to target when the condition is met
Click the + button if you would like to add another action that occurs when the condition is met
Click Save Action
Click Save Now in the upper-right corner of your page to save your changes. Click Publish to publish these changes to your live page

Note: Set a Value actions are designed to insert text into text-based fields and are not intended for adding financial amounts to pricing fields. If your page doesn’t include any text-entry fields, the Set Value action won’t show up in your list of available events.

Price Change Actions

In TicketSpice, you can dynamically update the price based on the selected payment method. For example, you can automatically increase the price of your tickets by 15% when someone pre-registers for your event.

Pro Tip: Price change actions will change the price only when the condition event is met. If the condition (aka trigger) is not met, the price change actions will not take place. For example, if you create an action to reduce the price of your t-shirts from $10 to $5 for attendees who pay by credit card, the price of the t-shirt will remain $10 until that condition is met. Once the attendee opts to pay by credit card, the price will then automatically change to $5.

Note: Price change actions affect each ticket or item, not the total order amount. If you're using these actions, it's important to set up your price change action with the understanding that the discount or increase will apply to every ticket or item on the order.

For example, if you set a $10 discount on your VIP ticket level for attendees who pre-register for your event, and someone pre-registers for two VIP tickets, the total discount on the order will be $20. The $10 discount will be applied to each ticket.

On the right-hand side, select your price change action
- Set Price will set the price of the field(s) to a new value that you set. If this option is selected, set the price in the text field
- Increase Price will increase the price of the field(s) by a $ or % amount that you set. If this option is selected, choose whether you would like to adjust the price by $ or %, and enter the value increase in the text field
- Decrease Price will decrease the price of the field(s) by a $ or % amount that you set. If this option is selected, choose whether you would like to adjust the price by $ or %, and enter the value decrease in the text field
- Apply Discount will apply a discount on the field(s) by a $ or % amount that you set. If this option is selected, choose whether you would like to adjust the price by $ or %, and enter the discount in the text field
- Limit Discount will limit the discount on a field(s) to a certain number on merchandise fields. If this option is selected, choose the limit of the discount in the text box that appears
- Set Fee will change the fee on your ticket level(s) to the new amount you enter. If you choose this option, enter the desired fee in the text field on the right. This will override the default fee set in the page builder
- Multiply Coupon increases the value of a coupon by the multiplier you set. This action multiplies the coupon's value when someone enters a valid coupon and meets the trigger condition. If this option is selected, set the multiplier in the text field that appears on the right
Choose the Field(s) on which you would like to adjust the price when the condition is met
Click the + button if you would like to add another action that occurs when the condition is met
Click Save Action
Click Save Now in the upper-right corner of your page to save your changes. Click Publish to publish these changes to your live page

Note: This Limit Discount applies to ticket levels, merchandise fields, and quantity boxes, not multiple choice fields and donation fields.

Users must use the Apply Discount action for the Limit Discount action to work. If users do not use the Apply Discount action, the Limit Discount action will not apply.

Users must add the Apply Discount event and the Limit Discount event within the same action by clicking the + button on the right-hand side of the action. If users create two separate actions (even if they use the same trigger), the Limit Discount field will not apply.

Capacity Limit Actions

In TicketSpice, you can dynamically adjust the overall capacity of your event based on the selected payment method. For example, you can decrease the capacity from 500 to 400 when someone pre-registers for your event.

Pro Tip: Capacity actions override the default capacity settings configured in the page builder. These capacity actions only take effect when the condition event is met. If the condition isn't met, the Capacity Limit action won't apply. For example, if you create an action to set the capacity to 500 for attendees who pay by credit card, that limit will only apply when that condition is met. If an attendee selects another payment method, the event will have the standard capacity set in the page builder.

If you want the same capacity to apply in all situations, no action is necessary. In this case, we recommend setting the capacity directly in the page builder.

Note: You can only use actions to lower the capacity below the default set in the page builder. If you need the capacity to be higher in certain situations, we recommend increasing the overall default capacity and then using actions to reduce the limit in all other cases.

On the right-hand side, find and select Set Capacity Limit from the dropdown
Enter the new capacity limit for your event in the text field on the right
Select the Tickets option from the dropdown
Click the + button if you would like to add another action that occurs when the condition is met
Click Save Action
Click Save Now in the upper-right corner of your page to save your changes. Click Publish to publish these changes to your live page

Ticket Limit Actions

In TicketSpice, you can dynamically adjust the maximum number of tickets a buyer can purchase in a single order based on the selected payment method. For example, you can change the maximum number of tickets allowed per order from 5 to 3 when someone pre-registers for your event.

Pro Tip: Set Tickets Per Order actions override the default ticket limit settings you set on the page builder. Additionally, actions will only take place when the condition event is met. If the condition event is not met, the Set Tickets Per Order actions will not take place. For example, if you create an action to allow buyers to purchase up to 5 tickets when an attendee pays by offline payments, this limit will only take place when that payment method is selected.

If you want to set the same ticket limit in all circumstances, no action is necessary. In this case, we recommend setting this limit in the page builder itself.

On the right-hand side, select Set Tickets Per Order from the dropdown
Enter the maximum number of tickets allowed per order in the text field on the right
Select the Tickets field from the dropdown
Click the + button if you would like to add another action that occurs when the condition is met
Click Save Action
Click Save Now in the upper-right corner of your page to save your changes. Click Publish to publish these changes to your live page

Manage Your Actions

Find the Action you would like to manage, and click any of the following icons:

The pencil icon allows you to edit the action
The pages icon allows you to copy the action
The + icon allows you to create a new action
The trash can icon allows you to delete the action

FAQs

What's the best way to test my actions?

We recommend using Preview mode to test your actions. Preview Mode allows you to review the visual and communication experience of your event page without processing real payments or saving data. Since Preview Mode respects actions and date-based conditions, you can test your page in real time to ensure everything functions as expected.

To use Preview mode, go to your TicketSpice edit page
Save any changes on your page by clicking Save in the top-right corner
Select the Preview button in the top right corner

Warning: Because the Preview mode is only used for testing, do not share this URL with attendees. This link will not accept real orders or payments.

Why is my live page still showing pre-registration, offline payments, or credit card payment options when I've disabled these payment methods on my TicketSpice page?

A common reason a disabled payment method still appears on the live page is that there is an action on the page that references that payment method. Actions override the payment settings in the page builder. So, if an actions includes a reference to a payment method, it will appear on the live page — even if that method is turned off in your settings.

To fix this, review your actions and remove any references to the payment method you no longer want to offer.

Create Actions That Trigger Based on the Attendee's Email or other Text Inputs

Create Actions that Trigger Based on the Attendee's Date of Birth

Create Actions that Trigger Based on the Inventory Left for Your Event

Create Actions that Trigger Based on the Date or Time Your Attendee Goes to Your Event

Create Actions that Trigger Based on the Ticket Level an Attendee Selects