Elevate Connector 

In this Article
Related Articles


With FormAssembly's Elevate Connector, you can easily process one-time credit card payments and set up recurring credit card payments. This connector is available for Premier plans and above and must be set up on a form-by-form basis.

Provided you have a Elevate account, you can follow the steps below to configure the connector and begin processing payments.

We also recommend reading more about how you can use reCAPTCHA to prevent spam submissions, as well as our Connector Labels to keep your connectors organized.


In addition to a FormAssembly account, you'll also need a Elevate account to process payments.

Required Fields

Different from our other payment connectors, you should not add fields for credit card information in your form. After setting up and saving your connector, credit card information fields will be added automatically. 

As you build your form, make sure to collect the following information:

  • Cardholder's first name
  • Cardholder’s last name
  • Cardholder's email address
  • Donation type (single / recurring)
  • Donation amount
  • Donation frequency (day, week, month, year)
  • Donation interval (must be an integer, every ___ day/week/month/year)

Please Note: Unlike our other payment connectors, the Elevate Connector cannot be skipped by setting the quantity to 0.  Any form the connector is enabled on must collect credit card information and must run every time the form is submitted. You can refer to this blog post for an example of how to set up a two-form process to help address this limitation.

Configuration Steps

  • Step 1. Your Elevate Authorization
  • Step 2. Donation Information
  • Step 3. Donor  Information
  • Step 4. Product Metadata

Prior to configuring your connector, you will need to add it to your connector timeline.

First, select the form you are working with and go to the Connectors page.

Next, add the connector into the Form Submitted portion of the timeline and click Configure.

Step 1. Your Elevate Authentication 

The first step in your connector setup will be to connect to Elevate.  You will need to decide if you are connecting to your Sandbox or Production instance.

From that instance, you will be able to get your Client ID, Merchant ID, and the Gateway ID for the specific payment gateway you would like to use.  Please note, only one payment gateway can be used with each form.

Please Note:  Make sure the URL of the integration instance you are pulling the IDs from matches your connector.  For example, if you are connecting to the Sandbox instance, your URL would look like this: with demo in the URL. 

Step 2. Donation Information

Once you have entered your credentials, you are ready to configure your donation information.

In the form, you will need to have fields for:

  • Donation type (single / recurring)
  • Donation amount
  • Donation frequency (day, week, month, year)
  • Donation interval (must be an integer, every ___ day/week/month/year)

Even if you plan to only collect one type of donation, you will still need to have fields in the form to map to. The Elevate Connector cannot use formulas. You can use hidden fields to accomplish this if you do not want respondents to choose between donation types, intervals, etc. 

Donation type and frequency will need to be mapped to radio buttons in your form.  We also recommend adding a number validation to the interval field in your form. 

Step 3. Donor Information

Finally, you will need to map your donor information in the connector.

At a minimum, you will need to collect and map:

  • Cardholder's first name
  • Cardholder’s last name
  • Cardholder's email address

Please Note: Your payment gateway may require additional information to successfully process payments.  If you are receiving error messages from your payment gateway, it may be because you are not sending all the required information.  When in doubt, confirm with your payment gateway what information is required.

Step 4. Product Metadata

This section allows the donations to be linked to a Salesforce campaign. In order to locate the Salesforce campaign, you can select one of two options:

  1. "Defined here:" This option allows you to link a single campaign to each donation by typing the Campaign ID into the text field. Every donation submitted through this connector will be linked to the associated campaign.
  2.  "Defined in the form:" This option allows you to dynamically link a different campaign to each donation by utilizing a Campaign ID collected in the form. To do this, you will need to select the form field which will be collecting the Campaign ID. This field can be prefilled with a Campaign ID, filled in by the form respondent, or you can even use Form Calculations to pull a different Campaign ID into this field based on previous form selections.

Auto-Created Form Fields and Tokenization

When the Elevate Connector is added to the timeline, enabled, and saved, it automatically adds 2 fields to its associated form. 

First, the connector will add the credit card information collection fields to your form:

These will all be added as a single field in the form of an HTML snippet.   These fields cannot be edited or styled. They will all be required for form submission.

Second, the connector will add an “Elevate Payment Token” field. This will be a hidden field that will be populated with the payment token upon submission of the form. 

If you would like to send this token to Salesforce, you can add a Salesforce Connector after the Elevate Connector in the Connector Timeline.  In your Salesforce Connector, you can map the Elevate Payment Token field to send the data to your records.

Please Note: Any Salesforce records you have configured to be created upon receiving a payment through Elevate will be created upon submission of a successful payment through your form. However, some of the actions that occur upon submission of a successful payment are asynchronous within Elevate. This means that even if a payment has been successfully completed, it may take time for Salesforce to fully run all the associated processes and triggers.  

Terms of Service · Privacy Policy