Developer Terms of Service

These StampMitra Developer Terms of Service constitute the governing contractual terms applicable to access to and use of the StampMitra Developer Platform, APIs, Software Development Kits, developer tools, documentation, Sandbox environment, Production environment, API credentials, and related developer services made available by BANI GLOBAL INDUSTRIES LLP (“StampMitra”, “Company”, “we”, “us” or “our”).

By creating a Developer Account, accepting these Terms electronically, generating or using API credentials, accessing the Sandbox or Production environment, submitting a Production access request, or otherwise accessing or using any portion of the Developer Platform, the Developer (“Developer”, “you” or “your”) agrees to be legally bound by these Terms and all policies incorporated into them.

These Terms are intended to operate as an electronically accepted contractual arrangement. Electronic acceptance, account activity, API-key use, system records and other electronic actions may constitute evidence of acceptance and use, subject to applicable law.

The StampMitra Developer Platform may be used by individual developers, freelancers, consultants, students, technical founders, independent developers, agencies, businesses, companies, LLPs, partnerships, institutions and other lawful organizations, subject to applicable eligibility and verification requirements.

Nothing in these Terms requires an individual developer to represent that they are a company or organization where they are lawfully operating as an individual.

1.1 These Terms are entered into between:

• BANI GLOBAL INDUSTRIES LLP, operating the StampMitra platform and related developer services; and
• the individual or legal entity registering for or using the StampMitra Developer Platform.

1.2 Where the Developer is an organization, the individual accepting these Terms represents and warrants that they have sufficient authority to bind that organization.

1.3 Where the Developer is an individual, these Terms apply to that individual in their personal capacity and, where applicable, to lawful professional or freelance activities conducted through the Developer Account.

1.4 These Terms govern the Developer's access to the Developer Platform and do not by themselves constitute a guarantee that every API, product, service, feature, geographic region, transaction type or underlying service will remain continuously available.

2.1 StampMitra provides a technology platform through which approved Developers may integrate specified StampMitra APIs and services into their own software, applications, websites, workflows and business processes.

2.2 Depending on eligibility, product availability and Production approval, the Developer Platform may provide access to services relating to:

• identity and information verification;
• business and document-related services;
• e-Stamp-related services;
• e-Sign-related services;
• application and transaction workflows;
• status and verification information;
• document processing;
• other APIs expressly made available by StampMitra.

2.3 The precise functionality available to a Developer is determined by:

• the Developer Account;
• workspace;
• project;
• environment;
• API subscription or entitlement;
• approved API scopes;
• applicable commercial terms;
• geographic availability;
• applicable law; and
• StampMitra's technical and risk controls.

3.1 These Terms may be accepted electronically through:

• checkbox acceptance;
• button-based acceptance;
• account registration;
• API activation;
• Production application;
• electronic confirmation;
• use of API credentials; or
• other electronic mechanisms implemented by StampMitra.

3.2 The Developer acknowledges that electronic acceptance may create a legally binding contractual relationship.

3.3 The Information Technology Act, 2000 recognizes electronic records and provides that a contract is not unenforceable solely because its formation occurred through electronic means.

3.4 StampMitra may retain records relating to acceptance, including:

• timestamp;
• account identifier;
• IP address;
• browser/device information;
• version of Terms;
• acceptance event;
• account information;
• authentication records; and
• relevant system logs.

3.5 Such records may be retained as business, security, compliance or evidentiary records subject to applicable law.

For these Terms:

