Skip to main content
Available in🇮🇳 India
Every non-2xx response from the Onboarding APIs carries the same error envelope. Branch your handling on error.reason, the stable machine-readable field. Show error.description to the sub-merchant.
Error
Handy TipsA failed verification check is not an error. It returns 200, with the code in the element’s verification.error_code. Know more about failed-check codes.

Error Fields

The table below lists the fields of the error object:

Error Classes

The table below lists the error classes and their sources:

Reasons by HTTP Status

The table below lists the reasons each HTTP status carries:
Watch Out!Razorpay can add new reasons. Handle an unknown reason by its HTTP status.
Refer to the Errors reference for every reason, when it occurs and its sample description.
Last modified on November 18, 2026