This is an old revision of the document!
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.
This document is intended for Versago administrators and end-users that are responsible for supporting the payments process. End-users do not have access to the configuration functions.
The following pages contain additional information that may be helpful with understanding these processes.
This document is intended for Versago administrators. End-users do not have access to this 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.
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.
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.
Notes
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.
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.
This report utilizes a SQL View as the data source. The View must be created manually in the database. Code to create the View is provided below.
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.
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.
In general, the “Response” information will be the most helpful for troubleshooting unsuccessful transactions since it shows the reason a transaction was rejected.