• “API” means an application programming interface made available by StampMitra.
• “API Key” means a credential or authentication mechanism used to authenticate an API request.
• “Developer Account” means the account created by a Developer on the Developer Platform.
• “Developer Platform” means the StampMitra developer portal, documentation, dashboards, API-management functionality and associated systems.
• “Documentation” means technical documentation, API references, integration instructions, SDK documentation, examples and related materials.
• “Production” means the live environment approved for real or operational API transactions.
• “Sandbox” means the testing environment made available by StampMitra.
• “Project” means an application, integration or technical project configured within a Developer workspace.
• “Workspace” means an administrative environment containing Projects, users, credentials, configurations and related resources.
• “End User” means a person whose information, transaction, application or request is submitted to or processed through a Developer's integration.
• “Underlying Service Provider” means an external service provider, authorized data source, technology provider, regulated entity, infrastructure provider, service network, government-authorized source or other third party used by StampMitra in connection with providing or supporting a service.
• “Service” means any API, verification, document, e-Stamp, e-Sign, data, processing or related service made available by StampMitra.
• “Confidential Information” means non-public information disclosed by one party to the other that reasonably should be understood to be confidential.

5.1 The Developer must provide accurate and lawful information during registration.

5.2 An individual Developer must be legally capable of entering into a binding agreement under applicable law.

5.3 An organization must ensure that its representative has authority to accept these Terms.

5.4 StampMitra may impose additional eligibility conditions for specific Production APIs.

5.5 Certain APIs may require:

• identity verification;
• business verification;
• use-case verification;
• domain verification;
• additional documentation;
• regulatory information;
• financial information;
• organization information;
• technical-security review; or
• other compliance checks.

5.6 Sandbox access may be made available with substantially lower onboarding requirements than Production access.

6.1 StampMitra may support at least the following account classifications:

• (a) Individual Developer — An individual may register as an individual Developer without representing themselves as a company.
• (b) Organization — An organization may register as a company, LLP, partnership, institution or other lawful entity.

6.2 StampMitra may request additional information when an Organization seeks Production access.

6.3 An individual Developer working for clients remains responsible for ensuring that their use of StampMitra APIs is authorized by the relevant client.

6.4 Where a Developer processes data for clients, the Developer remains responsible for determining the appropriate contractual and data-protection relationship with those clients.

7.1 The Developer shall provide accurate, current and complete information.

7.2 The Developer shall promptly update material information that becomes inaccurate.

7.3 The Developer shall not:

• impersonate another person;
• use false identity information;
• create accounts for fraudulent purposes;
• misrepresent organizational authority;
• provide fabricated business information; or
• deliberately circumvent verification requirements.

7.4 StampMitra may suspend or restrict an account where information appears materially inaccurate, fraudulent or misleading.

8.1 StampMitra may verify Developer identity, contact information, organization details, domain ownership, use case, payment information or other relevant information.

8.2 Verification requirements may differ between:

• Sandbox;
• Production;
• individual accounts;
• organization accounts; and
• individual API products.

8.3 Submission of information does not guarantee approval.

8.4 StampMitra may request additional documentation where reasonably required for security, fraud prevention, regulatory compliance or service eligibility.

9.1 StampMitra may use OTP-based verification for:

• mobile verification;
• account authentication;
• account recovery;
• security-sensitive actions;
• credential management; or
• other account-protection purposes.

9.2 OTPs must not be disclosed to another person.

9.3 StampMitra will not ordinarily request a Developer to disclose an authentication OTP through an unsecured or unauthorized channel.

9.4 Developers are responsible for maintaining control over their registered mobile number and email address.

10.1 The Developer is responsible for protecting:

• passwords;
• API Keys;
• access tokens;
• OTPs;
• recovery mechanisms;
• team-member credentials;
• webhook secrets;
• private credentials; and
• other authentication information.

10.2 API Keys must be treated as confidential credentials.

10.3 Developers must not place secret Production API Keys in:

• public Git repositories;
• browser-side JavaScript;
• mobile application binaries where extraction is reasonably possible;
• publicly accessible source code;
• public documentation; or
• other insecure locations.

10.4 Where technically appropriate, API credentials should be stored using a secure secrets-management mechanism.

11.1 The Developer must immediately rotate or revoke credentials reasonably believed to have been compromised.

11.2 StampMitra may revoke or rotate credentials where it reasonably believes that:

• a credential has leaked;
• abnormal usage is occurring;
• unauthorized access is suspected;
• fraud is suspected;
• security controls have been bypassed; or
• continued use presents a material security risk.

