versago:payment_configuration_and_reports
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
versago:payment_configuration_and_reports [2020/08/12 09:21] dlee [Payments Configuration] |
versago:payment_configuration_and_reports [2020/11/04 11:19] (current) dlee |
||
|---|---|---|---|
| Line 38: | Line 38: | ||
| - 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. | ||
| - | |||
| - | {{ : | ||
| - | |||
| - | - 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. | ||
| - | - Select the card that matches the label on the field. | ||
| - | - 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: | ||
| - | - Enter the port used by your Bizweaver instance. | ||
| - | - 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. | ||
| ====== Payment Selection Report Setup ====== | ====== Payment Selection Report Setup ====== | ||
| Line 130: | Line 104: | ||
| - | |||
| - | |||
| - | ====== Reports Overview ====== | ||
| - | |||
| - | 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 Payments Recap Report ====== | ||
| - | |||
| - | Detailed information about successful payment transactions can be viewed using the “Versago Payments Recap” report. This report displays details about each transaction, | ||
| - | |||
| - | Use the [[# | ||
| - | |||
| - | ===== Versago Payments Recap – Main Report ===== | ||
| - | |||
| - | {{ : | ||
| - | |||
| - | - Expand the row to see a list of invoices paid. | ||
| - | - 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. | ||
| - | |||
| - | {{ : | ||
| - | |||
| - | * Click the __Transaction ID__ link to view details of the transaction. | ||
| - | |||
| - | ===== Payments Log Sub-report ===== | ||
| - | |||
| - | {{ : | ||
| - | |||
| - | - Click on the __CC Request__ or __eCheck Request__ link as appropriate to view the information that was sent to the gateway for processing. | ||
| - | |||
| - | ===== Payments Log Request (CC and eCheck) Sub-report ===== | ||
| - | |||
| - | {{ : | ||
| - | |||
| - | {{ : | ||
| - | |||
| - | ===== Payments Response (CC and eCheck) Sub-report ===== | ||
| - | |||
| - | {{ : | ||
| - | |||
| - | {{ : | ||
| - | |||
| - | * 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. | ||
| - | |||
| - | {{ : | ||
| - | |||
| - | - 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.1597238484.txt.gz · Last modified: 2020/08/12 09:21 by dlee
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial 4.0 International
