JavaScript is disabled. Some features may not work. You can also read the static version: View text version

Wallet Payment

Create a payment transaction for paying from a prepaid Wallet. Once you have the response, depending on the “method” attribute, you will have to take the next step. If you receive GET, then take the value in the “URL” attribute and redirect the user to this location. If you receive POST, then “params” attribute will hold a map containing key-value pairs.

For Web, you can create a form with these parameters as hidden variables and auto submit the form. Example code in Javascript: Serialize Parameters.

For Android, serialize this data such that it can be loaded to WebView directly via postData. Example code in Java: Serialize Parameters.

Scroll inside to view more

payment_method	Wallet name
ALIPAY	ALIPAY Wallet
APPLEPAY	APPLEPAY
GOOGLEPAY	Googlepay Wallet
GRABPAY	GRABPAY WALLET
WECHATPAY	WeChat Pay
ALIPAY	ALIPAY Wallet
GOPAY	GOPAY WALLET
GRABPAY	GRABPAY WALLET
GOOGLEWALLET	Google Wallet
APPLEPAY	APPLEPAY
ZALOPAY	ZaloPay Wallet
VNPAY	VNPAY Wallet
SHOPEEPAY	SHOPEEPAY WALLET
QR_SHOPEEPAY	SHOPEEPAY QR WALLET
QR_GOPAY	GOPAY QR WALLET
GOPAY	GOPAY WALLET
SHOPEEPAY_QR	Shopeepay QR
GOPAY_QR	GoPay QR
DANA	Dana Wallet
DANA_QR	Dana QR
LINKAJA	Linkaja Wallet
LINKAJA_QR	Linkaja QR
OVO_COLLECT	Ovo Collect
GOOGLEWALLET	Google Wallet
LAZADAPAY	LAZADAPAY
LINEPAY	LinePay
WECHATPAY	WeChat Pay
PAOTANGPAY	PAOTANGPAY
GOOGLEWALLET	Google Wallet
GRABPAY	GRABPAY WALLET
APPLEPAY	APPLEPAY
TRUEMONEY	TrueMoney
PAYPAL	PayPal
KBANK_CARD	KBANK Card
FIB	FIB
PAYME	PAYME wallet
STCPAY	StcPay wallet
MWALLET_QR	MWALLET QR wallet

HANDLING POST

When you get POST as the authentication method in the response, then the customer must be redirected using a form. Example HTML code is given to you. Depending on your client language, choose the appropriate way to create the form.

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 sending HTTP 302 from your server. However, if the API call was made from the browser, then you can utilize the code snippet provided.

Request

Response

API Endpoints

Production Link

POST

https://api.juspay.in/txns

                      Basic Auth
                      *
                      

Base64 Encoded username:password

required

Consists of two parts.

Username: API Key obtained from Juspay dashboard
Password: Empty string

Example:-
Basic MUQ2QUxxxxxxxxxxxxU5QTIxQzNFNTQwNkFDMEZCOg==

                      x-merchantid
                      
                      

string

Recommended

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

                      version
                      
                      

string

Optional

Pass the date in YYYY-MM-DD format.
Note: If a version is provided, the response will include data corresponding to that specific version date.

It is recommended not to enforce strict validation on the entire response on the merchant's side to allow for future key additions.

Example:-
2023-01-01

                      Content-Type
                      *
                      

String

Required

application/x-www-form-urlencoded

Body

                      order_id
                      *
                      

string

Required

Unique Identifier for the order. Should be Alphanumeric with character length less than 21.

                      merchant_id
                      *
                      

string

Required

ID of the merchant_account that you hold with us.

                      payment_method_type
                      *
                      

string

Required

Must be WALLET

                      payment_method
                      *
                      

string

Required

The actual payment method that was selected by the user.

                      redirect_after_payment
                      *
                      

Boolean

Required

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.

                      format
                      *
                      

json

Required

it is set to json, then the response will be HTTP 200 with a JSON formatted text. Otherwise, the response is HTTP 200 with the HTML response where user will be redirected to bank page within 3 secs.

Response Body

                      order_id
                      
                      

string

Unique Identifier for the order which is passed in the api request

                      txn_id
                      
                      

string

Transaction ID for the order.

                      status
                      
                      

string

Refers to status of the order

                      payment
                      
                      

object

                      authentication.method
                      
                      

string

It provides the details about the type of authentication method. It can be either GET or POST

                      authentication.url
                      
                      

String

User can be directed to the targeted payment method page by loading the URL in the browser

                      authentication.params
                      
                      

Object

Only when you have POST as the authentication method

                      key1
                      
                      

String

Using the key value pair, form must be created and direct the user appropriately.

Response Body

                      user_message
                      
                      

String

Error message can be displayed to the user

Example:- Invalid merchant id. Cannot process your request.

                      error_message
                      
                      

String

Provides the reason for the error

Example:- Invalid Request

                      error
                      
                      

Boolean

Denotes whether error is present or not

Example:- true

                      error_info
                      
                      

JSON

Additional information on the error message

                      user_message
                      
                      

String

Error message can be displayed to the user

Example:- Please pass valid merchant_id in request.

                      fields
                      
                      

Array

Details on the missing field with which the error occurred

                      developer_message
                      
                      

String

Detailed info on the error

Example:- merchant_id is invalid.

                      category
                      
                      

String

category of the error

Example:- USER_ERROR

Have questions?
Need help? Contact support
LLM? Read llms.txt