12.1 StampMitra may provide Workspaces for organizational separation of Projects and access.

12.2 Workspace administrators may control:

• team membership;
• roles;
• permissions;
• Projects;
• API access;
• credentials;
• webhook configurations;
• IP allowlists; and
• other Workspace-level settings.

12.3 The Developer is responsible for ensuring that Workspace members receive only the permissions necessary for their functions.

13.1 A Project represents an application or technical integration.

13.2 StampMitra may associate each Project with separate:

• API Keys;
• environments;
• API scopes;
• usage limits;
• webhooks;
• IP restrictions;
• logs; and
• Production approvals.

13.3 Developers must not use one Project's credentials to improperly bypass controls applicable to another Project.

14.1 StampMitra may provide Sandbox access for development and testing.

14.2 Sandbox data, responses and simulations may not represent actual Production results.

14.3 Sandbox availability may differ from Production.

14.4 Developers must not assume that:

• Sandbox responses guarantee Production responses;
• Sandbox limits equal Production limits;
• simulated records represent real records; or
• Sandbox functionality will remain permanently unchanged.

14.5 StampMitra may reset, modify or discontinue Sandbox functionality where reasonably required.

15.1 Production access is subject to approval.

15.2 StampMitra may evaluate:

• Developer identity;
• business or professional purpose;
• intended use case;
• API requested;
• expected volume;
• technical implementation;
• security posture;
• compliance requirements;
• payment status;
• geographic considerations; and
• risk indicators.

15.3 Approval for one API does not automatically constitute approval for every other API.

15.4 Production access may be granted on an API-specific basis.

15.5 StampMitra may impose conditions on Production access, including:

• rate limits;
• transaction limits;
• IP allowlists;
• approved domains;
• webhook restrictions;
• usage categories;
• geographic restrictions;
• additional verification; or
• other reasonable controls.

16.1 StampMitra may provide separate credentials for Sandbox and Production.

16.2 Test credentials and live credentials are technically and contractually distinct.

16.3 Developers must not:

• publish Production credentials;
• share credentials with unauthorized persons;
• sell credentials;
• transfer credentials without authorization;
• use credentials to provide unauthorized API access to third parties; or
• attempt to derive secret credentials from publicly exposed application code.

16.4 StampMitra may revoke credentials without prior notice where necessary to protect security or prevent misuse.

17.1 StampMitra may implement API scopes or entitlements limiting what a Developer may access.

17.2 The Developer shall use each API only within its approved scope.

17.3 Attempting to access an endpoint outside the Developer's authorized scope constitutes a violation of these Terms.

18.1 StampMitra may apply rate limits at:

• account level;
• Workspace level;
• Project level;
• API level;
• IP level;
• credential level; or
• other technical levels.

18.2 Developers must implement appropriate retry, backoff and error-handling mechanisms.

18.3 Repeatedly attempting requests after rate-limit responses in a manner that materially increases system load may constitute abusive usage.

19.1 StampMitra Documentation is provided for authorized integration purposes.

19.2 Developers shall follow the current technical requirements published by StampMitra.

19.3 StampMitra may update Documentation to reflect:

• security requirements;
• technical changes;
• API version changes;
• regulatory requirements;
• operational changes; or
• service improvements.

20.1 Subject to these Terms, StampMitra grants the Developer a limited, non-exclusive, non-transferable, revocable right to access and use the APIs solely for the Developer's approved integration.

20.2 No ownership of StampMitra technology is transferred to the Developer.

20.3 The Developer receives no implied license beyond the rights expressly granted.

21.1 StampMitra and its licensors retain all rights, title and interest in:

• APIs;
• source code;
• software;
• Documentation;
• trademarks;
• logos;
• interfaces;
• databases;
• platform architecture;
• technical methodologies;
• designs;
• workflows; and
• other proprietary materials.

21.2 Nothing in these Terms transfers StampMitra intellectual property to the Developer.

21.3 StampMitra trademarks may not be used without authorization.

22.1 Except for StampMitra materials incorporated into the Developer's integration, the Developer retains rights in its own application, software and independently developed materials.

