OPTION 1
Native generation
Issuing Verifiable Digital Document And Credential From Scratch
- Suitable when there is no digital file yet
- Html template needs to be prepared
- Multiple ways to handle recipient data (CSV Upload & API integration)
- Issuer provides the required credential data and recipients data on issuance
- Blockchain notarization via cryptographic proof (hash representation)
OPTION 2
External Generation
Issuing Verifiable Digital Document And Credential From Existing Digital File
- Suitable when the digital file exists in some form (doesn’t have to be complete).
- Issuer provides the required credential data and recipients data on issuance.
- Blockchain notarization via cryptographic proof (hash representation).
OPTION 3
Multiple Parties Generation
- Allows issuance of digital verifiable documents and credentials cross multiple organizations
- Provides full control, traceability and auditing of issued credentials and documents cross multiple organizations
- Provides full control, traceability and auditing of issued credentials and documents cross multiple organizations
- Support for co-signatories.
Provides and Support The Following Points
- Validity and originality of issued digital documents and credentials
- Legitimacy and authenticity of issuer and recipient
- Access and privacy rights of issuer and recipient
AcVerify Support and Answer The Following
Yes, if it passed the onboarding check (organizational) and became part of the verify.it permissioned blockchain network
Yes, if the cryptographic proof for the credential is stored on the blockchain and the respective transaction was signed by the issuer.
Yes, if the credential status is Published.
Yes, if the recipient is in control of the email address configured in the system.
The veracity aspect is not part of the verification (responsibility of the issuer).
Yes. If cryptographic proofs of all concerned parties are available on the credential or document.