When applicants check their SASSA SRD R370 status, they only see simplified labels such as Pending, Approved, Referred, or Declined. However, each of these statuses actually represents a deeper internal process that SASSA does not publicly display.

See Also: SASSA Status Check

These hidden internal signals called “micro-status codes”tell the system how far your application has progressed, whether additional checks are required, and whether your profile carries risk indicators.

Understanding these micro-status codes can help applicants interpret delays, identify possible issues, and manage expectations more clearly. While SASSA does not reveal these internal signals, they can be understood through consistent patterns observed in the system.

What Are Micro-Status Codes?

Micro-status codes are internal signals used by SASSA’s verification system to determine the next action required on your application. The system does not show these codes to the public, but they influence:

• How long your application remains “Pending”
• Whether your profile is flagged for extra review
• Whether your approval requires a second-level check
• Whether additional financial verification is needed
• When your pay date is assigned

Think of micro-status codes as the “sub-steps” between major status updates. For example, an applicant marked as “Pending” may internally be in P-1, P-2, or P-3, depending on verification progress.

Install: SASSA App

Micro-Codes Behind “Pending”

“Pending” looks simple on the dashboard, but the system uses several micro-codes to determine your eligibility.

P-1: Identity Signal Verification

This means your ID, name, and personal records are still being checked with Home Affairs.
Typical causes:

• Recent ID updates
• Mismatched details
• System load delays

P-2: Financial Verification Queue

Your banking and income data are being collected from external partners. This stage often takes the longest because banks and financial databases update at different speeds.

P-3: Behaviour and Risk Pattern Check

The system evaluates your historical application behaviour to ensure no suspicious or inconsistent patterns exist.

A profile can remain “Pending” for days or weeks depending on how long each micro-stage takes.

The Micro-Codes Behind “Approved”

• “Approved” also has several layers. Not all approvals are ready for payment.
• A-1: Initial Approval Granted: You passed the identity and financial checks, but backend data still needs to finalize.
• A-2: Secondary Verification Completed: This means your risk score, historical records, and data stability have passed all checks.
• A-3: Payment Queue Pending: The most common sub-code before a pay date appears. You are approved, but your payment is not yet scheduled.
• A-4: Pay Date Assigned: This is the final verification micro-code. Once this is completed, the dashboard shows a pay date.

Micro-Codes Behind “Referred”

“Referred” is often misunderstood. While the dashboard shows a general label, the underlying micro-codes clarify the cause.

• R-1: Identity Recheck Required: Your ID needs re-verification due to mismatch or unresolved Home Affairs update.
• R-2: Bank Verification Mismatch: Your bank account details conflict with your ID, surname, or Home Affairs record.
• R-3: Risk-Flagged Account: The system detected behaviour or patterns needing manual or deeper automated checks.
• R-4: Alternative Income Flag: A possible income source has been detected and needs confirmation. Each “Referred” micro-code triggers a different verification path, which is why some applicants wait longer than others.

Micro-Codes Behind “Declined”

A decline is also not a single outcome internally. Micro-codes determine the reason.

D-1: Income Source Identified

The system detected financial activity above the SRD threshold.

• D-2: Identity Mismatch or Instability: Your ID details did not pass verification at Home Affairs.
• D-3: UIF/NSFAS Conflict: The system detected income or funding from alternative sources.
• D-4: Inconsistent Data Pattern: Your details conflict with historical data or banking records. Applicants with D-codes typically require a formal appeal.

Check Out (For SASSA Beneficeries): SASSA Payment Dates

Why These Micro-Codes Matter

Understanding these internal signals helps applicants:

• Understand why someone approved today gets a pay date later
• Realize why “Pending” can last for weeks
• See why “Referred” does not always mean a problem
• Identify whether their delay may be caused by ID, bank, or income issues
• Know when to expect a pay date after approval

Although SASSA does not publish micro-codes, their patterns show how the system evaluates risk, eligibility, and payment priority.

Can Applicants Influence the Micro-Codes?

Yes, indirectly and accurate and consistent information helps your application move smoothly through micro-codes:

• Use a stable bank account
• Ensure your Home Affairs details are correct
• Avoid frequent bank detail changes
• Keep your contact details up to date
• Do not use accounts receiving regular income

The more consistent your data, the faster your application passes through hidden verification layers.

FAQs

Why does my status stay “Pending” for so long?

Your application may be stuck in one of the micro-codes like P-2 (financial check) or P-3 (risk pattern review).

What does it mean if I’m approved but no pay date yet?

You are likely in micro-code A-3, where your payment is queued but not yet finalized.

Does “Referred” always mean a problem?

No. It sometimes means the system needs additional identity or bank confirmation, not a rejection.

Can SASSA support give me these micro-codes?

No, they are internal only. But the visible status on your dashboard is influenced by them.