These Terms and Conditions govern access to and use of Nirmaata Reconciliation and Provisioning System, including hosted payment pages, payment links, reconciliation workflows, transaction status services, settlement references, payout records, reporting, webhook notifications, support workflows, and related operational tools.
1. Acceptance of Terms
By accessing NRPS, integrating with our APIs, using merchant credentials, submitting payment references, or using the management portal, you agree to follow these terms. If you use the services on behalf of an organization, you confirm that you are authorized to bind that organization.
2. Service Scope
NRPS provides technology and operational services for payment request creation, payment page generation, reference submission, automated confirmation where enabled, reconciliation, status reporting, settlement tracking, payout reference recording, webhook delivery, and support handling.
NRPS does not replace the merchant's obligation to deliver goods or services, handle customer communication, maintain accurate records, comply with applicable laws, or resolve customer disputes.
3. Merchant Responsibilities
- Provide complete and accurate merchant, bank, business, webhook, contact, and compliance information.
- Keep API credentials, webhook secrets, login credentials, and whitelisted access details confidential.
- Use only authorized systems, domains, IP addresses, and users for accessing NRPS services.
- Verify transaction status before provisioning orders or services in the merchant system.
- Maintain correct return URLs, webhook endpoints, customer support channels, and operational contacts.
- Notify Nirmaata promptly about suspected credential misuse, unauthorized access, disputes, or security concerns.
4. Authorized Users and Access
Merchants and platform users may receive role-based access based on assigned permissions. Each user is responsible for actions performed through their account. Shared accounts, unauthorized access, credential resale, and attempts to bypass permissions are prohibited.
5. Payment Requests and Reconciliation
Payment requests must contain valid order details, supported amounts, customer information, and allowed payment methods. Manual confirmations depend on submitted references, proof where available, and operational review. Automated confirmations depend on provider responses and system matching.
Merchants must not submit duplicate, false, misleading, negative, manipulated, or unauthorized requests. Nirmaata may reject, fail, hold, review, or investigate requests where data is invalid, suspicious, expired, duplicated, unsupported, or inconsistent.
6. Webhooks and Status Updates
NRPS may send webhook notifications to configured merchant endpoints. Merchants are responsible for keeping webhook URLs available, secure, and capable of idempotent processing. Webhook delivery may be retried according to operational policy, but merchants should always verify status using the available status APIs before final provisioning.
7. Settlements, Payouts, and Fees
Settlement and payout records in NRPS are operational references based on verified transactions, applicable fees, and platform processes. Merchant discount rates, charges, adjustments, holds, reversals, or deductions may apply as per commercial agreement, configuration, or operational policy.
8. Prohibited Use
Users must not misuse NRPS for unlawful activity, unauthorized collections, fraudulent submissions, credential sharing, abusive traffic, vulnerability testing without permission, false support claims, duplicate reference abuse, or any activity that may harm customers, merchants, providers, banks, Nirmaata, or platform integrity.
9. Data, Records, and Audit Trail
NRPS may retain logs, API requests, webhook attempts, provider responses, user actions, support messages, transaction records, reconciliation records, and audit entries for security, dispute handling, reporting, compliance, and operational continuity.
10. Availability and Maintenance
We aim to keep services reliable and available, but access may be affected by scheduled maintenance, emergency maintenance, provider availability, hosting issues, banking restrictions, network failures, incorrect configuration, or events beyond our control. Critical issues should be reported to support immediately.
11. Security
NRPS uses safeguards such as role-based access, permission controls, hashed passwords, HTTPS where configured, credential controls, audit logs, webhook signing, and operational monitoring. Users must also apply reasonable security practices within their own systems.
12. Support and Disputes
Support tickets may be raised for failed transactions, refunds, reconciliation issues, technical incidents, and operational questions. Users must provide accurate references such as request ID, order ID, UTR or RRN, amount, date, screenshots, or other details required to investigate.
13. Confidentiality
Pricing, credentials, routing information, provider configuration, operational procedures, webhook secrets, reports, and merchant-specific data must be treated as confidential unless disclosure is required by law.
14. Limitation of Liability
To the maximum extent permitted by law, Nirmaata is not liable for indirect, incidental, consequential, punitive, or special losses, including loss of revenue, loss of business, failed downstream provisioning, provider outages, incorrect merchant configuration, or third-party system failures. Any liability is limited according to the applicable written agreement.
15. Changes to Services or Terms
We may update features, operating rules, security requirements, fees, integrations, documentation, or these terms from time to time. Continued use after changes are published or communicated means the updated terms are accepted.
16. Contact
For service questions, support, or legal notices, contact support@nirmaata.com.