22.2 The Developer grants StampMitra only the permissions reasonably necessary to provide the API services.

23.1 Developers may provide suggestions, feature requests, technical feedback or other comments.

23.2 StampMitra may use such feedback without compensation, provided that such use does not improperly disclose the Developer's Confidential Information.

24.1 API responses are generated based on the request, available information, applicable service rules and system conditions.

24.2 StampMitra does not warrant that every response will always be:

• complete;
• error-free;
• uninterrupted;
• instantaneous;
• available in every jurisdiction; or
• suitable for every intended business purpose.

24.3 Developers remain responsible for appropriate validation and handling of API responses.

25.1 Where an API depends on external data or an external service, StampMitra may not independently control the underlying data.

25.2 The Developer shall not represent API results as independently verified by StampMitra unless expressly stated.

25.3 Developers must implement appropriate business logic for:

• null values;
• stale data;
• failed requests;
• partial responses;
• status changes;
• duplicate responses;
• timeouts; and
• asynchronous processing.

26.1 Verification services may depend upon information obtained from authorized sources and service networks.

26.2 A successful API response does not necessarily constitute a legal certification, governmental approval, professional opinion or guarantee of future validity unless expressly stated.

26.3 Developers shall not misrepresent the nature of a verification result.

27.1 Where StampMitra provides e-Stamp-related functionality, the Developer shall comply with applicable:

• stamp laws;
• state-specific requirements;
• registration requirements;
• document requirements;
• identity requirements;
• payment requirements; and
• service-specific instructions.

27.2 Stamp duty, government charges, processing fees and other amounts may vary by jurisdiction, instrument, value, article, location and applicable rules.

27.3 StampMitra does not guarantee that a particular instrument will be accepted by every authority or institution unless such acceptance is expressly represented.

28.1 e-Sign functionality may depend upon applicable service providers, identity verification requirements, technical availability and legal requirements.

28.2 Developers shall ensure that users provide the required authorization and consent for electronic signing.

28.3 Developers must not use e-Sign functionality for unauthorized signatures, impersonation, fraudulent documents or unlawful purposes.

29.1 StampMitra may rely on third-party and underlying service providers in delivering certain Services.

29.2 Such providers may support:

• infrastructure;
• data access;
• verification;
• payment processing;
• document processing;
• identity services;
• electronic signatures;
• communications;
• government-connected services; or
• other technical or operational functions.

29.3 The identity, commercial arrangements, technical architecture and internal relationships of particular Underlying Service Providers may constitute confidential business information of StampMitra and/or its contractual counterparties.

29.4 StampMitra is not required to disclose confidential upstream commercial relationships merely because an API or Service is accessed through the StampMitra Platform.

30.1 The Developer shall not attempt to discover or infer confidential upstream provider relationships through:

• reverse engineering;
• traffic analysis;
• unauthorized endpoint discovery;
• credential manipulation;
• undocumented API inspection;
• response fingerprinting; or
• other improper means.

30.2 Nothing in this section prevents lawful use of publicly available information unrelated to confidential StampMitra arrangements.

31.1 The Developer shall not use confidential information obtained through StampMitra to deliberately circumvent StampMitra's contractual or commercial relationships.

31.2 This restriction does not prohibit a Developer from independently obtaining a service that is lawfully and publicly available without use of StampMitra Confidential Information.

31.3 This section is intended to protect legitimate confidential commercial relationships and shall be interpreted subject to applicable law.

32.1 A Service may become unavailable because of circumstances outside StampMitra's reasonable control, including:

• third-party outages;
• government-system downtime;
• network failures;
• infrastructure failures;
• regulatory restrictions;
• maintenance;
• upstream capacity limitations;
• cybersecurity events; or
• force majeure events.

32.2 StampMitra may not be responsible for failures caused exclusively by an external provider or external system, subject to applicable law and the applicable SLA.

33.1 Where the Developer provides StampMitra-powered functionality to its End Users, the Developer remains responsible for its own:

