PRD summary
Problem
Merchants need timely working capital without leaving the platform workflow.
Goal
Increase merchant retention, GMV, product stickiness, and platform revenue while avoiding support/compliance blowups.
Non-goal
The platform should not become an unlicensed lender or absorb unmanaged credit risk unless explicitly intended.
Primary metric
Eligible merchants shown offers → accepted offers → repeat usage → merchant retention/GMV lift.
Required decisions
| Decision | Options | Owner |
|---|---|---|
| Product type | MCA, loan, line of credit, pay-over-time, spend card | Product + legal |
| Provider model | Native processor capital, white-label partner, lender network | Product + finance |
| Data sharing | Platform sales only, bank data, accounting data, processor data | Data + legal |
| Branding | Provider branded, co-branded, white-label | Product + marketing + legal |
| Support model | Provider handles all, platform first-line, shared escalation | Merchant services |
| Economics | Referral fee, rev share, origination economics, no economics | Finance + partnerships |
User stories
- •As a merchant, I can see whether I am pre-qualified without filling out a long form.
- •As a merchant, I can understand total repayment cost, repayment mechanics, and provider identity before accepting.
- •As an account manager, I can explain eligibility, basic terms, and support routing without giving financial advice.
- •As finance, I can track originations, revenue share, refunds/clawbacks, and support cost.
- •As compliance, I can review all merchant-facing disclosures and data-sharing flows before launch.
Launch checklist
- •Run sample underwriting on real merchant population.
- •Review merchant-facing disclosures, provider terms, privacy/data flows, and support scripts.
- •Instrument funnel: impressions, eligibility, started application, completed application, accepted offer, funded, repeat.
- •Create complaint/escalation runbook before launch.
- •Start with a limited merchant segment before broad rollout.