Document Requirements
Every document needs a "requirement" specified to tell Proof what is required to consider a transaction complete. A good way to think about it is specifying the "type of document". Each requirement type implies a different set of authentication and signing requirements for the signer to complete the transaction.
Document requirements for Proof-type transactions
If you are looking to send a Proof transaction for identity verification, this is currently managed as a signer-level requirement. See the
signerobject in Create Transaction as well thesignerobject in our API Object Reference.The Proof transaction type is not compatible with documents requiring notarization - it can only be set up with an
eSigndocument.
| Requirement | Description | Knowledge-based Authentication (KBA) Required? | US SSN Required? | # Forms of ID Required | Notary Meeting Required? | Notary Seal Required? | Notary Signature Required? |
|---|---|---|---|---|---|---|---|
notarization | A document that requires notarization. | Yes | Yes | 1 | Yes | Yes | Yes |
esign | A document that requires just a signature. | No | No | 0 | No | No | No |
identity_confirmation | Used to support the signing of PS form 1583 for signers without a US SSN. Requires the signer to undergo identity confirmation instead of notarization. | No | No | 2 | Yes | No | Yes |
Updated about 1 year ago