Payment Policy

Payment Policy
Legal

Payment Policy

Product: Nexus School ERP
Operated by: Nexus ERP
Last Updated: August 12, 2026

This Payment Policy explains how payments made through Nexus School ERP are initiated, processed, recorded, refunded, and managed.

1. Scope

This policy applies to payments made through Nexus School ERP for services or fees configured by a school or institution.

It may cover:

  • School fees
  • Tuition fees
  • Admission fees
  • Examination fees
  • Transport fees
  • Hostel fees
  • Library fees
  • Activity fees
  • Other institutional charges
  • Nexus ERP subscription payments where applicable

2. Payment Gateway Integrations

Nexus School ERP may support integration with multiple payment gateways.

The available payment methods depend on:

  • School configuration
  • Country
  • Payment provider
  • Currency
  • Payment method
  • Regulatory requirements
  • Technical availability

Payment methods may include:

  • Credit cards
  • Debit cards
  • UPI
  • Net banking
  • Bank transfers
  • Digital wallets
  • Other methods supported by the selected payment gateway

3. Payment Processing

When a user initiates a payment:

  1. The applicable invoice or fee information is displayed.
  2. The user selects an available payment method.
  3. The user may be redirected to a payment gateway or secure payment interface.
  4. The payment provider processes the transaction.
  5. The payment provider returns the transaction result.
  6. Nexus School ERP records the transaction status.
  7. A receipt or payment confirmation may be generated.

4. Payment Information

Nexus ERP may receive:

  • Customer name
  • Transaction ID
  • Order ID
  • Invoice number
  • Amount
  • Currency
  • Payment status
  • Payment method
  • Payment date
  • Gateway reference
  • Refund information
  • Failure information

Payment providers may independently collect payment credentials.

Nexus ERP does not intentionally request users to provide OTPs, PINs, passwords, or CVV information directly to Nexus ERP employees.

5. Payment Authorization

A transaction is considered successful only when confirmation is received from the relevant payment provider or authorized payment system.

A payment showing as pending, failed, cancelled, or incomplete should not be considered successfully completed.

6. Failed Transactions

A transaction may fail because of:

  • Insufficient funds
  • Bank rejection
  • Incorrect payment information
  • Payment gateway errors
  • Network problems
  • Authentication failure
  • Bank downtime
  • User cancellation
  • Fraud/security controls

Users should not repeatedly retry a transaction if their bank account has already been debited.

They should first verify the transaction status.

7. Duplicate Payments

If a user believes they have made a duplicate payment, they should contact the school or payment support team with:

  • Transaction ID
  • Order ID
  • Amount
  • Date
  • Payment reference

The school or payment provider may investigate the transaction.

8. Refunds

Refunds are subject to the school's applicable refund policy and the payment gateway's processing rules.

Nexus ERP does not independently determine whether a school fee should be refunded unless specifically agreed with the school.

Where a refund is approved:

  • The refund may be initiated through the payment gateway.
  • Processing time may depend on the payment provider and bank.
  • The original payment method may be used for the refund where supported.
  • Gateway or transaction charges may be treated according to the school's refund terms and applicable law.

9. Payment Gateway Charges

Payment gateway providers may charge:

  • Transaction fees
  • Processing fees
  • Taxes
  • Settlement charges
  • Refund charges
  • Other applicable fees

Responsibility for such charges will depend on the agreement between the school, Nexus ERP, and/or payment provider.

10. Currency

Payments may be processed in currencies supported by the selected payment gateway and school configuration.

Any currency conversion charges may be imposed by banks or payment providers.

11. Taxes

Applicable taxes may be added to invoices or payments according to applicable law.

Tax treatment may vary by country, school, service, and transaction type.

12. Payment Security

Payment processing may occur through secure third-party payment providers.

Nexus ERP uses reasonable security measures to protect payment-related information handled by its Platform.

Users should never provide:

  • OTPs
  • PINs
  • CVVs
  • Passwords
  • Banking credentials

to anyone claiming to represent Nexus ERP or the school.

13. Payment Disputes

For school-related payments, users should normally contact the school first.

For payment processing issues, users may also contact the applicable payment provider.

For Nexus ERP subscription payments, users may contact:

Payment Support: [Payment Support Email]

14. Chargebacks

Where a payment is reversed or charged back by a bank or payment provider, the related invoice may be marked unpaid or reversed.

The school or Nexus ERP may request supporting information concerning the transaction.

15. Settlement

For school fee collection, settlement of funds may occur directly between the payment provider and the school/merchant according to their respective arrangements.

Nexus ERP does not necessarily hold or control funds collected on behalf of schools.

16. Fraud Prevention

Transactions may be subject to automated fraud detection and security checks.

A transaction may be declined, delayed, or reviewed where suspicious activity is detected.

17. Third-Party Payment Providers

Payment providers operate independently and have their own:

  • Privacy policies
  • Terms
  • Security controls
  • Refund procedures
  • Transaction limits
  • Processing timelines

Users should review the relevant provider's policies.

18. Payment Records

Nexus School ERP may retain transaction records for:

  • Accounting
  • Reconciliation
  • Reporting
  • Customer support
  • Fraud prevention
  • Legal compliance
  • Dispute resolution

Retention is subject to applicable law and contractual requirements.

19. No Guarantee of Bank or Gateway Availability

Nexus ERP cannot guarantee continuous availability of third-party banking or payment services.

A payment may fail because of circumstances outside Nexus ERP's control.

20. Policy Changes

This Payment Policy may be updated when payment methods, regulations, technology, or business practices change.

The latest version will be published through the applicable Nexus ERP website or Platform.

21. Contact

Nexus ERP
Product: Nexus School ERP

Payment Support: payment@ambastunity.org
General Support: support@ambastunity.org
Website: nexus.ambastunity.org

Registered Address: Delhi
Country: India

For school-managed accounts, users may also contact their school or educational institution.

© 2026 Nexus ERP. All Rights Reserved.

     Security Note: All sensitive student data is encrypted at rest and in transit.