Aura Setup and Support

Adding and/or Hiding Static Defaulted Values

The Aura form can be enhanced further to allow default values to be added directly within the script once it has been embedded within the webpage or via the URL of the webpage directly. These defaulted values will be visible to the end user unless additional hidden values are included within the script (certain values only).

Method 1: Adding Values Via the Script Directly

The below table of variables can be appended to the value of the ‘src’ tag in the script, following the PaymentBoxPID variable by using the following format &[variable]=[value].

For example, to default the Country field value to US:

• Copy of the original script copied from the Aura setup page:

<script type="text/javascript" src="https://www.iatspayments.com/AURA/AURA.aspx?PID=PACE4C7CC915152DCB"></script>

• Copy of the script after appending the default values to set the default Country field to US:

<script type="text/javascript" src="https://www.iatspayments.com/AURA/AURA.aspx?PID=PACE4C7CC915152DCB&Country=US"></script>

To hide fields within the Payment section and therefore the defaulted value, un-check the “Visible” checkbox beside the field within Aura setup. Even though the field is hidden, the defaulted value is still pushed to iATS.

Please note that some Recurring Schedule fields do not have a “Visible” checkmark option, such as the End Date. In order to hide these values (only values indicated in table below), specific variables can be hidden by using the following format: &[Hidevariable]=[True]

For example, to hide the Recurring End Date:

• Copy of the script after hiding the defaulted End Date:

<script type="text/javascript" src="https://www.iatspayments.com/AURA/AURA.aspx?PID=PACE4C7CC915152DCB&HideRecurringEndDate=True"></script>

The following input fields can be defaulted with specific values for the end user using the script method above:

The following fields can be hidden from the end user using the script method above:

Method 2: Adding to URL

The below table of variables can be appended to the URL by using the following format:

?[variable]=[value].

For example, to default the Country field value to US:

http://home.iatspayments.com/test?Country=US

Using this method you have the option of utilizing the BELOW table of values, but may also add your own custom fields if desired. Please note these custom fields will be sent to iATS and included in the “Aura Post Back” contents if collecting data via post, however does not interact with our Salesforce application Brickwork.

• For example, to default a custom field to Generic Annual Appeal:
  http://home.iatspayments.com/testFundName=GenericAnnualAppeal
• To combine variables include an “&” ampersand after each entry, such as:
  http://home.iatspayments.com/testIATS_PaymentItemInput_CountryUS& FundName=GenericAnnualAppeal

The following input fields can be defaulted with specific values for the end user using the URL method above:

Pre-populating Dynamic Values

The Aura form can be customized to pre-populate dynamic values for the end user. For example, if a member is signing up for a yearly membership, a series of questions can be asked on a prior web-page. Depending on the responses to the questions, a different dollar amount can be pre-populated in the Total field.

You can pre-populate values by appending additional values to the script or the page URL where the Aura form is embedded. All variables can be appended by using the following format: &[variable]=[value].

The variables' names must be standard ones within the default tables above in order to pre-populate the proper values.

For example, if the page URL where Aura form is embedded is https://www.SAMPLE.com, the correct method to pre-populate the first name and last name is to update the URL to https://www.SAMPLE.com?Firstname=first name&LastName=last name.

Note: Please be aware that if the same variable is appended to both Aura script and page URL, the values within the Aura script will be overwritten.

Email Customization

Additional customizations can be applied to the Notification Email that is sent to the end user.

When the variables listed below are added to the Email set-up, the information will be contained within the body of the email.

If the end user did not provide information in the field, for example if the Comment field was left blank, the variable field within the email body ([#COMMENT#]) will contain a blank space.  To avoid this, the field can be marked as required in the Aura Setup. 

Note:

• Emails containing <img> tags may be blocked by the end user’s email account due to security concerns, and may prevent the email from being delivered successfully. Images can be added at your discretion.
• The below values are case sensitive. Please use only uppercase letters as per table.

Adding Images to Description Using HTML

Format for placing an image:

<IMG SRC=’image.gif’ ALT="some text" WIDTH=32 HEIGHT=32>

Note: The value in width and height are just examples. The ALT stands for ‘alternate text’. It tells the browser that if it cannot find the image, it just displays the text. It also tells what the image is about if anyone cannot view the image.

• SRC stands for “source”. This is an attribute. It’s telling the browser where to go to find the image. You will need to indicate the full URL of the image in the source attribute.

For example: src=http://www.testwebsite.org/publicImages/thumb_donorbutton2.jpg

Note: The URL of the image above is just an example. You will need to provide the correct URL.

• Please note that when adding an image in the Description box, the URL value in SRC should be enclosed in single quotes and not double quotes.

To make the image work in the Description box, here is the correct code:

The following are basic image formats (and recommended) on the web:

• GIF
• JPEG or JPG
• PNG

If you have any questions regarding adding images using HTML, please contact iATS Customer Care at 0808-234-0466, or iatscs@iatspayments.com.