These three products solve real problems that most teams don't know Stripe already handles: until they've half-built a worse version themselves.
Zeeshan
Founder · Published
We repeatedly see teams building custom infrastructure for a problem Stripe already solves, simply because the relevant product wasn't on their radar during initial integration planning. Identity, Financial Connections, and Terminal are the three we point to most often. Each replaces a category of custom work most teams underestimate the cost of.
If your product needs KYC-style identity verification (marketplaces onboarding sellers, fintech products with regulatory requirements), Stripe Identity handles document capture, liveness checking, and verification status: instead of integrating a separate third-party KYC vendor alongside your existing Stripe relationship.
For underwriting, income verification, or any product that needs read access to a customer's bank account data, Financial Connections provides this directly inside the Stripe ecosystem rather than requiring a second integration with a dedicated open-banking provider.
Terminal is easy to overlook if your product started as online-only, but the moment an online business adds any in-person component: a pop-up, a delivery-driver card reader, an in-office payment. Terminal shares the same underlying Stripe account and reporting rather than requiring a disconnected point-of-sale system.
Stripe insights, monthly
One email a month, no spam, unsubscribe anytime.
No spam, unsubscribe anytime.
Both use the same PaymentSheet under the hood. The differences that matter are in setup, not in the payment flow.
The official plugin covers most stores. Here's how to tell when it doesn't, before you've built the wrong thing.
Manual tax tables work fine until they don't. Here's the point where automation pays for itself.