Station 04 · The money floor

Software where every paisa reconciles.

Payments, wallets, ledgers and the APIs that connect them. Built audit-logged and compliance-aware — boring in exactly the way money software should be.

Scope a fintech build
Capabilities

What we build on the money floor.

PAYMENTS

Payment orchestration

One integration, many rails: cards, UPI, netbanking, wallets. Smart routing between gateways, automatic retries, graceful failure states.

RazorpayPayUCashfreeStripe
UPI

UPI journeys

Collect flows, intent flows, dynamic QR, autopay mandates — with the edge cases (timeouts, pending states, duplicate callbacks) engineered, not ignored.

Dynamic QRAutopayIntent / Collect
LEDGERS

Wallets & ledgers

Double-entry ledgers where balances are derived, never stored loose. Wallets, credits, refunds, holds — every state change journaled and reversible.

Double-entryIdempotentAudit log
RECON

Settlement & recon

Dashboards that match gateway settlements to orders to bank statements — and surface every mismatch with a paper trail, daily.

T+1 reconMIS reportsAlerts
SUBSCRIPTIONS

Billing engines

Plans, proration, trials, dunning, GST-compliant invoicing — subscription mechanics that survive real customers doing weird things.

RecurringGST invoicesDunning
ONBOARDING

KYC & onboarding flows

Document capture, verification API integrations, status tracking and manual-review queues — onboarding that converts without cutting corners.

eKYC APIsReview queuesConsent logs
API request logs streaming on a wall screen beside an architecture diagram
THE ENGINE ROOM — LIVE REQUEST LOGS, STAGING CLUSTER
API development

APIs other developers thank you for.

Whether it's the backbone of your product or a partner-facing platform, we design APIs as products: predictable, versioned, documented and observable.

  • REST & GraphQL — consistent resources, real pagination, honest error codes.
  • Auth done right — API keys, OAuth2, JWT rotation, scoped permissions.
  • Rate limits & quotas — per-plan throttling with clear headers, not mystery 429s.
  • Docs & sandbox — OpenAPI specs, a try-it console, webhooks with replay.
  • Observability — request logs, latency dashboards, alerting from day one.
Integrations

If it has an endpoint, we've probably wired it.

  • Payment gateways RAZORPAY · PAYU · STRIPE
  • WhatsApp Business API MESSAGING
  • SMS & email providers MSG91 · SES
  • Accounting software TALLY · ZOHO
  • Logistics & shipping SHIPROCKET · DELHIVERY
  • Maps & geolocation GOOGLE · MAPBOX
  • KYC & identity APIs AADHAAR · PAN · GST
  • ERP & inventory systems SAP-ADJACENT · CUSTOM
  • Analytics & events GA4 · MIXPANEL
  • AI model APIs CLAUDE · GPT · WHISPER
  • Banking & payout APIs PAYOUTS · VAN
  • Marketplace channels AMAZON · SHOPIFY
Doctrine

Rules the money floor never breaks.

RULE 1

Idempotent everything

Retries can't double-charge. Every mutation carries a key; duplicates are no-ops, by design.

RULE 2

Derived balances

Balances are computed from journaled entries. If the ledger and the balance ever disagree, the ledger wins.

RULE 3

Append, never edit

Corrections are new entries, not edits. The audit trail is complete or it isn't an audit trail.

RULE 4

Reconcile daily

Orders vs gateway vs bank — matched every day, with mismatches alerting a human before customers notice.

Move money with software that balances.

Scope a fintech build See all services