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.

API Endpoints
Sandbox Link
GET
https://sandbox.juspay.in/customers/{customer_id}/wallets
Production Link
GET
https://api.juspay.in/customers/{customer_id}/wallets
Authorization Header
Headers
Path Params
200 : Success
400 : Invalid Input data

API Latency Guidelines

What is API Latency?

Time taken by the server to respond to the API request.

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.

Scroll inside to view more
Transaction Percentile
Latency (ms)
TP50 (ms)
11.85
TP90 (ms)
18
TP99 (ms)
33.71
TP99.9 (ms)
51.14
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.

Scroll inside to view more
Transaction Percentile
Latency (ms)
TP99.99 (ms)
415.57
Last updated 1 month ago