Monto

Client Snapshot

• Client: Monto — fintech enabling employees to access earned wages on demand via a mobile-first experience.
• Context: A transactional fintech product lives or dies by data consistency, payment reliability, auditability, and user trust. The platform had to scale quickly while remaining stable, maintainable, and integration-ready.
• Overview: Fintech · Full Product Build + Ongoing Development
• Client from: Mexico
• Development: 2021 - 2023
• Team Size: 6 (Architect/Backend/Frontend/UX/PM)
• Company Goals after Launch: 10+ enterprise clients · 10,000+ employees onboarded

‍

Project Overview

Built Monto’s end-to-end earned wage access platform—delivering an MVP in 10 months, then scaling the product in tandem through 2021–2023 during rapid growth milestones (including Y Combinator).

‍

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.

‍

Challenge

• 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.

‍

What We Delivered (Modules & Capabilities)

‍

‍We implemented Monto’s core product as modular, production-grade subsystems—each designed for correctness, observability, and scalability:

‍

‍A) Onboarding

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

B) Payroll Cycle Ingestion

• Ingestion pipeline for payroll cycle data to support eligibility, earned wage computation inputs, and schedule-aware availability.
• Background processing patterns (queue-based async) to manage periodic/batch operations safely and predictably.

C) Ledger & Reconciliation

• Ledger-style records and reconciliation workflows to ensure 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 to improve transparency and reduce support burden (status updates, confirmations, exception handling).
• Structured notification triggers tied to transaction and onboarding lifecycle milestones.

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 to support idempotent execution and consistent state transitions in a real-world payment ecosystem.

5) Technical Implementation (Stack & Architecture)Backend

• Ruby on Rails backend with PostgreSQL as the system of record.
• Redis for caching and background job orchestration/memory (async workloads, event handling, batch ingestion).
• Integration-layer hardening for payment flows (idempotency keys, retry strategy, failure-mode handling).

‍

Infrastructure

• Hybrid mobile application using Ionic (Angular) to support iOS/Android with a unified codebase and consistent experience.

‍‍Deployed on AWS using:

• ‍EC2 for compute
• ‍RDS for managed PostgreSQL
• ‍S3 + CloudFront for asset storage and global delivery
  
  • Built for practical scalability (environment separation, performance-aware asset delivery, and production deployment hygiene).

‍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 clients and onboarded 10,000+ employees to the apps.
• Growth-ready engineering foundation: continued building through 2021 and 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 YC), balancing speed with reliability in a trust-sensitive fintech environment.

‍

Team & Delivery Model

‍

Team (6-person pod):

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 (with iterative usability improvements across releases).

‍

Project Manager (PM): Delivery planning and sprint orchestration, backlog prioritization with stakeholders, requirements clarification, cross-functional coordination (design/engineering/client), timeline and scope control, risk/issue management, and release governance to ensure predictable execution.

‍

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

‍

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

‍

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

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

‍