Partner Terms

Application of these terms

These Partner Terms apply to any business ("Partner") that has been approved to use the RupeeBiz platform. They are supplemented by the executed commercial agreement or order form between the Partner and TRUEHOST IT SERVICES PVT LTD., by the Developer Terms and by the Acceptable Use Policy. Where the executed agreement conflicts with these terms, the executed agreement prevails.

Onboarding and approval

Access to the platform follows a discovery conversation, commercial agreement, verification and technical enablement. RupeeBiz may decline an application, or withdraw an approval, at its discretion where the proposed use is outside our service scope, presents unacceptable risk, or cannot be verified.

Sandbox access granted for evaluation does not by itself create a right to production access.

Verification and KYC obligations

The Partner shall, before enablement and thereafter on request, provide:

• proof of incorporation or registration and details of its business activity;
• statutory registrations applicable to it, and identification of its authorised signatories;
• bank account details for settlement, together with supporting evidence;
• details of the platform, app or website on which the services will be presented.

The Partner shall:

• ensure the information supplied is true, complete and kept current, and notify us promptly of any material change, including a change of control, business model or settlement account;
• carry out its own customer due diligence on its end customers to the extent required by law applicable to it;
• co-operate with periodic re-verification and with any request for information made by an operator, biller or authority.

The services

RupeeBiz provides infrastructure that allows the Partner to offer everyday transactional services — principally mobile and DTH recharge and utility bill payments, and FASTag where supported — inside the Partner's own platform, through an embedded app experience, an instant web experience or a direct API integration.

The catalogue of supported operators, billers and categories is determined by the upstream providers available to us and may change. RupeeBiz does not guarantee the continued availability of any particular operator, biller or category.

Integration obligations

The Partner shall:

• integrate in accordance with the documentation and any integration guidance we provide, and complete the agreed test cases in sandbox before going live;
• display transaction status, amounts and any charges accurately to its end customers, and not present a transaction as successful before a success response has been received;
• present required disclosures, terms and consents to its end customers on its own platform;
• not alter, mask or misrepresent responses returned by the platform;
• use the RupeeBiz name and marks only as permitted in writing, and remove them on termination;
• apply platform changes and version upgrades within the notice periods communicated to it.

Transaction handling

Each transaction is initiated by the Partner on behalf of an end customer and is executed against the relevant operator or biller. RupeeBiz transmits the request, returns the status made available to it and maintains the transaction record.

• A transaction may return as successful, failed or pending. A pending transaction is resolved when the operator or biller confirms the final position.
• The Partner is responsible for the accuracy of the identifiers it submits, such as the mobile number, consumer number or account reference. Transactions completed against a valid but incorrect identifier supplied by the end customer may not be reversible.
• Transaction limits, velocity checks and risk controls may be applied and may be varied where necessary to protect the platform or comply with an upstream requirement.
• Reversals and refunds are handled as described in the Refund and Cancellation Policy.

Commercials, settlement and reconciliation

Pricing, commissions and any minimum commitments are set out in the executed commercial agreement and are not published on this page.

• Transactions are ordinarily funded from a prepaid balance maintained by the Partner. The Partner is responsible for maintaining sufficient balance; transactions may be declined where the balance is insufficient.
• RupeeBiz makes transaction reports available through the partner dashboard to support reconciliation.
• The Partner shall reconcile its records against those reports at the agreed frequency and raise any discrepancy within the agreed window. Discrepancies raised after that window may be harder to resolve because upstream providers apply their own dispute windows.
• Amounts recorded in the RupeeBiz system are the reference records for reconciliation, without prejudice to the Partner's right to dispute an entry.
• Taxes are payable as applicable, and each party is responsible for its own tax compliance.

Division of responsibilities

Responsibilities are divided as follows.

RupeeBiz manages

• Recharge and Bill Payment infrastructure and service-provider connectivity
• Transaction processing and transaction-status handling
• Service monitoring and backend operations
• Reports and reconciliation support
• Technical assistance and integration support

The Partner manages

• The customer relationship, platform experience and branding
• Offers, rewards, recommendations and cross-selling strategy
• Customer communication and its own core business growth
• First-line support to its end customers

Shared

• The customer-support process and escalation path
• Communication about failed transactions
• Campaign design, performance review and service improvement

The Partner is the point of contact for its end customers. RupeeBiz supports the Partner's support team; it does not deal directly with the Partner's customers unless separately agreed.

Support and service communication

Support is provided through the channels notified to the Partner. Planned maintenance is notified in advance where practicable; unplanned disruption, including upstream operator or biller downtime, is communicated as soon as reasonably possible. RupeeBiz does not publish an uptime commitment on this page.

Compliance and audit

The Partner shall comply with all laws applicable to its business and to the services it offers, including those relating to consumer protection, data protection, anti-money-laundering and taxation. The Partner shall provide reasonable co-operation and information where an operator, biller, auditor or authority requires it in connection with the services.

Suspension

RupeeBiz may suspend the services, in whole or in part and with or without prior notice where the circumstances require, if:

• there is a reasonable suspicion of fraud, misuse or a breach of the Acceptable Use Policy;
• the Partner's balance is insufficient or a payment is overdue;
• a legal, regulatory or upstream requirement obliges us to suspend;
• continuing the services would present a security risk to the platform or to other partners.

We will inform the Partner of the reason for suspension and of what is required to restore service, unless prevented by law.

Term and termination

The engagement continues for the term stated in the executed agreement. Either party may terminate for convenience on the notice period stated there, and either party may terminate immediately for material breach that is not remedied within a reasonable cure period, or on insolvency of the other party.

On termination:

• access to the production environment and credentials ceases;
• the Partner shall remove RupeeBiz marks and any embedded experience from its platform;
• the parties shall complete reconciliation and settle amounts due;
• records shall be retained for the period required by law and by the retention terms in our Privacy Policy.

Confidentiality

Each party shall keep confidential the non-public information disclosed by the other, including commercial terms, technical documentation, credentials, transaction data and roadmaps, and shall use it only for the purposes of the engagement. The obligation does not apply to information that is public through no breach, was already lawfully held, is independently developed, or must be disclosed by law — in which case the disclosing party shall be notified where permitted. Confidentiality survives termination.

Indemnity and liability

The Partner shall indemnify RupeeBiz against claims, losses and costs arising from its breach of these terms, its misuse of the platform, the content and conduct of its own platform, or its infringement of any law or third-party right.

Neither party is liable for indirect or consequential loss. Any aggregate liability cap is as stated in the executed commercial agreement. Neither party is liable for failure caused by events beyond its reasonable control, including failures of telecom operators, billers, banks, payment systems or public infrastructure.

Governing law

These terms are governed by the laws of India, with jurisdiction as stated in the executed agreement or, failing that, the courts at [city to be confirmed], Maharashtra.