PIX PISP Transaction
This operation retrieves information about all the available payment methods available for the merchant through Juspay. Consume data for all enabled wallets on the Juspay platform from the response and display them on the Checkout page.
Create Payload to call Process API for PIX PISP transaction. Refer code snippets on the right for reference.
Unique uuid-v4 string
Example: abcd-12345-abcd-12345
Value: in.juspay.hyperapi
Parameters required to call Hyper SDK API
Must be cardTxn for Card Process calls.
order id pertaining to the order for which the payment is started.
A valid credit/debit card number entered by the user.
Represent the expiry month of the card as MM (two digits only)
Represent the expiry year of the card as YY (two digits only)
CVV of the card. Usually three digits. Optional for all VISA saved cards, PLUXEE | SODEXO saved cards, and saved cards of select issuing banks of MASTERCARD
Required for client side authentication
This is a boolean variable and accepts true/false. If set to true, then the card will be tokenised when the transaction is successful. Else, the card will not be saved.
Card holder name. Should contain alphabetical characters only.
This is network of the card number provided. One of VISA/MASTERCARD/MAESTRO/AMEX/RUPAY. Mandatory for AMEX to verify the input of 4 digit CVV.
To show a loader for the processing state.
Default is false. Set it to true if the user wishes to perform an EMI transaction on the given card.
Represents the bank that issued the card. Value must be one of the entries mentioned under EMI Bank in the support matrix here
.
The tenure of the EMI in number of months.
The type of EMI ie STANDARD_EMI or NO_COST_EMI
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
THREE_DS/OTP
This is a customer’s consent flag. This should be always TRUE in case of a mandate transaction.
It will CARD for cards transaction
Mandatory for BRL transactions