Page and orientation
Confirm page numbering, source dimensions and whether coordinates refer to the original or a transformed image.
BETASIGNATURE INTEGRATION
Bring signature evidence into your document workflow.
Connect detection, positioning, reference comparison and agreed validations to the systems that process your scanned documents. Start with the current beta contract and the decisions your team needs to support.
Forms · contracts · mandates · delivery notes · cheques
Document → signature evidenceILLUSTRATION
THE FOUR QUESTIONS
Two drawn signature candidates appear on this fictional agreement. Their positions do not identify the signers.
Synthetic drawings and example workflow. No upload, model inference or live validation is performed here.
CHOOSE THE PROCESSING PATH
Request the evidence your workflow needs.
A presence workflow can begin with detection and positioning. A verification workflow additionally needs authorised reference samples for the intended signer. Decide where references come from, how a detected region is associated with the expected field and which validations should run.
Define the boundary between beta processing and your application. Your system may own document intake, expected signer roles and final review decisions. Agree supported operations, execution timing and result handling against the current signature contract before implementing.
CONCEPTUAL DATA MAP
Keep the document, region, reference and decision connected.
These are categories to discuss, not response keys or a sample API payload. Confirm which information the beta returns and which your application maintains.
| Category | Useful information to agree | Purpose |
|---|---|---|
| Source | Document identity, page identity and relevant image dimensions. | Trace a region to the correct source. |
| Region | Candidate identity, position and any available crop representation. | Highlight and inspect the same writing. |
| Reference | Intended signer association, authorised sample provenance and set version. | Explain what the candidate was compared with. |
| Comparison | Available comparison evidence and its interpretation. | Keep reference comparison separate from detection confidence. |
| Validation | Agreed checks, their outcomes and unresolved reasons. | Support the required document action. |
| Review | Decision owner, supporting evidence and the recorded reason. | Connect processing evidence with the operational decision. |
POSITIONING CONTRACT
Agree coordinates before drawing the first overlay.
The position must describe the image your reviewer sees. A resized preview, rotated page or extracted crop can have a different coordinate frame from the source. Establish the mapping rather than applying one set of numbers to every rendering.
Units and shape
Confirm pixels or normalised units, coordinate origin and the region representation. Do not assume a particular bounding-box convention.
Crop and display mapping
Agree how any crop, scaling, rotation or deskew relates back to the full page, including partial or overlapping candidates.
RESULT HANDLING
Give incomplete evidence its own next step.
Distinguish a completed check with no detected candidate from an unusable image, an unavailable reference or a processing failure. These conditions need different handling. A missing reference is not a low comparison score, and a failed request is not a document decision.
Agree the actual outcome vocabulary, review ownership, timeouts, retry behaviour and duplicate-submission handling. For asynchronous processing, establish how your system obtains completion and associates it with the original document. Do not assume a webhook, idempotency mechanism or automatic approval path without confirming the contract.
BEFORE IMPLEMENTATION
Resolve inputs, references and data handling together.
Input scope
Confirm accepted file types, multi-page handling, image limits and whether full-page or crop inputs apply to each operation. Match these to your capture process.
Reference ownership
Agree who authorises samples, associates them with the intended signer, updates the set and retires old versions. Confirm how references are supplied for comparison.
Deployment and access
Discuss beta hosting options, authentication, permitted users, image/reference storage, retention and review access. Confirm the arrangements for this signature scope.
Acceptance
Use labelled document cases to test the complete integration, including unresolved outcomes and reviewer evidence, before setting operational acceptance criteria.
QUESTIONS & ANSWERS
Integration: practical questions.
Where do we obtain the current signature API contract?
Request it during the beta integration discussion. Confirm operations, accepted inputs, output structures, authentication and result handling for your scope. The conceptual data map on this page is not an executable endpoint specification.
Can we integrate only detection and positioning?
Detection and positioning support a presence and location workflow without authorised reference samples. Confirm the requested operations against the beta contract. If you add verification, agree how relevant references are supplied and how comparison evidence is handled.
Can the beta process our PDFs, image files or page crops?
Confirm accepted formats, page limits and crop handling against the current beta contract. Bring your capture and rendering requirements to the evaluation; general scanned-document scope does not establish support for every file format or input variation.
Can signature images and references stay on our infrastructure?
Discuss that requirement during evaluation. ChequeDB has an on-premise processing offering, but the signature beta's deployment scope, storage locations, access and retention arrangements need to be agreed explicitly.
CHEQUEDB SIGNATURES · BETA
Start with your documents.
Define the checks that matter.
Discuss your document types, signature references and validation workflow with the ChequeDB team.