Purpose:
The purpose of the this document is to help the person to configure and deploy the POS payment plugin with respect to different types of payment devices.
...
Project Description
This project is related to POS Plug-in Management.
Scope/Requirement Statement
Earlier, the MoP (Mode of Payment) configuration was a challenge as configured data needed to be synchronized in each POS system, separately. Hence, more the number of POS greater was the challenge. This was a big headache.
The challenges described above has triggered the requirement to have a solution to centralized The complexities of configuring the various MOPs in different POS, gave birth to POS Plugin Manager, which allows centralized the configuration and synchronization process with respect to MOP (Mode of Payment). The aim is to make life easy for the people responsible to perform the configuration.
...
Step #A: Configuring Plug-in Manager in Ginesys HO user interface
Step #B: MoP (Mode of Payment) configuration in Ginesys HO user interface
Step #C: Data Synchronization based on site from HO to POS
...
| Info |
|---|
| All the above mentioned steps are described with the screenshots for easy reference, in this document. |
Assumption
System prerequisites are met
Ginesys HO version availability (minimum v12.5.1). Recommendation is to have the latest available version.
POS version availability (minimum v2.5.1). Recommendation is to have the latest available version.
Payment reference number would not be displayed in the POS Bill. In-case if it is needed, an official requirement has to come through the respective Account Manager.
Any URL that Ginesys will provide needs whitelisting
The port number that would listen to the HTTP request needs to be kept open
Auto POS Plugin would support the following Paytm (in case the payment partner is Paytm) devices:
...
| Expand |
|---|
| title | Step #A: Configuring Plug-in Manager in Ginesys HO user interface |
|---|
|
Under the Setup tab, click on the Plugin Manager under Configure section.
 Click on Add to start configuring a new Plugin Manager. Under the General tab enter the following for the required fields.
 The name of the Plugin Short Code is a sample name only. In real deployment, Plugin Short Code needs to be provided by Ginesys and the same needs to be set for the Plugin Short Code. Hence it would vary from payment partner to payment partner.
| Tip |
|---|
Important - Please check the respective partners page for the Plugin Short Code and Plugin Assembly Name.
Irrespective of brand, EaseMyRetail should be selected as Plugin Vendor . |
| Info |
|---|
Target Config File Name: This is the original configuration file name as required by the plugin dll. File name should be without extension. |
- Do the Hook Mapping.
| Info |
|---|
Note: Copy-Paste the following values (to avoid typo) for the respective fields:
Hook Type : POS_PAY_PROCESS
Class Name : PaymentProcessor (Ginesys to provided this. Hence it will vary from partner to partner)
Method Name : ProcessPayment (Ginesys to provided this. Hence it will vary from partner to partner) |
| Tip |
|---|
Important - Please check the respective partners page for the Class Name and the Method Name. |
Move to the Config Files tab to specify the config file name. Click on the Add Row button to add a new row.  By clicking on the Add Row button, multiple configuration files can be added one after another. However any one can be marked as “Is Default”. Scroll to the right to find the Browse button for the newly added row.
 Enable the Is Default option.
 Click on the Browse button.
 Select the config file called app.config (this is a generic/sample configuration file).
 | Info |
|---|
It would be critical/important to select the proper app.config file and the basis would be which payment device is in use for taking the payment? Devices can be of two types - DQR and EDC. DQR is available in wired mode only. However, EDC devices are available in wired as well as wireless mode. Refer to the assumption section for detail.
Link to go to the application configuration page for Paytm
|
Click on the Upload button and then click on the OK button.
 Assign the site. The process is similar to how the site has been moved from the list of available site to the list of assigned site box.
 | Info |
|---|
In the “Site Allocation” tab and under the “Assigned Sites” list, the site against which the “Config File” column is blank for that the default configuration file (the one which has been selected for “Is Default”) will be considered. But if for an allocated site, the “Config File” column has a file name, that specific configuration file would be considered. |
Click on the save and close button at the top to save the Plugin Manager configuration.
 The configured Plugin Manager will now appear in the list of configured plugin managers.
 Plugin Manager configuration is now completed.
|
5.
11.
13.
Login to GinesysWeb HO from browser
| Anchor |
|---|
| MoP (Mode of Payment) configuration in Ginesys HO user interface |
|---|
| MoP (Mode of Payment) configuration in Ginesys HO user interface |
|---|
|
| Expand |
|---|
| title | Step #B: MoP (Mode of Payment) configuration in Ginesys HO user interface |
|---|
|
Login to Ginesys Web HO from browser.
 Image Added
| Info |
|---|
The user credential must have the required privileges. |
|
2.
Configure MoP (Method of Payment).
|
3.
 Image Added
- Select the tab called
|
“RETAIL MANAGEMENT”- “Desktop POS Manager”.
 Image Added
Select “Setup” option.
Select “Mode of Payment” option under the “Configuration” section.
To add the new MoP, click on the “Add” button.
|
4. - Mode of Payment is the selected tab by default.
 Image Added
- Specify the name of the MoP and it’s short code (maximum length: 5)
|
5. - Select mode as Credit Card.
|
6.
 Image Added
Select “Paytm” as third party POS Plugin name.
 Image Added
| Tip |
|---|
This is the one we have configured earlier. |
|
7.
- Move to the “Site Allocation” tab.
|
8.
 Image Added
- Select a site from the list of Available Sites.
|
For this testing purpose, select GINNI RETAIL-GARIA. However, any other sites can be selected in the actual scenario.9. -
- Move the highlighted site from left to right by clicking the right (->) arrow.
 Image Added
The selected site would now appear in the Assigned sites list.
|
Please observe that GINNI RETAIL-GARIA site is no more there in the list of Available Sites.
 Image Added
Now, scroll to the right, double click under the Ledger and select Credit Card from the list.
 Image Added
| Info |
|---|
The ledger name should have been decided and configured in Ginesys HO by the brand. Here Credit Card has been selected as a sample value only. For the brand, in all probability, it would be different. If a Sub Ledger is associated with the Ledger, then the Sub Ledger should also be selected for successful configuration. |
|
10. A. Save - Save the MoP.
 Image Added
It will now try to save the configuration and displays the following while operation is in progress.
 Image Added Once the newly configured MoP is saved it would appear in the list of configured MoPs.
 Image Added
| Tip |
|---|
This step (#B) is a one-time activity to be performed in majority of the cases. |
MoP configuration is now completed.
|
Click on the following shortcut to open the Ginesys Launchpad desktop application.
The following screen will appear:
2. Select the System Utilities option from the left panel.
3. Click on the Data Sync option from the right panel and then click on Yes in the User Account Control dialog.
4. Login to the Data synchronization application.
5. The Data Exchange Dashboard will appear in the Data Sync window. Click on the SYNC All button.
6. It will start syncing the configuration immediately.
7. Click on the Close button once you see the following lines:
Make sure to run through this step (#C) every time you make changes in the app.config file.
Data Synchronization based on site from HO to POS is completed.
...
