Billing, API Credits & Refund Policy

1.1. This StampMitra Billing, API Credits & Refund Policy (“Billing Policy”) governs subscription charges, API usage charges, API credits, prepaid balances, transaction charges, invoices, taxes, payments, refunds, reversals, disputes, failed payments, billing adjustments, promotional credits, and related commercial matters applicable to StampMitra Developer Services.

1.2. This Policy establishes the commercial framework under which Developers may purchase, consume, renew, replenish, or otherwise use paid StampMitra Developer Services.

1.3. This Policy is intended to provide transparency regarding:

• (a) subscription billing;
• (b) API usage billing;
• (c) transaction-based charges;
• (d) prepaid API credits;
• (e) promotional credits;
• (f) taxes;
• (g) invoices;
• (h) payment processing;
• (i) failed payments;
• (j) refunds;
• (k) cancellations;
• (l) billing disputes;
• (m) chargebacks;
• (n) credit expiry;
• (o) account suspension for non-payment; and
• (p) billing-related termination.

2.1. This Billing Policy forms part of the StampMitra Developer Services contractual framework.

2.2. It shall be read together with:

• (a) StampMitra Developer Terms of Service;
• (b) StampMitra Developer Privacy Policy;
• (c) StampMitra Data Processing Addendum;
• (d) StampMitra API Acceptable Use Policy;
• (e) StampMitra API Security Policy;
• (f) StampMitra API SLA & Service Availability Policy;
• (g) StampMitra Third-Party & Underlying Services Policy;
• (h) applicable Service Terms; and
• (i) applicable commercial order forms or Enterprise agreements.

2.3. In the event of conflict, the applicable contractual hierarchy under the Developer Terms shall apply.

2.4. A separately executed Enterprise commercial agreement may contain billing terms that supplement or override this Policy for the applicable Developer.

3.1. “Billing Account” means the account or commercial profile associated with payment obligations.

3.2. “Billing Cycle” means the recurring period for which a subscription or recurring service charge is calculated.

3.3. “API Credits” means prepaid monetary or usage value made available for eligible API services.

3.4. “Promotional Credits” means credits granted for promotional, marketing, trial, goodwill, referral, or other limited purposes.

3.5. “Usage Charge” means an amount calculated based on API usage, transactions, requests, services, documents, or another measurable unit.

3.6. “Subscription Fee” means a recurring fee applicable to a Developer plan.

3.7. “Transaction Charge” means a fee associated with a transaction or service request.

3.8. “Invoice” means a billing document issued by StampMitra or an authorized billing system.

3.9. “Payment Method” means a card, bank account, UPI method, or other supported payment instrument.

3.10. “Refund” means a return of an amount previously paid, subject to this Policy and applicable law.

3.11. “Chargeback” means a payment reversal initiated through a payment institution, card issuer, bank, or similar financial institution.

3.12. “Taxes” includes applicable GST and other legally applicable taxes, duties, levies, or governmental charges.

4.1. Applicable pricing shall be the pricing displayed or otherwise communicated through an authorized StampMitra commercial channel at the time of purchase or order.

4.2. Pricing may vary according to:

• (a) API;
• (b) service;
• (c) Developer plan;
• (d) transaction volume;
• (e) geography;
• (f) enterprise arrangements;
• (g) promotional offers; and
• (h) other applicable commercial conditions.

4.3. Pricing information may be updated prospectively subject to applicable contractual requirements.

4.4. Developers should review applicable pricing before purchasing or enabling paid services.

5.1. Certain services may require:

• (a) subscription payment;
• (b) per-request payment;
• (c) per-transaction payment;
• (d) prepaid credits;
• (e) minimum commitments;
• (f) onboarding charges;
• (g) enterprise fees; or
• (h) a combination thereof.

5.2. The applicable pricing model will depend upon the service.

6.1. Where a Developer subscribes to a paid plan, the applicable Subscription Fee becomes payable according to the stated Billing Cycle.

