--- page_title: List Wallets product: API Reference page_source: https://juspay.io/in/docs/api-reference/docs/express-checkout/list-wallets openapi: https://juspay.io/in/docs/api/swagger?document=https%3A%2F%2Fjuspay.io%2Fin%2Fdocs%2Fapi-reference%2Fdocs%2Fexpress-checkout%2Flist-wallets 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 Wallets Wallets can be listed only in the context of a `Customer`. This API will return the list of wallets which may or may not be **linked** . If a direct debit is enabled by the provider for your setup, you can activate the same for customers using the `authenticate` and `link` APIs. > **Note** > For linked wallets, the balance in the response may not be the current balance.`last\_refreshed` field represents the date & time when the balance was updated last. Use `refresh` wallet API to update the balance for individual wallets. This results in a network call to the wallet provider and hence the response might be slow. ## Endpoints: - Sandbox: https://sandbox.juspay.in/customers/{customer_id}/wallets - Production: https://api.juspay.in/customers/{customer_id}/wallets ## 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: #### version: Refer to #Introduction for latest version - Tags: string #### 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/customers/guest_user/wallets \ -u your_api_key: \ -H 'x-routing-id: customer_1122'\ ``` ### Sample Response: #### Response: ```json { "list": [ { "wallet": "MOBIKWIK", "token": "tk_bkc87beikjcnlblc87asa897sb8anisjkl8b", "last_refreshed": "2023-09-11T08:29:47Z", "juspay_bank_code": "JP_MOBIKWIK", "object": "wallet_account", "id": "wlm_Giuln7b8Uy78uyhjI", "current_balance": 100, "sub_details": [ { "payment_method": "MOBIKWIK", "payment_method_type": "WALLET", "last_refreshed": "2023-09-11T08:29:47Z", "current_balance": 100 } ], "linked": true }, { "wallet": "PAYTM", "token": "tk_biknby8976v567uygjkhvc5x3789h0npou", "last_refreshed": "2023-09-11T08:29:46Z", "juspay_bank_code": "JP_PAYTM", "object": "wallet_account", "id": "wlm_vUtyjb78klnU8l", "current_balance": 45, "sub_details": [ { "payment_method": "PAYTM_POSTPAID", "payment_method_type": "WALLET", "last_refreshed": "2023-09-11T08:29:46.985Z", "current_balance": 22250 }, { "payment_method": "PAYTM", "payment_method_type": "WALLET", "last_refreshed": "2023-09-11T08:29:46Z", "current_balance": 45 } ], "linked": true } ], "offset": 0, "count": 2, "total": 2, "object": "list" } ``` #### Metadata: ```json { "object": "list", "list": [ { "id": "wlt_d10hncoc6xldk", "object": "wallet_account", "wallet": "PAYTM", "token": null, "current_balance": null, "linked": false, "last_refreshed": null, "metadata": { "mobile_number": "9999999999" }, "gateway_reference_id": null } ], "count": 1, "offset": 0, "total": 1 } ``` ## Path Parameters: #### customer_id: Customer Id - Value: Example:- cust19374 - Tags: String, Mandatory ## API Responses: ### 200: #### List Wallets: - Value: - **Object**: - Tags: String - **List**: - Value: - **Id**: - Tags: String - **Object**: - Tags: String - **Wallet**: - Tags: String - **Token**: - Tags: String - **Current_balance**: - Tags: String - **Linked**: - Tags: Boolean - **Last_refreshed**: - Tags: String - Tags: Array of objects - **Count**: - Tags: Integer - **Offset**: - Tags: Integer - **Total**: - Tags: Integer - Tags: JSON #### Metadata: - Value: - **Object**: - Tags: String - **List**: - Value: - **Id**: - Tags: String - **Object**: - Tags: String - **Wallet**: - Tags: String - **Token**: - Tags: String - **Current_balance**: - Tags: String - **Linked**: - Tags: Boolean - **Last_refreshed**: - Tags: String - **Metadata.mobile_number**: - Value: - Tags: string - **Gateway_reference_id**: - Tags: String - Tags: Array of objects - **Count**: - Tags: integer - **Offset**: - Tags: integer - **Total**: - Tags: integer - Tags: JSON ### 400: #### object: - Description: {} - Tags: Object ### 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) | 11.85 | | TP90 (ms) | 18 | | TP99 (ms) | 33.71 | | TP99.9 (ms) | 51.14 | | 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) | 415.57 | > | Recommended Timeout(ms) | 1000 | > --- ## See Also - [Wallet](https://juspay.io/in/docs/api-reference/docs/express-checkout/wallet) - [Create Wallet](https://juspay.io/in/docs/api-reference/docs/express-checkout/create-wallet)