CDI
- Dec 21, 2023
- 3 min read

Start Taking Payments in Laserfiche Cloud

By Kyle Knebel

December 2023 Consultants Corner

Setting up the Payment Gateway

For Laserfiche Cloud users, CDI is proud to introduce support for Authorize.net and Forte for Credit Card and eCheck payments. With a Cloud Payment Gateway subscription purchased through CDI, you can begin taking payments by credit card or Check.

Setting up payment acceptance in Laserfiche Forms Business processes is quick and easy. All it takes are three components and just a few minutes of configuration time.

The main components needed are:

CDI’s Cloud Payment Gateway subscription (contact your CDI Account Representative)
An Authorize.net plan or Forte payment solution plan (and possibly a Merchant account) from those vendors.
A Laserfiche Cloud Account and access to Process Automation

Having purchased a CDI Cloud Payment Gateway subscription, the Payment Gateway components will already be available in your Cloud system for use in Forms Business Processes. You are now ready to build an e-form accepting credit card payments. Let’s look at a simple example of an Authorize.net based payment form for a Credit Card-based transaction.

Step 1: Setup the Payment Gateway

Go to the CDI Cloud payment gateway link provided to you when you purchased the CDI Cloud Payment Gateway subscription. This will be a unique link for your Cloud account that enables the payment gateways. You will need to accept the request for CDI Cloud Apps to access your Cloud account.

After accepting the request, begin setting up your Profile for the chosen payment provider. In our example, we’ll use Authorize.net.

Enter the Profile name describing the profile, which can be anything you desire. For example, “Sandbox – Authorize.net” when creating a profile for testing purposes. (Note: Sandbox profiles do not charge real money to a credit card when running tests.)

For production, you’ll want to create another profile that does not use the “Sandbox” switch, as seen at the bottom of the profile credentials box.

Add the API Login Id and then the Transaction Key to complete the profile. These values are provided by Autorize.net with your account.

Once the profile is created, it will display properties on the right side of the screen with two tabs, Settings and Configuration.

SETTINGS: The Settings tab allows you to configure acceptance of Credit Cards or eChecks/ACH transactions. For today, we’ll just configure it to accept Credit Cards.

Your Merchant Credentials will be automatically filled in. In the Payment Dialog Options section, toggle the “Accept Credit Cards” switch. Optionally, you can enter additional text for the payment pop-up dialog box’s title and enter alternative text that appears on the “Pay” button that is at the bottom of the payment pop-up dialog box.

CONFIGURATION: The Configuration tab provides the required information to be used in your form.

Step 2: Build the Form (Classic only, at this time)

Three fields are required on the form, and the names of those field variable names are listed in the top half of the configuration properties box. The “Amount_Due” field should be a Currency field and typically is a required field. Also, it should be read-only unless the form is designed to allow a user to enter the amount to pay.

The “Transaction ID” and “Authorization Code” fields can and should be hidden fields on the form. End users don’t need to see them. If hiding these two fields, make sure to set the “Save the data when the field/section/page is hidden” setting on each hidden field.

Next, at the bottom of the Configuration properties box is the line of JavaScript code that needs to be copied and pasted into the form’s JavaScript tab.

Insert the JavaScript code at the very top of the JavaScript section above any other existing code, if any.

Step 3: Configure the Rules Service Task within the Process Diagram

The image below is a sample and not indicative of a complete process diagram. The Rules Service task must immediately follow the Message Start Event.

Add the Rules Service task to your process diagram.

Choose the “Web Request” rule type, then choose the “CDI Forms Payment Gateway Capture” rule from the list.

Next, Click the “Add input values” link to configure the mapping of fields to the rule.

Select all the values in the list, then click “Update.”

For the “profileId” Rule parameter, you will need to use the unique value found in the JavaScript string you copied earlier.

Insert the Id value into the “profileId” box, and then add the field variables to the other three Input values, as shown.

Save and publish the process when it is completed.

Now, test your new form process. It will check for a valid credit card, but if using the Sandbox mode, no money will be charged to that card. If you subsequently toggle the Sandbox mode off, then real money will be charged! 😊

Submitting the form should result in seeing the Credit Card transaction window appear, as shown in this demonstration form screenshot.