6.2. Subscription Fees may be charged:

• (a) monthly;
• (b) annually;
• (c) according to another stated period; or
• (d) according to an Enterprise agreement.

6.3. Subscription fees may continue until cancellation, expiry, suspension, or termination according to applicable terms.

7.1. Where automatic renewal is expressly disclosed and enabled, a subscription may renew automatically at the end of the applicable Billing Cycle.

7.2. The applicable Payment Method may be charged for the renewal.

7.3. Developers are responsible for maintaining a valid Payment Method.

7.4. Automatic renewal may be subject to applicable payment-provider rules and authorization requirements.

8.1. Developers may cancel recurring services through the applicable Developer Platform functionality or designated support channel.

8.2. Cancellation generally prevents future renewal but does not automatically reverse charges already incurred.

8.3. Any refund resulting from cancellation is subject to this Policy and the applicable commercial terms.

9.1. StampMitra may offer free trials.

9.2. A trial may be:

• (a) time-limited;
• (b) usage-limited;
• (c) API-limited;
• (d) feature-limited;
• (e) eligibility-limited; or
• (f) subject to verification.

9.3. Unless expressly stated otherwise, a free trial does not constitute a commitment to provide unlimited or uninterrupted access.

10.1. Where a trial does not require payment information, no payment will ordinarily be charged merely because the trial ends.

10.2. Where payment information is collected and automatic conversion is expressly disclosed, the applicable commercial terms shall govern.

11.1. Certain APIs may be charged according to usage.

11.2. Usage may be measured according to:

• (a) API requests;
• (b) successful transactions;
• (c) submitted transactions;
• (d) processed documents;
• (e) verification requests;
• (f) service-specific units;
• (g) credits consumed; or
• (h) another published measurement unit.

11.3. The applicable API documentation or pricing page determines the relevant measurement methodology.

12.1. A billable event may occur when a Developer:

• (a) invokes a billable API;
• (b) submits a billable transaction;
• (c) consumes a billable service;
• (d) purchases credits;
• (e) activates a paid plan; or
• (f) triggers another commercially defined event.

12.2. Whether an unsuccessful request is billable depends upon the applicable service pricing terms.

13.1. StampMitra may provide API Credits for eligible services.

13.2. API Credits may be:

• (a) purchased;
• (b) prepaid;
• (c) promotional;
• (d) granted as part of a plan;
• (e) provided as goodwill; or
• (f) issued under an Enterprise agreement.

13.3. API Credits are not automatically equivalent to cash.

14.1. A Developer's available API Credit balance may be displayed through the Developer Platform.

14.2. Credit balances may be adjusted to reflect:

• (a) usage;
• (b) refunds;
• (c) reversals;
• (d) promotional grants;
• (e) corrections; or
• (f) billing adjustments.

15.1. Credits may be deducted when an eligible billable event occurs.

15.2. The applicable service may define whether credits are consumed for:

• (a) submitted requests;
• (b) successful requests;
• (c) completed transactions;
• (d) attempted processing; or
• (e) another defined event.

16.1. Where multiple types of credits are available, StampMitra may determine a reasonable consumption order.

16.2. Such order may consider:

• (a) expiry date;
• (b) promotional restrictions;
• (c) purchased credits;
• (d) service eligibility; and
• (e) applicable commercial rules.

17.1. Promotional Credits may be issued subject to specific terms.

17.2. Promotional Credits may be:

• (a) non-transferable;
• (b) non-refundable;
• (c) restricted to specified APIs;
• (d) restricted to specified Developers;
• (e) restricted to specified periods; or
• (f) subject to usage limits.

18.1. Promotional Credits may expire on the date specified at issuance.

18.2. If no expiry period is specified, StampMitra may define a reasonable promotional validity period.

18.3. Expired Promotional Credits have no cash value unless required by applicable law.

19.1. Purchased API Credits may be subject to validity or expiry conditions stated at purchase.

