POSTFetch Saved Cards
Use Case
Used by merchant to fetch both saved and token cards mapped to Unique customer identifier and MID combination
Request Attributes
Head
Attribute | Description |
---|---|
tokenType string mandatory | Authorization method for this request. Possible values: JWT |
token string mandatory | Authorization string corresponding to the JWT token. Example: 739816707d7444XXXXXXXX6cb4264d0a1590145379323 |
Body
Attribute | Description |
---|---|
mid string mandatory | Paytm provides MID as a unique identifier to each merchant. Example: INTEGR7769XXXXXX9383 |
custId string mandatory | Unique customer identifier of the merchant’s customer. |
filterTokenCards boolean optional | To filter out tokenised cards and return only saved cards |
Response Attributes
Body
Attribute | Description |
---|---|
savedCardId string(45) | Unique for every card binding to user |
cardType string | Type of the card |
cardScheme string | The network used for card token generated |
expiryDate string | Expiry of the card or card token |
cardSuffix string | Last 4 digits of the card or card token |
panUniqueReference string | Token reference number provided by card network. |
issuerCode string | Code of the bank issuing the card |
issuingBankName string | Name of the bank issuing the card |
displayName string | Display name of the card |
cardFirstSixDigits string | Bank Identifier Number of Card |
isEligibleForCoft string | Status whether bin is eligible for card on file tokenization or not. Possible Values: true, false |
isCardCoft string | This flag indication whether card is already tokenized or not |
tokenBin string | Bank Identifier Number of Token |
tokenStatus string | The status of the token. Must be one of the four possible values. |
curl -X POST 'https://securegw-stage.paytm.in/savedcardservice/merchant/coft/cards' \
--header 'Content-Type: application/json' \
--data '{"head":{"tokenType":"JWT","token":"{token}"},"body":{"mid":"{mid}","custId":"{custId}"}}'