Skip to main content
POST
Create Payment Request

Authorizations

x-api-key
string
header
required

Merchant API Key

x-signature
string
header
required

Generated request signature

Body

application/json
quoteAmount
string
required

Amount that needs to be collected from end user

quoteCurrCode
string
required

Base currency of the quoteAmount

referenceId
string<ReferenceId>
required

This is a partner ID to map a billing session with their generated ID. This cannot be the same for two sessions.

payMethod
enum<string>
required

The payMethod that is to be used to collect the payment from the end customer.

For different payMethod there are different params to send the correspoding values mandatory for that payMethod.As of now only UPI is supported.

Available options:
UPI,
CC,
DC,
NB
email
string

Customer's email. Require this to send an invoice.

phoneNo
string

The customer's Indian phone number in the format of +91-XXXXXXXX

name
string<AllowedString>

Name of the customer

returnUrl
string<uri>

If the payMethod is CC, DC, NB Then this parameter is Mandatory needed to redirect the user after the session is completed. The end customer will be redirected to this URL with the status of the session.

meta
object

To add meta params in the session. They will be passed in the webhook and query API as well.

Response

200 - application/json

createPaymentRequest

status
string

The response from the API

sub_status
string

Used for internal purposes only

data
object

Contains the sessionId and URL.