Wiki

Scale Your Enterprise

User Tools

Site Tools

Trace: • Filters • Introduction (Bizweaver) • downloads • Versago Upgrade • Introduction (Email and Password Configuration) • Site Theme • Introduction (Payments) • Links • APP - Report Maintenance and Delivery Screens • System
versago:payment_configuration_and_reports

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
versago:payment_configuration_and_reports [2019/06/04 14:28]
runger 		versago:payment_configuration_and_reports [2020/11/04 11:19] (current)
dlee
Line 2: Line 2:
  
 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 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.
- 
-====== Audience ====== 
- 
-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. 
  
 ====== Related Pages====== ====== Related Pages======
Line 11: Line 7:
 The following pages contain additional information that may be helpful with understanding these processes. The following pages contain additional information that may be helpful with understanding these processes.
  
-  * [[versago:email_password_configuration|Versago – Email & Password Configuration]]+  * [[versago:email_password_configuration|Email & Password Configuration]]
  
 ====== Special Terminology ====== ====== Special Terminology ======
Line 18: Line 14:
  
 ====== To Begin ====== ====== To Begin ======
- 
-This document is intended for Versago administrators. End-users do not have access to this function. 
  
   * Click on the Admin link in the profile section of the Versago home page to access the Administration console.   * Click on the Admin link in the profile section of the Versago home page to access the Administration console.
Line 32: Line 26:
   * Click on the “Payment Setup” link in the Admin console to begin.   * Click on the “Payment Setup” link in the Admin console to begin.
  
-{{:versago/payments1.png?576x208}}+{{  :versago/payments1.png?576x208  }}
  
   - Select the appropriate **Payment Gateway** from the drop-down list.   - Select the appropriate **Payment Gateway** from the drop-down list.
Line 39: Line 33:
   - Enter the **Merchant Login** provided by your gateway.   - Enter the **Merchant Login** provided by your gateway.
   - Enter the **Merchant Password** provided by your gateway.   - Enter the **Merchant Password** provided by your gateway.
-  - Select the payment method(s) you wish to accept.  \\ \\ <WRAP center round important 50%>+  - Select the payment method(s) you wish to accept.  \\ \\ <WRAP center round important 100%>
 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. 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.
 </WRAP> </WRAP>
   - Click the Demo option during testing only. This option must be cleared for production operations.   - Click the Demo option during testing only. This option must be cleared for production operations.
  
-====== Mapping SAP Business One Values ====== 
  
-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.+====== Payment Selection Report Setup ====== 
 +Review the **//[[versago:report_configuration|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. 
 +===== To Begin ===== 
 +  * 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.
  
-{{:versago/payments2.png?576x298}}+===== Report Setup tab =====
  
-  - 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. +  * The format selected in the Presentation Form section **must** be “Report/Chart.” 
-    - Select the card that matches the label on the field. +  * The “Enable Paging” option should not be selected.
-    - The internal SAP code is displayed in the right-hand column. +
-    - If you do not accept a particular type of card (Discover in this example), leave the field blank. +
-  - Click the look-up icon in the “eCheck GL Account” field to select the appropriate GL account where bank transfers will be posted. +
-    - The internal SAP code is displayed in the right-hand column. +
-  - Enter the URL to your Bizweaver instance that will process the payments into SAP Business One. +
-    - Be sure to include HTTP:%%//%% or HTTPS:%%//%% as appropriate. +
-  - Enter the port used by your Bizweaver instance. +
-  - Enter the Bizweaver workflow ID that will process the payments into SAP Business One.+
  
-**Notes**+===== Filters tab =====
  
-  * Credit cards must be defined in your SAP Business One system before item 1 can be defined. +  * All options described in the basic configuration are available. 
-  * The internal SAP codes are displayed for support purposes only. The user does not need to be concerned with them during the configuration process. +  * For externally facing reports there will almost always be a User Profile value. This way users will only see their documents.
-  * 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.+===== Display Tab =====
  
 +  * All options described in the basic configuration are available.
  
 +===== Record Submission Tab =====
  
-====== Reports Overview ======+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.
  
-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.+{{  :versago/recordsub2.png?384x109  }} 
  
-====== Versago Payments Recap Report ======+Also select the “Process Payments” option checkbox if this report will be used for accepting and processing credit card and eCheck payments.
  
-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.+Configuration of Record Submission reports for payments is described in the documents //Versago – Payments Setup//.
  
-<WRAP center round important 60%> +See the //**[[record_submission_configuration|Record Submission Configuration]]**// page for detailed information on configuring the record submission information.
-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.   +
-</WRAP>+
  
-Create the view in the **VersagoData** database (or whatever database name you may be using to capture Versago form data). +===== Calendar tab =====
-<code sql> +
-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 +
-</code>+
  
 +This tab is skipped in this setup process.
  
-Use the [[#payments-transaction-log-report|Payments Transaction Log]] report for information about unsuccessful transactions.+===== Sub-Report tab =====
  
-===== Versago Payments Recap – Main Report =====+  * All options described in the basic configuration are available.
  
-{{:versago/payments3.png?700}}+===== Links tab =====
  
-  - Expand the row to see a list of invoices paid. +  * All options described in the basic configuration are available.
-  - The “SAP Posting Status” indicates if the transaction has been posted into SAP Business One. +
-    - “0” indicates that the transaction has not been processed. +
-    - “1” indicates that the transaction has been posted successfully. +
-    - “9’ indicates that the transaction posting failed. +
-      - Click on a “9” to see the reason the SAP posting failed.+
  
-{{:versago/payments4.png?700}}+===== Chart tab =====
  
-  * Click the __Transaction ID__ link to view details of the transaction.+Charts should not be used with Record Selection reports.
  
-===== Payments Log Sub-report =====+====== Back-End Processing ======
  
-{{:versago/payments5.png?700}}+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.
  
-  - Click on the __CC Request__ or __eCheck Request__ link as appropriate to view the information that was sent to the gateway for processing.+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.
  
-===== Payments Log Request (CC and eCheck) Sub-report =====+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.
  
-{{:versago/payments6.png?700}}+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.
  
-{{:versago/payments7.png?700}} +<WRAP center round important 60%> 
- +The following discussions assumes that you have some knowledge about database triggers and have access to the SQL Server tools needed to install them. 
-===== Payments Response (CC and eCheck) Sub-report ===== +</WRAP>
- +
-{{:versago/payments8.png?700}} +
- +
-{{:versago/payments9.png?700}} +
- +
-  * Click on the __Response__ link to view the information that was sent to back from the gateway. +
- +
-====== Payments Transaction Log Report ====== +
- +
-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.+
  
-{{:versago/payments10.png?700}}+The SQL database needs to be initialized to allow triggered (immediate) processing to occur.  The initialization process is described **//[[bw:call_bizweaver_web_service_from_sql_server|here]]//**.  Examples of the trigger used to initiate Bizweaver processing are then found in the lower section of the page.
  
-  - 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. 
  
-In general, the “Response” information will be the most helpful for troubleshooting unsuccessful transactions since it shows the reason a transaction was rejected. 
  
versago/payment_configuration_and_reports.1559672926.txt.gz · Last modified: 2019/06/04 14:28 by runger

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial 4.0 International
CC Attribution-Noncommercial 4.0 International Valid HTML5 Valid CSS Driven by DokuWiki