Error Codes

The following lists client/server error codes that HyperSDK returns in response to calls.

Error Message:Reason not available
Description:
Failure reason is unknown due to non-availability of error message from the Payment gateway partner.
How to handle response?
In case of increase in errors, please reach out to Juspay support for clarification

Error Message:Unable to parse response
Description:
Something went wrong. This is mainly due to API failures or incorrect business logic.
How to handle response?
1) Please ensure that all parameters are passed as per documentation.
2) Please ensure that order creation was completed for the particular order ID passed for transaction call.(applicable if you are required to create order through server to server call)

Error Message:
User_aborted
Description:
User backpressed after landing on Bank OTP page/ Netbanking Login page/ Wallet redirection page.
How to handle response?
Allow user to retry the payment

Error Message:
{ \"payload\": { \"cardExpYear\": \"Type mismatch: expected String, found Undefined\" } }
Description:
Integration error due to type mismatch in parameters. The error message will state the parameter name and expected type.
How to handle response?
Please refer documentation and verify the parameters

Sample Error Message:
Chrome custom tabs not found. Please add it to your dependencies
Description:
Dependencies (mentioned in the error message) are not added
How to handle response?
Add the respective dependency or sdk

Error Message:
Transaction status is awaited
Description:
Delay in updation of transaction status. Awaiting response from PG.
How to handle response?
Invoke the Juspay Order Status API to check the status.

Error Message:
Page not found
Description:
Unable to redirect to a valid URL to proceed with transaction
How to handle response?
Check dashboard configuration (or) contact Juspay Support

Sample Error Message:
Card params not found, Sdk params not found etc.
Description:
Mandatory configurations on Juspay dashboard are incorrect/incomplete
How to handle response?
Check dashboard configuration (or) contact Juspay Support

Error Message:
Submit OTP allowed is false
Description:
This is an error specific to Native OTP flow, where the user had exceeded the limit of incorrect OTP submissions. This will mostly lead to issuer blocking the users' card.
How to handle response?
Allows user to retry payment with different payment method.

Sample Error Message:
Gpay fallback feature is unsupported
Description:
Hyper SDK configurations for your Merchant ID are incomplete/ incorrect
How to handle response?
Contact Juspay Support

Error Message:
Transaction Failed at bank end.
Description:
Transaction failure at PG end. The error message sent by the respective PG for various use cases will be passed for corrective action.
How to handle response?
"Allow user to retry the payment.
Take corrective action to reduce such errors by getting in touch with respective PG."

Error Message:
Start Activity in background failed, CCT activity timeout
Description:
This may happen in case of Chrome Custom Tab payment flows (such as Amazonpay, Paypal) wherein the App was minimised before launching CCT activity. Hence CCT cannot be opened as app is in background. Also CCT force timeouts after 180 sec
How to handle response?
"This is a limitation pertaining to CCT payment flow. Hence allow user to retry payment in this case."

Error Message:
Cred App is not present in device
Description:
Transaction can not go through the cred application
How to handle response?
Take appropriate action, give user message "You have uninstalled the CRED application". Allow user to retry payment with alternate payment methods.

Error Message:
initiate() can only be called once without terminate()
Description:
Initiate was called multiple times on an instance before terminating the SDK
How to handle response?
Please use isInitialised() to check whether the SDK has been initiated and reinitiate the payment