Digital Signature
Nafath-authenticated signing, or a single-call lite signature.
In production, this replaces: wet-ink signatures, courier round-trips, and unverified scanned documents.
- Authenticate (current step)
- Nafath code
- Verified
- Signed
Step 1 — Authenticate the signer
Digital Signature is a Premium product: no accounts link, no customer consent journey. Smart Signature verifies the signatory through Nafath before it will sign, and nothing is sent until you press the button.
Request
Smart Signature identifies the signatory by ID rather than taking a full KYC block. Three calls run in order, and the same POINumber ties all of them to the person Nafath verified.
- 1AuthenticateSigner — returns the Nafath code the signatory has to confirm
- 2CheckStatus — reports whether they have confirmed it yet
- 3SignDocuments — signs the PDF once they are authenticated
AssuranceLevel is the one optional query parameter — Medium, the default, or High. The reference publishes a single response and its own call omits the parameter, so this omits it too.
POST /neotek/neotek-sandbox/digital-signature-smart/v1/authenticate-signer/1234567890
No body, and no content-type: that header is required on SignDocuments only, the one call that carries one.
No requests yet
Start a demo flow — each simulated API call appears here as it fires.
Step 2 · Read the reference
Digital Signature documentation
Endpoints, auth, payloads, and error handling for production.
Open the docsStep 3 · Build for real
Start your first sandbox call
Create a sandbox app, copy your client credentials, and call Digital Signature with real bank data.
Start your first sandbox call