19.2. Where no expiry condition is expressly stated, the credits may remain available subject to account status and applicable service changes.

19.3. Any applicable statutory requirements concerning prepaid balances shall prevail.

20.1. API Credits are generally associated with the Developer Account for which they were purchased.

20.2. Credits must not be sold, transferred, assigned, exchanged, or otherwise commercially distributed unless expressly authorized.

21.1. API Credits do not constitute a bank deposit, payment instrument, security, investment, or stored-value product unless expressly designated otherwise under applicable law.

21.2. Credits generally cannot be redeemed for cash except where required by applicable law or expressly agreed.

22.1. Applicable Taxes may be charged in addition to stated prices unless expressly stated as tax-inclusive.

22.2. Developers are responsible for applicable taxes arising from their purchase or use of StampMitra services.

22.3. GST may be applicable to eligible supplies in accordance with applicable law.

23.1. Developers should provide accurate tax information where requested.

23.2. Incorrect or incomplete tax information may affect invoice treatment.

23.3. StampMitra may require appropriate documentation to apply tax treatment or exemptions.

24.1. Where applicable, Developers may be requested to provide:

• (a) legal name;
• (b) billing address;
• (c) GSTIN;
• (d) state;
• (e) tax registration details; and
• (f) other billing information.

24.2. Developers are responsible for the accuracy of information supplied.

25.1. Where applicable, StampMitra may issue tax invoices or equivalent billing documents.

25.2. Invoice availability may depend upon successful payment and accurate billing information.

26.1. Invoices may include:

• (a) Developer information;
• (b) service description;
• (c) billing period;
• (d) taxable amount;
• (e) applicable taxes;
• (f) credits;
• (g) discounts;
• (h) transaction references; and
• (i) total amount payable.

27.1. Developers must maintain accurate:

• (a) legal name;
• (b) billing address;
• (c) email address;
• (d) tax information;
• (e) Payment Method information; and
• (f) other billing details.

27.2. Developers must promptly update outdated billing information.

28.1. StampMitra may support payment methods made available through authorized payment infrastructure.

28.2. Payment methods may include:

• (a) cards;
• (b) UPI;
• (c) bank transfers;
• (d) net banking;
• (e) other electronic payment methods; and
• (f) Enterprise invoicing where separately agreed.

29.1. Payments may be processed through authorized payment infrastructure.

29.2. Payment processing may be subject to separate terms of the relevant payment institution.

29.3. StampMitra may not control every aspect of payment authorization, settlement, reversal, or banking operations.

30.1. A payment is considered received when the applicable payment system confirms successful receipt according to the applicable transaction flow.

30.2. A payment initiation screen or bank-side pending status does not necessarily mean that payment has been successfully received.

31.1. A payment may fail because of:

• (a) insufficient funds;
• (b) bank rejection;
• (c) payment-method restrictions;
• (d) authentication failure;
• (e) payment-provider outage;
• (f) fraud controls;
• (g) incorrect information; or
• (h) other reasons.

32.1. StampMitra or its payment infrastructure may attempt payment retries where applicable.

32.2. Developers should maintain a valid Payment Method for recurring services.

33.1. Repeated payment failure may result in:

• (a) billing reminders;
• (b) restricted access;
• (c) suspension;
• (d) cancellation; or
• (e) termination.

33.2. Applicable notice requirements shall be governed by the relevant commercial terms.

34.1. Amounts that remain unpaid after becoming due may be treated as overdue.

34.2. StampMitra may restrict paid services where permitted under the applicable contractual terms.

35.1. StampMitra may issue:

• (a) invoices;
• (b) payment confirmations;
• (c) renewal reminders;
• (d) payment failure notices;
• (e) credit balance notifications;
• (f) billing adjustment notices; and
• (g) other billing communications.

36.1. Successful payments may generate electronic receipts or equivalent confirmation.

36.2. A payment receipt does not necessarily mean that every underlying service transaction has completed successfully.

37.1. If a Developer believes that a payment was duplicated, the Developer should notify StampMitra promptly.

