Octopus Payments Platform - Cooperative Collections
Built and launched a cooperative-focused payments product handling service collections, wallet flows, OTP verification, and settlement logic in active production.
June 1, 2024 · 6 min
At a glance
- Outcome
- About 1,000 daily service-collection operations in active cooperative contexts
- Ownership
- Owned architecture, Android and Flutter flows, and the settlement logic behind daily collections.
- Timeline
- Jan 2017 - Jun 2024
- Stack
- Flutter · Android · Firebase · REST APIs · Twilio SMS · OTP Verification
Impact metrics
- ~1,000 service-collection operations per day
- Launched in two credit cooperatives
- Commission and settlement logic automated in production
Why this matters
This case shows payment workflow design, third-party integrations, and product trust under real daily transaction volume.
Context
Octopus was built at V@COMM to help credit cooperatives run service collections with clear reconciliation and daily operational visibility.
The platform was deployed in two cooperatives (El Progreso and San Martin) and supported telecom collection flows, including ENTEL recharges and postpaid payments.
Problem
Cooperative operators needed a reliable way to process high-volume collections while keeping settlement, commissions, and daily reconciliation accurate.
Most workflows were fragmented across manual steps, which increased operational risk and delayed reporting.
Constraints
- Flows had to work under real cash-collection pressure and long daily operation windows.
- Service-payment integrations required OTP and SMS verification reliability.
- Operators needed printable receipts directly from Android devices.
- Commission and settlement logic had to be auditable by cooperative teams.
Approach
I led technical delivery across API integration, Android flows with printer support, and Flutter wallet capabilities.
The system integrated third-party services, Firebase, and Twilio-backed messaging for verification and operational notifications.
I also implemented settlement and commission rules so cooperative teams could track daily collections and earnings without manual reconciliation.
Results
- Approximately 1,000 daily service-collection operations in active production.
- Deployment across two credit cooperatives with recurring real-world usage.
- Telecom payment and recharge support delivered through stable operational workflows.
- Faster daily closeout through clearer commission and settlement calculation paths.
Learnings
- Payment products succeed when reconciliation is treated as a product requirement, not a back-office add-on.
- Receipt and verification reliability are trust-critical for operators and end users.
- Clear operational ownership boundaries reduce failure points in high-volume daily collection environments.