1. Overview

The Surepass connector provides comprehensive access to identity verification and e-signature services, enabling Aadhaar validation, bank account verification, and electronic document signing workflows through Leena AI Agents.

Surepass is an identity verification and digital signature platform that provides KYC (Know Your Customer) services and e-signature capabilities. The Surepass connector allows Leena AI to automate identity verification workflows, validate financial information, and facilitate electronic document signing seamlessly.

API Details

Leena AI integrates with Surepass via REST APIs.

Documentation link: https://surepass.io

2. Setup

The Surepass connector uses Bearer Token authentication.

A. Prerequisites

Before setting up the Surepass connector, ensure you have:

• A Surepass account with appropriate API access
• Valid API token from Surepass dashboard
• Access to your Leena AI workspace with connector management permissions
• Basic understanding of KYC (Know Your Customer) and e-signature concepts
• Compliance with applicable Indian data protection and privacy regulations

B. Get credentials

Here is how to obtain API credentials from Surepass:

1. Access Surepass Dashboard:
   1. Log in to your Surepass account at https://surepass.io
   2. Navigate to the API Settings or Developer section
   3. Locate your API credentials section
2. Generate or Copy API Token:
   1. If you don't have an API token, generate a new one
   2. Copy the API token securely
   3. Store it in a secure location for reference

C. Add connection

Here is how to add a connection on Leena AI:

1. Log in to your Leena AI workspace

2. Navigate to Settings > Integrations

3. Click on Add Connector

4. Search for "Surepass" and select it from the list

5. Configure the connector:

   1. API Token: Your Surepass API token (e.g., sk_live_xxxxxxxxxxxxx)
   2. Authentication Type: Bearer Token (auto-selected)
   
   

6. Required Permissions and Compliance:

Regulatory Compliance:

• Ensure compliance with Aadhaar Act and UIDAI guidelines
• Follow RBI guidelines for bank account verification
• Adhere to IT Act provisions for electronic signatures
• Maintain data privacy as per Indian data protection laws

Required Permissions:

• E-sign service activation
• Aadhaar verification service access
• Bank verification service access
• Document storage and retrieval permissions

7. Test the connection and save the configuration

3. Actions

The following actions are supported for the Surepass connector:

A. Aadhaar Validation

Validates an Aadhaar number for basic identity verification. The Agent can leverage the skill (workflow) to verify Aadhaar numbers issued by the Government of India. Here are some common use cases:

• Identity Verification: Verify user identity during onboarding
• KYC Compliance: Fulfill Know Your Customer requirements
• Age Verification: Confirm age range of users
• Basic Validation: Check if Aadhaar number is valid

Input Parameters

Here are the input parameters required to set up this action:

Mandatory

Here is a sample JSON input:

{
  "Number": "123456789012"
}

Response

The action returns validation results including:

• Age range of the Aadhaar holder
• Gender
• State of residence
• Mobile number availability status
• Last 4 digits of Aadhaar (masked)

B. Bank Details Verification

Validates bank account with penny drop verification. The Agent can leverage the skill (workflow) to verify bank account details and confirm account existence. Here are some common use cases:

• Account Verification: Verify bank account before processing payments
• KYC Validation: Validate financial information for compliance
• Penny Drop Test: Confirm account is active and accessible
• Account Holder Verification: Verify account holder name

Input Parameters

Here are the input parameters required to set up this action:

Mandatory

Optional

Here is a sample JSON input:

{
  "Bank account number": "1234567890",
  "IFSC": "SBIN0001234",
  "Include IFSC details": true
}

Response

The action returns verification results including:

• Account holder name
• Account existence status
• Bank details (if ifsc_details=true)
• IMPS reference number
• Transaction status

C. Initialize E-Sign

Creates a new electronic signature request with configuration options. The Agent can leverage the skill (workflow) to initiate electronic signature workflows for documents. Here are some common use cases:

• Document Signing: Enable electronic signatures on PDFs
• Digital Onboarding: Facilitate paperless onboarding processes
• Agreement Execution: Execute contracts and agreements digitally
• Compliance Documentation: Obtain legally valid electronic signatures

Input Parameters

Here are the input parameters required to set up this action:

Mandatory

Optional

Here is a sample JSON input:

{
  "Is PDF pre-uploaded": false,
  "Signing reason": "Part of the onboarding process",
  "Signature Positions": {
    "Page number": 2,
    "X coordinate": 10,
    "Y coordinate": 45
  },
  "Full Name": "John Doe",
  "Mobile Number": "9876543210",
  "Email": "[email protected]"
}

Response

Upon successful initialization, the action returns:

• Client ID for the signature request
• E-signature session details
• Document status

D. Get Signed Document

Retrieves the signed PDF document. The Agent can leverage the skill (workflow) to download or access electronically signed documents. Here are some common use cases:

• Document Retrieval: Download signed documents
• Archive Management: Store signed documents in document management systems
• Audit Trail: Retrieve documents for compliance and audit purposes
• Document Distribution: Share signed documents with relevant parties

Input Parameters

Here are the input parameters required to set up this action:

Mandatory

Here is a sample JSON input:

{
  "Client ID": "1001234"
}

Response

The action returns:

• Download URL for signed document
• Document metadata
• Signature details