01
Digital payment experience
A streamlined payment journey designed to help students and customers find their accounts and choose an available payment method.
GCashBankQR payments
Back to our work
Awonsa · Product development case study
Making payment management simpler.
Introducing InstiPays: a custom payment management platform designed to bring institutional collections, transaction visibility, and settlement workflows into a more connected digital experience.
Custom software
Payment workflows
Institution-focused
Explore the project
Project overview
One platform. Connected payment workflows.
InstiPays is a custom software project developed by Awonsa around the operational needs of institutions collecting payments. Its focus is to connect the payer experience with the administrative work behind collections, transaction monitoring, and settlement management.
Instead of treating payments as an isolated checkout step, the platform is designed to account for the wider process: identifying the right account, recording payment activity, and giving authorized teams tools to manage their operations.
Project type
Custom software
Business focus
Payment management
Primary audience
Institutions & finance teams
Development partner
Awonsa
The challenge
Payment collection involves more than accepting money.
A payment may be only one part of a much larger administrative process. Institutions also need to identify accounts, organize collections, monitor transactions, and keep financial records connected.
The operational questions
How can payers find the correct student or customer account?
How can finance teams review payment activity in one place?
How should collections and schedules be organized?
How can institutions monitor settlement-related information?
The solution
A payment platform shaped around the entire workflow.
InstiPays brings payer-facing payment journeys and institution management workflows into one platform concept. Each capability addresses a different part of the process, while keeping the overall experience connected.
02
Transaction visibility
A centralized workspace for reviewing payment activity, monitoring transaction statuses, and accessing payment records.
TransactionsPayment records
03
Collections management
Tools designed to organize collections, track payment schedules, and give finance teams a clearer view of outstanding payments.
CollectionsSchedules
04
Settlement workflows
A structured approach to monitoring settlement information and keeping payment activity connected to the institution receiving funds.
SettlementsReconciliation
05
Institution-centered management
A platform architecture designed around individual institutions, with company-scoped records and role-based access to operational data.
InstitutionsUser roles
06
Security-conscious architecture
Authentication, account permissions, and institution-level data boundaries are important considerations throughout the platform design.
AuthenticationAccess control
How it works
From account lookup to payment management.
The intended experience connects the payer's journey with the administrative tasks that follow a payment.
STEP 01
Find the account
The payer looks up the relevant student or customer account using its reference information.
STEP 02
Choose a payment method
The available payment options are presented as part of the intended payment experience.
STEP 03
Track the transaction
Payment activity can be reviewed through transaction records and the institution's management workspace.
STEP 04
Manage collections
Finance teams use centralized records to support collection monitoring and settlement-related workflows.
Architecture & engineering
Built with a focus on maintainability and clear data boundaries.
InstiPays uses a modern web application and API architecture. Its institution-centered design considers how user access, company-scoped records, payment activity, and backend operations fit together.
Keep the payment journey understandable for payers.
Give finance teams a centralized view of payment activity.
Organize data around the institution it belongs to.
Design workflows that can evolve with operational needs.
Application architecture
Conceptual overview
Frontend application
Next.js · React · Tailwind CSS
Backend API
Python · FastAPI · SQLAlchemy
Relational database
MariaDB / MySQL
Payment provider connectivity and institution-level controls are treated as distinct parts of the overall platform architecture.
Technology stack
Next.js
Web application framework
React
Interactive user interfaces
Python + FastAPI
Backend API development
SQLAlchemy
Database access and ORM
MariaDB / MySQL
Relational data storage
PayMongo
Payment provider integration approach
The thinking behind the product
Technology should fit the work. Not the other way around.
InstiPays reflects Awonsa's approach to custom software: understand the operational problem, organize the workflow, and build around the people who use the system.
Keep the payment journey understandable for payers.
01
Give finance teams a centralized view of payment activity.
02
Organize data around the institution it belongs to.
03
Design workflows that can evolve with operational needs.
04
The bigger picture
Better visibility.
Clearer workflows.
More connected operations.
The goal is to give institutions a more structured way to manage payment-related work—connecting the payer experience with the records and workflows their teams depend on.
Have an idea worth building?
Let's build a solution around your business.
Whether you're improving an existing process or building something entirely new, Awonsa can help you explore the right digital solution for your business.