ParseAPI Honest answers
An honest answer
is useful.
Your app makes decisions with this data. Knowing what a result means is part of the answer.
See it in actionMEANING MATTERS
Three values. Different decisions.
trueThe condition holds.
A field such as valid has a defined meaning for that API. Your app can act on that specific result.
falseThe condition does not hold.
A negative result can still be a successful lookup. It tells your app something useful.
nullNo value to report.
A field may be unknown or not applicable. Keep that distinction when the next decision depends on it.
PRECISION IN THE RESPONSE
See exactly what matched.
A BIN lookup returns the published prefix it matched. More specific records keep their own metadata, including the unknowns.
YOUR INPUT
437374008 digits matched.
The record identifies the issuer and card type. Its brand is unknown, so brand stays null, even though a shorter six-digit record has a brand.
See the BIN reference/bin/43737400{
"bin": "43737400",
"prefix": "43737400",
"country": "VN",
"issuer": "UOB",
"brand": null,
"type": "credit",
"prepaid": null
}Confidence comes from context.
Show the match.
The returned BIN prefix tells you the specificity of the record. A six-digit match stays a six-digit match.
Preserve the unknowns.
A more specific BIN record never borrows missing fields from its parent. A known issuer can sit beside an unknown brand.
Keep failure distinct.
If a VAT registry check is unavailable, the API returns an error. It does not report registered: false.
READ THE WHOLE ANSWER
Valid for what?
An email can have a valid format and still need a deliverability check. A phone can fit its numbering plan without proving someone will answer.
Each API defines what it checks. Your app can choose the evidence the decision needs.
BUILD WITH PARSEAPI
Build on an answer you understand.
Clear fields. Explicit matches. Room for what is unknown.