The payment widget provides a link between doForms and the Flint Payment App (www.flint.com) which is available for Android and iOS. Flint is a feature rich payment system that allows payments to be made in cash, by check, or using a debit or credit card. No card scanner hardware is required. Just use the camera to take a picture of the card. Note that Flint is available for US payments only.
Place this widget at the point in your form where you wish to collect a payment for goods or services. In the example below, the Payment widget is placed after a series of questions that describe services provided.
Pressing the "Flint Payment" button above will transfer control from the doForms app to the Flint payment app where the payment is made (see below). During the transfer from doForms to Flint, doForms will pass the following parameters to the Flint app. Values for these parameters come from prior (upstream) question widgets in your form:
- Transaction Subtotal
- Transaction Tax
- Transaction Memo
- Recipient Email Address
- Customer Name
- Customer Phone
The flint screen will look similar to the picture below:
Upon completion of the Flint payment transaction, control is passed back to the doForms app, after which the form will be completed as normal (see below). During the transfer back from Flint to doForms, the Flint app will pass the following parameter back to doForms:
- Transaction ID
- Amount Paid
When you set up the Payment widget in your form, you will select downstream “destination” questions where these values will be written. On the mobile device the completed and confirmed payment might look something like this:
Note that the Flint app must be installed on the same mobile device as doForms and you must be signed up with a Flint account before using. The user must also be "logged in" to the Flint app. Click here to sign up for a Flint account, then download the app to your device from the Play Store or App Store.
Adding the Auto-number widget is as simple as using a “drag and drop” motion to place it on the form canvas. The properties that are "passed to Flint" are shown as the top set of arrows in the illustration below. The properties that are "returned by Flint" are the bottom two arrows below.
The Payment widget has the following special properties which you use to control its look and behavior. Some of these are illustrated above.
Caption text - Refers to the question caption as presented to the user. Think of this as the title for the question; it should be self-descriptive. We recommend no more than three words for optimal display on mobile devices.
Hint - Additional help for the question will be displayed; short clear sentences work best. Use 80 characters or less for optimal display on mobile devices. The maximum number of characters is 500, including spaces. The following HTML formatting tags are currently recognized:
Android: <br>, <i>, <b>, <u>, <font color="xxx">, <H1>, <H2>, <H3>, <H4>, <H5>, <P>, <a>, <div>;
PDF reports: <br>, <font color="xxx">.
Data name - Represents the name of the data that will be displayed in column headings. This property is automatically filled in based on the Caption Text but may be modified in the properties area. We recommend one or two word data names to keep column headings short. The maximum number of characters is 30. Spaces are not permitted in the Data Name field.
Use image – Check this option if you wish to upload or select a custom button image.
Image – Allows you to upload or select a custom button image to be used as a button (as an alternative to a standard doForms button shape). There is no restriction on the size of the image. If you want your custom buttons to have text, then this text needs to be embedded in the image prior to upload. Accepted image formats are JPG, GIF and PNG.
Button text – Allows you to specify the text that will be displayed in a standard button format. If you use an image instead of the standard button format, the image will need to contain any desired text.
Button/Image justification – Controls the justification of the standard button or button image (left, center, right).
Transaction subtotal (required input) - Subtotal to be paid. Select a prior Numeric or Calculation widget in the form that will provide this value. The Total Amount that will be paid will be calculated as the sum of Transaction Subtotal plus Transaction Tax. It must be a value less than or equal to 99999.99.
Transaction tax (input) – The transaction tax to be added to the Subtotal. Select a prior Numeric or Calculation widget in the form that will provide this value. It must be a value less than or equal to 99999.99.
Transaction memo (required input) – Description of transaction (e.g., payment for specific goods or specific services). Select a prior Text or Lookup widget in the form that will provide this value. It cannot contain ampersand (&) characters.
Recipient email address (optional input) – Email address that will receive email receipt. Select a prior Text or Lookup widget in the form that will provide this value. Only one email address can be provided. Value cannot contain ampersand (&) characters.
Customer name (optional input) – Name of customer. This can be different than the name of the credit card holder (e.g., a company name). Select a prior Text or Lookup widget in the form that will provide this value. It must be less than 64 characters. Value cannot contain ampersand (&) characters.
Customer phone (optional input) – Customer’s telephone number. This can be different than the phone number of the credit card holder. Select a prior Numeric-Integer, Text or Lookup widget in the form that will provide this value. Value cannot contain ampersand (&) characters.
Transaction ID (returned value) – ID of Flint payment transaction if successful. Select a Text destination question for this returned value if you wish to include it in your form.
Amount paid (returned value) – Total amount paid by customer. Select a Numeric destination question for this returned value if you wish to include it in your form.
Advanced - Clicking on the Advanced arrow will reveal “Relevance conditions” properties that can be used of further control the behavior of your form using sophisticated logical statements. Please refer to http://support.doforms.com/hc/en-us/articles/200446034 for more information on these properties.