In the ever-evolving digital world, e-signing services have become integral to fintech and other industries. iCreditWorks, a forward-thinking startup, decided to develop an in-house e-signing service, moving away from third-party dependencies. This case study explores their journey, highlighting the use of Java, Spring, cloud storage, and MySQL in building their custom solution.
Before delving into the technical development, it’s crucial to understand the legal framework. The E-Sign Act legitimizes electronic records and signatures, ensuring their legal standing. Compliance with this act was a primary consideration in developing the in-house e-signing service.
{{baseUrl}}/api/e-sign/v1/document/{contentType}
{
"docCode": "GEN-MPN-01",
"contextId": "LN-1000109-01",
"localePreference": "en-US",
"fields": {
"CurrentDate": "09/03/2023",
...
}
}
{{baseUrl}}/api/e-sign/v1/document/signature/{{eSignDocumentUUID}}/html
// Pre-signed URL generation for AWS S3
Calendar calendar = Calendar.getInstance();
calendar.setTime(new Date());
calendar.add(Calendar.MINUTE, 5); // URL valid for 5 minutes
String presignedUrl = this.awsS3Client.generatePresignedUrl(
s3BucketName, documentPath, calendar.getTime(), HttpMethod.GET
).toString();
Ensuring document integrity and confidentiality is paramount. Key security measures include:
iCreditWorks’ transition to an in-house e-signing solution resulted in significant cost savings, enhanced brand consistency, and operational control. The shift represents a strategic move towards digital autonomy and innovation.
iCreditWorks shares its e-signing microservice’s codebase on GitHub, encouraging collaboration and improvement within the tech community. This initiative reflects their commitment to empowering other businesses to leverage their pioneering work.
Dive deeper into iCreditWorks’ inspiring journey of building their e-signing service on our blog. Discover the full story, complete with technical details, code examples, and insights into the strategic advantages of in-house development.