KTJS — Cooperative Digital Ecosystem with Flutter Mobile App, Marketplace & Accounting

KTJS required a cooperative platform that went beyond internal administration. Members needed direct access to cooperative services from their smartphones, while administrators still required centralized operational control, approvals, transactions, and accounting.

The challenge was to unify the mobile member experience across multiple business domains: registration, membership, savings, wallet, digital products, marketplace, business opportunities, social services, notifications, and financial reporting.

Member services and cooperative operations involve many different workflows. Without one integrated platform, membership data, financial transactions, marketplace activity, social programs, and administrative processes can become fragmented across multiple channels and difficult to reconcile.

KTJS Mobile — Flutter App for Members

ORIZA developed KTJS as a multi-channel platform with the Flutter application as the primary member-facing front end. The app connects directly to the production API at https://ktjs.omediatek.web.id/api, keeping mobile activity synchronized with web-based operations.

Actual Flutter Application Screens

The following screens were captured directly from the KTJS Flutter build, not from mockups.

The mobile app supports the member journey from authentication and onboarding through transactions, marketplace services, and community features. Laravel provides the central business rules, security, approvals, and external integrations.

Verified KTJS Mobile Features

• Login, basic registration, OTP, account recovery, and account security.
• Member registration, membership agreement, onboarding, profile, and e-KTA verification.
• Member savings, mutations, deposits, monthly obligations, and savings reports.
• Wallet, top-up, transfer, withdrawal, and payout account profile.
• Digital products/PPOB, catalog search, favorites, inquiry, payment, and transaction history.
• Marketplace: catalog, cart, checkout, shipping, payment, orders, returns, and refunds.
• Member advertisements and chat.
• Business opportunities, proposals, participation, contributions, progress, and profit distribution.
• Charity programs and donations.
• Athlete Care: programs, donations, updates, expenses, and athlete records.
• Social campaigns, social accounts, tasks, points, leaderboard, and growth logs.
• Firebase-based push notifications.

Web Operations Platform

• Filament Admin for members, marketplace, wallet, PPOB, cashback, social, charity, athlete care, notifications, RBAC, and audit logs.
• A separate Accounting panel for chart of accounts, journals, period closing, reconciliation, trial balance, income statements, financial position, cash flow, SHU, and report exports.

• Laravel Sanctum for API authentication.
• Firebase Cloud Messaging for push notifications.
• Duitku and Komerce for payment flows.
• Digiflazz for digital-product catalog and transactions.
• OrizaShop payment/PPOB router for selected transaction integrations.
• Fonnte for WhatsApp communication.
• e-KTA validation against the official apps2.psht.or.id domain.
• Geolocation, NFC/mobile scanner, QR, WebView, image/file picker capabilities in Flutter where required by features.

Mobile + Backend Architecture

Flutter uses a centralized API client pointing to the KTJS production endpoints. Sensitive session/token data is stored using secure storage, while the backend enforces authentication and authorization with Laravel Sanctum and RBAC.

Operationally, Admin and Accounting are separated so member-service transactions and financial functions can be managed according to their respective responsibilities.

KTJS now has a unified digital foundation connecting the member experience on smartphones with administrative and financial processes in the backend. Mobile does not operate as a standalone system: data and transactions flow through the same business rules as the operational platform.

This architecture allows the cooperative to add services incrementally without creating disconnected applications for every need. This case study does not claim unverified ROI or growth figures.

Mobile: Flutter / Dart, Dio, flutter_secure_storage, Firebase Messaging, local notifications, geolocator, mobile scanner, NFC, QR, WebView.

Backend: PHP 8.4, Laravel 13.24, Laravel Sanctum 4.3, Filament 5.7.6, MySQL/Percona 8-compatible.

Integrations: Duitku, Komerce, Digiflazz, OrizaShop transaction router, Fonnte, Firebase.