Empty or invalid name at bank
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
Invalid account
Bank account details are invalid across all partner banks. This is a limitation on the bank’s end.
Account blocked
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 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
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
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.
Do Penny Drop and Verification Suite work in the pre-production (test) environment?
Do Penny Drop and Verification Suite work in the pre-production (test) environment?
In Secure ID, Penny Drop is a real transaction, so it works only in the Production environment. It does not perform a real verification in the Pre-Production (Test) environment. Instead, the Test environment returns mock responses that you can use to test and validate your integration before moving to Production.
Why am I getting a 422 Unprocessable Entity error when using the Bank Account Validation API?
Why am I getting a 422 Unprocessable Entity error when using the Bank Account Validation API?
A 422 Unprocessable Entity error in the Bank Account Validation API can occur for the following reasons:
- You are using the deprecated V1 endpoint (for example,
/payout/v1/validation/bankDetails), which is being retired. Migrate to the Bank Account Verification Sync V2 API. - The required feature is not enabled for your account. Contact your Account Manager or fill in the Support Form to enable it.
- There are invalid or missing request parameters.
- The request does not meet the API’s validation requirements.
Why does the bank account verification API return 'id_not_found' for a valid bank account?
Why does the bank account verification API return 'id_not_found' for a valid bank account?
The
id_not_found status in the Bank Account Verification Sync V2 API can occur for the following reasons:- The account is returned as invalid by available sources.
- IMPS mode is not enabled for the specific bank account and IFSC combination. The verification process may rely on IMPS.
Why am I getting a 404 error or 'internal_error' when calling the Geo Coding API?
Why am I getting a 404 error or 'internal_error' when calling the Geo Coding API?
A 404 error or
api_error message can occur if you are using incorrect credentials. Ensure you are using API keys specifically generated from the Merchant Dashboard rather than general Payment Gateway credentials. Secure ID Client IDs should start with CF.