Monto

Client Snapshot

• Client: Monto — fintech enabling employees to access earned wages on demand via a mobile-first experience.
• Industry: Fintech / Earned Wage Access (EWA)
• Development: 2021–2023
• Team Size: 6 (Architect / Backend / Frontend / UX / PM)
• Services: Full Product Build + Ongoing Development
• Stack: Ruby on Rails · PostgreSQL · Redis · Ionic (Angular) · AWS (EC2, RDS, S3, CloudFront)
• Post-launch: 10+ enterprise clients · 10,000+ employees onboarded · Y Combinator

‍

The Problem

A transactional fintech product lives or dies by data consistency, payment reliability, auditability, and user trust. Monto needed to:

• Deliver a production-grade MVP fast while building a foundation that could sustain enterprise onboarding and high-frequency usage without a rewrite.
• Implement robust financial workflows (disbursement + transaction lifecycle + reconciliation) where failures can't be “best effort.”
• Operate with a lean build pod while maintaining engineering discipline: async processing, idempotency, retries, and clean separation of domain modules.

‍

The Solution

Axented operated as Monto's product engineering team, owning architecture, backend, mobile delivery, cloud infrastructure, and the transactional integration layer required to move money reliably. We implemented Monto's core product as modular, production-grade subsystems — each designed for correctness, observability, and scalability.

A) Onboarding

• Employer onboarding workflows and employee enrollment flows.
• Configuration of organizational rules, eligibility, and initial operational parameters for wage access.

B) Payroll Cycle Ingestion

• Ingestion pipeline for payroll cycle data to support eligibility, earned wage computation, and schedule-aware availability.
• Queue-based async background processing to manage periodic/batch operations safely and predictably.

C) Ledger & Reconciliation

• Ledger-style records and reconciliation workflows ensuring traceability of earned wage operations and payouts.
• Designed for auditability: aligning platform state with payment execution state, supporting reprocessing paths when external events fail or arrive out of order.

D) Notifications

• Event-driven notifications tied to transaction and onboarding lifecycle milestones — improving transparency and reducing support burden.

E) Payment Disbursement

• Disbursement orchestration integrated with STP, engineered to be resilient under partial failures.
• Patterns for retries, error classification, and safe recovery without duplicating payouts.

F) Payment Transactions

• Transaction lifecycle management (creation → processing → confirmation/settlement states).
• Built for idempotent execution and consistent state transitions in a real-world payment ecosystem.

‍

Tech Stack & Infrastructure

• Backend: Ruby on Rails + PostgreSQL (system of record) + Redis (caching, async job orchestration)
• Mobile: Ionic (Angular) hybrid app for iOS/Android with unified codebase
• Cloud: AWS — EC2 (compute), RDS (managed PostgreSQL), S3 + CloudFront (assets + global delivery)
• Integration: STP payment layer with idempotency keys, retry strategy, and failure-mode handling

‍

Results

• MVP delivered in 10 months: from zero to a working platform capable of onboarding employers and employees and executing core wage access workflows.
• Scaled adoption: ramped 10 major enterprise clients and onboarded 10,000+ employees to the apps.
• Growth-ready engineering foundation: continued building through 2021–2023 (post-MVP) without needing a platform rewrite — supporting versioned releases and feature expansion.
• Execution under high stakes: sustained delivery velocity through key growth milestones, including Y Combinator, balancing speed with reliability in a trust-sensitive fintech environment.

‍

KPIs

10 months — MVP delivered from zero to production-ready platform

10,000+ — Employees onboarded to the EWA platform

10+ — Enterprise clients ramped post-launch

‍

Team & Delivery Model

Architect / Tech Lead: System architecture, payment integration strategy, engineering standards, infrastructure direction.

Backend Engineer: Rails development, data modeling, background processing, reconciliation workflows.

Frontend Engineer: Ionic/Angular hybrid app delivery, UX implementation.

UX/UI Designers: User research synthesis, end-to-end user flows, wireframes and high-fidelity UI, design system/components, interactive prototyping, and UX specs/handoff to engineering.

Project Manager (PM): Delivery planning and sprint orchestration, backlog prioritization, cross-functional coordination, timeline and scope control, risk/issue management, and release governance.

• Operating model: Iterative delivery with continuous prioritization, incremental releases, and tight client collaboration to keep engineering aligned with GTM needs.

‍