37.2. StampMitra may investigate payment records and, where appropriate, issue a correction or refund according to applicable terms.

38.1. StampMitra may correct billing errors.

38.2. Corrections may include:

• (a) additional charges;
• (b) credits;
• (c) refunds;
• (d) invoice corrections; or
• (e) balance adjustments.

39.1. Usage may be measured through StampMitra's technical metering systems.

39.2. Metering may rely upon:

• (a) API logs;
• (b) transaction records;
• (c) billing records;
• (d) credit ledgers;
• (e) request identifiers; and
• (f) other operational data.

40.1. StampMitra's usage records may be used as the primary basis for calculating API usage charges unless an applicable commercial agreement provides otherwise.

40.2. Developers may request reasonable clarification of material billing discrepancies.

41.1. Developers must notify StampMitra of a disputed charge within a reasonable period after becoming aware of the issue.

41.2. The dispute should identify:

• (a) invoice;
• (b) transaction;
• (c) amount;
• (d) date;
• (e) reason for dispute; and
• (f) supporting information.

42.1. StampMitra may review:

• (a) API logs;
• (b) transaction records;
• (c) payment records;
• (d) credit balances;
• (e) invoices;
• (f) system events; and
• (g) applicable commercial terms.

43.1. A billing dispute concerning one charge does not automatically suspend unrelated undisputed payment obligations.

44.1. Where StampMitra confirms a billing error attributable to StampMitra, StampMitra may provide an appropriate adjustment, credit, or refund.

44.2. The remedy may depend upon the nature of the error.

45.1. Developers remain responsible for charges arising from:

• (a) authorized account activity;
• (b) Developer application configuration;
• (c) automated requests;
• (d) repeated requests;
• (e) improperly configured integrations; or
• (f) authorized users acting within the Developer Account.

46.1. If unauthorized activity results from Developer-side credential compromise, billing responsibility may depend upon the circumstances and applicable law.

46.2. Developers must promptly report suspected compromise to reduce potential losses.

47.1. Refunds are generally available only where:

• (a) expressly provided by this Policy;
• (b) required by applicable law;
• (c) a billing error has occurred;
• (d) StampMitra expressly approves the refund; or
• (e) an applicable commercial agreement provides for the refund.

48.1. The following do not automatically create a refund entitlement:

• (a) unused subscription time;
• (b) unused API credits;
• (c) Developer application errors;
• (d) Developer-side downtime;
• (e) unsuccessful customer transactions;
• (f) external provider rejection;
• (g) failure to use purchased services;
• (h) forgotten cancellation; or
• (i) temporary API interruption, except where an applicable SLA expressly provides otherwise.

49.1. Refund requests should identify:

• (a) Developer Account;
• (b) payment reference;
• (c) amount;
• (d) date;
• (e) reason; and
• (f) relevant supporting documentation.

50.1. Where approved, refunds may generally be processed through the original Payment Method or another lawful method determined by StampMitra.

50.2. Payment-provider processing timelines may affect the time required for the refunded amount to reach the Developer.

51.1. StampMitra does not control all banking or payment-provider processing timelines.

51.2. A refund may therefore require additional processing time after approval.

52.1. Purchased API Credits are generally non-refundable after consumption.

52.2. Unused credits may be refundable only where:

• (a) expressly stated in the applicable commercial terms;
• (b) required by law; or
• (c) approved by StampMitra.

53.1. Promotional Credits generally have no cash refund value.

53.2. Promotional Credits may be revoked where:

• (a) obtained fraudulently;
• (b) obtained through multiple-account abuse;
• (c) used in violation of promotional terms; or
• (d) otherwise improperly obtained.

54.1. Subscription refunds, where any, are governed by the applicable subscription terms.

54.2. Unless expressly stated otherwise, cancellation does not automatically create a pro-rata refund for unused subscription time.

55.1. Transaction-related refunds may depend upon:

