Payment Module Development Challenge

Development of a Reusable Payment Integration Module for I-STEM Facility Booking Records (FBR).

1. Background

The Indian Science Technology and Engineering facilities Map (I-STEM) facilitates access to scientific and research infrastructure available across participating institutions in India.

Through the Facility Booking Record (FBR) mechanism, users can initiate requests to access equipment and research facilities hosted by participating institutions.

Different institutions may follow different payment procedures depending on their administrative structure, financial policies and authorised payment gateway or financial management systems.

There is an opportunity to develop a reusable integration approach that enables institutions to connect their existing payment systems with the I-STEM FBR workflow through standardised APIs.

2. Problem Statement

How can a reusable, secure and configurable payment integration module be developed to enable participating institutions to retrieve authorised Facility Booking Records from I-STEM, process payments through their respective institutional payment systems and communicate verified payment transaction statuses back to the I-STEM portal through APIs?

The proposed solution should accommodate variations in institutional payment workflows while ensuring reliable communication, transaction traceability, payment-status reconciliation and compatibility with I-STEM's approved API specifications.

3. Objectives

The objective of this challenge is to develop a reusable software module that:

  • Retrieves authorised FBR details from I-STEM through approved APIs.
  • Integrates with institutional payment gateways or financial systems.
  • Facilitates payment processing according to institutional requirements.
  • Communicates verified payment-status updates to I-STEM.
  • Maintains transaction references and reconciliation records.
  • Handles payment failures, duplicate notifications and transaction exceptions.
  • Provides implementation documentation, source code and SOPs.

4. Functional Requirements

The proposed solution should address the following functional requirements:

  1. FBR Integration: Retrieve and validate the relevant Facility Booking Record using the approved I-STEM API interface.
  2. Payment Initiation: Enable payment initiation through the institution's authorised payment gateway or financial system.
  3. Payment Processing: Support the institution's applicable payment workflow, including transaction reference generation and confirmation.
  4. Status Communication: Send authenticated payment-status updates to I-STEM through approved APIs.
  5. Transaction Tracking: Maintain unique transaction identifiers and corresponding FBR references.
  6. Failure Management: Handle failed, pending, timed-out and unsuccessful payment transactions.
  7. Reconciliation: Support transaction reconciliation, duplicate notifications and applicable refund or reversal scenarios.
  8. Status Synchronisation: Ensure that payment information communicated to I-STEM is consistent with verified institutional records.

5. Technical and Security Requirements

The proposed implementation should incorporate the following:

  • Secure API authentication and authorisation.
  • Encrypted communication using HTTPS.
  • Signed status callbacks or equivalent approved verification mechanisms.
  • Unique event identifiers and idempotency controls to prevent duplicate processing.
  • Timestamp validation and replay protection.
  • Secure management of configuration parameters and credentials.
  • Appropriate error handling, logging and reconciliation mechanisms.
  • Separation of testing and production environments.

6. Expected Deliverables

Participants are expected to submit the following:

01. Source Code
Complete source code of the developed payment integration module.
02. Architecture
System architecture and integration workflow diagram.
03. API Documentation
API integration documentation, request and response specifications.
04. Installation Guide
Installation, configuration and deployment instructions.
05. SOP
Standard Operating Procedure for implementation and operation.
06. Test Cases
Tests for successful, failed, pending and duplicate transactions.
07. Demonstration
Demonstration of the integration using a sandbox environment.
08. Dependencies and Licensing
README, technology stack, third-party dependencies and applicable licence information.

7. Expected Outcome

The intended outcome is a reusable and configurable payment integration solution that can be adapted by different participating institutions with minimal redevelopment, subject to their respective technical, financial, security and administrative approvals.

Suitable contributions may be documented and showcased through the I-STEM Code Exchange Hub to encourage institutional collaboration and software reuse.

8. Who Can Participate?

Students, research scholars, faculty members, software developers, technology professionals and participating institutions are encouraged to contribute to this challenge.

Individual contributors and teams may participate in accordance with the challenge guidelines and applicable institutional requirements.

9. Proposed Evaluation Criteria

Submissions may be assessed on the basis of:

  • Functional completeness and accuracy.
  • API integration quality and reliability.
  • Security and transaction-handling approach.
  • Configurability and reusability.
  • Documentation and implementation SOP.
  • Testing coverage and demonstration quality.
  • Maintainability and adaptability.

Final evaluation methodology and weightage will be communicated separately in the official challenge guidelines.

10. Important Participation and Responsibility Note

Participation in the I-STEM Code Exchange Hub is voluntary. Contributors must ensure that they have the authority to share submitted software and associated materials.

I-STEM will facilitate discovery and collaboration but will not guarantee the security, suitability, performance or regulatory compliance of contributed software.

Each adopting institution remains responsible for independently assessing, testing, approving, configuring, deploying and maintaining any adopted solution.

Participants must use synthetic FBR data and sandbox payment credentials for development and demonstrations. Production credentials and confidential financial information must not be included in submissions.