Credit / Debit Saved Card transaction
This operation needs to be called before loading the payment page to get the details of the cards stored by the user.
This action starts a saved card transaction with THREE_DS authentication.
Create Payload to call Process API for New Cards transaction. Refer code snippets on the right for reference.
Payload Parameters
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 card token obtained using /card/list API or cardList SDK call. If you send this parameter, then card_number, name_on_card, card_exp_year, card_exp_month fields are not required. If the token is generated using the /card/tokenize API, card_number, name_on_card, card_exp_year, card_exp_month and card_security_code fields are not required.
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 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.
Cryptogram is required to be passed in tavv
Pass Token requester id
The PAR value as is received from the network. Can be used to check uniqueness of cards for use case of Offers, EMI etc.
Token's last four. Optional in case of certain networks.