Loading…
Topic
9 posts about Fintech. Every summary links to the original.
See the idea
Buy Now, Pay Later is a deferred-settlement trade-off: merchants gain conversion while underwriting, fraud, and collections risk move elsewhere. This diagram maps the benefit, the cost, and the condition that decides.
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
Newest first
Ridgeline, a cloud-native investment management platform, rebuilt its performance analytics layer after Postgres could not handle the scale of larger customers. The team evaluated Redshift, SingleStore, Trino over Iceberg, and a custom in-memory engine before choosing ClickHouse for its analytical performance and lower cost. They adopted ClickHouse Cloud on AWS, using separate organizations for staging and production and per-customer services, with assistance from ClickHouse engineers. Historical data lands in Apache Iceberg via a Spark pipeline and is queried through ClickHouse, while recent data is written directly into ClickHouse. The architecture enabled Ridgeline to serve customers 10x larger than before and more than double its live customer count.
Fintech companies handling savings, credit, and investments require customer service that builds trust and meets strict regulatory requirements. Intercom’s Fin AI agent, powered by large language models, uses existing knowledge content to automatically resolve over half of customer queries on average. Fundrise reported Fin handled over 50% of support cases within three months, while Sharesies achieved an almost 70% resolution rate over email in 12 weeks. Fin delivers real-time personalization by pulling live transaction data from external systems, supports over 45 languages with real-time translation, and scales during peak periods like tax season. It includes compliance safeguards such as automatic escalation of regulated activities to licensed agents and integration with KYC and AML processes.
Indian organizations in regulated industries are modernizing legacy data infrastructures with MongoDB to achieve scale and compliance. Physics Wallah, serving over 7 million students, built a compliant multi-tenant payment platform on MongoDB Atlas using ACID transactions, Change Streams for audit trails, and native search. Flipkart uses MongoDB Atlas for high-throughput writes and real-time payment aggregation during mega sales like The Big Billion Days, with seamless horizontal sharding. IBS Software scaled three mission-critical platforms, processing billions of records and millions of searches daily with sub-100ms API responses and 99.99% uptime, while iTravel Cruise achieves 100,000 TPS at 5ms latency. Companies like Kore.ai and PineLabs use MongoDB Enterprise Advanced for on-premises deployments requiring high availability, strict security, and low-latency transaction processing.
The post argues that financial-services AI adoption is widespread, but execution—not model capability or strategy—is determining who captures value in 2026. It attributes stalled pilots to fragmented legacy infrastructure, inconsistent data, weak lineage, and insufficient control for governed, real-time workflows such as fraud detection, pricing, and personalization. Firms advancing further treat data as a managed asset, embed governance in data and model pipelines, and align data, analytics, and AI teams around shared definitions, workflows, and metrics. The proposed remedy is a unified lakehouse environment combining storage, compute, governance, lifecycle management, orchestration, streaming, and AI workflows, with Unity Catalog providing centralized access control, lineage, and auditing. The conclusion is that by the end of 2026, firms that embed AI into operational decisioning at scale will pull ahead of organizations still running pilots.
First Block features Gerry Giacomán Colyer, Clara’s co-founder and CEO, discussing the company’s founding, rapid growth, and expansion of AI agents for finance operations across Latin America. Clara’s bank partner shut down only months after launch, prompting the team to secure direct issuer licenses with Visa and MasterCard in two weeks and build more robust infrastructure from the outset. The episode connects that resilience to product-led growth: a self-serve onboarding flow supported more than 20,000 customers across three countries, from pre-revenue startups to the Mexican Stock Exchange. The company is now applying its transaction data across Latin American businesses to a financial analyst agent that automates policy enforcement and approval workflows. It also covers the founding lesson from a previous company’s financial-tooling difficulties, early milestones, scaling decisions, and a roadmap across markets, alongside questions about efficiency, resilient infrastructure, and distinctive data advantages.
The post argues that startups should pursue asymmetric outcomes: bets with potentially large upside and limited, manageable downside, rather than optimizing for average advice or minimizing every risk. Drawing on the founders’ experience building Paribus and Ramp, it applies this principle to choosing a problem space, hiring, vendors, product development, and fundraising. An outsized seed round enabled Ramp to pursue financial services despite high barriers to entry, while early hiring favored exceptional, fast-growing people over candidates who matched every competency checklist. It also recommends testing scrappy vendors, listening to customer problems rather than proposed solutions, and selecting reputable investors with clean terms. Ramp’s counterexample is credit risk: because revenue is about 1% of lending, a mistake can cost roughly 100 times its reward, so threatening risks should be isolated from bolder bets.
Ramp documents seven engineering principles intended to codify how its teams build systems, make decisions, and collaborate as the company grows. The principles call for choosing technology according to each system’s context, moving aggressively on reversible decisions while treating durable interfaces cautiously, and aligning system models with customer concepts. They also favor opinionated product experiences, accepting duplication over a harmful abstraction while continuing to seek abstractions that reflect meaningful shared behavior. Rather than implementing requests literally, engineers investigate underlying needs, such as notifying a CFO instead of making approval a bottleneck, and break projects into small, independently prioritized chunks. These chunks can be owned by small teams called “pods,” while the principles remain adaptable rather than ironclad rules.
My summer at Ramp recounts a three-month internship at the financial automation startup, following an introduction to its mission, growth, and product. During the placement, the author standardized physical-card shipping data, improved accounting workflows, handled profile-picture and UX work, and resolved production issues while improving endpoint and application performance. The main project, Filtering and Renaming GL, let Ramp administrators control accounting-option visibility by cardholder department and rename cryptic options within Ramp. The internship also provided observations about fintech opportunity, Ramp's rapid growth, transparency, ownership-driven culture, and the speed-quality trade-off described as product velocity. The author planned to continue at Ramp part-time while entering the third year of college.
Financial software must round values when money cannot be transacted beyond two decimal places, creating precision loss and “hanging pennies.” The post demonstrates that rounding two percentage-based charges separately on $10.10 produces $0.53, while summing the unrounded amounts and rounding once produces $0.54; currency conversions can amplify the effect. Its eight recommendations include notifying stakeholders, using banker’s rounding, retaining maximum available precision in data types, applying one consistent method, marking rounding explicitly, consulting government standards, rounding only when required, and documenting rules for users. It identifies taxes, discounts, interest, distributed payments, shared liabilities, and rates as recurring sources of rational values in financial calculations. The conclusion is that rounding cannot be avoided in financial software, but teams can control where it occurs and how its consequences are handled.
The best engineering reads, once a week.
