Secure ID Troubleshooting

Common integration errors and solutions for Secure ID

Empty or invalid name at bank

This issue arises when the customer’s name isn’t accessible through IMPS rails from partner banks. This is a bank-side limitation. The name can’t be retrieved in this case.

Invalid account

Bank account details are invalid across all partner banks. This is a limitation on the bank’s end.

Account blocked

The account is valid but currently blocked, so transactions can’t be processed. As part of the penny drop validation, we attempted to deposit ₹1 into the account. However, the transaction failed due to the blocked status.

To troubleshoot this issue, follow this step:

• Coordinate with the customer to verify and reactivate the account via their bank.

UTR not generated

UTR generation usually occurs during penny drop validation. In this case, a different validation mechanism was used to improve the success rate, so a UTR wasn’t generated.

To troubleshoot this issue, follow this step:

• If UTR generation is required for all validations, fill in the Support Form to enable this configuration for your account.

Bank Account Validation (BAV) Fraud

This issue arises when there are excessive penny drop attempts made (for example, more than 15 in 24 hours) to the same account and IFSC code.

To troubleshoot this issue, follow this step:

• Fill in the Support Form to unblock affected accounts.

Blocked by CORS policy

This issue arises when you call Cashfree’s APIs through your frontend.

To troubleshoot this issue, follow this step:

• To avoid CORS errors while integrating Cashfree’s API, route the API requests through your backend server. Your backend can handle the request and pass the response back to the frontend. This approach bypasses browser-imposed CORS restrictions, as the call is made server-side.