• user interface;
• user notices;
• contractual terms;
• privacy disclosures;
• consents;
• data collection;
• customer support;
• business claims; and
• legal compliance.

33.2 The Developer shall not represent itself as StampMitra or imply an agency relationship unless expressly authorized.

The Developer shall not use the Platform or APIs for:

• fraud;
• impersonation;
• unlawful surveillance;
• unauthorized identity verification;
• credential theft;
• phishing;
• malware;
• unlawful financial activity;
• unlawful document creation;
• forged documents;
• unauthorized signatures;
• evasion of regulatory controls;
• harassment;
• unlawful discrimination;
• infringement of intellectual property;
• unauthorized data extraction;
• security attacks;
• denial-of-service activity;
• credential stuffing;
• automated abuse;
• unauthorized resale of API access;
• circumvention of rate limits; or
• any other unlawful or prohibited purpose.

35.1 Developers shall not conduct security testing against Production systems without prior written authorization.

35.2 Prohibited activities include unauthorized:

• penetration testing;
• vulnerability scanning;
• load testing;
• stress testing;
• denial-of-service testing;
• endpoint fuzzing;
• credential testing; or
• exploitation attempts.

35.3 Security researchers should use any officially designated security-reporting channel made available by StampMitra.

Except to the extent expressly permitted by applicable mandatory law, the Developer shall not:

• reverse engineer;
• decompile;
• disassemble;
• extract source code;
• bypass security controls;
• reconstruct proprietary algorithms; or
• attempt to discover confidential system architecture.

37.1 The Developer shall promptly notify StampMitra if it becomes aware of:

• unauthorized API access;
• credential compromise;
• significant data leakage;
• security incidents involving StampMitra APIs;
• malicious use of its integration; or
• a material vulnerability affecting StampMitra services.

37.2 The Developer shall cooperate reasonably with incident investigation and containment.

38.1 StampMitra may monitor API usage for:

• security;
• fraud detection;
• capacity planning;
• abuse prevention;
• service quality;
• billing;
• compliance;
• debugging; and
• operational purposes.

38.2 Monitoring may include metadata, request patterns, response status, IP information, timestamps, usage volume and other technical information, subject to applicable law and the Privacy Policy.

39.1 StampMitra may maintain API logs for operational, security, compliance and billing purposes.

39.2 Logs may include:

• timestamps;
• endpoint information;
• status codes;
• request identifiers;
• API Project;
• authentication identifiers;
• IP addresses;
• latency;
• usage quantities; and
• other technical metadata.

40.1 Paid API Services may be subject to applicable pricing published by StampMitra or agreed commercially with the Developer.

40.2 Charges may be calculated based on:

• subscription fees;
• API usage;
• successful transactions;
• processing volume;
• credits;
• enterprise arrangements; or
• other applicable commercial terms.

40.3 The Developer is responsible for reviewing applicable pricing before Production usage.

41.1 Where StampMitra provides prepaid or promotional API credits, such credits may be subject to:

• expiration;
• API-specific restrictions;
• non-transferability;
• non-convertibility into cash; and
• promotional conditions.

41.2 Promotional credits do not necessarily have monetary value unless expressly stated.

42.1 Billing disputes should be raised promptly through the designated billing/support channel.

42.2 The Developer should provide:

• transaction identifiers;
• relevant dates;
• usage details;
• invoices; and
• the basis of the dispute.

42.3 StampMitra may investigate usage records and system logs in resolving billing disputes.

43.1 Applicable taxes, including GST where legally applicable, may be charged in addition to stated prices.

43.2 The Developer shall provide accurate tax information where required.

43.3 Tax treatment may vary according to:

• Developer status;
• jurisdiction;
• place of supply;
• nature of service; and
• applicable law.

44.1 Refund eligibility shall be governed by the applicable Billing, Credits & Refund Policy and any specific commercial arrangement.

44.2 Unauthorized, fraudulent or abusive usage may not qualify for refund.

44.3 Where an external service has already been successfully processed or a third-party cost has been incurred, refund treatment may be subject to the relevant service terms.

