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.

For the payment information in Versago to be processed into SAP Business One, some specific values must be defined. This is done using the “Versago Payment Info Mapping” form.

1. Click the look-up (funnel) icon in each credit card field to see a list of credit cards defined in your SAP Business One system.
   1. Select the card that matches the label on the field.
   2. The internal SAP code is displayed in the right-hand column.
   3. If you do not accept a particular type of card (Discover in this example), leave the field blank.
2. Click the look-up icon in the “eCheck GL Account” field to select the appropriate GL account where bank transfers will be posted.
   1. The internal SAP code is displayed in the right-hand column.
3. Enter the URL to your Bizweaver instance that will process the payments into SAP Business One.
   1. Be sure to include HTTP:// or HTTPS:// as appropriate.
4. Enter the port used by your Bizweaver instance.
5. Enter the Bizweaver workflow ID that will process the payments into SAP Business One.

Notes

• Credit cards must be defined in your SAP Business One system before item 1 can be defined.
• The internal SAP codes are displayed for support purposes only. The user does not need to be concerned with them during the configuration process.
• Your system administrator should be able to provide you with the information needed for items 3 and 4.
• The workflow to process payments from Versago will need to be imported (or created) in Bizweaver before item 5 can be set. This value will be different for each installation.

Once any of the codes have been defined and saved, the associated report, “Versago Payment Info Mapping” must be used to review and update values. The maintenance form will not allow more than one record to be created.

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. One is to have the Bizweaver workflow set on a schedule so that it executes periodically during the day. Second 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.

A basic database trigger to initiate Bizweaver processing for payments will look like this.

payments_trigger_sql.txt

CREATE TRIGGER [dbo].[twbs_tr_VersagoPayments]
ON [dbo].[Versago_Payments]
AFTER INSERT
AS
BEGIN
-- SET NOCOUNT ON added to prevent extra result sets from
-- interfering with SELECT statements.
SET NOCOUNT ON;
--
DECLARE
@vgo_BatchID INT,
@object INT,
@url VARCHAR(5000),
@bw_url nvarchar(100),
@bw_WorkflowID INT,
@bw_port INT,
@pArgVariableName nvarchar(50)
--
/* It may be necessary to change all instances of "vgoCommon" to a different name if you have used a different name */
SELECT
t0.BW_URL, t0.BW_Port, t0.BW_WorkflowID
FROM vgoCommon..twbs_vgo_payment_InfoMapping t0
--
SET @pArgVariableName = 'vgo_BatchID'
SELECT @vgo_batchid = (SELECT vgo_batchid FROM inserted)
SELECT @bw_url = (SELECT t0.bw_url FROM vgoCommon..twbs_vgo_payment_InfoMapping t0)
SELECT @bw_port = (SELECT t0.bw_port FROM vgoCommon..twbs_vgo_payment_InfoMapping t0)
SELECT @bw_Workflowid = (SELECT t0.BW_WorkflowID FROM vgoCommon..twbs_vgo_payment_InfoMapping t0) 
--
SELECT @url = @bw_url + '/BWService/api/workflow/InvokeWorkFlow?pTaskID=' + CAST(@bw_WorkflowID AS VARCHAR) + '&pStartAfter=0&pArguments={' + @pArgVariableName + ':' + CAST(@vgo_BatchID AS VARCHAR) + '}'
EXEC sp_OACreate 'MSXML2.XMLHTTP', @object OUT;
EXEC sp_oamethod @object, 'open', NULL, 'get', @url
EXEC sp_oamethod @object, 'send'SELECT @url
--select @responsetext as [Response]
-- select @url
EXEC sp_oadestroy @object
END

The following video illustrates this process.

.

Two main reports are provided for users to review payment transactions and resolve issues. These reports are Versago Payments Recap and Payments Transaction Log. The standard location for these reports is in the ‘Payments Admin” menu category.

Detailed information about successful payment transactions can be viewed using the “Versago Payments Recap” report. This report displays details about each transaction, including invoices paid, information sent to the processing gateway, and the response from the gateway.

Create the view in the VersagoData database (or whatever database name you may be using to capture Versago form data).

CREATE VIEW [dbo].[vgo_vw_PaymentTransactions] AS
SELECT DISTINCT
t0.vgo_transid,
(SELECT SUM(x0.BalDue) FROM Versago_Payments x0 WHERE x0.vgo_transid = t0.vgo_transid GROUP BY x0.vgo_transid) AS [TtlAmtPaid],
CASE t0.vgo_paymenttype
WHEN 1 THEN 'Credit Card'
WHEN 2 THEN 'eCheck'
END AS [TransType],
CAST(t0.vgo_paymentdate AS DATE) AS [vgo_PaymentDate],
(SELECT COUNT(*) FROM Versago_Payments x0 WHERE x0.vgo_transid = t0.vgo_transid) AS [DocCount],
t0.vgo_PostingStatus, t0.vgo_PostingDate, t0.vgo_PostingId
FROM Versago_Payments t0

Use the Payments Transaction Log report for information about unsuccessful transactions.

1. Expand the row to see a list of invoices paid.
2. The “SAP Posting Status” indicates if the transaction has been posted into SAP Business One.
   1. “0” indicates that the transaction has not been processed.
   2. “1” indicates that the transaction has been posted successfully.
   3. “9’ indicates that the transaction posting failed.
      1. Click on a “9” to see the reason the SAP posting failed.

• Click the Transaction ID link to view details of the transaction.

1. Click on the CC Request or eCheck Request link as appropriate to view the information that was sent to the gateway for processing.

• Click on the Response link to view the information that was sent to back from the gateway.

The Payments Transaction Log report is like the Payments Processing Recap report, except that it shows both successful and unsuccessful transactions.

Note that the “Transaction ID” for unsuccessful transactions begins with “E” followed by the log record ID, and the date & time of the transaction.

1. Click on the “CC Request” or “eCheck Request” link as appropriate to view the information that was sent to the gateway for processing.
2. Click on the “Response” link to view the information that was sent to back from the gateway.

In general, the “Response” information will be the most helpful for troubleshooting unsuccessful transactions since it shows the reason a transaction was rejected.