Credit / Debit Card transaction
This operation helps to get Card details using card bin (First 6 digits of the card). You can also use this operation to check if a card is eligible for ATM PIN payments.
Use the following optional parameters to check card eligibility for -
1. Mandates - "checkMandateSupport":true (Mandatory to pass for Mandate Payments)
2. DOTP - "checkDirectOtpSupport":true
3. Tokenization - "checkTokenizeSupport":true
Refer below details to create Process Payload for Card Txns.
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.
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/VISA_CHECKOUT
This is a customer’s consent flag. This should be always TRUE in case of a mandate transaction.

