Tutorial: Set Up Conditional Payment Connectors With Workflow


Join our newsletter!

Receive the latest data collection news in your inbox.

If you’ve been playing around with our new Workflow solution, you’ve probably found many new use cases to help your organization upgrade your form usage and streamline processes. One use case you might not have tried yet is setting up conditional payment connectors. 

If you have a situation where you want to easily offer multiple payment types or you have a form that only takes payments some of the time, Workflow can help you set things up so your connector only runs when you want it to. 

Conditional Payment Connectors Before Workflow

Before Workflow, you could add conditional payment connectors but you would have to use a workaround, such as a two-form process or using form calculations to set the values in one connector to zero. 

Without one of these workarounds, payment connectors would run every time the form was submitted, but with Workflow they can run only when you need them to. 

Setting Up Conditional Payment Connectors 

If you’re interested in this tutorial, you’re probably experiencing one of the two situations: 

  • You have two different types of payment methods, PayPal and Stripe for example, and you’re trying to run one or the other.
  • You have one type of payment connector but you don’t want it to run every time the form runs.

In both of these situations, the conditional path capabilities in Workflow will let you trigger payment connectors conditionally with much less manual work. 

Let’s break down the general flow: 

  1. Set up one form that allows people to choose how they would like to submit their payment, such as through PayPal, Stripe, Authorize.Net.
  2. Based on the answer, configure the conditional settings to send the respondent down a path specific to their selection. Essentially, this will send them to a form that uses the payment connector they indicated. 

Note: To use this method on a form that doesn’t always collect payment submissions, simply add a question at the end of your form to let people specify whether or not they would like to donate. If the answer is no, they would simply be sent to a thank you page upon submit. If the answer is yes, you could simply direct them to a payment form using the conditional pathing abilities in Workflow. 

Using Workflow vs. Workarounds 

If you ever used a two-form process to conditionally run a payment connector, you’ve essentially done what we’re describing here, just with more manual work and configuration. Workflow offers several real benefits over the previous workarounds: 

  • With Workflow, this process is much more seamless than using workarounds. It also allows you to visualize your process from a high-level instead of having to picture the flow of data between forms in your head. 
  • Instead of having to manage multiple different forms and redirect formulas, you’re managing one Workflow with individual workflow responses. 
  • Using Workflow, you no longer have to build complicated, lengthy redirect URLs or deal with URL length limits when you want to redirect users to certain forms.

Could you use this use case at your organization? Explore other ways Workflow could take your organization to the next level.

Don’t just collect data
— leverage it