Body
Process OTP
This will complete the authentication and authorization. It takes OTP as input and returns the transaction response.
Note
id path parameter is the unique id generated for the transaction in a generate OTP API call.
Request
Response
API Endpoints
Sandbox Link
POST
https://sandbox.juspay.in/v2/txns/{id}/authenticate
Production Link
POST
https://api.juspay.in/v2/txns/{id}/authenticate
Authorization Header
Basic Auth
*
Base64 Encoded Username:Password
Mandatory
Consists of two parts.
Username: API Key obtained from Juspay dashboard
Password: Empty string
Example:- Basic MUQ2QUxxxxxxxxxxxxU5QTIxQzNFNTQwNkFDMEZCOg==
Headers
Content-Type
*
String
Mandatory
application/x-www-form-urlencoded
x-routing-id
*
String
Required
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.
Example:- customer_1122
Path Params
id
*
String
Mandatory
Transaction Id
Example:- txn_035b4e708d5148478828ea3136a9efd7
Request Schema: application/json
Basic Parameters
challenge_id
*
String
Mandatory
Challenge id generated against the transaction in generating OTP API call.
answer.otp
*
String
Mandatory
OTP to be sent for authenticating the transaction.
auto_capture
String
Optional parameter. Send false if you want to capture at a later stage. The default is true.
200 : Success
Response Body
id
String
Unique id generated for the transaction.
order_id
String
Order Id provided by you while order creation.
txn_id
String
Transaction id for a given order.
status
String
Status of the transaction. If you receive ���CHARGED”, then the transaction is successful. “AUTHORIZED” in case if auto_capture is false.
gateway
String
Gateway through which authorization process was performed.
created
String
Creation date of transaction.
resp_code
String
Gateway response code for the transaction.
resp_message
String
Error message from the gateway in case if the transaction failed.
payment_info
object
This contains the payment details provided during the transaction.
payment_gateway_response
object
This will give the payment response received from the gateway.
refunds
Array
List of refunds attempted for a given transaction.
400 : Invalid Input data
Response Body
status
String
invalid_request_error
error_code
String
invalid
error_message
String
Invalid authentication account id
401 : Authentication Failed
Response Body
status
String
error
error_code
String
access_denied
error_message
String
Invalid Authentication
Have questions?
- Need help? Contact support
- LLM? Read llms.txt