Development of a Telegram bot for signing petitions via Diia.Signature

A Telegram bot is needed for automating the signing of petitions using Diia.Signature. The goal is to create a convenient tool that allows users to verify their identity through Diia, sign petitions, and store signature data in a database and archive. The project already has a detailed technical specification, a testing environment, and documentation from Diia — everything will be provided to the contractor. The previous attempt at implementation was unsuccessful due to missed deadlines, so I am looking for a responsible specialist who can complete the work on time.  

Technical Specification: Automation of Petition Signing with Diia.Signature

1. Project Goal

Create a solution where the user can verify their identity through Diia and sign a petition (or appeal) using Diia.Signature, and the confirmation of the signature must be stored in a separate archive and in the database.

2. Business Process Description

1. Identity Verification:
   • The user receives a link/button to verify their identity through Diia.
   • After successful authorization, we receive the user's data (full name, date of birth, address, etc.).
2. Signing the Petition:
   • The user sees available petitions/appeals.
   • Selects one of them and clicks “Sign”.
   • The generated hash of the petition is sent to the Diia server to create a signing request.
   • The user receives a link (deeplink) from Diia, which they follow to the Diia application to sign the petition.
3. Saving Results:
   • Diia sends the signed hash of the document to the endpoint specified by us.
   • The data is stored in the database (list of signatories), and files/signatures are stored in the archive.
   • The user is sent a message that the petition has been successfully signed.

3. Required Functionality

1. Identity Verification through Diia:
   • Sending a request for user verification.
   • Receiving results (name, date of birth, and other required data).
2. Generating and Sending a Signing Request:
   • Forming the hash of the petition according to GOST 34.311 or another algorithm supported by Diia (DSTU / ECDSA).
   • Creating an offer and receiving a deeplink for signing.
3. Receiving the Signed Hash:
   • Endpoint for receiving signed data from Diia.
   • Storing the signature (hash) and user data.
4. Feedback to the User:
   • Notification of successful signing.
5. Data Archiving:
   • The ability to store signed data (hash) and other service information in a separate archive (e.g., ZIP).
   • Linking the signature to a specific petition.

4. Legal and Technical Aspects

• Using HTTPS for all external and internal requests to ensure security.
• Using the official Diia API:
  • Obtaining a session token (acquirer_token).
  • Implementing the creation of branch, offer, and signing requests according to the documentation.
• User data (full name, date of birth, address) should be stored in the database, where they will be used to verify the status of the signatory.

5. Final Result

1. User:
   • Easily verifies their identity through Diia.
   • Signs a petition in a few clicks, receiving a deeplink and transitioning to the Diia application.
2. Service:
   • Has an endpoint that receives signed hashes from Diia and stores them along with user data.
   • Provides an archive of signatures for each petition (documents + hashes).
3. Administration:
   • A database of signatories for each petition.
   • The ability to download the signature archive at any time.
4. Security and Transparency:
   • Verified identities through Diia.
   • Legally significant electronic signature.

6. Comments and Wishes

• The freelancer can choose any convenient tools (frameworks, implementation methods) — the main thing is that the results meet the requirements.
• The application must be a Telegram bot, where the user can conveniently familiarize themselves with and sign the petition.

Testing in the Diia sandbox environment.

7. Provided Materials

• Technical specification (described above).  
• Test tokens: (will be provided to the contractor after agreeing on all cooperation details)
• Documentation from Diia: link to Google Docs, GitHub SDK.

8. Requirements for the Contractor

• Experience with Telegram Bot API and integrations through API (preferably with Diia.Signature).  
• Knowledge of Python, Node.js, or another suitable language for implementation.  
• Ability to work with documentation and testing environment.  
• Strict adherence to deadlines and regular progress reports.