NB Mandate Transactions
This operation retrieves information about all the available Mandate payment methods available for the merchant through Juspay. Consume data for all enabled wallets on the Juspay platform from the PaymentMethoad API
response and display them on the Checkout page.
User Journey Flow
This operation helps the merchant to redirect user to the Bank page selected by the user and complete payment through NetBanking.
Create Payload to call Process API for NB Payments. Refer code snippets on the right for reference.
Request Parameters
Unique uuid-v4 string
Example: abcd-12345-abcd-12345
Value: in.juspay.hyperapi
Parameters required to call Hyper SDK API
Must be nbTxn for NB Process calls.
order id pertaining to the order for which the payment is started.
The actual payment method that was selected by the user. For NetBanking transactions, it must be one of from the Payment Method table here.
Required for client side authentication
The key offers should be passed only when juspay offers are being used. The value for this key can set as the offerID which is received from /v1/offers/list api
This is a customer’s consent flag. This should be always TRUE in case of a mandate transaction
EMANDATE in case of PIX/NB/Wallet.
MANDATE in case of card
Bank IFSC. Required for emandate/e-NACH.
Bank account number. Required for emandate/e-NACH.
Account holder name. Should contain alphabetical characters only. Required for emandate/e-NACH.