This document describes the steps to configure Versago to accept credit card and eCheck payments. It also describes the reports available to provide traceability for Versago Payments processing.

The following pages contain additional information that may be helpful with understanding these processes.

• Email & Password Configuration

• “eCheck” means payments based on checking accounting information submitted through a payment gateway such as Authorize.net.

• Click on the Admin link in the profile section of the Versago home page to access the Administration console.
• Payments configuration is found in the Settings category to access the function.

The Payment configuration function is used to identify the payment gateway, and associated credentials, to be used for processing payments accepted through Versago.

Email will also need to be configured to allow the user to send a confirmation page for their payment transaction.

• Click on the “Payment Setup” link in the Admin console to begin.

1. Select the appropriate Payment Gateway from the drop-down list.
   1. As of August 2018, the only available gateway is Authorize.Net. Additional gateways will be provided in future releases.
   2. Your company will need an account with the selected gateway before completing this setup since this is how you will get your credentials.
2. Enter the Merchant Login provided by your gateway.
3. Enter the Merchant Password provided by your gateway.
4. Select the payment method(s) you wish to accept.
   
   

   Be sure the checkbox is cleared if you do not want to accept a payment method. In the illustration above, American Express is not accepted and will not be presented as an option for the user.

5. Click the Demo option during testing only. This option must be cleared for production operations.

Review the Reports Configuration page. The basic process through the “Display” step is the same for record selection reports. Details of the basic setup are not included in this document.

• Click on the Admin link in the profile section of the Versago home page to access the Administration console.
• Reports, Charts and Calendars configuration is found under the Dynamic Content category of the menu.

• The format selected in the Presentation Form section must be “Report/Chart.”
• The “Enable Paging” option should not be selected.

• All options described in the basic configuration are available.
• For externally facing reports there will almost always be a User Profile value. This way users will only see their documents.

• All options described in the basic configuration are available.

The “Record Submission” page is used to configure the report for record selection. When the “Enable Record Submission” checkbox is selected, additional configuration items are displayed.

Also select the “Process Payments” option checkbox if this report will be used for accepting and processing credit card and eCheck payments.

Configuration of Record Submission reports for payments is described in the documents Versago – Payments Setup.

See the Record Submission Configuration page for detailed information on configuring the record submission information.

This tab is skipped in this setup process.

• All options described in the basic configuration are available.

• All options described in the basic configuration are available.

Charts should not be used with Record Selection reports.

In a Versago environment, back-end processing is typically done using Bizweaver. The information here refers to Bizweaver but other process flow tools might be used as well.

Most record submission reports will have an associated Bizweaver workflow to handle additional processing. For payments this might be creating SAP Business One Incoming Payment transactions. Or it might be updating the status on a group of orders.

There are two ways to initiate this processing. The most basic approach is to have the Bizweaver workflow set on a schedule so that it executes periodically during the day.

The more sophisticated approach is to initiate the workflow when the submission is saved to the database. For the second option a database trigger is used.

The SQL database needs to be initialized to allow triggered (immediate) processing to occur. The initialization process is described here. Examples of the trigger used to initiate Bizweaver processing are then found in the lower section of the page.