45.1 Developers expecting material API volumes shall communicate their requirements to StampMitra where requested.

45.2 StampMitra may require:

• capacity planning;
• technical review;
• commercial approval;
• dedicated infrastructure;
• higher-tier limits; or
• additional controls.

StampMitra may suspend or restrict access where reasonably necessary because of:

• violation of these Terms;
• security risk;
• suspected fraud;
• unlawful activity;
• non-payment;
• excessive usage;
• credential compromise;
• inaccurate information;
• regulatory requirements;
• third-party restrictions; or
• operational necessity.

StampMitra may immediately suspend access without prior notice where continued access reasonably presents a material:

• security risk;
• fraud risk;
• legal risk;
• financial risk;
• service-integrity risk; or
• risk to other customers or users.

StampMitra may suspend only:

• one API;
• one Project;
• one credential;
• one environment;
• one endpoint;
• one user;
• one Workspace; or
• one category of activity.

Partial suspension may be used instead of full account suspension where appropriate.

49.1 Production access may be periodically reviewed.

49.2 StampMitra may request updated information where:

• usage materially increases;
• the use case changes;
• a new API is requested;
• risk indicators change;
• regulatory requirements change; or
• security requirements change.

The Developer may discontinue use of the Platform at any time, subject to:

• outstanding payment obligations;
• surviving contractual obligations;
• applicable data-retention requirements; and
• any committed enterprise arrangement.

StampMitra may terminate or discontinue a Developer Account where permitted by applicable law, including where:

• the Developer materially breaches these Terms;
• unlawful activity is identified;
• fraudulent activity is identified;
• continued service presents unacceptable risk;
• payment obligations remain materially unpaid;
• the Developer repeatedly violates API restrictions; or
• StampMitra discontinues the relevant service.

Upon termination:

• API access may cease;
• API credentials may be revoked;
• Production access may be disabled;
• outstanding amounts may remain payable;
• confidentiality obligations continue;
• intellectual-property rights remain unaffected; and
• provisions intended by their nature to survive shall survive.

53.1 Each party shall protect the other party's Confidential Information using reasonable safeguards.

53.2 Confidential Information shall be used only for purposes connected with the contractual relationship.

53.3 The receiving party shall restrict disclosure to persons who have a legitimate need to know and are subject to appropriate confidentiality obligations.

Confidential Information does not include information that the receiving party can demonstrate:

• was already lawfully known;
• becomes publicly available without breach;
• is independently developed;
• is lawfully received from another source; or
• must be disclosed by law.

55.1 Each party shall comply with laws applicable to its respective activities.

55.2 The Developer is responsible for ensuring that its integration complies with laws applicable to its business, users and processing activities.

55.3 Nothing in these Terms authorizes unlawful processing or use of information.

56.1 Processing of personal data shall be governed by applicable data-protection law and the StampMitra Privacy Policy and, where applicable, a Data Processing Addendum.

56.2 Depending upon the particular processing activity, StampMitra and the Developer may have different legal roles concerning personal data.

56.3 Neither party shall assume that the other party is automatically a data fiduciary, data processor, controller or equivalent role for every processing activity.

56.4 The parties shall determine their respective responsibilities based on the actual processing activity and applicable law.

57.1 StampMitra may disclose information where required by:

• law;
• court order;
• governmental authority;
• lawful regulatory direction; or
• other legally enforceable process.

57.2 Where legally permissible, StampMitra may provide appropriate notice concerning such requests.

58.1 To the maximum extent permitted by applicable law, Services are provided on an “as available” and “as is” basis.

58.2 StampMitra does not guarantee that the Platform will always be:

• uninterrupted;
• error-free;
• secure against every possible threat;
• available at every location;
• compatible with every software environment; or
• suitable for every business purpose.

58.3 Nothing in this section excludes warranties that cannot lawfully be excluded.

59.1 API results and platform functionality do not automatically constitute:

• legal advice;
• tax advice;
• financial advice;
• professional certification;
• governmental approval; or
• professional consultation.

