--- page_title: List Stored Cards product: API Reference page_source: https://juspay.io/in/docs/api-reference/docs/express-checkout/list-stored-cards openapi: https://juspay.io/in/docs/api/swagger?document=https%3A%2F%2Fjuspay.io%2Fin%2Fdocs%2Fapi-reference%2Fdocs%2Fexpress-checkout%2Flist-stored-cards llms_txt: https://juspay.io/in/docs/llms.txt product_llms_txt: https://juspay.io/in/docs/api-reference/llms.txt --- ## API Version: default # List stored cards List all the cards stored for a customer. This API gives back only tokens and other metadata relevant to the cards stored in Juspay Locker. > **Note** > **Supported networks -** Visa supports cvv-less token transactions across issuers. (Available in sandbox)Mastercard supports cvv-less token transactions for limited 20 issuers. (To be made available by May 07, 2023)**Supported gateways -** > > * Paytm V2 > * Cybersource > * Payu > * Razorpay > **Note** > > ### Supported banks for Mastercard > > > > 1. HDFC Bank > 2. Punjab National Bank > 3. Axis Bank > 4. Bank Of India > 5. Citibank > 6. Standard Chartered Bank > 7. SBI > 8. Union Bank of India > 9. RBL Bank > 10. South Indian Bank > 11. ICICI Bank > 12. City Union Bank > 13. SBM > 14. Yes Bank > 15. Karur Vysya Bank > 16. IndusInd Bank > 17. IDBI Bank > 18. Federal Bank > 19. Bandhan Bank ## Endpoints: - Sandbox: https://sandbox.juspay.in/cards - Production: https://api.juspay.in/cards ## Request Type: GET ## Authorization: #### Basic Auth: Consists of two parts. * Username: API Key obtained from Juspay dashboard * Password: Empty string - Value:

Example:-
Basic MUQ2QUxxxxxxxxxxxxU5QTIxQzNFNTQwNkFDMEZCOg==

