Feel free to reach techsupport@surepass.io for any technical support or guidance.
Authorization
header as Bearer TOKEN
.https://sandbox.surepass.io
https://kyc-api.surepass.io
Header | Required | Description |
---|---|---|
Authorization | Yes | Bearer token authentication using JWT |
Content-Type | Yes | application/json |
Parameter | Type | Required | Description |
---|---|---|---|
first_party | String | Yes | Name of the first party on the stamp paper |
second_party | String | Yes | Name of the second party (use generic terms like "Borrower") |
state | String (Enum) | Yes | Two-letter state code where the stamp will be issued |
article_id | Integer | Yes | Specific article ID for the stamp type |
amount | Integer | Yes | The stamp duty amount in INR |
consideration_amount | Integer | Yes | The consideration amount for the agreement |
quantity | Integer | Yes | Number of identical stamps to order |
description | String | Yes | Brief description of the stamp purpose |
state
parameter must be one of the following two-letter codes: :::warning Sandbox Limitations
In the sandbox environment, only the following values are supported:
- **State:** `DL` (Delhi)
- **Article ID:** `22128`
:::
#### Second Party Naming Guidelines
Always use a generic name for the second party to allow the stamp paper to be reused for other e-sign processes.
**Acceptable generic names:**
- "Borrower" ✅
- "Second Party" ✅
- "Lessee" ✅
**Names to avoid:**
- "Deepak Raj" ❌
- "Surjal Pvt Ltd" ❌
- "Mr. John Smith" ❌
#### Example Request
```json
{
"first_party": "ABC Pvt Ltd",
"second_party": "Borrower",
"state": "DL",
"article_id": 22128,
"amount": 40,
"consideration_amount": 1,
"description": "Estamp"
}
Parameter | Type | Description |
---|---|---|
data | Object | Contains the Estamp order details |
data.client_id | String | Unique identifier for the client |
data.stamp_id | String | Unique identifier for the stamp |
data.created_at | String | Timestamp of order creation (ISO format) |
data.amount | Integer | Monetary value of the stamp in INR |
data.consideration_amount | Integer | Value of the transaction/agreement |
data.first_party | String | Name of the first party |
data.second_party | String | Name of the second party |
data.state | String | Two-letter state code |
data.status | String Enum | Current status of the order |
data.on_hold | Boolean | Indicates if the order is on hold |
data.link | String or null | Link to access the stamp (if available) |
status_code | Integer | HTTP status code |
success | Boolean | Indicates if the request was successful |
message | String | Response message |
message_code | String | Code representing the message |
status
field can have the following values:pending
: Order is being processedavailable
: Estamp is ready for useon_hold
: Order is temporarily on holdused
: Estamp has been utilized{
"data": {
"client_id": "stamp_v2_jxXNHjntEoeaMHiiVcUi",
"stamp_id": "stamp_v2_jxXNHjntEoeaMHiiVcUi",
"created_at": "2024-12-24T13:55:40.168229",
"amount": 40,
"consideration_amount": 1,
"first_party": "ABC Pvt Ltd",
"second_party": "Borrower",
"state": "DL",
"status": "pending",
"on_hold": false,
"link": null
},
"status_code": 200,
"success": true,
"message": "Success",
"message_code": "success"
}
{
"status_code": 401,
"success": false,
"message": "Invalid or expired token",
"message_code": "unauthorized"
}
curl --location --request POST 'https://kyc-api.surepass.app/api/v1/stamper-v2/order-stamp' \
--header 'Content-Type: application/json' \
--data-raw '{
"first_party": "ABC Pvt Ltd",
"second_party": "Borrower",
"state": "DL",
"article_id": 22128,
"amount": 40,
"consideration_amount": 1,
"description": "Estamp"
}'
{
"data": {
"client_id": "stamp_v2_jxXNHjntEoeaMHiiVcUi",
"stamp_id": "stamp_v2_jxXNHjntEoeaMHiiVcUi",
"created_at": "2024-12-24T13:55:40.168229",
"amount": 40,
"consideration_amount": 1,
"first_party": "ABC Pvt Ltd",
"second_party": "Borrower",
"state": "DL",
"status": "pending",
"on_hold": false,
"link": null
},
"status_code": 200,
"success": true,
"message": "Success",
"message_code": "success"
}