59.2 Developers remain responsible for obtaining appropriate professional advice where required.

To the extent permitted by applicable law, the Developer shall defend, indemnify and hold harmless StampMitra, its partners, officers, employees and authorized representatives from third-party claims, losses, liabilities, damages, penalties, costs and reasonable expenses arising from:

• unlawful use of the Platform;
• breach of these Terms;
• infringement of third-party rights;
• misuse of API credentials;
• unauthorized processing of personal data;
• Developer products or services;
• Developer representations to End Users; or
• fraudulent or negligent conduct by the Developer.

61.1 To the maximum extent permitted by applicable law, StampMitra shall not be liable for indirect, incidental, special, consequential, exemplary or punitive losses, including loss of profits, revenue, goodwill, business opportunity or anticipated savings, except where such exclusion is prohibited by law.

61.2 The final monetary liability cap, if applicable to a particular commercial plan, shall be determined by the applicable commercial agreement or published commercial terms.

61.3 Nothing in these Terms is intended to exclude liability that cannot lawfully be excluded or limited.

StampMitra shall not be responsible for delay or failure caused by events beyond reasonable control, including:

• natural disasters;
• war;
• terrorism;
• civil unrest;
• government restrictions;
• internet failures;
• major infrastructure failures;
• cyber incidents;
• third-party outages;
• telecommunications failures;
• power failures;
• epidemics or pandemics; or
• other comparable events.

StampMitra may modify, improve, restrict, replace or discontinue Services.

Where reasonably practicable, material changes affecting active Developers may be communicated through appropriate channels.

64.1 StampMitra may introduce new API versions.

64.2 Older API versions may eventually be deprecated.

64.3 Deprecation notices may specify:

• affected version;
• replacement version;
• migration requirements;
• expected sunset date; and
• other relevant technical information.

64.4 Developers are responsible for migrating integrations within applicable timelines.

StampMitra may maintain records reasonably necessary to:

• establish usage;
• calculate charges;
• investigate security incidents;
• demonstrate compliance;
• resolve disputes;
• prevent fraud; and
• maintain platform integrity.

StampMitra may take reasonable administrative or technical measures to protect:

• Platform security;
• customer information;
• API infrastructure;
• third-party systems;
• service availability;
• legal compliance; and
• commercial integrity.

Such measures may include credential rotation, throttling, access restrictions, suspension and termination.

StampMitra may provide technical or account support through designated channels.

Support availability, response targets and service levels may vary by:

• account type;
• subscription;
• API;
• enterprise arrangement; and
• applicable SLA.

These Terms do not create:

• partnership;
• employment;
• agency;
• joint venture;
• franchise; or
• fiduciary relationship

between StampMitra and the Developer unless expressly agreed in writing.

The relationship is non-exclusive unless a separate written agreement expressly provides otherwise.

The Developer may not assign or transfer these Terms or material rights under them without StampMitra's prior written consent, except where such restriction is prohibited by applicable law.

StampMitra may assign these Terms as part of a merger, restructuring, corporate reorganization, transfer of business or similar transaction, subject to applicable law.

StampMitra may use affiliates, contractors, infrastructure providers and other service providers to operate and support the Platform, subject to applicable contractual and legal requirements.

If any provision is determined to be invalid, unlawful or unenforceable, the remaining provisions shall continue to the extent permitted by law.

Failure to enforce a provision does not constitute a permanent waiver of that provision.

These Terms, together with incorporated policies, applicable commercial terms and specific written agreements, constitute the agreement governing the Developer's use of the Platform.

Where documents conflict, the following order generally applies unless expressly stated otherwise:

• 1. a specific written commercial agreement;
• 2. a Data Processing Addendum, for data-processing matters;
• 3. applicable Service-Specific Terms;
• 4. these Developer Terms;
• 5. other incorporated policies;
• 6. Documentation, where technical implementation matters are concerned.

These Terms shall be governed by and interpreted in accordance with the laws of India, subject to applicable conflict-of-law principles.

