Rules & compliance
Payments infrastructure at fintech scale
Pratyank’s work at Clearco, before PlainSpoken.
Payment systems serving 5,500+ businesses in 20+ countries, an audit trail for payment activity, a $2.5M payment bug fixed so it couldn’t recur, and 30% faster API and database runtime.
- Businesses served in 20+ countries
- 5,500+
- Payment bug traced and fixed so it couldn’t recur
- $2.5M
- Faster API and database runtime
- 30%
The situation
Clearco funds e-commerce businesses and collects repayment from their revenue. Payments touch real money across many countries, so correctness, auditability and rate limits all matter. Clearco also carries privacy (PIPEDA and CPRA), AML and sanctions, and seven-year record-retention obligations, and its US repayments run over ACH under NACHA rules.
What was hard
A critical bug put $2.5M in payments at risk. Rate limiting was misbehaving across 600+ accounts. And analytics and ML teams needed clean, timely event data without slowing the payment path.
What Pratyank did
- Designed a TypeScript/NestJS distributed payment system with REST APIs.
- Built an audit system so payment activity could be traced and reviewed, supporting SOC 2 controls and seven-year record retention.
- Built ACH payment flows under NACHA rules, and handled card and banking data within PCI DSS scope.
- Built event-driven async workflows with Kafka, BullMQ and GCP Pub/Sub, feeding BigQuery for analytics and ML-driven financial workflows.
- Traced and fixed the $2.5M payment bug by refactoring and modularizing the code so the failure class could not recur.
- Fixed rate limiting across 600+ accounts and tuned APIs and queries.
What changed
Payments ran reliably for 5,500+ businesses in 20+ countries. API and database runtime improved 30%, and the data platform got a dependable event stream.
Bring us in when you move money, need payment flows that are correct under load, or are untangling a risky legacy payments codebase.