The MyProof identity verification API proves document-derived facts such as age, residency, nationality, document validity, and identity match. It is built for teams that need a verification answer without transmitting the full government ID.
Frequently asked questions
What is an identity verification API?
An identity verification API lets a business ask for verified facts from a government ID, such as age, residency, document validity, nationality, or identity match, and receive a result that can be used in its own product flow.
How does MyProof avoid collecting ID data?
The customer's phone reads the document and evaluates the policy locally. MyProof sends the business only the verification answer and a receipt reference, not the ID image, document number, birthdate, address, or biometric data.
Is MyProof only for age checks?
No. Age is one predicate. The same identity verification API can support residency, document validity, nationality, and identity match checks when those facts are present on the government document and allowed by the policy.
Can one verification combine multiple facts?
Yes. A policy can require age and residency and document validity together. The predicates are evaluated on the device and returned as one result, so the business does not need to collect each underlying data field.
What does the server receive?
The server receives a boolean result for the requested policy and a signed receipt reference that can be logged for audit. The server does not receive the customer's full ID data.