POSTDC EMI Eligibility API
Use Case
This API can be used to check the eligibility of the customer for DC EMI using the registered mobile number with the Debit card bank account.
Request Attributes
Head
Attribute | Description |
---|---|
version string optional | Version of the API. Example: v1 |
channelId string optional | The parameter value identifies the Channel for which the API call is initiated. Possible Values: APP, WEB, WAP, SYSTEM |
requestTimestamp string mandatory | EPOCH timestamp of the time at which request is being sent. |
tokenType string mandatory | This is for authentication method. |
token string mandatory | For tokenType CHECKSUM, It's value to be sent should be the checksum string created by using Paytm checksum library. |
Body
Attribute | Description | ||||
---|---|---|---|---|---|
mid string mandatory | Paytm provides MID as a unique identifier to each merchant. For your staging MID, click here. You get the production MID post the account activation. Example: INTEGR7769XXXXXX9383 | ||||
emiTypes Array of Strings mandatory | Types of emi for which the eligibility has to be checked Example: [DEBIT_CARD] | ||||
channelCode string optional | The bank code for which the user eligibility for Debit Card EMI has to be determined. Example: "ICICI" | ||||
userInfo object mandatory | User's mobile number used to determine the user's eligibility for Debit card EMI | ||||
userInfo +
| |||||
txnAmount string optional | The amount for which DebitCard EMI eligibility is to be retrieved |
Response Attributes
Head
Attribute | Description |
---|---|
responseTimestamp string | EPOCH timestamp of the time at which response is being sent. Example: 1588402269 |
version string | Version of the API passed in the request. Example: v1 |
clientId string | Paytm use the merchant key on the basis of clientId parameter value. It requires only if the merchant has more than one key. |
signature string | You should validate the parameter values by verifying the signature comes in the response. It ensures that parameter values not tempered. Signature string can be verified by using Paytm checksum library. |
Body
Attribute | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
resultInfo object | This parameter gives the information about the result of the API response | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
resultInfo +
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
emiEligibility Array of objects | Returns the plans available which are available for Debit Card EMI on the basis of the eligibility determined using the phone number and channelCode | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
emiEligibility +
|
Response Codes & Messages
resultCode | resultStatus | resultMsg |
---|---|---|
0000 | S | Success |
3004 | F | EMI not configured on merchant |
9999 | F | Something went wrong |
3001 | F | Internal Processing Error |
3001 | F | Unable to determine eligibility for HDFC at this time |
curl --location 'https://securestage.paytmpayments.com/theia/api/v1/checkEMIEligibility' \
--header 'Content-Type: application/json' \
--data '{"head":{"version":"v1","requestTimestamp":"{{timestamp}}","channelId":"WEB","tokenType":"ACCESS","token":"{{accessToken}}"},"body":{"userInfo":{"mobileNumber":"9999999999"},"mid":"{{YOUR-MID-HERE}}","channelCode":"HDFC","emiTypes":["DEBIT_CARD"]}}'