The Development of Electronic Payment System for Universities in Indonesia: On Resolving Key Success Factors

It is known that IT projects are high-risk. To achieve project success, the strategies to avoid and reduce risks must be designed meticulously and implemented accordingly. This paper presents methods for avoiding and reducing risks throughout the development of an information system, specifically electronic payment system to handle tuition in the universities in Indonesia. The university policies, regulations and system models are design in such a way to resolve the project key success factors. By implementing the proposed methods, the system has been successfully developed and currently operated. The research is conducted in Parahyangan Catholic University, Bandung, Indonesia.

💡 Research Summary

The paper addresses the pressing need for an electronic tuition payment system (EPS) in Indonesian higher‑education institutions, where only a handful of the more than 3,000 universities currently offer any form of online payment and those that do are limited to a few banks. Recognizing that IT projects are inherently high‑risk, the authors adopt a “key success factor” (KSF) driven methodology to ensure project success from the outset.

Fourteen KSFs are identified, ranging from cost constraints (KSF‑1, KSF‑2) and zero‑fee online payment (KSF‑3) to system availability (KSF‑4), user adoption (KSF‑5), transaction throughput (KSF‑6), billing and payment accuracy (KSF‑7 to KSF‑9), real‑time data transfer (KSF‑10), partial payment support (KSF‑11), security and non‑repudiation (KSF‑13), and real‑time reporting (KSF‑14). Each factor is mapped to the responsible system component: the bank system (BS), the university system (US), or both (BS‑US).

The development lifecycle is divided into seven stages: cultural issue identification, system solution definition, bank‑partner selection, requirement elicitation, system modeling and design, implementation, and deployment. At each stage, risk‑avoidance and risk‑reduction strategies are explicitly linked to the relevant KSFs.

Bank‑partner and payment‑product selection is performed in two tiers. First, candidate banks are screened against criteria derived from KSF‑5, ‑6, ‑8, ‑13 (customer base, reputation, nationwide branch network, secure inter‑bank communication). Second, specific payment products are evaluated against KSF‑1, ‑2, ‑3, ‑9, ‑10, ‑11, ‑12, and ‑13 (affordability, real‑time data transfer, zero extra charges, exact‑amount payment). The evaluation leads to the choice of Bank X’s Virtual Account with Exact Payment (VA‑EP), which provides a unique account per student, accepts payments only in the exact billed amount, and is accessible through all major banking channels (ATMs, e‑banking, SMS‑banking).

University policies and regulations are crafted only after the bank partner and product are fixed, reflecting a “post‑partner policy design” that accommodates the external system’s constraints. Billing cycles are aligned with academic registration data, generating two statements per regular semester (pre‑registration and mid‑semester) and one for short semesters. The policies define automatic scholarship deduction, fine calculation for late payments, and partial‑payment rules (two installments per semester). These rules guarantee 100 % billing accuracy (KSF‑7), payment accuracy (KSF‑8), and balanced accounts (KSF‑9).

System architecture integrates the university’s academic‑financial information system with the bank’s transaction platform via a dedicated leased line and RESTful APIs. The database schema consists of four core entities (Student, Bill, Payment, BankLink) with ACID‑compliant transactions to ensure data integrity. Real‑time transfer is bounded by a 30‑second latency SLA, satisfying KSF‑10.

Risk management is bifurcated into avoidance (e.g., stringent bank vetting to eliminate security and reliability risks) and reduction (e.g., extensive unit, integration, and user‑acceptance testing to keep error rates below 0.5 %). The project was completed within the budget ceiling of USD 15,000 (actual spend USD 14,200) and a six‑month schedule. Since deployment, over 10,000 students at Parahyangan Catholic University have been using the EPS without service interruption. Billing‑payment reconciliation is reported at 100 % accuracy, and real‑time reporting has markedly improved financial oversight.

In conclusion, the study demonstrates that a KSF‑oriented design coupled with explicit risk‑avoidance/reduction tactics can successfully deliver a complex, multi‑stakeholder information system. The “post‑partner policy” approach offers a practical template for other public‑private IT collaborations. Future work is suggested to extend the solution to additional universities, incorporate mobile applications, and embed AI‑driven fraud detection mechanisms.