mO SharemO Share

We’re excited to announce that the latest information is now available on our new site, the Ginesys One Wiki!. Visit the site for up-to-date resources and insights. We look forward to continuing to support you there!

PhonePe App Config File

Owned by Aparajita Basu Roy
Last updated: Sept 13, 2022
3 min read

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 three ways - 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:

Important - Note that for the generic Ginesys configuration the 3rd and 4th steps need the following details -

Assembly name: GINESYSPhonepe
Class name: Phonepe
Method name: PhonepeAcceptPayment

 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 #D: Pulling/syncing down the required configuration from ERP via Data Exchange in the POS system

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

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.

 

  1. Create the app.config file for DQR and UPI and Click and Collect from the samples given. 

 

Sample content of the app.config file for PhonePe device

{
"SecurityParams":
{
"MerchantId": "merchant id",
"StoreId": "store id",
"TerminalId": "terminal id",
"SaltKey": "salt key value",
"SaltIndex": "salt index value",
"XProviderId": "X provider id",
"PaymentProcess": 0 or 1 or 2
},
"APIParams":
{
"DynamicQRCodeGenerationURL":"https://mercury-t2.phonepe.com/v3/qr/init",
"DynamicQRCodeCheckPaymentStatusURL":"https://mercury-t2.phonepe.com/v3/transaction",
"ClickAndCollectPaymentRequestURL":"https://mercury-t2.phonepe.com/v3/charge"
}
}

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.

Click to download this app.config 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

  • Click and Collect (PaymentProcess=0)

  • QR code scanning from the cashier's screen (PaymentProcess=1)

  • QR code scanning from the device screen (PaymentProcess=2)

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.