The difference
A raw-data response returns the underlying information in full — a complete name, a full registry photo. A masked response confirms enough to be useful — a partial name, a status — without exposing the full underlying record.
Why masking is the safer default
Most callers of a verification API need to know whether a check passed, not the full content of what was checked. Defaulting to masked responses limits what's exposed if a response is ever logged, cached, or intercepted somewhere it shouldn't be.
When raw data access should be separate
Where fuller access is genuinely needed, it should be a distinct, more tightly gated capability — not the default shape of a routine validation response.