Failure isn't a single category
A verification call can fail in meaningfully different ways: the registry couldn't be reached, the number wasn't found, the face didn't pass liveness, or the face didn't match closely enough. Collapsing all of these into one generic 'verification failed' response throws away information the client needs.
Why distinct error codes matter to the integrator
A client building a real onboarding flow needs to react differently to a liveness failure (ask the user to recapture) than to a not-found registry status (ask the user to recheck the number) — distinct, documented error codes are what make that possible.
What shouldn't be exposed in an error
Error responses should describe the failure clearly without leaking sensitive detail — confirming a mismatch without exposing what the actual registry record contains, for instance.