- Tags: Base64 Encoded Username:Password, Mandatory ## Headers: #### Content-Type: application/x-www-form-urlencoded - Tags: String, Mandatory #### x-merchantid: Merchant ID provided by Juspay - Tags: String, Mandatory #### x-routing-id: We recommend passing the customer_id as the x-routing-id. If the customer is checking out as a guest, you can pass an alternative ID that helps track the payment session lifecycle. For example, this could be an Order ID or Cart ID. > **Warning** > This ID is associated with the customer. It plays a key role in ensuring consistency and maintaining connections across different systems. If you fail to pass the same x-routing-id for the same customer in all related API calls, it could lead to issues with API functionality. Therefore, it’s crucial that you use the same x-routing-id for all requests tied to the same customer. - Value: customer_1122 - Tags: String, Required ## Sample Code Snippets: ### Sample Request: #### Request Code Snippet: ```request curl -X GET https://api.juspay.in/cards?customer_id=guest_user&options.check_cvv_less_support=true \ -H 'x-routing-id: customer_1122'\ -H your_api_key: ``` ### Sample Response: #### Response: ```json { "cards": [ { "card_sub_type": "TITANIUM", "token": { "tokenization_status": "ACTIVE", "support_token_transaction": true, "last_four_digits": "5937", "cvv_less_support": true, "vault_provider": "NETWORK_TOKEN", "par": "V0010013820031519535347554746", "card_reference": "token_4149513e22e2e58ead99e1ecdd541f10", "expiry_month": "01", "token_supported_gateways": [ "PAYTM_V2", "BILLDESK", "EASEBUZZ" ], "card_fingerprint": "27po8sn3gehxumesqx9oi6xmv9", "cvv_less_details": [ { "gateway": "PAYTM_V2", "gateway_reference_ids": [ "DEFAULT_NULL" ] }, { "gateway": "BILLDESK", "gateway_reference_ids": [ "DEFAULT_NULL" ] }, { "gateway": "EASEBUZZ", "gateway_reference_ids": [ "DEFAULT_NULL" ] } ], "cvv_less_supported_gateways": [ "PAYTM_V2", "BILLDESK", "EASEBUZZ" ], "provision_token_id": "XXXXXXXXX", "card_isin": "486876061", "expiry_year": "2025" }, "extended_card_type": "CREDIT", "tokens": [ { "tokenization_status": "ACTIVE", "last_four_digits": "5937", "provider_category": "NETWORK", "vault_provider": "NETWORK_TOKEN", "par": "V0010013820031519535347554746", "card_reference": "cref_cda437e968bb47d38b5dee7d2ba74a79", "card_token": "token_4149513e22e2e58ead99e1ecdd541f10", "expiry_month": "01", "card_fingerprint": "27po8sn3gehxumesqx9oi6xmv9", "provision_token_id": "XXXXXXXXX", "card_isin": "486876061", "expiry_year": "2025" } ], "nickname": "", "provider_category": "NETWORK", "vault_provider": "JUSPAY", "card_reference": "token_4149513e23e2e5gead99e17cdd541f10", "card_type": "CREDIT", "metadata": { "origin_customer_id": "customer_id", "origin_merchant_id": "merchant_id" }, "card_issuer": "SBI", "card_token": "tkn_1b6fcc1045944fdfb5020a92e4fa1f91", "health": "UP", "card_exp_month": "01", "mandate_support": true, "provider": "VISA", "card_sub_type_category": "RETAIL", "expired": false, "card_fingerprint": "27po8sn3gehxumesqx9oi6xmv9", "tokenize_support": false, "juspay_bank_code": "JP_SBI", "card_exp_year": "2025", "name_on_card": "name", "country_code": "356", "atm_pin_auth_support": false, "card_number": "XXXX-XXXXXXXX-5937", "card_isin": "486876061", "card_brand": "VISA", "card_issuer_country": "INDIA" } ], "merchantId": "merchant_id", "customer_id": "customer_id" } ``` ## Query Parameters: #### options. atm_pin_auth_support: This is a boolean variable and accepts true/false. If set to `true`, then the card eligibility check for ATM PIN payments will be done. - Tags: Boolean #### options.check_cvv_less_support: options.check_cvv_less_support - Tags: Boolean #### customer_id: Customer ID which represents the user uniquely. This is same as the object_reference_id using which customer was created - Tags: String, Mandatory, Max Length : 300 #### options.check_mandate_support: To verify if the card is supported for mandates - Tags: Boolean, Optional ## API Responses: ### 200: #### customer_id: - Description: Customer Id given in the request - Tags: string, Max Length : 300 #### merchantId: - Description: Merchant id associated with Juspay - Tags: string, Max Length : 255 #### cards: - Description: Array of stored cards that belongs to the given user represented by the Customer ID. Each member of the array is an associative array that represents a stored card of the user. - Value: - **Card_token**: - Description: Token representing the card. Payment has to be initiated using this token. Tokens are by definition short lived and so, please do not cache them in your system. Expired tokens will lead to transactions being declined. - Tags: String - **Card_reference**: - Description: A reference identifier that doesn’t change for the stored card. Use this identifier to store any metadata that you wish. For example, you can store card type or card bin or even transaction data using this reference - Tags: String, Max Length : 256 - **Card_fingerprint **: - Description: A string that uniquely identifies the card across the board. When the same card is stored across multiple accounts, same fingerprint will be returned. This can be used to identify duplicates. - Tags: String, Max Length : 256 - **Card_number**: - Description: Masked card number that can be displayed to the customer. - Tags: String - **Card_isin**: - Description: First 6 digits of the card - Tags: String - **Card_expiry_year**: - Description: Year of expiry of the card - Tags: String - **Card_exp_month**: - Description: Month of expiry of the card - Tags: String - **Card_type**: - Description: Indicates if the card is either CREDIT or DEBIT. Please note that this information is inferred. Not all cards will have this information. - Tags: String - **Card_issuer**: - Description: Indicates the bank which issued the card. This again is not available all the time. We make our best effort to get this information for all cards. - Tags: String, Max Length : 256 - **Card_brand**: - Description: Indicates the name of the card switch provider.Please note that this information is inferred - Tags: String - **Name_on_card**: - Description: Cardholder name given while storing the card - Tags: String, Max Length : 256 - **Nickname**: - Description: Returns the given nickname while storing the card - Tags: String - **Expired**: - Description: Indicates whether the stored card is expired or not - Tags: String - **Atm_pin_auth_support **: - Description: Indicates if the card is eligible for ATM PIN payments. - Tags: String - **Cvv_less_support **: - Description: Indicates if the tokenised card is eligible for cvv-less payments. Merchants can stop collecting the CVV value for eligible tokens. - Tags: String - **Cvv_less_supported_gateways **: - Description: List of gateways which are available for cvv-less token transactions. Juspay's dynamic routing will be applied among these gateways. Alternatively, a Gateway ID pertaining to one of the listed gateways can be passed in Create Order API to force route the transaction. - Tags: String - Tags: Array Of Objects ### 401: #### status: - Description: error - Tags: string #### error_code: - Description: access_denied - Tags: string ### API Latency Guidelines #### **What is API Latency?** Time taken by the server to respond to the API request. #### **Average API Percentile Metrics and Recommended Timeout** **TP50 (ms)** : This represents the median latency, meaning 50% of all requests are completed in this time or less. It indicates the typical performance experienced by the majority of users. **TP90 (ms)** : This value shows that 90% of requests are completed within this time, leaving 10% of requests that take longer. It gives insight into the performance for a broader set of users, beyond the median. **TP99 (ms)** : This value indicates that 99% of requests finish within this time, with only 1% of requests taking longer. It helps identify outlier cases where latency may become an issue for a small group of users. **TP99.9 (ms)** : This metric captures extreme latency outliers, where only 0.1% of requests take longer than this value. It’s useful for understanding edge cases where performance degrades for very few users. **TP99.99 (ms)** : This measures the most rare and severe performance outliers, where just 0.01% of requests exceed this time. Monitoring this helps in addressing the rarest and most critical latency issues that may impact user experience in exceptional scenarios. | Transaction Percentile | Latency (ms) | |---|---| | TP50 (ms) | 17.28 | | TP90 (ms) | 51.57 | | TP99 (ms) | 126.85 | | TP99.9 (ms) | 206.42 | | Recommended Timeout(ms) | 1000 | > **Warning** > The recommended timeouts are based on TP99.9 data, though edge cases (0.01% of requests) may still exceed these limits and are captured in the TP99.99 data as shown below. > > > | Transaction Percentile | Latency (ms) | > |---|---| > | TP99.99 (ms) | 488.85 | > | Recommended Timeout(ms) | 1000 | > --- ## See Also - [Add Card](https://juspay.io/in/docs/api-reference/docs/express-checkout/add-card) - [Delete Card](https://juspay.io/in/docs/api-reference/docs/express-checkout/delete-card)