The parties shall endeavour to resolve material disputes through good-faith discussions before commencing formal proceedings, except where immediate legal or injunctive relief is reasonably required.

Where a dispute is required to be resolved by arbitration under the applicable contractual arrangement, the arbitration shall be conducted in accordance with applicable Indian arbitration law.

The detailed arbitration mechanism, including the applicable seat, venue, number and appointment of arbitrator(s), language and procedural arrangements, shall be governed by the applicable written agreement and applicable law.

Nothing in these Terms prevents either party from seeking urgent interim or protective relief from a court of competent jurisdiction where legally available, including relief concerning:

• confidentiality;
• intellectual property;
• cybersecurity;
• unauthorized access;
• misuse of credentials; or
• protection of confidential information.

Formal legal notices shall be delivered through the designated legal/contact channels published by StampMitra or otherwise specified in the applicable agreement.

For legal-policy communication, the designated contact is: [email protected]

The following policies may form part of the Developer contractual framework:

• 1. Developer Privacy Policy;
• 2. Data Processing Addendum;
• 3. API Acceptable Use Policy;
• 4. Third-Party & Underlying Services Policy;
• 5. API Security Policy;
• 6. API SLA & Service Availability Policy;
• 7. Billing, Credits & Refund Policy;
• 8. Verification, e-Stamp & e-Sign Service Terms; and
• 9. API Versioning, Suspension & Deprecation Policy.

Where an incorporated policy contains provisions specifically applicable to a particular subject matter, those provisions shall govern that subject matter to the extent of the specific conflict, unless a written commercial agreement provides otherwise.

The provisions concerning:

• intellectual property;
• confidentiality;
• payment obligations;
• data protection;
• indemnification;
• limitation of liability;
• dispute resolution;
• governing law;
• audit and records;
• provider confidentiality; and
• other provisions that by their nature should survive

shall survive termination to the extent permitted by law.

Except where expressly stated otherwise, these Terms do not create enforceable rights for third parties.

These Terms may be published in English and may subsequently be translated into other languages.

In case of inconsistency between language versions, the version expressly designated by StampMitra as controlling shall prevail, subject to applicable law.

For legal and contractual matters: Legal Team, BANI GLOBAL INDUSTRIES LLP — Email: [email protected]

For technical and developer support, Developers should use the support channels displayed within the StampMitra Developer Platform.

By selecting “I Agree”, creating an account, activating an API, requesting Production access, generating or using API credentials, or otherwise accessing or using the StampMitra Developer Platform, the Developer confirms that:

• 1. they have read these Terms;
• 2. they understand these Terms;
• 3. they have authority to accept these Terms where acting for an organization;
• 4. the information supplied to StampMitra is accurate to the best of their knowledge;
• 5. they agree to comply with applicable law;
• 6. they agree to the incorporated policies applicable to their use;
• 7. they accept responsibility for their API integration and credentials; and
• 8. they agree to be legally bound by these Terms.

• Document: StampMitra Developer Terms of Service
• Document Type: Master Developer & API Services Agreement
• Version: 1.0
• Status: FINAL — PUBLISHED TERMS
• Effective Date: 05 October 2026
• Last Updated: 05 October 2026
• Operator: BANI GLOBAL INDUSTRIES LLP
• Platform: StampMitra Developer Platform
• Legal Contact: [email protected]
• Prepared by: Legal Team, BANI GLOBAL INDUSTRIES LLP

This document is intended to constitute the governing Developer Terms for the StampMitra Developer Platform when duly published and made available to Developers in accordance with applicable law and StampMitra's electronic contracting process.

It should be read together with the applicable Privacy Policy, Data Processing Addendum, Acceptable Use Policy, Security Policy, Billing Policy, Service-Specific Terms and other incorporated policies.

BANI GLOBAL INDUSTRIES LLP reserves the right to update these Terms in accordance with the change-management provisions contained herein and applicable law.

© 2026 BANI GLOBAL INDUSTRIES LLP. All rights reserved.

Prepared by: Legal Team — [email protected]