YC Application for Fintech Startups — What to Write

This page covers exactly what to write in each key field of a fintech YC application, with frameworks specific to lending, payments, banking infrastructure, and wealth products.

Partners reading a fintech application are answering five questions that are specific to this category:

1. Do you understand the regulatory environment you are operating in?

Fintech regulation varies enormously by product type and geography. A lending product, a payments product, and a wealth management product each face different regulatory regimes. Partners want to see that you know exactly which regulations apply to you and what your compliance posture is — not vague awareness, but specific knowledge.

2. Is your unit economics model sound at the level of basis points, not just percentages?

Fintech margins are often thin and precise. "We take a small fee" is not an answer. Partners want exact take rates, exact interchange economics, exact net interest margin — the specific numbers that determine whether your business model actually works at scale.

3. How do you build trust with a user handling their money?

Trust is the core product in financial services. Partners evaluate whether your application demonstrates that you understand this — through security posture, transparency in how you handle user funds, and evidence that users have trusted you with real money already.

4. What is your relationship with the underlying financial infrastructure?

Are you building on top of a banking-as-a-service provider, a card issuer, a payment processor? Or do you hold direct licenses? Partners want clarity on your infrastructure dependencies and what happens if a partner relationship changes.

5. Is this a feature or a business?

Many fintech ideas are genuinely useful features that large banks or fintech platforms could add easily. Partners probe whether your product has a standalone business model and distribution motion, or whether it is more naturally a feature inside someone else's platform.

50-Character Description

Formula: [Financial function] for [specific user]

Strong examples:

• "Working capital loans for Indian kirana stores"
• "Cross-border payments for Indian freelancers"
• "Credit scoring for thin-file borrowers in India"
• "Embedded lending for B2B marketplaces"

Avoid: "fintech platform," "financial solution," "neobank for X" without specifying the actual financial function performed.

Product Description (~150 words)

Structure: User → financial pain point → your mechanism → regulatory/infrastructure posture → current scale

"[User] currently faces [specific financial friction — can't access credit, pays high fees, lacks visibility]. We provide [specific financial product] through [mechanism — your own balance sheet, a partner bank, a licensed NBFC structure]. We operate under [specific regulatory framework] and currently have [X] users / ₹Y disbursed / ₹Z processed."

Example:

"Independent kirana store owners in tier 2 India cannot access working capital because they have no formal credit history and banks require collateral they don't have. We provide 30-day working capital advances based on their UPI transaction history, disbursed through our NBFC partner under RBI's digital lending guidelines. We have disbursed ₹42 lakh across 380 loans with a 96% on-time repayment rate."

The Regulatory Posture Field

This field does not always exist explicitly on the application, but you should address it within your traction or insight fields regardless. State your exact regulatory position:

"We operate as a lending service provider partnered with a registered NBFC. We are not a regulated lender ourselves — our partner holds the NBFC license and we provide the technology and underwriting layer under a co-lending arrangement compliant with RBI's November 2022 digital lending guidelines."

If you do not yet have regulatory clarity, say so honestly and describe your plan: "We are currently operating in a regulatory gray zone for our specific product category and are in active consultation with a fintech regulatory counsel to determine the correct licensing structure before we scale beyond our current pilot."

The Unit Economics Field

Fintech unit economics require precision that other categories do not. State:

• Take rate or interest rate (exact, not rounded)
• Cost of capital (if lending)
• Default rate or chargeback rate
• Net interest margin or net take rate after cost of funds
• CAC and payback period in the context of financial product lifetime value

"We charge a 2.5% fee per transaction. Our cost of processing through our payment partner is 0.4%. Net take rate is 2.1%. At our current volume of ₹18 lakh/month, that produces ₹37,800/month in net revenue. Default rate on our lending product is 2.3%, in line with our underwriting model's target."

The Trust and Security Field

Address this explicitly even if not directly asked:

"We do not hold custody of user funds directly — all transactions settle through our payment partner's regulated escrow account. Our platform is PCI-DSS compliant for card data handling. We have had zero security incidents and zero fund losses across 18 months of operation."

The Infrastructure Dependency Field

Be explicit about what you have built versus what you depend on:

"We have built the underwriting model, the user-facing application, and the WhatsApp-based disbursement flow. We depend on [Partner Bank] for the regulated lending license and [Payment Processor] for fund movement. If either relationship changed, we would need 2-3 months to transition to an alternative partner — we have already identified backup partners for both."

Lending products:

• Default rate under 5% for unsecured consumer lending is generally acceptable at early stage
• Repeat borrower rate above 40% signals product-market fit
• Loan disbursement growth MoM above 20% is strong

Payments products:

• Take rate sustainability — net take rate after processing costs should support unit economics at scale, not just at subsidized early volume
• Transaction success rate above 95% is the baseline expectation
• Merchant/user retention month-over-month above 85%

Wealth and investment products:

• AUM growth rate and net new asset flow
• User engagement with the product beyond initial deposit (recurring contribution rate)
• Regulatory licensing status for investment advice if applicable

Banking infrastructure / B2B fintech:

• Number of integrated partners or platforms
• Transaction volume processed through the API
• Time-to-integration for new partners (shorter is better, signals product maturity)

Failure 1: Treating regulation as an afterthought

Founders who describe their product enthusiastically without addressing regulatory structure signal that they have not done the hardest part of building a fintech company. Regulatory clarity is not optional homework — it is core to whether the business can exist.

Failure 2: Vague unit economics

"We make money on transaction fees" without exact numbers is insufficient for fintech specifically because the margins are often thin enough that imprecision hides whether the business actually works. Know your numbers to the basis point.

Failure 3: No clear answer on capital requirements

Lending and certain payments businesses require capital beyond typical SaaS — either balance sheet capital for lending or working capital for payment float. Founders who do not address how they will fund this growth (their own balance sheet vs. partner bank vs. raised debt facility) leave a critical question unanswered.

Failure 4: Underestimating the trust-building timeline

Fintech products often face longer adoption curves than other software because users are inherently more cautious with products that touch their money. Applications that project SaaS-speed adoption curves for a lending or wealth product signal a misunderstanding of category-specific dynamics.

Failure 5: Building a feature, not a company

"We help users round up their purchases and invest the difference" is a feature most banking apps could add in a quarter. The strongest fintech applications explain why their approach has a standalone distribution motion and a defensible position that a bank or larger fintech platform could not simply replicate.

Indian fintech founders should lead with India-specific infrastructure context that strengthens rather than weakens the application: UPI's transaction volume, the RBI's digital lending guidelines, the specific NBFC partnership model, and the underserved credit population (the "credit invisible" population with no formal credit history). These are legitimate, fundable market dynamics — but they require one sentence of translation for a global reader. Do not assume a YC partner in San Francisco knows what an NBFC co-lending arrangement is; explain it briefly, then move forward with confidence.