Topic Details
https://whop.com/blog/rss/
Last item retrieved
<item><title><![CDATA[Integrated vs. embedded payments: Which is better for your platform?]]></title><description><![CDATA[Both integrated and embedded payments allow platforms to accept transactions and move money through their network, but only embedded payments offer opportunity for revenue growth and custom control. ]]></description><link>https://whop.com/blog/integrated-vs-embedded-payments/</link><guid isPermaLink="false">69c9d2f2b1ac550001325488</guid><category><![CDATA[Payments]]></category><dc:creator><![CDATA[Liv Carr]]></dc:creator><pubDate>Tue, 31 Mar 2026 02:35:47 GMT</pubDate><media:content url="https://whop.com/blog/content/images/2026/03/integrated-vs-embedded.webp" medium="image"/><content:encoded><![CDATA[<img src="https://whop.com/blog/content/images/2026/03/integrated-vs-embedded.webp" alt="Integrated vs. embedded payments: Which is better for your platform?"><p>For platforms, SaaS products, and online marketplaces, payments aren't just infrastructure, they're a main revenue driver. </p><p>That's why companies are shifting from simple payment integrations toward embedded payments, where transactions happen directly within the platform. </p><p>And it's a big shift: embedded finance transaction volume is projected to exceed $7 trillion in the US alone by 2026, with a CAGR of 35.5%. That's because how users pay and how sellers get paid <em>directly</em> affects platform growth, retention, and revenue.</p><p>So what are the differences between integrated payments and embedded payments?</p><p>In this guide, I'll break down how both models work, how platforms can monetize payments, and which approach makes sense for your product.</p><h2 id="what-are-integrated-payments">What are integrated payments?</h2><figure class="kg-card kg-image-card"><img src="https://whop.com/blog/content/images/2026/03/Integrated.jpg" class="kg-image" alt="Integrated vs. embedded payments: Which is better for your platform?" loading="lazy" width="2000" height="1125" srcset="https://whop.com/blog/content/images/size/w600/2026/03/Integrated.jpg 600w, https://whop.com/blog/content/images/size/w1000/2026/03/Integrated.jpg 1000w, https://whop.com/blog/content/images/size/w1600/2026/03/Integrated.jpg 1600w, https://whop.com/blog/content/images/size/w2400/2026/03/Integrated.jpg 2400w" sizes="(min-width: 720px) 720px"></figure><p>Integrated payments simply connect a <a href="https://whop.com/blog/payment-processors/" rel="noreferrer">payment processor</a> directly to your platform or software through a <a href="https://whop.com/blog/what-is-a-payment-api-or-payment-gateway/" rel="noreferrer">payment API</a>, plugin, or pre-built integration. Your product then connects to a third-party provider that handles the core payment processing.</p><p>Common integrated payment providers include <a href="https://whop.com/blog/what-is-stripe/" rel="noreferrer">Stripe</a>, <a href="https://whop.com/blog/square-payments/" rel="noreferrer">Square</a>, and Worldpay, which offer APIs that allow software products to connect checkout flows to external payment infrastructure.</p><p>When a customer makes a purchase, the transaction moves through the processor’s acquiring banks and card networks, and the processor typically manages merchant onboarding, compliance, settlement, and much of the payment experience.</p><p>For startup SaaS companies and early-stage platforms, integrated payments can be the fastest way to start making money. Connect to a payment processor’s API, add your checkout functionality, and begin processing payments.</p><p><strong>But there’s a trade-off: </strong>The payment provider owns most of the checkout experience, and most of the potential revenue.</p><p>And that's not the only con.</p><h3 id="pros-and-cons-of-integrated-payments">Pros and cons of integrated payments</h3>
<!--kg-card-begin: html-->
<table><thead><tr><th>Pros</th><th>Cons</th></tr></thead><tbody><tr><td>Fast to implement (often within days or weeks)</td><td>Limited control over the payment experience</td></tr><tr><td>Lower technical complexity</td><td>Revenue typically shared with the provider</td></tr><tr><td>Built-in compliance and risk management</td><td>Merchant onboarding controlled by processor</td></tr><tr><td>Access to established payment infrastructure</td><td>Harder to customise pricing and flows</td></tr><tr><td>Reliable support and documentation</td><td>Platform captures less value from transactions</td></tr></tbody></table>
<!--kg-card-end: html-->
<p>The larger your platform's user base gets, the more revenue you're missing out on.</p><p>Embedded payments flip that on its head, giving your platform a way to increase revenue simply from transactions flowing through your product. </p><p>Let's go deeper.</p><h2 id="what-are-embedded-payments">What are embedded payments?</h2><p><a href="https://whop.com/blog/embedded-payments/" rel="noreferrer">Embedded payments</a> take things a step further than simple integrations. Instead of connecting to an external processor, payments become a built-in part of your platform.</p><figure class="kg-card kg-image-card"><img src="https://whop.com/blog/content/images/2026/03/Embedded.jpg" class="kg-image" alt="Integrated vs. embedded payments: Which is better for your platform?" loading="lazy" width="2000" height="1125" srcset="https://whop.com/blog/content/images/size/w600/2026/03/Embedded.jpg 600w, https://whop.com/blog/content/images/size/w1000/2026/03/Embedded.jpg 1000w, https://whop.com/blog/content/images/size/w1600/2026/03/Embedded.jpg 1600w, https://whop.com/blog/content/images/size/w2400/2026/03/Embedded.jpg 2400w" sizes="(min-width: 720px) 720px"></figure><p>That means your sellers can onboard, accept payments, and receive payouts directly inside the platform.</p><p>Think about platforms like Uber or Airbnb. Riders and guests pay through the app, and individual merchants aren’t connecting their own payment providers.</p><p>You can design your own onboarding flows, control pricing and transaction fees, manage payouts, and build a payment experience that fits your product.</p><p>But (arguably most importantly), embedded payments also create a new revenue stream. A recent industry survey found <strong>over 90%</strong> of independent software vendors (ISVs) expect embedded payments to significantly increase platform revenue.</p><p><strong>TL;DR</strong>: Instead of just moving money, embedded payments let you capture a share of fees from financial activity happening on your network.</p><blockquote>In the not-too-distant future, I believe nearly every company will derive a significant portion of its revenue from financial services.<br><br> — Angela Strange, General Partner, a16z</blockquote><div class="kg-card kg-cta-card kg-cta-bg-blue kg-cta-minimal " data-layout="minimal">
<div class="kg-cta-content">
<div class="kg-cta-content-inner">
<div class="kg-cta-text">
<p><b><strong style="white-space: pre-wrap;">Mindbody makes more than half their revenue from embedded finance products, FYI. So yeah, the opportunity is huge. </strong></b></p>
</div>
</div>
</div>
</div><h3 id="pros-and-cons-of-embedded-payments">Pros and cons of embedded payments</h3>
<!--kg-card-begin: html-->
<table><thead><tr><th>Pros</th><th>Cons</th></tr></thead><tbody><tr><td>Full control over the payment and checkout experience</td><td>More complex to implement than simple integrations</td></tr><tr><td>Ability to capture revenue from transaction volume</td><td>Additional compliance responsibilities (KYC, AML, risk monitoring)</td></tr><tr><td>Control over merchant onboarding and payouts</td><td>Longer implementation timeline</td></tr><tr><td>Access to full transaction data within the platform</td><td>Requires payments infrastructure or a PayFac provider</td></tr><tr><td>Stronger platform stickiness and monetisation opportunities</td><td>More operational oversight of payment flows</td></tr></tbody></table>
<!--kg-card-end: html-->
<h2 id="how-do-embedded-payments-work">How do embedded payments work?</h2><p><a href="https://whop.com/blog/embedded-finance-providers/" rel="noreferrer">Embedded finance</a> tools (like payments) are possible for platforms through what's called a Payment Facilitator (PayFac) or Merchant of Record (MoR). </p><p>Let's run through how each model operates, especially from a platform's POV.</p><h3 id="payfacs">PayFacs</h3><p>A Payment Facilitator (<a href="https://whop.com/blog/what-is-a-payfac/" rel="noreferrer">PayFac</a>) allows a platform to onboard sellers as sub-merchants under a master merchant account, instead of requiring every seller to open their own merchant account with a bank.</p><p>This is why onboarding can happen in minutes instead of days.</p><figure class="kg-card kg-image-card"><img src="https://whop.com/blog/content/images/2026/03/MID--1---1-.jpg" class="kg-image" alt="Integrated vs. embedded payments: Which is better for your platform?" loading="lazy" width="2000" height="1125" srcset="https://whop.com/blog/content/images/size/w600/2026/03/MID--1---1-.jpg 600w, https://whop.com/blog/content/images/size/w1000/2026/03/MID--1---1-.jpg 1000w, https://whop.com/blog/content/images/size/w1600/2026/03/MID--1---1-.jpg 1600w, https://whop.com/blog/content/images/size/w2400/2026/03/MID--1---1-.jpg 2400w" sizes="(min-width: 720px) 720px"></figure><p>Sellers start accepting payments through the platform almost immediately, while the PayFac manages the infrastructure connecting the platform to payment processors and acquiring banks.</p><p>But becoming a <strong>registered PayFac</strong> comes with serious responsibilities. </p><p>You'd have to handle your own identity verification (KYC/KYB), underwriting, transaction monitoring, and ongoing compliance with card network rules.</p><h3 id="payfac-as-a-service">PayFac-as-a-Service</h3><p>That sounds like a headache, am I right? It's that complexity that drives platforms to choose a <strong>PayFac-as-a-Service (PFaaS)</strong> instead.</p><p>With PFaaS, a payments provider supplies the facilitator infrastructure while the platform embeds payments directly into its product. </p><p>The provider looks after the annoying parts: licensing, compliance frameworks, and risk systems. Your platform still controls the user experience and transaction flow, though. </p><p>This means you can embed payments, onboard sellers quickly, and monetize transactions without building a full payments operation yourself.</p><div class="kg-card kg-cta-card kg-cta-bg-blue kg-cta-minimal " data-layout="minimal">
<div class="kg-cta-content">
<div class="kg-cta-content-inner">
<div class="kg-cta-text">
<p><b><strong style="white-space: pre-wrap;">Mastercard's </strong></b><a href="https://www.mastercard.com/news/insights/2025/the-future-of-payment-facilitation-the-rise-of-payfac-as-a-service/" class="cta-link-color"><b><strong style="white-space: pre-wrap;">white paper</strong></b></a><b><strong style="white-space: pre-wrap;"> found that using a PFaaS can reduce time to market from months to weeks, if not less (compared to platforms becoming their own PayFac). </strong></b></p>
</div>
</div>
</div>
</div><h3 id="merchant-of-record-mor-one-step-beyond-a-payfac">Merchant of Record (MoR): One step beyond a PayFac</h3><figure class="kg-card kg-image-card"><img src="https://whop.com/blog/content/images/2026/03/MoR.jpg" class="kg-image" alt="Integrated vs. embedded payments: Which is better for your platform?" loading="lazy" width="2000" height="1125" srcset="https://whop.com/blog/content/images/size/w600/2026/03/MoR.jpg 600w, https://whop.com/blog/content/images/size/w1000/2026/03/MoR.jpg 1000w, https://whop.com/blog/content/images/size/w1600/2026/03/MoR.jpg 1600w, https://whop.com/blog/content/images/size/w2400/2026/03/MoR.jpg 2400w" sizes="(min-width: 720px) 720px"></figure><p>A <a href="https://whop.com/blog/mor/" rel="noreferrer">Merchant of Record (MoR)</a> model goes a step further than a PayFac. The MoR becomes the legal seller for the transaction, handling <a href="https://whop.com/blog/ecommerce-payment-processing/" rel="noreferrer">payment processing</a>, tax calculation and remittance, <a href="https://whop.com/blog/chargebacks/" rel="noreferrer">chargebacks</a>, fraud monitoring, and regulatory compliance.</p><p>For platforms, this removes a huge amount of operational overhead.</p><p>You can still embed payments directly into your product, onboard sellers, and route payouts across your platform. But the MoR manages the regulatory and financial side of the transaction behind the scenes.</p><blockquote><em>The next generation of billion-dollar payments companies won’t look like Stripe or Square. Instead, they’ll be vertically specific software companies who monetize payments.</em> <br><br>— Richie Serna, CEO & Co-Founder, Finix</blockquote><div class="kg-card kg-cta-card kg-cta-bg-blue kg-cta-minimal " data-layout="minimal">
<div class="kg-cta-content">
<div class="kg-cta-content-inner">
<div class="kg-cta-text">
<p><b><strong style="white-space: pre-wrap;">Whop acts as a Merchant of Record, removing operational overhead and anxiety, and allowing platforms to set up and process embedded payments in the same time as payment integration with other providers.</strong></b></p>
</div>
<a href="https://whop.com/network" class="kg-cta-button kg-style-accent" style="color: #FFFFFF;">
Whop Payments Network
</a>
</div>
</div>
</div><h2 id="integrated-vs-embedded-payments-a-side-by-side-comparison">Integrated vs embedded payments: A side-by-side comparison</h2><p>Both integrated and embedded payments allow you to accept transactions inside your product, but the difference is between who controls the experience and who captures the value from payment flows.</p><p>But if you're running your own marketplace, SaaS, or user platform? You most likely care about revenue potential, control, and compliance. </p><p>While it's true that integrated payments offer the fastest path to accepting payments, it doesn't mean it's necessarily what's best for platforms long-term. </p><p>Here's how the two options stack up with those concerns in mind:</p>
<!--kg-card-begin: html-->
<table>
<thead>
<tr>
<th>Feature</th>
<th>Integrated payments</th>
<th>Embedded payments</th>
</tr>
</thead>
<tbody>
<tr>
<td>Control</td>
<td>Provider controls most flows</td>
<td>Platform controls checkout & payouts</td>
</tr>
<tr>
<td>Revenue</td>
<td>Processor keeps most fees</td>
<td>Platform captures transaction share</td>
</tr>
<tr>
<td>Implementation</td>
<td>Fast to launch</td>
<td>More setup required</td>
</tr>
<tr>
<td>Onboarding</td>
<td>Handled by processor</td>
<td>Handled by platform</td>
</tr>
<tr>
<td>Compliance</td>
<td>Mostly provider responsibility</td>
<td>Shared or platform responsibility</td>
</tr>
<tr>
<td>User experience</td>
<td>External or provider-branded flows</td>
<td>Native platform checkout</td>
</tr>
</tbody>
</table>
<!--kg-card-end: html-->
<p>Integrated payments are ideal for early-stage platforms prioritizing speed. Embedded payments make more sense when payments become a core part of the platform’s business model.</p><div class="kg-card kg-cta-card kg-cta-bg-blue kg-cta-minimal " data-layout="minimal">
<div class="kg-cta-content">
<div class="kg-cta-content-inner">
<div class="kg-cta-text">
<p><b><strong style="white-space: pre-wrap;">Platforms that integrate financial services are valued about 23% higher on average, according to investment firm William Blair.</strong></b></p>
</div>
</div>
</div>
</div><h3 id="how-to-choose-between-integrated-and-embedded-payments">How to choose between integrated and embedded payments</h3><p>Integrated payments may be the better choice if your platform:</p><ul><li>Needs to launch payments quickly</li><li>Has limited engineering resources</li><li>Doesn't want to make revenue from payments (interesting call)</li></ul><p>Embedded payments may make more sense if your platform:</p><ul><li>Processes large transaction volumes</li><li>Wants to monetize payments</li><li>Needs full control over <a href="https://whop.com/blog/create-checkout-links-whop/" rel="noreferrer">checkout</a>, onboarding, and payouts</li><li>Is building a marketplace, creator economy platform, or SaaS ecosystem</li></ul><p>And remember, embedded payments don't necessarily take weeks with modern providers. <a href="https://whop.com/blog/whop-payments-network/" rel="noreferrer">Whop</a> provides a simple, out-the-box, full-stack payments solution for platforms, SaaS, and marketplaces with embedded finance built in. </p><figure class="kg-card kg-video-card kg-width-regular" data-kg-thumbnail="https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/media/2026/03/embedded-checkout-1_thumb.jpg" data-kg-custom-thumbnail="https://whop.com/blog/content/images/2026/03/whop-embedded-checkout-1.png">
<div class="kg-video-container">
<video src="https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/media/2026/03/embedded-checkout-1.mp4" poster="https://img.spacergif.org/v1/1920x1080/0a/spacer.png" width="1920" height="1080" playsinline preload="metadata" style="background: transparent url('https://whop.com/blog/content/images/2026/03/whop-embedded-checkout-1.png') 50% 50% / cover no-repeat;"></video>
<div class="kg-video-overlay">
<button class="kg-video-large-play-icon" aria-label="Play video">
<svg xmlns="http://www.w3.org/2000/svg" viewbox="0 0 24 24">
<path d="M23.14 10.608 2.253.164A1.559 1.559 0 0 0 0 1.557v20.887a1.558 1.558 0 0 0 2.253 1.392L23.14 13.393a1.557 1.557 0 0 0 0-2.785Z"/>
</svg>
</button>
</div>
<div class="kg-video-player-container">
<div class="kg-video-player">
<button class="kg-video-play-icon" aria-label="Play video">
<svg xmlns="http://www.w3.org/2000/svg" viewbox="0 0 24 24">
<path d="M23.14 10.608 2.253.164A1.559 1.559 0 0 0 0 1.557v20.887a1.558 1.558 0 0 0 2.253 1.392L23.14 13.393a1.557 1.557 0 0 0 0-2.785Z"/>
</svg>
</button>
<button class="kg-video-pause-icon kg-video-hide" aria-label="Pause video">
<svg xmlns="http://www.w3.org/2000/svg" viewbox="0 0 24 24">
<rect x="3" y="1" width="7" height="22" rx="1.5" ry="1.5"/>
<rect x="14" y="1" width="7" height="22" rx="1.5" ry="1.5"/>
</svg>
</button>
<span class="kg-video-current-time">0:00</span>
<div class="kg-video-time">
/<span class="kg-video-duration">0:16</span>
</div>
<input type="range" class="kg-video-seek-slider" max="100" value="0">
<button class="kg-video-playback-rate" aria-label="Adjust playback speed">1×</button>
<button class="kg-video-unmute-icon" aria-label="Unmute">
<svg xmlns="http://www.w3.org/2000/svg" viewbox="0 0 24 24">
<path d="M15.189 2.021a9.728 9.728 0 0 0-7.924 4.85.249.249 0 0 1-.221.133H5.25a3 3 0 0 0-3 3v2a3 3 0 0 0 3 3h1.794a.249.249 0 0 1 .221.133 9.73 9.73 0 0 0 7.924 4.85h.06a1 1 0 0 0 1-1V3.02a1 1 0 0 0-1.06-.998Z"/>
</svg>
</button>
<button class="kg-video-mute-icon kg-video-hide" aria-label="Mute">
<svg xmlns="http://www.w3.org/2000/svg" viewbox="0 0 24 24">
<path d="M16.177 4.3a.248.248 0 0 0 .073-.176v-1.1a1 1 0 0 0-1.061-1 9.728 9.728 0 0 0-7.924 4.85.249.249 0 0 1-.221.133H5.25a3 3 0 0 0-3 3v2a3 3 0 0 0 3 3h.114a.251.251 0 0 0 .177-.073ZM23.707 1.706A1 1 0 0 0 22.293.292l-22 22a1 1 0 0 0 0 1.414l.009.009a1 1 0 0 0 1.405-.009l6.63-6.631A.251.251 0 0 1 8.515 17a.245.245 0 0 1 .177.075 10.081 10.081 0 0 0 6.5 2.92 1 1 0 0 0 1.061-1V9.266a.247.247 0 0 1 .073-.176Z"/>
</svg>
</button>
<input type="range" class="kg-video-volume-slider" max="100" value="100">
</div>
</div>
</div>
</figure><h2 id="why-platforms-are-moving-from-integrated-payments-to-embedded-payments-and-finance">Why platforms are moving from integrated payments to embedded payments and finance </h2><p>For years, the goal with platform payments was simple: connect a processor, enable transactions, and move on. </p><p>But as platforms scale, integrated payments start to leave a lot of cash on the table.</p><p>When marketplaces, SaaS platforms, and creator ecosystems process large volumes of transactions? Payments become one of the most scalable revenue opportunities you have. </p><p>So, instead of relying purely on <a href="https://whop.com/blog/sell-subscriptions-online/" rel="noreferrer">subscriptions</a> or platform fees, companies can capture a small share of all the financial activity happening across their network.</p><p>Over 60% of vertical SaaS platforms have embedded payments into their products, increasing both revenue and platform stickiness (when vendors rely on you to get paid, access funds, or manage money, switching becomes much harder).</p><p>Payments revenue scales directly with platform activity. As more buyers and sellers transact through the product, financial services revenue grows automatically alongside it.</p><h3 id="case-study-ohana-uses-whop-for-embedded-payments">Case study: Ohana uses Whop for embedded payments</h3><figure class="kg-card kg-video-card kg-width-regular" data-kg-thumbnail="https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/media/2026/03/Ohana-x-Whop-2_thumb.jpg" data-kg-custom-thumbnail>
<div class="kg-video-container">
<video src="https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/media/2026/03/Ohana-x-Whop-2.mp4" poster="https://img.spacergif.org/v1/3884x2160/0a/spacer.png" width="3884" height="2160" playsinline preload="metadata" style="background: transparent url('https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/media/2026/03/Ohana-x-Whop-2_thumb.jpg') 50% 50% / cover no-repeat;"></video>
<div class="kg-video-overlay">
<button class="kg-video-large-play-icon" aria-label="Play video">
<svg xmlns="http://www.w3.org/2000/svg" viewbox="0 0 24 24">
<path d="M23.14 10.608 2.253.164A1.559 1.559 0 0 0 0 1.557v20.887a1.558 1.558 0 0 0 2.253 1.392L23.14 13.393a1.557 1.557 0 0 0 0-2.785Z"/>
</svg>
</button>
</div>
<div class="kg-video-player-container">
<div class="kg-video-player">
<button class="kg-video-play-icon" aria-label="Play video">
<svg xmlns="http://www.w3.org/2000/svg" viewbox="0 0 24 24">
<path d="M23.14 10.608 2.253.164A1.559 1.559 0 0 0 0 1.557v20.887a1.558 1.558 0 0 0 2.253 1.392L23.14 13.393a1.557 1.557 0 0 0 0-2.785Z"/>
</svg>
</button>
<button class="kg-video-pause-icon kg-video-hide" aria-label="Pause video">
<svg xmlns="http://www.w3.org/2000/svg" viewbox="0 0 24 24">
<rect x="3" y="1" width="7" height="22" rx="1.5" ry="1.5"/>
<rect x="14" y="1" width="7" height="22" rx="1.5" ry="1.5"/>
</svg>
</button>
<span class="kg-video-current-time">0:00</span>
<div class="kg-video-time">
/<span class="kg-video-duration">0:43</span>
</div>
<input type="range" class="kg-video-seek-slider" max="100" value="0">
<button class="kg-video-playback-rate" aria-label="Adjust playback speed">1×</button>
<button class="kg-video-unmute-icon" aria-label="Unmute">
<svg xmlns="http://www.w3.org/2000/svg" viewbox="0 0 24 24">
<path d="M15.189 2.021a9.728 9.728 0 0 0-7.924 4.85.249.249 0 0 1-.221.133H5.25a3 3 0 0 0-3 3v2a3 3 0 0 0 3 3h1.794a.249.249 0 0 1 .221.133 9.73 9.73 0 0 0 7.924 4.85h.06a1 1 0 0 0 1-1V3.02a1 1 0 0 0-1.06-.998Z"/>
</svg>
</button>
<button class="kg-video-mute-icon kg-video-hide" aria-label="Mute">
<svg xmlns="http://www.w3.org/2000/svg" viewbox="0 0 24 24">
<path d="M16.177 4.3a.248.248 0 0 0 .073-.176v-1.1a1 1 0 0 0-1.061-1 9.728 9.728 0 0 0-7.924 4.85.249.249 0 0 1-.221.133H5.25a3 3 0 0 0-3 3v2a3 3 0 0 0 3 3h.114a.251.251 0 0 0 .177-.073ZM23.707 1.706A1 1 0 0 0 22.293.292l-22 22a1 1 0 0 0 0 1.414l.009.009a1 1 0 0 0 1.405-.009l6.63-6.631A.251.251 0 0 1 8.515 17a.245.245 0 0 1 .177.075 10.081 10.081 0 0 0 6.5 2.92 1 1 0 0 0 1.061-1V9.266a.247.247 0 0 1 .073-.176Z"/>
</svg>
</button>
<input type="range" class="kg-video-volume-slider" max="100" value="100">
</div>
</div>
</div>
</figure><p>Ohana built a platform for tenants to sublease their apartments and collect rent through a single system.</p><p>In reality, that's a lot going on behind the scenes: rent has to be collected from tenants each month, landlords need reliable payouts, and identity checks and compliance have to work smoothly for both sides of the transaction.</p><p>With payments embedded directly into the platform, Ohana's entire payment flow happens inside the product. Tenants pay rent, landlords receive payouts, and everything (onboarding, payments, and payouts) runs through a single system. </p><h2 id="embed-payments-and-boost-your-platforms-revenue-with-whop">Embed payments and boost your platform's revenue with Whop</h2><figure class="kg-card kg-video-card kg-width-regular" data-kg-thumbnail="https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/media/2026/03/Gif-Ohana-2-4_thumb.jpg" data-kg-custom-thumbnail>
<div class="kg-video-container">
<video src="https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/media/2026/03/Gif-Ohana-2-4.mp4" poster="https://img.spacergif.org/v1/3840x2160/0a/spacer.png" width="3840" height="2160" loop autoplay muted playsinline preload="metadata" style="background: transparent url('https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/media/2026/03/Gif-Ohana-2-4_thumb.jpg') 50% 50% / cover no-repeat;"></video>
<div class="kg-video-overlay">
<button class="kg-video-large-play-icon" aria-label="Play video">
<svg xmlns="http://www.w3.org/2000/svg" viewbox="0 0 24 24">
<path d="M23.14 10.608 2.253.164A1.559 1.559 0 0 0 0 1.557v20.887a1.558 1.558 0 0 0 2.253 1.392L23.14 13.393a1.557 1.557 0 0 0 0-2.785Z"/>
</svg>
</button>
</div>
<div class="kg-video-player-container kg-video-hide">
<div class="kg-video-player">
<button class="kg-video-play-icon" aria-label="Play video">
<svg xmlns="http://www.w3.org/2000/svg" viewbox="0 0 24 24">
<path d="M23.14 10.608 2.253.164A1.559 1.559 0 0 0 0 1.557v20.887a1.558 1.558 0 0 0 2.253 1.392L23.14 13.393a1.557 1.557 0 0 0 0-2.785Z"/>
</svg>
</button>
<button class="kg-video-pause-icon kg-video-hide" aria-label="Pause video">
<svg xmlns="http://www.w3.org/2000/svg" viewbox="0 0 24 24">
<rect x="3" y="1" width="7" height="22" rx="1.5" ry="1.5"/>
<rect x="14" y="1" width="7" height="22" rx="1.5" ry="1.5"/>
</svg>
</button>
<span class="kg-video-current-time">0:00</span>
<div class="kg-video-time">
/<span class="kg-video-duration">0:08</span>
</div>
<input type="range" class="kg-video-seek-slider" max="100" value="0">
<button class="kg-video-playback-rate" aria-label="Adjust playback speed">1×</button>
<button class="kg-video-unmute-icon" aria-label="Unmute">
<svg xmlns="http://www.w3.org/2000/svg" viewbox="0 0 24 24">
<path d="M15.189 2.021a9.728 9.728 0 0 0-7.924 4.85.249.249 0 0 1-.221.133H5.25a3 3 0 0 0-3 3v2a3 3 0 0 0 3 3h1.794a.249.249 0 0 1 .221.133 9.73 9.73 0 0 0 7.924 4.85h.06a1 1 0 0 0 1-1V3.02a1 1 0 0 0-1.06-.998Z"/>
</svg>
</button>
<button class="kg-video-mute-icon kg-video-hide" aria-label="Mute">
<svg xmlns="http://www.w3.org/2000/svg" viewbox="0 0 24 24">
<path d="M16.177 4.3a.248.248 0 0 0 .073-.176v-1.1a1 1 0 0 0-1.061-1 9.728 9.728 0 0 0-7.924 4.85.249.249 0 0 1-.221.133H5.25a3 3 0 0 0-3 3v2a3 3 0 0 0 3 3h.114a.251.251 0 0 0 .177-.073ZM23.707 1.706A1 1 0 0 0 22.293.292l-22 22a1 1 0 0 0 0 1.414l.009.009a1 1 0 0 0 1.405-.009l6.63-6.631A.251.251 0 0 1 8.515 17a.245.245 0 0 1 .177.075 10.081 10.081 0 0 0 6.5 2.92 1 1 0 0 0 1.061-1V9.266a.247.247 0 0 1 .073-.176Z"/>
</svg>
</button>
<input type="range" class="kg-video-volume-slider" max="100" value="100">
</div>
</div>
</div>
</figure><p>Integrated payments help platforms start accepting transactions quickly. But as platforms grow, payments usually evolve to become a core part of the product itself.</p><p>By merging checkout, onboarding, and payouts directly into the platform experience, you gain more control over how transactions happen and how you can monetize them.</p><p>Whop makes it simple, with an MoR-backed payments stack built for platforms, SaaS products, and marketplaces. Embed payments, orchestrate payments, onboard sellers, and route payouts inside your product without building any infrastructure yourself.</p><p><strong>Accept buyer payments, pay out sellers instantly, and handle compliance automatically with Whop.</strong></p><div class="kg-card kg-button-card kg-align-left"><a href="https://whop.com/network" class="kg-btn kg-btn-accent">Embed payments with Whop</a></div><hr><h2 id="integrated-vs-embedded-payments-faqs">Integrated vs. embedded payments FAQs</h2><h3 id="what-is-the-difference-between-integrated-and-embedded-payments">What is the difference between integrated and embedded payments?</h3><p>Integrated payments connect your platform to a third-party processor via API, and the provider handles onboarding and compliance. Embedded payments build the entire payment experience natively into your software, giving you full control over merchant onboarding, pricing, and the user experience.</p><h3 id="are-embedded-payments-better-than-integrated-payments">Are embedded payments better than integrated payments?</h3><p>It depends on your goals. Embedded payments offer more control and higher revenue potential but require greater technical investment. Integrated payments are faster to launch and simpler to maintain. Early-stage platforms often start integrated and migrate to embedded as they scale.</p><h3 id="what-is-a-payment-facilitator-payfac">What is a payment facilitator (PayFac)?</h3><p>A PayFac is a company that processes payments on behalf of sub-merchants under its own merchant ID. Embedded payments often use a PayFac or PayFac-as-a-Service model to allow platforms to onboard merchants directly.</p><h3 id="what-is-a-merchant-of-record-mor">What is a Merchant of Record (MoR)?</h3><p>A Merchant of Record (MoR) goes a step further than a PayFac, becoming the legal seller for a transaction – like Whop.</p><p>This means the MoR handles payment processing, taxes, chargebacks, fraud monitoring, and regulatory compliance, allowing platforms to embed payments and manage payouts without as many operational and legal responsibilities.</p><h3 id="how-long-does-it-take-to-implement-integrated-vs-embedded-payments">How long does it take to implement integrated vs embedded payments?</h3><p>Integrated payments can typically go live within 1 to 4 weeks using a provider’s API or pre-built integrations. Embedded payments usually take longer (often weeks to months), because platforms need to build checkout flows, seller onboarding, payouts, and compliance systems. </p><p>Full-stack, MoR solutions like Whop make it possible to embed payments much faster, with platforms able to launch checkout and start accepting payments almost instantly. </p><div class="kg-card kg-button-card kg-align-left"><a href="https://whop.com/network/" class="kg-btn kg-btn-accent">MoR-backed payments with Whop</a></div><h3 id="what-types-of-businesses-benefit-most-from-embedded-payments">What types of businesses benefit most from embedded payments?</h3><p>Vertical SaaS platforms, marketplaces, creator economy platforms, and any software company processing high transaction volumes benefit most. If payments are core to your user experience and you want to own the merchant relationship, embedded payments deliver the strongest ROI.</p>]]></content:encoded></item>
These legal disclaimers are here because this hub is run by Google as a service. If you don't want to agree to these terms you can use a different hub or even run your own. The PubSubHubbub protocol is decentralized and free.
©2022 Google - Terms of Service - Privacy Policy