Submit OTP for Maharashtra Challan Verification

Endpoint Overview

POST /api/v1/maharashtra-challan/submit-otp

Description

The Submit OTP API completes the two-step authentication process for retrieving traffic challan (fine) information for vehicles registered in Maharashtra, India. After initiating an OTP request, this endpoint validates the OTP code and returns comprehensive challan details including violation information, amounts due, payment status, and offense specifics.

This API provides instant access to official Maharashtra traffic police records, enabling businesses and individuals to verify outstanding traffic fines, check payment status, and retrieve detailed violation information for any vehicle registered in the state.

Key Benefits

Instant Verification: Real-time access to official Maharashtra traffic challan records with OTP-based security

Comprehensive Data: Retrieve complete challan history including offense details, amounts, dates, and payment status

Secure Authentication: Two-factor OTP verification ensures data privacy and authorized access

Compliance Ready: Access authentic government records for insurance claims, vehicle transfers, and compliance checks

Use Cases

Insurance & Finance

Fleet Management

Automotive Services

Vehicle Insurance Processing: Verify outstanding challans before policy issuance or renewal

Auto Loan Verification: Check traffic violation history during vehicle financing applications

Insurance Claim Validation: Confirm challan details when processing accident-related claims

Risk Assessment: Evaluate driver behavior patterns for premium calculations

Technical Implementation

Authentication

All API requests require authentication using a JWT Bearer token. Authentication follows these steps:

Obtain API Credentials: Register with Surepass to receive your API key.

Generate JWT Token: Use your API key to generate a JWT token.

Include in Requests: Add the token to the Authorization header as Bearer TOKEN.

Different authentication tokens are used for sandbox and production environments:

Sandbox: https://sandbox.surepass.app

Production: https://kyc-api.surepass.app

Request Parameters

Request Headers

Header	Required	Description
Authorization	Yes	Bearer token for API authentication. Format: `Bearer YOUR_JWT_TOKEN`
Content-Type	Yes	Must be set to `application/json`

Request Body

Parameter	Type	Required	Description
client_id	string	Yes	Unique client identifier received from the initial challan verification request. This links the OTP to the specific challan query session.
otp	string	Yes	6-digit OTP code sent to the registered mobile number or generated by the system. Must be submitted within the validity period (typically 5-10 minutes).

Example Request

{
    "client_id": "maharashtra_challan_afqOprZOdrcDazuUndHP",
    "otp": "123456"
}

Process Response

Response Parameters

Parameter	Type	Description
data	object	Container object holding all challan information
data.client_id	string	Echo of the client_id from the request for reference tracking
data.rc_number	string	Vehicle registration number (RC number) for which challans were retrieved
data.chassis_number	string	Chassis number of the vehicle
data.challan_details	array	Array of challan objects containing detailed information about each traffic violation
challan_details[].challan_number	string	Unique challan identification number issued by traffic authorities
challan_details[].amount	string	Total payable amount for the challan (formatted with comma separators)
challan_details[].rc_number	string	Vehicle registration number associated with this specific challan
challan_details[].towing_amount	string	Additional charges for vehicle towing (empty if not applicable)
challan_details[].challan_date	string	Date when the challan was issued (YYYY-MM-DD format)
challan_details[].challan_date_time	string	Complete timestamp of challan issuance (ISO 8601 format)
challan_details[].accused_name	string	Name of the person accused of the traffic violation (may be empty)
challan_details[].license_number	string	Driving license number of the accused (if available)
challan_details[].status	string	Payment status of the challan: "Paid" or "Unpaid"
challan_details[].offense_details	array	Array of offense objects detailing the specific violations
offense_details[].section	string	Motor Vehicle Act (MVA) section under which the violation falls
offense_details[].description	string	Human-readable description of the traffic offense
offense_details[].fine	string	Fine amount specified for this particular offense
status_code	integer	HTTP status code (200 for success)
success	boolean	Indicates whether the API call was successful (true/false)
message	string	Human-readable message describing the result
message_code	string	Machine-readable code for the message status

Example Successful Response

{
    "data": {
        "client_id": "maharashtra_challan_afqOprZOdrcDazuUndHP",
        "rc_number": "MH01TE1234",
        "chassis_number": "ME1KC111DH0123272",
        "challan_details": [
            {
                "challan_number": "MUMCM19001244123",
                "amount": "1,200",
                "rc_number": "MH01TE1234",
                "towing_amount": "",
                "challan_date": "2019-01-01",
                "challan_date_time": "2019-01-01T16:53:00",
                "accused_name": "MOHAMMAD SAJJAD IDRISI",
                "license_number": "",
                "status": "Unpaid",
                "offense_details": [
                    {
                        "section": "Sec 112/183(1) MVA (LMV).",
                        "description": "Speed violating by driver (LMV)",
                        "fine": "2000"
                    }
                ]
            },
            {
                "challan_number": "MUMCM19001244134",
                "amount": "200",
                "rc_number": "MH01TE1234",
                "towing_amount": "",
                "challan_date": "2018-01-01",
                "challan_date_time": "2018-01-01T15:10:00",
                "accused_name": "",
                "license_number": "",
                "status": "Unpaid",
                "offense_details": [
                    {
                        "section": "Sec 112/183(1) MVA (LMV).",
                        "description": "Speed violating by driver (LMV)",
                        "fine": "2000"
                    }
                ]
            },
            {
                "challan_number": "MUMCM19001244136",
                "amount": "200",
                "rc_number": "MH01TE1234",
                "towing_amount": "",
                "challan_date": "2018-02-02",
                "challan_date_time": "2018-02-02T14:50:00",
                "accused_name": "",
                "license_number": "MH0220080031345",
                "status": "Paid",
                "offense_details": [
                    {
                        "section": "Sec 112/183(1) MVA (LMV).",
                        "description": "Speed violating by driver (LMV)",
                        "fine": "2000"
                    }
                ]
            }
        ]
    },
    "status_code": 200,
    "success": true,
    "message": "Success",
    "message_code": "success"
}

