Case Studies › PayFrame
FinTech & Payments

Payments infrastructure SaaS platforms embed in days

Techdots built PayFrame's entire white-label payment gateway platform — from multi-tenant merchant onboarding and dynamic routing to real-time revenue share settlement and a fully embeddable SDK. The goal was to give SaaS founders a single integration that turns payments into a revenue center, not a compliance burden. We delivered a production-ready platform that went live with its first platform customer eight weeks after kickoff.

Start a Similar Project → ← All Case Studies
P
PayFrame
FinTech & Payments
40+
SaaS platforms onboarded in first 6 months
3.2x
Faster merchant onboarding vs. previous manual flow
$18M+
Monthly payment volume processed at launch
20 weeks
timeline
This engagement is best for
SaaS platforms looking to monetize payments without becoming a payment processor
FinTech infrastructure companies building for vertical SaaS markets
Marketplace or multi-sided platforms needing split payment and escrow logic
Startups pursuing PayFac-lite or embedded finance models under a master merchant
The Transformation

Before & After

Before
✕ Prospective platform customers had to integrate Stripe or Braintree directly, losing branding and revenue share opportunity
✕ Merchant onboarding required 3-5 days of manual KYB review with no self-serve flow
✕ Revenue splits between platform and sub-merchant were calculated manually in spreadsheets each month
✕ No unified dashboard for platform owners to monitor transaction health across their sub-merchants
✕ PCI scope concerns blocked several enterprise SaaS deals from closing
After
✓ Platform customers can embed fully branded payment flows using a single JavaScript SDK in under a day
✓ Automated KYB and KYC checks cut merchant approval time from 4 days to under 90 minutes on average
✓ Real-time revenue share calculations and automated payouts eliminated manual reconciliation entirely
✓ Platform owners get a live operations dashboard with per-merchant volume, dispute rates, and settlement status
✓ PayFrame's hosted fields architecture keeps platform customers entirely out of PCI scope
What We Built

Deliverables & Scope

Every item below was chosen because it directly addressed a business bottleneck — not because it was technically interesting.

01
Multi-tenant merchant onboarding engine with automated KYB/KYC orchestration via Persona and Middesk APIs
02
Embeddable JavaScript SDK with customizable hosted payment fields that render inside any SaaS product without exposing card data to the host
03
Dynamic payment routing layer supporting Stripe and Adyen as underlying processors with fallback logic and least-cost routing rules
04
Real-time revenue share engine calculating platform fees, interchange splits, and sub-merchant payouts on every settled transaction
05
Platform operator dashboard built in React with live transaction monitoring, dispute management, and merchant health scoring
06
Webhook delivery system with retry logic, signature verification, and per-platform event filtering for downstream SaaS integrations
ROI Logic

Why This Generated
Real Business Value

PayFrame's business model only works at scale when onboarding friction is near zero and platform operators trust the settlement math — both of which require deeply reliable infrastructure, not a patchwork of third-party tools. By building a purpose-designed multi-tenant core rather than adapting a generic payments library, PayFrame can charge a platform fee on every transaction processed by its customers' customers, creating a compounding revenue stream that grows automatically as each onboarded SaaS platform scales. The hosted fields and SDK approach also removed the single biggest sales objection — PCI compliance — which directly shortened enterprise sales cycles.

Key Outcomes
40+
SaaS platforms onboarded in first 6 months
3.2x
Faster merchant onboarding vs. previous manual flow
$18M+
Monthly payment volume processed at launch
Why It Worked

The Decisions That
Made the Difference

Good execution matters. But the right early decisions matter more.

01
We scoped the multi-tenancy model before writing a line of application code, ensuring every data, billing, and webhook boundary was correct from day one rather than retrofitted later
02
Choosing Stripe Connect and Adyen for Platforms as dual processor backends gave PayFrame immediate global acquiring coverage while the routing layer kept the business free from single-vendor lock-in
03
The hosted fields iframe architecture was a deliberate tradeoff — slightly more complex to build, but it meant platform customers could close enterprise deals without touching their own PCI audit scope
04
We shipped a working integration to the first pilot platform in week eight and iterated on the SDK and dashboard in parallel, so real merchant feedback shaped the product before it was publicly launched
Tech Stack
Ruby on Rails React.js PostgreSQL Redis AWS (ECS + RDS + SQS)
Integrations
Stripe Connect (underlying processor and managed payouts) Adyen for Platforms (EU/international acquiring) Persona (KYC identity verification) Middesk (business KYB and entity verification) Plaid (bank account verification for ACH payouts)
Start your project

Have a Similar Problem?

Start with a Software + AI Audit. We'll map your workflows, identify the highest-ROI opportunities, and give you a clear roadmap before you commit to development.

Get a Software + AI Audit → ← View All Case Studies