...
Purpose:
The purpose of the this document is to help the person to configure and deploy the POS payment through PhonePe with respect to different types of payment devices - UPI, QR-code and Click and Collect method. 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 POS billing by PhonePe. Using PhonePe payment device payment can be made in two three ways - using the card and using the QR code or UPI or Click and Collect.
For the configuration of the app-config file, Users of PhonePe would need the attribute values from PhonePe end:
| Info |
|---|
Important - Note that for the generic Ginesys configuration the 3rd and 4th steps need the following details - Assembly name: GINESYSPhonepe |
POS-Plugin Management
Following are the steps to be followed in sequence to manage the entire process for configuring the POS Plugin:
Step #A: Configuring Plug-in Manager in Ginesys ERP user interface
Step #B: MoP (Mode of Payment) configuration in Ginesys ERP user interface
Step #C: Data Synchronization based on site from ERP to POS
Step #E: Update the latest POS Plugin using the AutoUpdater
Step #F: Logout and login into the POS application
Step #G: Test whether payment is being possible from POS using the configured MOP
| Info |
|---|
All the above mentioned steps are described with the screenshots for easy reference, in this document. |
Assumption
The plugin will be installed in Ginesys POS Server.
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.
Any URL that PhonePe provides will be whitelisted.
| Expand | ||
|---|---|---|
| ||
|
Sample content of the app.config file for PhonePe device |
{ |
Note that the Base URLs have to be allowed by the firewall (if there is any) and confirmed by PhonePe.
The attribute values specified above are sample only.
...
| View file | ||
|---|---|---|
|
Attribute Description:
ATTRIBUTES | DESCRIPTIONS |
MerchantID | To be provided by PhonePe |
StoreId | Name of the store and to be provided by the enterprise |
TerminalId | To be setup by Ginesys as per client |
SaltKey | To be provided by PhonePe |
SaltIndex | To be provided by PhonePe |
XProviderId | To be provided by PhonePe |
PaymentProcess |
|
DynamicQRCodeGenerationURL | The URL value of this attribute would be provided and confirmed by PhonePe. PhonePe will generate the QR code dynamically when this URL will get called. |
DynamicQRCodeCheckPaymentStatusURL | The URL value of this attribute would be provided and confirmed by PhonePe. PhonePe will check the payment status dynamically when this URL will get called. |
ClickAndCollectPaymentRequestURL | The URL value of this attribute would be provided and confirmed by PhonePe. PhonePe will send the notification dynamically to the PhonePe payment app when this URL will get called. |