Instant Card Embossing Confirmation

post

https://uatmea-iss-apigw.creditpluspinelabs.com/cardmgmt/apis/v1/services/cardholder/embossingack

This API is used by the consumer (third party or bank) to confirm that the physical card has been embossed successfully. It is applicable for prepaid, credit and debit products issued on Pine Labs platform.

HTTP Status and Response Status Matrix

HTTP Code: This is the response status code issued by a server in response to a client's request made to the server.
Error Code: This is the error code returned by Credit+ Issuing application in the ‘code’ field of the response message indicating if the request was processed successfully or failed.
Reason: This is the description of the error code returned by Credit+ Issuing application.

HTTP Code	Error Code	Reason
201	000	Confirmation of embossment for the card is successful
400	001	Get Embossing Details API is not processed for the card
400	003	Given card is not processed as Instant card
400	005	Embossing details are already confirmed for the card
400	997	Mobile number field is manadatory when only last 4 digit of device number are provided
400	997	Atleast one field must be present
400	997	Mobile Number with ISD code is invalid
404	998	No Card Pack ID found for given details
400	997	Device Number (Either 16 digit card number OR last 4 digit of card number) should be present with mobile number
400	994	Invalid Encryption-Algorithm header value
400	994	Invalid Encryption Request Parameters
400	994	Cryptography error

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

deviceNumber

string

length ≤ 16

^[0-9]+$

Either 16 digit or last 4 digit Device number. Numeric. Maximum length: 16. If last 4 digits of the device number is received, then it is validated with the mobile number in the system. At least one of the conditional attributes (deviceNumber, mobileNumber) must be provided. Example: 4662910000000373

cardPackId

string

length ≤ 19

^[a-zA-Z0-9]+$

Card Pack ID. Alphanumeric. Maximum length: 19. Example: 4662910PVCRE0000000952

mobileNumber

string

length ≤ 15

^\+?[0-9]+$

Registered mobile number with ISD code. ISD code + Mobile number. Maximum length: 15. If mobile number is received, the last 4 digits of device number should also be part of the request. At least one of the conditional attributes (deviceNumber, mobileNumber) must be provided. Example: +919682858016

timestamp

string

required

^[0-9]+$

Current UTC timestamp in milliseconds. Numeric. AES key expiration criteria depends on input UTC timestamp. Applicable only for encrypted requests. Example: 1349333576093

Headers

Correlation-ID

string

^[a-zA-Z0-9-]{1,50}$

API Consumer must share Correlation-ID in HTTP header for API requests. The Correlation-ID must be unique for each request. It is recommended to generate a universally unique identifier (UUID) of length 32 or 36 that is compliant with RFC 4122. The maximum supported length is 50 alphanumeric characters. For example, ac97d177-9345-4934-8343-0f91a7a02836. If the Correlation-ID is not received in the incoming request, the system generates the UUID dynamically and assigns it to the request.

Source

string

API Consumer can share Source in HTTP header for API requests. For the list of Source values, see the Pre-conditions for HTTP Header of REST API topic in the Pre-requisite for Rest API section.

Response

Language

URL

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

201Successful response