| State | What to ask | What not to do |
|---|---|---|
| Written rejection | Exact reason/underwriting gap and whether correction would change eligibility | Immediate unchanged reapplication |
| Verification complete, no decision | Current stage, decision owner, pending item, target date | Assume silence means rejection |
| Portal and branch disagree | Which system owns the current application status | Open duplicate applications blindly |
| Collateral/upfront-fee surprise | Written basis and official scheme/lender rule | Pay an intermediary to “unlock” sanction |
← Full guide: MUDRA Loan Rejected (Reasons, Reapplication, and Complaint Path)
Do not mix rejection, delay, and scam risk
State. What to ask. What not to do. Written rejection. Exact reason/underwriting gap and whether correction would change eligibility.
Start here
State. What to ask. What not to do. Written rejection. Exact reason/underwriting gap and whether correction would change eligibility. Immediate unchanged reapplication. Verification complete, no decision. Current stage, decision owner, pending item, target date. Assume silence means rejection. Portal and branch disagree. Which system owns the current application status. Open duplicate applications blindly..
What applies to this exact problem
Check these first
- Written rejection: Exact reason/underwriting gap and whether correction would change eligibility.
- Verification complete, no decision: Current stage, decision owner, pending item, target date.
- Portal and branch disagree: Which system owns the current application status.
Fix it in this order
- Written rejection: Exact reason/underwriting gap and whether correction would change eligibility.
- Verification complete, no decision: Current stage, decision owner, pending item, target date.
- Portal and branch disagree: Which system owns the current application status.
- Collateral/upfront-fee surprise: Written basis and official scheme/lender rule.
- Open duplicate applications blindly.
- Pay an intermediary to “unlock” sanction.
Evidence to keep
- Udyam/GST/PAN and entity documents — keep it with the evidence for “Do not mix rejection, delay, and scam risk”.
- Bank statements and financials — keep it with the evidence for “Do not mix rejection, delay, and scam risk”.
- Quotation/invoice or working-capital evidence — keep it with the evidence for “Do not mix rejection, delay, and scam risk”.
- Sanction/rejection/grievance references — keep it with the evidence for “Do not mix rejection, delay, and scam risk”.
Do not make it harder
- Paying an agent who guarantees sanction For “Do not mix rejection, delay, and scam risk”, that can hide whether the underlying issue is actually resolved.
- Using inconsistent turnover or business-name data For “Do not mix rejection, delay, and scam risk”, that can hide whether the underlying issue is actually resolved.
- Treating in-principle approval as final disbursement For “Do not mix rejection, delay, and scam risk”, that can hide whether the underlying issue is actually resolved.
How you know it is fixed
- The next action has an owner and a traceable completion record for “Do not mix rejection, delay, and scam risk”.
- The official status changes to the expected final state, not merely “case closed” for “Do not mix rejection, delay, and scam risk”.
If this still isn't resolved
- Lender MSME/grievance desk State the unresolved issue explicitly: “Do not mix rejection, delay, and scam risk”.
- Official scheme/helpdesk where a scheme is involved State the unresolved issue explicitly: “Do not mix rejection, delay, and scam risk”.
- RBI CMS for eligible unresolved lender-service complaints State the unresolved issue explicitly: “Do not mix rejection, delay, and scam risk”.
Parent-guide references
These references support the parent guide and escalation context. Verify provider-, model-, policy-, or jurisdiction-specific details before an irreversible step.
Need the complete context?
This page solves one branch. The parent guide covers the full decision, edge cases, alternatives, and related checks.