Card Info
Get Card details using card bin upto 9 digits. You can also use this API to check if a card is eligible for ATM PIN, Mandate, direct OTP payments or tokenization.
This S2S API requires authentication and accepts bin upto 9 digits.
Networks have shifted to using 9-digit BINs for more accurate information. We are still maintaining the existing 6-digit BINs for compatibility. Merchants are requested to move to the 9 digits bin based fetching card information by December 10th, 2023
Basic Auth *
Base64 Encoded Username:Password
Consists of two parts:
Username: API Key obtained from Juspay dashboard
Password: Empty string
Example:-
Basic MUQ2QUxxxxxxxxxxxxU5QTIxQzNFNTQwNkFDMEZCOg==
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.
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.
Example:- customer_1122
Card bin details are required, with a variable length ranging from 6 to 9 digits.
Example:- 524368
Merchant ID which represents the merchant storing the card
This is a boolean variable and accepts true/false. If set to `true`, then the card eligibility check for mandate transactions
This is a boolean variable and accepts true/false. If set to true, then the card eligibility check for OTP payments will be done.
This is a boolean variable and accepts true/false. If set to true, then the card eligibility check for Tokenization payments will be done.
This works only for Token Bins
To check for a Token Bin instead of Card Bin
This is a boolean variable and accepts true/false
This is a boolean variable and accepts true/false
This is a boolean variable and accepts true/false
This is a boolean variable and accepts true/false
The length, varying from 6 to 9 digits, depends on available bin data. Defaulting to a maximum length of 9 digits, with fallback to 7 or 6 digits if higher length bin information is unavailable.
invalid_request_error
The API returns a 404 error for unavailable bin information or when the bin length is outside the 6-9 digit range
object_not_found
Cannot find what you are looking for
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)
| 5
|
TP90 (ms)
| 27.57
|
TP99 (ms)
| 60.28
|
TP99.9 (ms)
| 131.14
|
Recommended Timeout(ms)
| 1000
|
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)
| 224.57
|
Recommended Timeout(ms)
| 1000
|