Versions Compared

Old Version 2

changes.mady.by.user Aparajita Basu Roy

Saved on

compared with

New Version 3

changes.mady.by.user Aparajita Basu Roy

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 Credit and Debit Cards. 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 ways - using the card and using the QR code

...

Info

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

 

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.

...

View file
namephonepe-app.config

Attribute Description:

ATTRIBUTES

DESCRIPTIONS

MerchantID

To be provided by PhonePe

StoreId

Name of the store and to be provided by the enterprise

TerminalId

SaltKey

To be provided by PhonePe

SaltIndex

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.