Skip to content
PALBON-SuitesComplete ERP Solution
PALBONEkycPlatform services · Identity verification & e-signature

Verify who they are and sign the document, from the record itself

PALBONEkyc connects the suite to Digio. From a document you can ask a customer to complete an Aadhaar and PAN check through DigiLocker, or to sign the document with Aadhaar eSign, and the outcome comes back to your records on its own.

Capabilities

What is inside PALBONEkyc

eSignature requests

Send a document out for signing without leaving the system. The PDF is produced from the document's print format and uploaded for you.

  • Aadhaar-based signing for each signer
  • Signers read from the email or mobile fields you choose
  • Signers taken from the document or from a table on it
  • Optional sign link and access token with the request

eKYC requests

Ask a person to verify their identity through DigiLocker, using a template that covers Aadhaar and PAN.

  • One request per recipient found on the document
  • DigiLocker Aadhaar and PAN template
  • Customer name looked up from the customer record
  • Reference to the document that triggered the request

Request tracking

A log shows each request, what the provider replied, and where it stands now.

  • Digio request log with the linked document
  • Status from Pending through KYC Approved, KYC Rejected or Signed
  • Expired, terminated and failed requests recorded as such
  • Time the last update arrived and the full payload kept

Provider callbacks

Digio reports progress to the system as it happens, and the log updates itself without anyone checking a dashboard.

  • Webhook endpoint for eKYC and eSign events
  • Each call verified with an HMAC-SHA256 checksum
  • All callbacks refused until a webhook secret is set
  • Unrecognised events written to the error log

Workflow integration

Make a signature or a verification a step in an approval flow, so it starts when the document reaches the right stage.

  • Workflow tasks: Send eKYC Request and Make eSignature Request
  • Workflow states eKYC Requested and eSignature Requested
  • Set up the tasks once at installation
  • Choose which document types may be sent for signing

Connection settings

Digio credentials sit in one settings page, with a sandbox to test against before you go live.

  • Separate production and sandbox addresses and credentials
  • Credentials and webhook secret stored as protected passwords
  • Request expiry in days and customer notification switch
  • Settings open to System Managers only

Outcomes

What changes for your team

No document sent as an email attachment

The request goes from the record, and the status comes back to a log linked to that record.

Verification as a step, not a side task

Tied to a workflow, an identity check or a signature starts when the document reaches that stage.

A trail you can show

The log keeps who was asked, when, and exactly what the provider reported.

Connected

Better with the rest of the suite

PALBONEkyc shares its data with the other products, so nothing is entered twice.

FAQ

Questions about PALBONEkyc

Which service does it use?

Digio. You enter your own Digio credentials, with separate sandbox and production sets.

Does it store Aadhaar or PAN numbers?

The app has no Aadhaar or PAN field of its own. The log keeps the provider's reply for each request, and access to it is limited to System Managers.

Can we try it before going live?

Yes. Turn on the sandbox, enter the sandbox address and credentials, and requests go there instead of production.

See PALBONEkyc on your own data

Tell us how you work today. We will walk you through the products that fit, on your data and your terms.