About UPI via PPRO

General information about UPI via PPRO


Logo

Info

.....

TypePayments by Online Bank Transfer

 

 

Process flow chart


UPI process flow


interface


Payment with UPI (PPRO) via form interface

To make a UPI payment via PPRO over a form, please use the following URL:

upi.aspx

 

Key

Format

CND

Description

OrderDesc

ans..768

M

Description of delivered products, services etc.

Key

Format

CND

Description

AddrCountryCodea2OCountry code for the account holder’s invoicing address, 2 characters according to ISO 3166. Only IN allowed, defined within the code.
Name

an..50

O

Full name of consumer / shopper

Parameters for payments with UPI (PPRO)


Key

Format

CND

Description

QRCodeUrlans..1024OUsed for Desktop flows: A URL pointing to the PNG image showing the UPI application on their mobile device.
URI

ans..1024

O

Used for mobile app flows: an intent URI that can be triggered to bring/enable them to complete the payment

Return parameters for URLSuccess, URLFailure and URLNotify with UPI (PPRO)


Credit with reference

credit.aspx

Parameters for credits via socket connections


Response parameters for credits with UPI (PPRO) via socket connections


Batch processing via the interface

This section describes the parameters which must be transferred within the data set (Record) for executing a refund for UPI (PPRO) and which information can be found within the response file about the payment status.

Following table gives an overview of all batch versions that are possible for a specific action an their specialities:

Action

Version

Description

Credit

1.0 / 2.0

Standard version without return of parameter Code


1.x / 2.x

with RefNr (valid for all versions other than 1.0)

Description of the possible batch versions

The structure for UPI (PPRO) within a Batch file to be submitted is the following:

HEAD,<MerchantID>,<Date>,<Version>
UPI,Credit,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>  
FOOT,<CountRecords>,<SumAmount>


Example for Master MID function:

HEAD,[Master]MerchantID,Date,2.x
Type,Action,[Slave]MID,Amount,Currency,TransID,Data (depends on Action)
FOOT,CountRecords,SumAmount

Key

Format

CND

Description

Type

a..11

M

HEAD for Header, FOOT for Footer, UPI for UPI (PPRO)

Action

a..20

M

The parameter Action defines the type of transaction:

Credit

Description of fields within the record for Batch files

The record area within the response file for Batch transactions looks the following way:

HEAD,<MerchantID>,<Date>,<Version>
UPI,Credit,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>,<Status>,<Code>
FOOT,<CountRecords>,<SumAmount>

Key

Format

CND

Description

Action

a..20

M

The parameter Action defines the type of transaction:

Credit

Description of result parameters within the record for Batch files