Possible Error Responses

Invalid Client ID

Unauthorized

{
    "status_code": 400,
    "success": false,
    "message": "Invalid client_id",
    "message_code": "invalid_client_id"
}

The client_id provided doesn't exist or is malformed. Ensure you're using the client_id received from the initial challan request.

Integration Best Practices

Security Recommendations

Secure Token Storage: Store JWT tokens securely using environment variables or secure vaults; never hardcode in source code

OTP Handling: Implement rate limiting on OTP submission attempts to prevent brute force attacks (max 3-5 attempts)

HTTPS Only: Always use HTTPS for API calls to ensure encrypted data transmission

Client ID Validation: Validate client_id format and existence before OTP submission to reduce unnecessary API calls

Timeout Implementation: Set reasonable timeout values (30-60 seconds) for API requests to handle network issues gracefully

Sensitive Data Protection: Never log OTP values or complete responses containing personal information in production systems

User Experience Guidelines

OTP Timer Display: Show a countdown timer for OTP validity to encourage timely submission

Resend OTP Option: Provide a clear option to resend OTP if it expires or isn't received

Error Messaging: Display user-friendly error messages that guide users on corrective actions

Loading States: Show loading indicators during API calls to inform users the request is processing

Challan Summary: Present challan data in an organized, easy-to-read format with filtering options for paid/unpaid status

Payment Status Highlighting: Use visual indicators (colors, icons) to differentiate between paid and unpaid challans

Mobile Optimization: Ensure OTP input is optimized for mobile devices with appropriate keyboard type and auto-focus

Code Samples

cURL

Python

Node.js

Related APIs

Maharashtra Challan - Generate OTP: Initial API endpoint to generate OTP for a specific vehicle's RC number or chassis number before using this submit OTP endpoint

Maharashtra Challan - Payment Status: Verify real-time payment status updates for specific challan numbers

PAN Verification API: Cross-verify vehicle owner details with PAN information for comprehensive KYC

Driving License Verification: Validate driving license details associated with challan records

Vehicle RC Verification: Retrieve comprehensive vehicle registration details including owner information

Compliance and Legal Considerations

Data Privacy: All challan data is sourced from official Maharashtra Traffic Police records. Ensure compliance with data protection regulations when storing or processing personal information.

Purpose Limitation: This API should only be used for legitimate purposes such as verification, compliance checks, or authorized inquiries. Misuse of personal data is subject to legal action.

Consent Requirements: When using this API on behalf of individuals, ensure proper consent is obtained for accessing their vehicle's challan records.

Data Retention: Implement appropriate data retention policies. Do not store sensitive information longer than necessary for your business purpose.

Motor Vehicles Act Compliance: Challan information is governed by the Motor Vehicles Act, 1988. Users must comply with all applicable provisions.

Record Accuracy: While data is sourced from official records, always advise users to verify critical information directly with Maharashtra Traffic Police for legal proceedings.

Geographic Scope: This API is specific to Maharashtra state vehicles. For pan-India challan verification, additional state-specific APIs may be required.

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

curl --location --request POST 'https://kyc-api.surepass.app/api/v1/maharashtra-challan/submit-otp' \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data-raw '{ "client_id": "maharashtra_challan_afqOprZOdrcDazuUndHP", "otp": "123456" }'

{ "data": { "client_id": "maharashtra_challan_afqOprZOdrcDazuUndHP", "rc_number": "MH01TE1234", "chassis_number": "ME1KC111DH0123272", "challan_details": [ { "challan_number": "MUMCM19001244123", "amount": "1,200", "rc_number": "MH01TE1234", "towing_amount": "", "challan_date": "2019-01-01", "challan_date_time": "2019-01-01T16:53:00", "accused_name": "MOHAMMAD SAJJAD IDRISI", "license_number": "", "status": "Unpaid", "offense_details": [ { "section": "Sec 112/183(1) MVA (LMV).", "description": "Speed violating by driver (LMV)", "fine": "2000" } ] }, { "challan_number": "MUMCM19001244134", "amount": "200", "rc_number": "MH01TE1234", "towing_amount": "", "challan_date": "2018-01-01", "challan_date_time": "2018-01-01T15:10:00", "accused_name": "", "license_number": "", "status": "Unpaid", "offense_details": [ { "section": "Sec 112/183(1) MVA (LMV).", "description": "Speed violating by driver (LMV)", "fine": "2000" } ] }, { "challan_number": "MUMCM19001244136", "amount": "200", "rc_number": "MH01TE1234", "towing_amount": "", "challan_date": "2018-02-02", "challan_date_time": "2018-02-02T14:50:00", "accused_name": "", "license_number": "MH0220080031345", "status": "Paid", "offense_details": [ { "section": "Sec 112/183(1) MVA (LMV).", "description": "Speed violating by driver (LMV)", "fine": "2000" } ] } ] }, "status_code": 200, "success": true, "message": "Success", "message_code": "success" }

Submit OTP

Submit OTP for Maharashtra Challan Verification#

Description#

Use Cases#

Technical Implementation#

Request Headers#

Request Body#

Example Request#

Response Parameters#

Example Successful Response#

Possible Error Responses#

Integration Best Practices#

Code Samples#

Request

Responses