SDK Error Codes
The following table lists client/server error codes that the Hypercheckout SDK returns in response to calls.
Scroll inside to view more
|
Error Codes
|
Sample Error Message
|
Description
|
Error Handling
|
|---|---|---|---|
JP_001
| Unable to parse response
| This is mainly caused due to API failures or an incorrect business logic.
| Please ensure that all parameters are passed as per documentation. Please ensure that order creation was completed for the particular order ID that was passed for the transaction call (applicable if you are required to create order through server to server call).
|
JP_002
| User_aborted
| This error code is received when an user backpressed after landing on Bank OTP page/ Netbanking Login page/ Wallet Redirection page.
| Allow user to retry the payment.
|
JP_003
| { "payload": { "cardExpYear": "Type mismatch: expected String, found Undefined" } }
| This is an Integration error caused due to type mismatch in parameters. The error message will state the parameter name and expected type.
| Please refer this documentation and try verifying the parameters and it's type.
|
JP_004
| Chrome custom tabs not found. Please add it to your dependencies
| Dependencies (will be mentioned in the error message) are not added.
| Add the respective dependency in SDK.
|
JP_005
| No internet
| User is not connected to the internet.
| Allow user to retry the payment.
|
JP_006
| Transaction status is awaited
| Delay in updation of transaction status. Awaiting response from PG.
| Invoke the Juspay Order Status API to check the status.
|
JP_007
| Page not found
| Unable to redirect to a valid URL to proceed with transaction
| Check dashboard configuration (or) Contact Juspay Support
|
JP_008
| Card params not found, Sdk params not found etc.
| Mandatory configurations on Juspay dashboard are incorrect/incomplete
| Check dashboard configuration (or) Contact Juspay Support
|
JP_009
| Submit OTP allowed is false
| 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.
| Allows user to retry payment with different payment method.
|
JP_011
| Internal server error
| Server error
| |
JP_012
| Transaction Failed at bank end.
| Transaction failure at PG end. The error message sent by the respective PG for various use cases will be passed for corrective action.
| Allow user to retry the payment. Take corrective action to reduce such errors by getting in touch with respective PG
|
JP_013
| Payment timed out
| This is provided when UPI Collect waiting screen is timeout
| Invoke the Juspay Order Status API to check the status.
|
JP_014
| Startactivity in background failed, CCT activity timeout
| Minimised before launching cct activity
| CCT cannot be opened if app is in background. Also CCT force timeouts after 180 sec
|
JP_016
| Some error occured in Juspay Safe Mode
| Juspay Safe Mode could not rescue the transaction
| Reinitiate the payment
|
JP_017
| initiate() can only be called once without terminate()
| Initiate was called multiple times on an instance before terminating the SDK
| Using isInitialised() to check whether the SDK has been initiated or not
|
JP_018
| Signature expired / invalid signature
| The signature sent in SDK payload is either invalid or has expired (More than 180 mins)
| |
JP_019
| JUSPAY_DECLINED
| Transaction is declined from Juspay server end
| |
JP_020
| Customer creation is failing
| Customer creation failed at Juspay backend
| |
JP_022
| Network Call Timeout
| This is provided when Juspay SDK has not received response from Juspay server within set time period
| -
|