Body
Authenticate
Starts the authentication and linking process of the wallet with the customer. This API is used if the wallet was delinked earlier by the customer or you decided to skip authentication during wallet creation. The customer will get an OTP on his registered mobile number on successful completion of this step.
Request
Response
API Endpoints
Sandbox Link
POST
https://sandbox.juspay.in/wallets/{wallet_id}
Production Link
POST
https://api.juspay.in/wallets/{wallet_id}
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
wallet_id
*
String
Mandatory
Wallet Id of the wallet
Parameters
command
*
string
Required
Send it as authenticate if you want to start the authentication/linking process.
gateway_reference_id
string
Required in case of multiple MID setup
client_auth_token
string
Required for client side authentication
200 : Success
Response Body
id
string
wlt_q23xzki3pazgtezo
object
string
wallet_account
wallet
string
MOBIKWIK
token
null
current_balance
null
linked
boolean
last_refreshed
String
400 : Invalid Input data
Response Body
object
object