• (a) service status;
• (b) transaction state;
• (c) external system rules;
• (d) payment settlement;
• (e) applicable service terms; and
• (f) legal requirements.

56.1. Where a transaction involves an external system or underlying service provider, refund processing may depend upon the applicable external process.

56.2. StampMitra may communicate the applicable status to the Developer without guaranteeing a specific external refund timeline.

57.1. A failed transaction may not automatically result in an automatic refund.

57.2. Developers must first determine the transaction status through the applicable API or support process.

58.1. A transaction shown as pending should not automatically be treated as failed.

58.2. Developers must follow applicable reconciliation procedures.

59.1. If duplicate processing occurs, StampMitra may investigate the cause and determine whether a refund, credit, reversal, or other correction is appropriate.

60.1. Developers must not initiate unjustified chargebacks for valid StampMitra charges.

60.2. A chargeback may trigger:

• (a) account review;
• (b) suspension;
• (c) credit reversal;
• (d) additional verification; or
• (e) termination where permitted.

61.1. Developers must reasonably cooperate with legitimate payment-dispute investigations.

61.2. StampMitra may provide transaction records to authorized payment institutions where legally permitted.

62.1. StampMitra may reject, reverse, suspend, or investigate payments reasonably suspected to be fraudulent.

62.2. Promotional credits or purchased balances associated with fraudulent activity may be revoked.

63.1. Developers must protect Payment Methods and payment credentials.

63.2. StampMitra personnel should not require Developers to disclose full authentication credentials through ordinary support channels.

64.1. Payment processing may involve authorized payment infrastructure.

64.2. StampMitra may receive payment status and transaction information necessary to administer billing.

64.3. Handling of payment-related personal information is subject to applicable privacy requirements.

65.1. Payment transactions may be subject to terms and privacy practices of the relevant payment service provider.

65.2. StampMitra does not control external payment infrastructure.

66.1. Unless otherwise stated, prices for Indian Developers may be displayed in Indian Rupees (INR).

66.2. Enterprise or international arrangements may use another currency where expressly agreed.

67.1. Where a transaction involves currency conversion, applicable exchange rates, banking charges, taxes, or payment-provider fees may apply.

68.1. Developers may be responsible for bank, intermediary, payment-provider, or currency-conversion charges unless expressly stated otherwise.

69.1. Any withholding or tax deduction shall be handled according to applicable law and the applicable commercial agreement.

69.2. Developers responsible for withholding must provide appropriate documentation where required.

70.1. Developers are responsible for taxes arising from their own business, income, transactions, customers, or use of StampMitra services, except taxes imposed directly on StampMitra's income.

71.1. The person configuring billing must have authority to bind the relevant Developer or organization to applicable payment obligations.

71.2. StampMitra may rely upon account-level billing authorization unless otherwise notified.

72.1. Workspace administrators may be granted billing permissions.

72.2. Developers are responsible for assigning billing permissions appropriately.

73.1. Where an authorized Developer user purchases services within an account, the Developer remains responsible for reviewing its internal authorization controls.

73.2. Internal disputes between a Developer and its employees, contractors, or users do not automatically invalidate charges.

74.1. Closing a Developer Account does not automatically eliminate outstanding payment obligations.

74.2. Unpaid charges incurred before closure remain payable subject to applicable law and contractual terms.

75.1. Upon termination, the Developer remains responsible for charges incurred before termination.

75.2. Future recurring charges should cease according to the effective termination or cancellation date and applicable billing cycle.

76.1. Suspension caused by Developer misconduct, security concerns, non-payment, or policy violations does not automatically cancel outstanding charges.

76.2. Separate contractual provisions may determine whether any future recurring charges continue during suspension.

77.1. Reactivation may require:

• (a) payment of overdue amounts;
• (b) verification;
• (c) security review;
• (d) updated billing information; or
• (e) acceptance of revised commercial terms.

78.1. StampMitra may modify pricing prospectively subject to applicable contractual requirements.

