Skip to main content

Switch Your Pages to a New Payment Processor

Change your current TicketSpice pages to process through another payment processor

Hannah avatar
Written by Hannah
Updated today

Once you have added a new payment processor to your TicketSpice account, this article will walk through how to change your existing TicketSpice pages to the new payment processor.

Note: To switch your TicketSpice pages to a new payment processor, the payment processor must be added to your account. Click here to learn how to add a Webconnex Payments processor to your account. Click here to learn how to add a custom payment processor to your account.

Jump To...

Switch the Payment Processor

  • From the Pages screen, click the pencil icon under the page you want to edit

  • From the menu bar, hover over the Settings tab

  • Select Payment Methods

  • Click the trash can icon next to the payment processor you want to delete

  • Type delete to confirm that you would like to delete this payment processor from the page

  • Click Add Payment Method, and select the payment processor you would like to add

  • Click Save

  • Click Publish in the top right-hand corner to switch the payment processor

Warning: To start accepting payments through the new payment processor, you must click the Publish button in the top right-hand corner. This will set the page live and direct payments to the newly added payment processor..


FAQs

Can I switch the payment processor in the middle of my event? Will this disrupt my page?

You can switch your page's payment processor at any time without disrupting your event page or attendees' experience. Once you publish the change, the new processor immediately start accepting the new transactions, and there will be no interruption in payment processing as long as the new processor is properly set up.

Orders and payments submitted before switching will continue to be processed and refunded through the original payment processor. Any new orders and payments after the switch will be processed through the new payment processor.

Why am I receiving the error "Failed to add payment method?"

You are likely receiving this error because your page is already connected to a credit card processor. TicketSpice supports only one credit card processor per page. To add a new payment processor to your page, we recommend first deleting your current credit card processor, and then adding the new processor to the page.

If you've already deleted your current credit card processor from the page, we recommend performing a hard refresh on your page and then attempting to add the payment processor again. To do a hard refresh, you can use the following shortcuts

  • Windows: Ctrl+R

  • Mac: CMD+R

How Many Payment Processors Can be Attached to 1 TicketSpice Page?

A TicketSpice page can be connected to one credit card processor. If your organization would like to add more than one payment processor to a page, we recommend creating multiple TicketSpice pages, and adding a different payment processor to each of these pages.

Can I issue refunds for past payments if I remove a payment processor from my page in the middle of my event?

Yes, you can still issue refunds for past payments if a payment processor is removed from the page. Our system will issue these refunds through the former processor.

What happens to the old payment processor when we switch payment processors on a page?

The previous processor will remain in your account unless deleted by one of your users. If a user deletes the processor from TicketSpice, it will no longer appear as an option for linked processors, and users will no longer be able to issue refunds through TicketSpice. Deleting a processor from TicketSpice doesn't delete the processor's existence entirely β€” you can still access the payment processor directly from the payment processor's login.

We recommend not deleting a payment processor from your TicketSpice account after you've processed payments, as doing so will prevent you from issuing refunds through that processor in TicketSpice.

Did this answer your question?