Request Body

Object

Fields

Type

Length

Description(M/O))

tokenize_card_data

Complex object type

token

string

C- (Mandatory In case Merchant integrated token provisioning system other then Plural)

cryptogram

string

C- (Mandatory In case Merchant integrated token provisioning system other then Plural)

expiration_month

string

Expiry month of Card. Like- 12, 08,01

M

expiration_year

string

Expiry year of card. Like - 2024, 2025

M

pine_token_identifier

string

Unique non-guessable Guid by using unique key generation algorithm (OpenJDK8 - Java.util.UUID – version 1 based on timestamp – 36 characters)/
custom DB sequence Logic for each token reference.

C -( Mandatory In case Merchant integrated token provisioning via Plural only)

cvv

string

Card verfication value

M

customer_data

Complex object type

O

mobile_no

string

10 digits Customer mobile number

O

email_id

string

Customer email id

O

country_code

string

Country code of Indian country- 91

O

card_meta_data

Complex object type

O - This complex type parameter is optional

issuer_name

string

O

scheme_name

string

O

card_type

string

O

Response Body

Field Name

Description

M/O

content

string

HTML form received from card host which browser will be render to get OTP authencation viewYespayment_idlongPlural unique transaction idYesorder_idlongPlural order id

M

payment_id

long

Plural's unique payment id

M

order_id

long

Plural's order id

M

amount_in_paise

long

Transaction's amount in paise

M

response_code

integer

Success value is 1
Failure case appropriate response code like 6010,6020

M

response_message

string

Payment Successful!

M

Failure Response Body

Field Name

Data Type

Description

M/O

response_code

int

Failure case approriate response code like 6010,6020

M

response_message

string

Proper response message
Example- "Oops, something went wrong!"

M

Language
Authentication
Basic
base64
:
Click Try It! to start a request and see the response here!