SDK Error Codes
Sample Error Payload
SDK errors will be received in the following format:
Scroll inside to view more
|
Key
|
Type
|
Description
|
|---|---|---|
requestId
| String
| A unique randomly generated unique string for triggering any operation on HyperSDK. Usually used to match if response or callbacks are triggered for the same operation. Should be a UUID string. Click here for reference.
|
service
| String
| A reference to the Juspay product being consumed
|
payload
| String
| Contains all relevant information required to complete an operation in input or output of an operation in output.
|
error
| Boolean
| Root key to identify if an operation triggered on SDK was successful or failure.
|
errorCode
| String
| A set of defined codes for errors triggered for different cases for SDK.
|
errorMessage
| String
| Details about the error message to help figure out integration or transactional issues.
|
The following table lists client/server error codes that Hyper SDK returns in response to calls.
Juspay Errors
Scroll inside to view more
|
Error Codes
|
Description
|
Error Handling
|
Sample Error Messages
|
|---|---|---|---|
JP_000
| Reason Unavailable
| Contact Juspay Support
|
|
JP_001
| This is mainly caused due to 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
| This error code is received when a user backpressed.
| Allow user to retry the payment.
|
|
JP_003
| 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
| User based errors.
| Please ask the user to perform respective actions required.
|
|
JP_005
| User is not connected to the internet.
| Ask user to connect to the internet.
|
|
JP_006
| Delay in updation of transaction status. Awaiting response from PG.
| Invoke the Juspay Order Status API to check the status.
|
|
JP_007
| Unable to redirect to a valid URL to proceed with transaction
Not specific to UPI | Contact Juspay Support
|
|
JP_008
| Mandatory configurations on Juspay dashboard are incorrect/incomplete
| Check dashboard configuration (or) Contact Juspay Support
|
|
JP_009
| 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.
Not specific to UPI | Allows user to retry payment with different payment method.
|
|
JP_010
| Feature is not supported
| Contact Juspay Support
|
|
JP_011
| Server error
| Contact Juspay Support
|
|
JP_012
| 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_014
| Minimised before launching cct activity
Not specific to UPI | CCT cannot be opened if app is in background. Also CCT force timeouts after 180 sec
|
|
JP_015
| Transaction can not go through the cred application
Not specific to UPI | Take appropriate action, give user message 'Cred App is not present on your device'
|
|
JP_016
| Juspay Safe Mode could not rescue the transaction
Not specific to UPI | Reinitiate the payment
|
|
JP_017
| 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
| Required permissions to run SDK does not exists
| Allow users to grant those permissions
|
|
JP_019
| When NPCI CL does not return the challenge or throws a technical error
| Retry or contact the Juspay team
|
|
Sub Error Codes
These are the error codes that is sent inside the payload of responses. Sample JSON:
Scroll inside to view more
|
Process API
|
Sub Error Code
|
ERROR MESSAGE
|
|---|---|---|
upiBindActivateDevice
| APP_TOGGLED
| -
|

