Given below are sample error objects for bad request errors.
This error occurs when the value sent for a particular field exceeds the specified limit. For example, if you had sent a phone number with more than 10 digits.
Error Description | Next Step |
---|---|
The field_name must be x digits. | Check the length mentioned in the documentation and resend. |
This error occurs when you the send an invalid URL.
Error Description | Next Step |
---|---|
The url is not a valid URL. | Check the URL and resend. |
This error occurs when the value sent for a particular field is incorrect. For example, if you sent an invalid webhook event name.
Error Description | Next Step |
---|---|
Invalid event name/names: payment.authorized | Check the webhook event name and resend. |
This error occurs when a field is sent without any values. For example, if the Account entity parameter customer_facing_business_name
is sent without any value.
Error Description | Next Step |
---|---|
The business dba field is required. | Send the business name. |
This error occurs when the Razorpay team has evaluated the details, changed the activation status to needs_clarification
and has sought more details. Therefore, only those fields which are present in the requirements array
in the
Error Description | Next Step |
---|---|
Only fields requested for needs clarification are allowed for update. | Send only the highlighted fields. |
This error occurs when the Razorpay team is evaluating the submitted details and changed the activation status to under_review. Therefore, you cannot send any fields.
Error Description | Next Step |
---|---|
Merchant activation form has been locked for editing by admin | Do not send any requests. Wait for Razorpay team to revert. |
This error occurs when the activation is complete. At this point, you cannot send any fields.
Error Description | Next Step |
---|---|
Merchant activation form has been locked for editing by admin | Do not send any requests. |