78.2. Pricing changes may result from:

• (a) infrastructure costs;
• (b) external service costs;
• (c) taxes;
• (d) product changes;
• (e) market conditions;
• (f) regulatory changes; or
• (g) other commercial considerations.

79.1. Where required by contract or applicable law, StampMitra may provide advance notice of material recurring pricing changes.

79.2. Developers may be required to accept updated pricing to continue using affected paid services.

80.1. Enterprise Developers may receive individually negotiated pricing.

80.2. Enterprise pricing may include:

• (a) volume discounts;
• (b) minimum commitments;
• (c) onboarding fees;
• (d) transaction fees;
• (e) support fees;
• (f) custom SLAs; or
• (g) other commercial terms.

81.1. Volume-based pricing may be subject to eligibility conditions.

81.2. Developers must not artificially split transactions, accounts, or traffic to obtain unauthorized pricing benefits.

82.1. Promotional pricing may be subject to:

• (a) eligibility;
• (b) duration;
• (c) usage limits;
• (d) one-time availability;
• (e) account restrictions; and
• (f) other stated conditions.

83.1. Coupon codes may be subject to specific terms.

83.2. Coupons may not be:

• (a) transferred;
• (b) duplicated;
• (c) sold;
• (d) manipulated; or
• (e) used through unauthorized multiple accounts.

84.1. Referral credits may be subject to separate promotional terms.

84.2. Self-referrals, fraudulent referrals, circular referrals, or artificial account creation may invalidate referral benefits.

85.1. Free, beta, experimental, or preview services may be provided without the same commercial commitments applicable to paid Production services.

85.2. StampMitra may modify or discontinue such services subject to applicable contractual requirements.

86.1. Developers may contact designated support channels for billing issues.

86.2. Billing requests should include sufficient information for investigation but must not contain passwords, OTPs, API secrets, or other authentication credentials.

87.1. StampMitra may maintain billing records including:

• (a) invoices;
• (b) payment records;
• (c) credit ledger entries;
• (d) API usage;
• (e) refunds;
• (f) adjustments;
• (g) chargebacks; and
• (h) tax information.

88.1. Billing records may be retained for legal, accounting, tax, audit, contractual, security, and dispute-resolution purposes for periods permitted or required by applicable law.

89.1. StampMitra may make reasonable accounting corrections where:

• (a) duplicate charges occur;
• (b) metering errors are identified;
• (c) tax information changes;
• (d) payment reversals occur; or
• (e) other billing errors are identified.

90.1. Credit balances may be adjusted where necessary to correct:

• (a) technical metering errors;
• (b) duplicate credit issuance;
• (c) fraudulent activity;
• (d) payment reversals;
• (e) promotional abuse; or
• (f) accounting errors.

91.1. If adjustments cause a Developer Account to have a negative billing balance, the Developer may be required to settle the outstanding amount before continued paid usage.

92.1. Developers should raise billing disputes promptly after discovering the issue.

92.2. Delay in raising a dispute may make investigation more difficult.

92.3. Nothing in this section limits rights that cannot lawfully be waived.

93.1. Failure by StampMitra to immediately demand payment does not waive the underlying payment obligation.

94.1. Unless expressly agreed otherwise, Developers may not unilaterally deduct disputed amounts from unrelated invoices or payment obligations.

95.1. StampMitra may issue goodwill or commercial credits at its discretion.

95.2. Such credits do not establish a continuing obligation to issue similar credits in future cases.

96.1. Service Credits arising from an applicable SLA are distinct from API Credits.

96.2. Service Credits may be governed by the applicable SLA or Enterprise agreement.

97.1. Unless expressly stated otherwise, credits, promotional balances, discounts, coupons, and service credits do not constitute cash.

98.1. StampMitra may reverse credits that were:

• (a) issued in error;
• (b) fraudulently obtained;
• (c) obtained through abuse;
• (d) duplicated; or
• (e) subject to a payment reversal.

