You are reading the article Payment Request – Error Messages updated in October 2023 on the website Benhvienthammyvienaau.com. We hope that the information we have shared is helpful to you. If you find the content interesting and meaningful, please share it with your friends and continue to follow and support us for the latest updates. Suggested November 2023 Payment Request – Error Messages
This article lists the errors that might occur while generating Payment Requests, along with the corresponding solutions. You can find the error messages grouped under the respective Payment Gateways.
This article lists the errors that might occur while generating Payment Requests using PayU.
Only the Error Description (and not the Error Code) will appear while generating the payment link in TallyPrime.
Request OTP
Sl No.
Error Code
Error Description
Possible Reasons
Possible Solution
1
invalid_format
identity”: “Identity has invalid value
The mobile number is either blank or invalid.
.
2
404
not_found
User not found
The specified mobile number is not registered with the Payment Gateway.
Enter the , and try again.
3
422 locked
User account is locked
You have exceeded the limit for requesting OTPs.
Try again after 30 minutes.
OTP
Sl No.
Error Code
Error Description
Possible Reasons
Possible Solution
4
422
incorrect_otp
Otp is incorrect, 9 attempts remaining
,
The OTP is incorrect.
Enter a valid OTP and try again.
5
422
invalid_format
Code has invalid value
The OTP is blank.
Enter a valid OTP and try again.
6
422
expired_otp
The previous OTP has expired. Please request for a new OTP
The OTP has expired.
Request a new OTP and try again.
7
422
otp_already_used
Please request for a new OTP
The OTP has expired.
Request a new OTP and try again.
8
422
user locked incorrect_otp
“code”:”Otp is incorrect”,”user”:”User account is now locked”
The account is locked, as you have exceeded the limit of incorrect OTPs.
Contact the payment service provider. You will receive a link to unlock your account.
Alternatively, you can try again after 30 minutes, after which the account will be automatically unlocked.
Sl No.
Error Code
Error Description
Possible Reasons
Possible Solution
9
401
Unauthorized
Unauthorized
The session has expired.
Enter the newly generated OTP and try again.
10
402
Forbidden
Access Denied
This error might occur when:
The Merchant ID is invalid or incorrect.
The Merchant does not have the rights to generate link.
Enter a valid Merchant ID in the Merchant Profile, and try again.
Check if adequate rights are provided in the user account to generate link, that is, to View Bill and Add Bill.
11
400
Expiry cannot be less than or equal to the current date
The link expiry date is earlier than or the same as the current date (System Date).
This might happen when either the link expiry date or the System Date was changed to an earlier date.
Ensure that the link expiry date is later than the current date (System Date).
12
500
Internal Server Error
The Merchant ID is invalid, incorrect, or blank in the Merchant Profile.
This might happen when:
The Merchant ID is invalid or incorrect in the Merchant Profile.
The Merchant ID is blank in the imported Merchant Profile.
Enter a valid merchant ID in the Merchant Profile, and try again.
This article lists the errors that might occur while generating Payment Requests using Razorpay.
Only the Error Description (and not the Error Code) will appear while generating the payment link in TallyPrime.
OTP
Sl No.
Error Code
Error Description
Possible Reasons
Possible Solution
1
200
BAD_REQUEST_ERROR
Invalid_client
Validation failed. The login id must be a valid email address.
The e-mail address entered in the Merchant Profile is invalid.
Enter a valid and try again.
2
200
BAD_REQUEST_ERROR
Validation failed. The merchant id must only contain letters and numbers.
The Merchant ID contains special characters.
3
200
BAD_REQUEST_ERROR
Invalid merchant/user
Enter a and try again.
4
200
BAD_REQUEST_ERROR
Validation failed. The merchant id must be 14 characters.
The Merchant ID is invalid.
Enter a and try again.
5
200
BAD_REQUEST_ERROR
The current user profile is restricted from this action
The e-mail address entered in the Merchant Profile is not registered for this Merchant ID.
Enter a valid e-mail address in the Merchant Profile, and try again.
6
200
BAD_REQUEST_ERROR
The merchant id field is required.
The Merchant ID is blank in the Merchant Profile.
This might happen when the Merchant ID was removed from the imported Merchant Profile.
Enter a valid Merchant ID in the Merchant Profile, and try again.
7
200
BAD_REQUEST_ERROR
The login id field is required.
The e-mail address is blank in the Merchant Profile.
This might happen when the e-mail address was removed from the imported Merchant Profile.
Enter a valid e-mail address in the Merchant Profile, and try again.
Verify OTP
Sl No.
Error Code
Error Description
Possible Reasons
Possible Solution
8
200
BAD_REQUEST_ERROR
Invalid OTP
The OTP entered is invalid or expired.
Enter a valid OTP and
If you send an OTP request multiple times within 5 minutes, then you will receive the same OTP.
If you want a new OTP, then you have to wait for 5 minutes before sending a fresh request.
You will have to again wait for 5 minutes, and then
9
200
BAD_REQUEST_ERROR
Validation failed. The pin field is required.
The OTP is blank.
Enter a valid OTP and try again.
10
200
BAD_REQUEST_ERROR
The current user profile is restricted from this action
The Merchant ID is blank in the Merchant Profile.
This might happen when the Merchant ID was removed from the imported Merchant Profile.
Enter a valid Merchant ID in the Merchant Profile, and try again.
11
200
BAD_REQUEST_ERROR
Validation failed. The login id field is required.
The e-mail address is blank in the Merchant Profile.
This might happen when the e-mail address was removed from the imported Merchant Profile.
Enter a valid e-mail address in the Merchant Profile, and try again.
Sl No.
Error Code
Error Description
Possible Reasons
Possible Solution
13
400
BAD_REQUEST_ERROR
expire by: timestamp must be at least 15 minutes in future
The link expiry date is earlier than or the same as the current date (System Date).
This might happen when either the link expiry date or the System Date was changed to an earlier date.
Ensure that the link expiry date is later than the current date (System Date).
14
400
BAD_REQUEST_ERROR
name: the length must be between 1 and 255.
The Party A/c Name exceeds the allowed length (255 characters).
15
400
BAD_REQUEST_ERROR
contact: the length must be between 8 and 14.
The mobile number of the party is invalid.
Enter a valid mobile number for the party, and try again.
16
400
BAD_REQUEST_ERROR
The e-mail ID of the party is invalid.
Enter a valid e-mail ID for the party, and try again.
17
400
BAD_REQUEST_ERROR
amount exceeds maximum amount allowed.
The Amount entered exceeds the allowed limit.
Enter a valid Amount and try again.
18
400
BAD_REQUEST_ERROR
amount, should be a whole number for e.g. 2234 to create a payment link for 22.34 INR
The Amount entered exceeds the allowed limit.
Enter a valid Amount and try again.
19
400
BAD_REQUEST_ERROR
Must not be able to make live request when not activated
The Merchant Profile is yet to be activated by the payment service provider.
Verify the registration details and try again.
You're reading Payment Request – Error Messages
Update the detailed information about Payment Request – Error Messages on the Benhvienthammyvienaau.com website. We hope the article's content will meet your needs, and we will regularly update the information to provide you with the fastest and most accurate information. Have a great day!