HomeTallyPrimeAccountingBanking UtilitiesPayment Request - Error Messages

 

Explore Categories

 

 PDF

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.

PayU

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

422

invalid_format

identity”: “Identity has invalid value

The mobile number is either blank or invalid.

Enter the registered mobile number (without any prefix such as 0 or +91) in the Merchant Profile, and try again.

2

404

not_found

User not found

The specified mobile number is not registered with the Payment Gateway.

Enter the registered mobile number in the Merchant Profile, and try again.

3

422 locked

User account is locked

You have exceeded the limit for requesting OTPs.

Try again after 30 minutes.

Verify 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

The Merchant ID is invalid or incorrect.

Enter a valid Merchant ID in the Merchant Profile, and try again.

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.

Razorpay

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.

Request 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 e-mail address in the Merchant Profile, 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.

Enter a valid Merchant ID in the Merchant Profile, and try again.

3

200 

BAD_REQUEST_ERROR

Invalid merchant/user

The Merchant ID/e-mail address is invalid or incorrect.

Enter a valid Merchant ID/e-mail address in the Merchant Profile, and try again.

4

200 

BAD_REQUEST_ERROR

Validation failed. The merchant id must be 14 characters.

The Merchant ID is invalid.

Enter a valid Merchant ID in the Merchant Profile, 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

Validation failed.
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

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.

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 try again.

click here.

  • 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.
  • If you enter an incorrect OTP three times, then the fourth attempt will not be accepted, even if you enter the correct OTP.
    You will have to again wait for 5 minutes, and then generate a fresh request.

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).

Ensure that the Party A/c Name does not exceed 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

email: must be in a valid format for e.g. abcxyz@domain.com.

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.

Paytm

This article lists the errors that might occur while generating Payment Requests using Paytm.

Only the Error Description (and not the Error Code) will appear while generating the payment link in TallyPrime. However, if needed, you can view the Error Code by pressing F1 > TroubleshootingEvent Log.

Request OTP

Sl No.

Error Code

Error Description

Possible Reasons

Possible Solution

1

302

Phone number is missing in request

The mobile number is blank in the Merchant Profile.

This might happen when the mobile number was removed from the imported Merchant Profile.

Enter a valid mobile number in the Merchant Profile, and try again.

2

302

Merchant id is invalid in request

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.

3

RA_601

You have reached limit to send OTP. Please try again after 24 hours.

You have exceeded the limit for requesting OTPs, which is 10 OTPs per user per day.

Try again after 24 hours.

4

RA_5003

Phone number passed is not registered with the given reseller provided in the request

The Merchant ID is blank in the Merchant Profile, and the mobile number is not registered with Tally’s reseller ID.

Enter a valid mobile number that is registered with Tally’s reseller ID.

5

RA_5004

No merchant registered with the given phone number and reseller

The mobile number is not registered with the Merchant ID and the Payment Gateway.

Enter a valid mobile number that is registered with the Payment Gateway, and try again.

6

RA_5005

Merchant id passed is not registered with the given phone number and reseller provided in the request

The mobile number entered in the Merchant Profile is not registered with the Payment Gateway as a Merchant.

In the Merchant Profile, enter a valid mobile number that is registered with the Payment Gateway as a Merchant, and try again.

7

RA_5007

Multiple merchant ids are tagged with the provided reseller and phone number. Please provide the required merchant
id for which otp is to be generated.

The Merchant ID entered in the Merchant Profile is invalid, and the mobile number is registered with multiple Merchant IDs.

This might happen when Merchant Profile was imported with an invalid or blank Merchant ID.

Enter a valid Merchant ID and mobile number in the Merchant Profile, and try again.

The mobile number must be registered with only the current Merchant ID.

8

RA_5040

Please enter the correct phone number for which otp is to be generated.

The mobile number is invalid.

This might happen when Merchant Profile was imported with an invalid mobile number.

Enter the registered mobile number (without any prefix such as 0 or +91) in the Merchant Profile, and try again.

9

RA_5041

Please enter the correct user merchant id.

The Merchant ID entered in the Merchant Profile is invalid.

Enter a valid Merchant ID in the Merchant Profile, and try again.

10

RA_5050

Internal Service Error

There might be a temporary issue in the services provided by the Payment Gateway provider.

Try again after some time.

Verify OTP

Sl No.

Error Code

Error Description

Possible Reasons

Possible Solution

11

RA_602

Invalid OTP entered

The OTP is invalid.

Enter the correct OTP and try again.

12

RA_604

Oops ! You have reached OTP limit

You have entered three incorrect OTPs.

Generate a new OTP and try again.

13

RA_5050

Internal Service Error

There might be a temporary issue in the services provided by the Payment Gateway provider.

Try again after some time.

Sl No.

Error Code

Error Description

Possible Reasons

Possible Solution

14

100

Error is dependent on what risk send us

There might be security issues in the current transaction.

Try again after some time.

15

501

Internal Service Error

There might be a temporary issue in the services provided by the Payment Gateway provider.

Try again after some time.

16

502

Something bad happened.

There might be a temporary issue in the services provided by the Payment Gateway provider.

Try again after some time.

17

5023

Merchant Id is invalid.

The Merchant ID is either blank or invalid.

Enter a valid Merchant ID in the Merchant Profile, and try again.

18

6018

Email id is invalid in customer contact

The e-mail ID of the party is invalid.

Enter a valid e-mail ID for the party, and try again.

19

302

The input contains special characters. 

Please remove them and try again

The e-mail ID of the party is invalid.

Enter a valid e-mail ID for the party, and try again.

20

6019

Phone no is invalid in customer contact

The mobile number of the party is invalid. 

Enter a valid mobile number (without any prefix such as 0 or +91) of the party, and try again.

21

302

The input contains special characters. 

Please remove them and try again

The mobile number of the party is invalid. 

Enter a valid mobile number (without any prefix such as 0 or +91) of the party, and try again.

22

302

The input contains special characters. 

Please remove them and try again

The Remarks field contains special characters that are not allowed by the Payment Gateway.

Enter the Remarks without any special characters, and try again.

 

Post a Comment

Is this information useful?
YesNo
Helpful?