Error Codes

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

JP_001

• 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)

JP_002

• 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

JP_003

• 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 to documentation and verify the parameters

JP_004

• 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

JP_005

• Sample Error Message:
  No internet
• Description:
  User not connected to network
• How to handle response?
  Allow user to retry the payment

JP_006

• 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.

JP_007

• 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

JP_008

• 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

JP_009

• 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.

JP_010

• 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

JP_011

• Error Message:
  Internal server error
• Description:
  Server error
• How to handle response?
  Contact Juspay Support

JP_012

• 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."

JP_014

• Error Message:
  Startactivity in background failed, CCT activity timeout
• Description:
  Minimised before launching cct activity
• How to handle response?
  CCT cannot be opened if app is in background. Also CCT force timeouts after 180 sec

JP_015

• 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 "Cred App is not present on your device"

JP_016

• Error Message:
  Some error occured in Juspay Safe Mode
• Description:
  Juspay Safe Mode could not rescue the transaction
• How to handle response?
  Reinitiate the payment.

JP_017

• 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?
  Using isInitialised() to check whether the SDK has been initiated or not

JP_018

JP_019