Token's payment processing(Plural/Non Plural token requester)

post https://api-staging.pluralonline.com/api/v1/card/process/payment/tokenize?token={orderToken}

Request Body

Parameter Name	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

Parameter Name	Type	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	Unique payment id.	M
order_id	long	Unique order id.	M
amount_in_paise	long	Amount paid in paise.	M
response_code	string	Response code.	M
response_message	string	Short message about code.	M

Failure Response Body

Parameter Name	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

Credentials

Basic

base64

Click Try It! to start a request and see the response here!