A conversation guide for business, technology, security and procurement teams. Use this checklist to agree the scope of your proposal. It is not a service contract, coverage certification or security attestation.
Discuss your requirement with CEBS | Compare solutions
| Your need | Solutions to discuss |
|---|---|
| Capture identity information or review a business customer | ID Secure and Business Verification |
| Extract information or check an issued document | Document Intelligence and Document Verification |
| Complete an agreement and retain supporting evidence | Digital Signatures and Evidence Vault |
| Assess and improve security | Security Assurance |
| Maintain shared records across organisations | Blockchain Solutions, where a shared-record architecture adds value |
Record the issuing country, document name and version, front/back requirements, languages and scripts, fields required, and each check you expect. Identity reading, issuer-reference checks, physical originality and fraud detection are distinct requirements.
Agree an acceptance sample set, supported capture devices, lighting conditions, quality limits, exception handling and measurable pass criteria. Request the relevant test evidence before relying on a specific capability. A marketing document list does not establish tested coverage.
These are procurement questions, not claims that a certification or control has been independently verified.
Identify the business owner, technical lead and security reviewer. Agree the demonstration scenario, pilot samples, acceptance criteria, target dates, support responsibilities and commercial review. Do not send identity documents, credentials or sensitive customer records through the public enquiry form.
Published ID Secure budget guide | Integration overview | Security and privacy
Prepared 10 November 2026. Confirm the current proposal and scope with CEBS.