Wallet Direct Debit
Directly debit the amount from a Wallet that is linked to a Customer’s account. If the status in the response is CHARGED, then the payment is immediatley successful. If the status in the response is PENDING, then the user wallet doesn’t have sufficient balance for the payment and the topup URL is returned in the response
Wallet APIs : Link
Payments API :
Note: This is an authenticated call unlike other transaction APIs. This API must be invoked from your server directly. DO NOT send the API Key to client.
|
payment_method
|
Bank
|
|---|---|
GOPAY
| GoPay Wallet
|
DANA
| Dana Wallet
|
SHOPEE
| Shopee Wallet
|
GRABPAY
| GrabPay Wallet
|
HANDLING GET
When you get GET as the authentication method in the response, you may load the URL directly into the customer’s browser. You can easily achieve this by send HTTP 302 from your server. However, if the API call was made from the browser, then you can utilize the code snippet provided.
Consists of two parts.
Username: API Key obtained from Juspay dashboard
Password: Empty string
Example:-
Basic MUQ2QUxxxxxxxxxxxxU5QTIxQzNFNTQwNkFDMEZCOg==
Unique identifier for the merchant. This is the Merchant ID provided by Juspay. The value is case sensitive.
Passing this value will help us route efficiently at network level.
Example:- x-merchantid: testaccount
Pass the date in YYYY-MM-DD format
Example:-
2023-01-01
application/x-www-form-urlencoded
Unique Identifier for the order. Should be Alphanumeric with character length less than 21.
ID of the merchant_account that you hold with us.
Juspay wallet token for linked wallets. This is available in the /customers/:id/wallets API or /wallets/:id API.
Must be WALLET
The actual payment method that was selected by the user. For WALLET transactions, the values will be shared by Juspay team.
This is a boolean variable and accepts true/false. We recommend that you set this to true. If set to true, then the user is redirected to the return\_url configured for the order. If set to false, then the user will be stopped at the response page from the gateway. Your client should be able to read the page/title to infer that the user has completed the transaction.
If it is set to json, then the response will be HTTP 200 with a JSON formatted text. Otherwise, the response is HTTP 302 with the Location attribute having the destination URL.
Amount that the customer has to pay. Will accept stringified double or integer values with upto two decimal places. For example, "100.15" and "100" are valid input but "100.1532" is not valid.
It is the ID with which merchant refers to a customer object. This id is used to access the stored payment methods, allow EMI transactions and setup subscriptions.
In case of guest login it should be an empty string.
Example:- customer-id-007
Email address of the customer. If the backend gateway requires it, then you must send this value.
Example:- test@gmail.com
Mobile number or fixed line number of the customer. If the backend gateway requires it, then you must send this value.
Example:- 9999999912
ISO string of the currency. Accepted values are EUR, USD, GBP,HKD. Default value: INR
:order_id
:txn_id
CHARGED
error
Order timed out
invalid_request

