CASE STUDY 03 / 03

Autopay EG

A founder-built payment-confirmation SaaS that turns external Vodafone Cash and InstaPay evidence into reliable merchant invoice state.

System: Payment-confirmation automation SaaS
Ownership: Founder & Full-Stack Product Engineer
Technical difficulty: Concurrency-safe payment-event matching and idempotent notification
Production proof: Production Payment automation platform

A founder-built Egyptian payment automation platform that detects and matches Vodafone Cash and InstaPay transfers to merchant invoices.

01 / SITUATION

The operating context.

Buyers transfer money in an external wallet application. Merchants still need reliable detection, matching, confirmation, and notification inside their own systems.

Autopay EG is a founder-built Egyptian payment-automation SaaS that automates transfer detection, invoice matching, confirmation, and merchant notification. It supports Vodafone Cash and InstaPay through a combination of hosted invoices, Android payment-event ingestion, merchant APIs, webhooks, dashboards, and commerce integrations.

Buyers complete the payment in the external wallet application, while Autopay automates the merchant-side confirmation workflow. The product is best described as a merchant payment-detection and confirmation automation SaaS.

02 / OWNERSHIP BOUNDARY

What I owned, explicitly.

Role: Founder & Full-Stack Product Engineer
Ownership model: founder built
Responsibility boundary: Concurrency-safe payment-event matching and idempotent notification
Project status: live

03 / CONSTRAINTS

What made the system difficult.

Autopay does not hold funds or control the external Vodafone Cash or InstaPay transfer.
Android SMS or notification evidence can be delayed, duplicated, or incomplete.
Concurrent evidence must not confirm one invoice twice or corrupt merchant state.
Merchant APIs, signed webhooks, WooCommerce, and Shopify need deterministic outcomes.

04 / SYSTEM DECISIONS

Boundaries chosen for a reason.

Authenticate evidence at ingestion

Problem: Mobile-detected payment evidence crosses an untrusted network boundary.
Boundary: The Android application submits evidence through secure HMAC ingestion.
Why it mattered: The matching workflow starts from authenticated application evidence rather than an assumed bank API.

Separate matching from invoice state

Problem: External evidence is uncertain while merchant invoice state must remain deterministic.
Boundary: A matching and risk engine evaluates evidence before changing invoice state.
Why it mattered: Duplicate or conflicting evidence cannot become an unchecked confirmation path.

Deliver outcomes asynchronously

Problem: Merchant systems and commerce plugins are not always available at confirmation time.
Boundary: Redis and Horizon workers deliver signed webhooks and integration updates.
Why it mattered: Retries and idempotent notification remain outside the core matching transaction.

05 / FAILURE PATHS

Failure belongs in the architecture.

Duplicate evidence is handled through concurrency-safe matching and idempotent state changes.
Delayed callbacks remain queue-backed rather than blocking invoice confirmation.
Signed webhooks let merchants verify notification authenticity.
Failed merchant delivery can be retried without claiming a second payment.

06 / SYSTEM ANATOMY

Read the boundaries before the components.

Autopay EG architecture overview — Public architecture overview of Android evidence detection, HMAC ingestion, matching, invoice state, queues, signed webhooks, and merchant integrations.

07 / PRODUCTION EVIDENCE

Only the proof the public record supports.

Production: Payment automation platform; Supports Vodafone Cash and InstaPay detection, matching, webhooks, and commerce integrations.

08 / WHAT CHANGED

The capability left behind.

The product automates merchant-side confirmation while preserving the distinction between payment evidence and external fund transfer.

09 / TECHNICAL STACK

Technology with a job to do.

Laravel 11: Evidence ingestion, matching, invoice state, APIs, and signed webhooks.
Vue 3: Supporting production technology.
Inertia.js: Supporting production technology.
PostgreSQL: Durable merchant, invoice, and payment-event state.
Redis: Horizon queues, retries, and notification delivery.
Kotlin: Android SMS and notification evidence detection.
WooCommerce: Merchant checkout and confirmation integration.
Shopify: Merchant commerce integration.
Docker: Supporting production technology.