99.1. Billing balances and credits generally remain associated with the relevant Developer Account.

99.2. Transfers between accounts require StampMitra approval unless the platform expressly provides a transfer mechanism.

100.1. Where an Organization account owns a Workspace, the organization is responsible for applicable billing obligations associated with that Workspace.

100.2. Internal ownership disputes do not automatically invalidate charges.

101.1. Freelancers may use StampMitra services for authorized client projects.

101.2. The Freelancer remains responsible for charges incurred through their Developer Account unless otherwise contractually arranged.

102.1. Where a Developer uses StampMitra on behalf of a client, the Developer must clearly establish who is responsible for StampMitra charges.

102.2. StampMitra may rely upon the billing configuration associated with the relevant Developer Account.

103.1. Developers must not represent StampMitra API charges as their own regulated or governmental fees.

103.2. Any resale, white-label, or commercial redistribution arrangement requires appropriate authorization where applicable.

104.1. A Developer may charge its own customers for its own products or services subject to applicable law and contractual restrictions.

104.2. Developers must not falsely represent StampMitra's charges as mandatory government fees unless they are actually applicable and accurately described.

105.1. Where a StampMitra service involves government fees or statutory charges, such amounts may be separate from StampMitra's service fees.

105.2. Developers must not misrepresent service fees as government fees.

106.1. Certain services may involve third-party or external charges.

106.2. Such charges may be passed through or incorporated into the applicable pricing structure.

106.3. The identity of confidential underlying service providers does not need to be publicly disclosed solely because a charge incorporates an external cost.

107.1. External service costs may change.

107.2. StampMitra may adjust applicable pricing prospectively subject to contractual requirements.

108.1. Where an external transaction is reversed, cancelled, or refunded, StampMitra may adjust the Developer's corresponding billing balance according to applicable service rules.

109.1. Where a refund is appropriate but a full refund is not justified, StampMitra may issue a partial refund or credit.

110.1. Refunds may be denied where:

• (a) the service was validly delivered;
• (b) the transaction was successfully completed;
• (c) the Developer's application caused the issue;
• (d) the Developer violated applicable terms;
• (e) the request is fraudulent;
• (f) the amount has already been consumed or settled; or
• (g) refund is otherwise excluded by applicable terms or law.

111.1. StampMitra may investigate unusual billing activity.

111.2. Fraud indicators may include:

• (a) multiple accounts created to obtain promotions;
• (b) repeated payment reversals;
• (c) stolen payment instruments;
• (d) artificial usage;
• (e) suspicious credit consumption;
• (f) manipulated transaction data; or
• (g) other abnormal activity.

112.1. StampMitra may restrict billing or service functionality where reasonably necessary to address suspected payment fraud, chargeback abuse, or material billing irregularities.

113.1. Repeated unjustified chargebacks may be treated as a material contractual violation.

114.1. Developers may remove or update Payment Methods where the Developer Platform permits.

114.2. Removing a Payment Method does not automatically cancel outstanding obligations.

115.1. Developers are responsible for updating expired or invalid Payment Methods.

115.2. Failed recurring payment attempts may result in service restrictions.

116.1. Billing communications may be sent to the email address or contact information associated with the Developer Account.

116.2. Developers are responsible for maintaining accurate contact information.

117.1. Developers consent to receiving electronic billing records and commercial notices where permitted by applicable law.

118.1. StampMitra may retain records demonstrating:

• (a) subscription acceptance;
• (b) pricing acceptance;
• (c) purchase;
• (d) credit purchase;
• (e) billing changes;
• (f) cancellation; and
• (g) other commercial actions.

119.1. Billing and usage records may be subject to reasonable audit or reconciliation.

119.2. Enterprise agreements may establish additional audit procedures.

120.1. Non-public billing information may constitute confidential information.

120.2. Developers must protect invoices, usage reports, pricing arrangements, and commercial terms from unauthorized disclosure.

121.1. Individually negotiated Enterprise pricing may be confidential.

121.2. Developers must comply with any applicable confidentiality agreement.

122.1. StampMitra may disclose billing and tax information to competent authorities where legally required.

123.1. Billing-related personal data shall be handled according to applicable privacy and data-protection requirements.

123.2. The StampMitra Developer Privacy Policy governs applicable personal-data processing.

124.1. Developers are responsible for securing billing access.

124.2. Unauthorized billing resulting from compromised Developer credentials should be reported promptly.

125.1. StampMitra may use technical and administrative controls to detect billing fraud.

125.2. Such controls may result in additional verification or temporary restrictions.

126.1. Service availability matters are governed by the StampMitra API SLA & Service Availability Policy.

126.2. Billing consequences of service incidents are governed by this Policy and any applicable SLA.

127.1. Service Credits and API Credits are distinct.

127.2. Service Credits compensate eligible service-level failures where contractually applicable.

127.3. API Credits are generally prepaid or promotional value used to consume eligible API services.

128.1. StampMitra may determine whether an approved adjustment is provided as:

• (a) a refund;
• (b) API Credit;
• (c) Service Credit;
• (d) invoice adjustment; or
• (e) another commercially appropriate mechanism,

subject to applicable law and contractual terms.

129.1. Nothing in this Policy limits rights or remedies that cannot lawfully be excluded or limited.

130.1. StampMitra may update this Billing Policy to reflect:

• (a) pricing changes;
• (b) payment-system changes;
• (c) tax changes;
• (d) legal requirements;
• (e) service changes;
• (f) accounting requirements; or
• (g) operational requirements.

130.2. Material changes shall be communicated where required by applicable law or contract.

131.1. If a written Enterprise commercial agreement expressly conflicts with this Policy, the Enterprise agreement shall govern the conflicting subject matter.

131.2. The remaining provisions of this Policy shall continue to apply.

132.1. If any provision is held invalid or unenforceable, the remaining provisions shall continue to apply to the maximum extent permitted by law.

133.1. Failure to enforce any billing provision on one occasion does not constitute a permanent waiver.

134.1. This Billing Policy shall be governed by the laws of India, subject to the dispute-resolution provisions of the StampMitra Developer Terms of Service.

• BANI GLOBAL INDUSTRIES LLP
• LLPIN: ACI6373
• Registered Office: 2-A/3, Kundan Mansion, Asaf Ali Road, Turkman Gate, Central Delhi, NCT of Delhi, India – 110002
• Developer Platform: https://developer.stampmitra.in/
• Legal Contact: [email protected]

By using paid StampMitra Developer Services, the Developer acknowledges that:

• (a) applicable services may involve subscription, usage, transaction, credit, or other charges;
• (b) API Credits are subject to applicable credit terms;
• (c) Promotional Credits may be restricted and may expire;
• (d) applicable Taxes may be charged;
• (e) Developers are responsible for maintaining accurate billing information;
• (f) Developers are responsible for valid Payment Methods;
• (g) failed payments may result in service restrictions;
• (h) refunds are subject to this Policy, applicable commercial terms, and law;
• (i) chargebacks must be legitimate;
• (j) billing and usage records may be maintained for accounting, tax, legal, security, and dispute purposes; and
• (k) the Developer remains bound by all applicable StampMitra policies and agreements.

• Policy Name: StampMitra Billing, API Credits & Refund Policy
• Policy Number: 08/10
• Version: 1.0
• Status: FINAL — PUBLISHED POLICY
• Effective Date: 05 October 2026
• Last Updated: 05 October 2026
• Operator: BANI GLOBAL INDUSTRIES LLP
• LLPIN: ACI6373
• Registered Office: 2-A/3, Kundan Mansion, Asaf Ali Road, Turkman Gate, Central Delhi, NCT of Delhi, India – 110002
• Legal Contact: [email protected]
• Prepared By: Legal Team, BANI GLOBAL INDUSTRIES LLP
• Developer Platform: https://developer.stampmitra.in/