Why the Checkout Is Becoming Invisible
Think about the last time you bought something online and never saw a "redirecting to payment provider" screen. No pop-up window. No second-guessing whether the page you landed on was legitimate. You tapped a button, the money moved, and you were back on the merchant's site before you finished blinking. That seamless experience is the visible tip of embedded payments — and the model behind it is quietly redrawing the economics of ecommerce.
Embedded payments are no longer a niche fintech curiosity. Bain & Company projects that financial services embedded into ecommerce and other software platforms will exceed $7 trillion in US transaction value by 2026, up from $2.6 trillion in 2021. For Shopify merchants and the operators who serve them, that shift isn't abstract. It changes how you get paid, how fast you access capital, and how much margin your platform captures versus passes through to you.
This is a strategic explainer, not a setup tutorial. If you just want to wire up a processor, our guide on how to set up Shopify Payments covers the mechanics. Here we're going up a level: what embedded payments are, how they differ from embedded finance and Banking-as-a-Service, why the model matters to your store's unit economics, and how Shopify itself became one of the best case studies in the world for this trend. By the end, you'll understand the system you're already operating inside — and where it's heading as AI agents start checking out on your customers' behalf.
What Embedded Payments Actually Are
At its simplest, embedded payments means payment processing is built directly into the software you already use, instead of bolted on as a separate service you redirect customers to. The transaction happens inside the platform's interface, branded as the platform's own, with the underlying processor invisible to the buyer.
The classic contrast is the old gateway-redirect model. A decade ago, clicking "Pay" often shipped customers off to a third-party page hosted by a payment processor, where they re-entered card details under a different brand, then bounced back to the store afterward. Every redirect was a chance to lose the sale to friction, distrust, or a slow-loading external page.
The embedded model collapses that journey. As Lightspeed's overview of embedded payments puts it, the goal is to let consumers complete purchases in-app or on-site without ever being redirected to an external page. Shopify Payments is the textbook example: merchants accept cards natively inside Shopify, with no separate gateway to configure or hand customers off to.
Embedded vs. integrated payments
These two terms get used interchangeably, but there's a meaningful distinction:
- Integrated payments connect a third-party processor to your software so data flows between them — but you still typically maintain a separate relationship and merchant account with that processor.
- Embedded payments go further: the platform owns the payment experience end-to-end, often onboarding you as a sub-merchant under its own account, so the processor relationship is invisible to you and your customer.
Finix's breakdown of embedded vs. integrated payments frames it well — integration is about connection, embedding is about ownership of the full flow.
Why "invisible" is the whole point
The defining trait of this model is that the connection between software and money movement becomes nearly invisible to the end user. Fewer screens, fewer brands, fewer reasons to abandon. That invisibility is exactly why these systems lift conversion — a theme we'll return to when we talk unit economics.
Embedded Payments vs. Embedded Finance vs. BaaS
The single biggest source of confusion in this space is treating three related terms as synonyms. They're nested layers, not interchangeable labels. Getting the hierarchy right is what lets you reason clearly about where Shopify's products fit and where the industry is heading.
Here's the clean definitional breakdown:
| Term | What it is | Layer | Ecommerce example |
|---|---|---|---|
| Embedded payments | Payment acceptance built directly into a non-financial platform | Front-end (a single financial function) | Shopify Payments processing a card at checkout |
| Embedded finance | Any financial product — payments, lending, insurance, banking — integrated into a non-financial platform | Front-end (the full category) | Shopify Capital, Shop Pay Installments, Shopify Balance |
| Banking-as-a-Service (BaaS) | Banks exposing core banking functions via APIs so non-banks can offer financial products | Back-end (infrastructure) | A chartered bank powering a merchant's branded business account |
The relationship is straightforward once you see it stacked:
- Embedded payments are a subset of embedded finance. Payments are one financial product; embedded finance is the umbrella over payments, lending, insurance, and more.
- BaaS powers embedded finance from underneath. As Stripe explains in its embedded finance vs. BaaS guide, embedded finance is the front-end access layer customers see, while BaaS is the back-end banking functionality that makes it legally and technically possible.
Why merchants conflate them (and why it costs you)
Most merchants experience all three as one smooth surface — you never see the chartered bank behind your business account or the acquirer behind your card processing. But conflating them obscures real strategic questions: Who actually holds your funds? Who bears compliance risk? Who can change the take-rate? Understanding the layers tells you which relationships you can negotiate and which you're simply renting.
The front-end vs. back-end mental model
Adyen's explainer on embedded finance vs. BaaS offers a useful shorthand: embedded finance is defined by front-end access to financial services, BaaS by back-end banking functionality. When you read a fintech announcement, ask which layer it's describing. A "new business account" is usually embedded finance riding on BaaS rails. A "new card-processing feature" is usually embedded payments.
How the Model Works Under the Hood
Underneath the invisible checkout sits a specific commercial machine. The most important concept to understand is the payment facilitator — usually shortened to PayFac — because it's the mechanism that lets a software platform offer native payment acceptance without making every merchant set up their own processor account.
The PayFac and sub-merchant structure
In the traditional model, every business needed its own merchant account, which meant a slow underwriting process that could take weeks. The PayFac model flips this. According to NMI's guide to the payment facilitator model, a payment facilitator owns a master merchant account and onboards businesses as sub-merchants under that umbrella. The PayFac handles transaction processing, underwriting, and risk on the sub-merchants' behalf.
The practical payoff: onboarding that once took two weeks now takes 24 to 48 hours. When you sign up for Shopify Payments and start accepting cards almost immediately, you're being onboarded as a sub-merchant under Shopify's facilitator structure. That speed is a feature of the model, not a coincidence.
ISVs, white-label, and PayFac-as-a-Service
Most software companies don't want to build payment infrastructure from scratch — the compliance and risk burden is enormous. So a layer of providers offers white-label or PayFac-as-a-Service arrangements. Stripe's explanation of white-label PayFacs describes it cleanly: a third party supplies the underlying technology, processing infrastructure, compliance, and risk management, while the ISV (independent software vendor) wraps it in its own branding.
This is why so many vertical SaaS tools now have "payments" in their pitch. The pattern looks like this:
- The platform partners with a payment facilitator or PayFac-as-a-Service provider.
- The provider supplies pre-built flows, APIs, and compliance scaffolding.
- The platform customizes the branding and UI so payments feel native.
- The platform onboards its users as sub-merchants and earns a share of each transaction.
Who carries the risk
A critical nuance: PayFacs assume real risk. They're responsible for the sub-merchants beneath them, which means chargebacks, fraud, and compliance failures roll up to the facilitator. That's part of why platforms charge a margin on processing — they're not just passing payments through, they're underwriting them. If you've dealt with a hold or a chargeback dispute, you've seen this risk function in action. Our guide on handling your first chargeback on Shopify shows the merchant side of that same risk machinery.
Why the Model Matters for Ecommerce
It's easy to file this under "interesting plumbing." But the model reshapes four things merchants and operators actually care about: conversion, data, unit economics, and new revenue lines. Let's take them in turn.
Conversion: fewer redirects, more completed sales
Every redirect, re-entry, and unfamiliar brand at checkout is a leak. Embedding payments seals those leaks by keeping buyers on-site through the moment of purchase. This is also why embedded financing options convert: when Shopify layered Shop Pay Installments into checkout via its Affirm partnership, Shopify reported a 28% drop in checkout abandonment for eligible flows. Reducing friction at the exact decision point moves the needle more than almost any top-of-funnel tactic. If conversion is your focus, pair this with our Shopify checkout optimization tips.
Data: owning the full transaction signal
When payments live inside your platform, the platform sees the entire transaction lifecycle — approvals, declines, refunds, dispute patterns, cash-flow timing. That data feeds smarter fraud screening, dynamic financing offers, and faster payouts. A merchant redirecting to an external gateway hands that signal away. Keeping it in-platform is what makes products like working-capital advances possible in the first place.
Unit economics and new revenue lines
Here's the part operators should sit up for. Payment processing isn't a cost center for platforms — it's a revenue engine.
| Dimension | Traditional gateway redirect | Embedded payments model |
|---|---|---|
| Onboarding speed | Days to weeks | 24–48 hours |
| Checkout experience | Off-site, multi-brand | On-site, single brand |
| Who captures processing margin | Third-party processor | The platform |
| Data ownership | Split with processor | Platform-owned |
| New revenue lines | Limited | Lending, accounts, installments |
As North's developer blog notes, owning payment functionality gives software companies a new revenue stream on top of a better customer experience. For Shopify, payments and financial services are a fast-growing share of revenue precisely because the platform monetizes the money movement it already facilitates. Understanding this helps you read the take-rate on your own statements with clearer eyes — and explore more in our payments and checkout resources.
Shopify as the Embedded Finance Case Study
No company illustrates the payments-to-finance arc better than Shopify. It started with payments and methodically layered financial products on top, turning a commerce platform into a fintech stack. Walking through its products makes the abstract model concrete.
Shopify Payments and Shop Pay
Shopify Payments is the foundation: native card acceptance inside the admin, no external gateway, merchants onboarded as sub-merchants. Shop Pay extends this with an accelerated, tokenized checkout that remembers buyer details across the Shopify network — the conversion layer sitting directly on top of the payment rail.
Shopify Capital: embedded lending
In 2016, Shopify made its first move beyond payments with Shopify Capital. Because the platform already sees each merchant's full sales history, it can underwrite financing in a way a cold-start lender cannot. Per Shopify's own Help Center on Capital, it offers merchants working-capital funding drawn from that transaction data — embedded lending powered by embedded payment visibility.
Shopify Balance and Shop Pay Installments
Two more products complete the picture:
- Shopify Balance is a business account interface where merchants view cash flow, pay bills, and receive sales payouts — in some cases days earlier than a traditional bank would settle them. This is embedded finance in its banking form.
- Shop Pay Installments, built on a partnership with Affirm, lets shoppers split purchases over time. Shopify's Shop Pay Installments documentation describes plans offering interest-free payments over several months on qualifying order values. This is embedded consumer lending at the point of sale.
If you want the merchant-facing setup for that last one, see our Shop Pay Installments setup guide and our broader walkthrough on adding buy now, pay later to a Shopify store.
The strategic lesson
Shopify's playbook is the embedded-finance thesis in miniature: start by embedding payments to own the transaction, use that data to embed lending and banking, and capture margin at every layer. Each product reinforces the others, raising merchant retention and gross merchandise value. That's why the model is so attractive to platforms — and why understanding it helps you evaluate every "we now offer financing" pitch that lands in your inbox.
The Agentic and Embedded Finance Future
The next chapter of embedded payments is being written by AI. As shopping increasingly happens through AI agents that research, compare, and buy on a customer's behalf, payments have to become not just invisible to humans but consumable by software. Embedded rails are the precondition for that shift.
Why agents need embedded rails
An AI agent can't navigate a redirect-heavy, human-only checkout the way a person can. It needs programmatic, embedded payment endpoints it can call directly. The platforms that already own the payment rail are best positioned to expose those endpoints safely. Our explainer on what agentic commerce is and how it works maps this transition in detail, and our piece on agentic checkout digs into the purchase moment specifically.
Embedded finance gets programmatic
It's not only payments. Financing offers, fraud checks, and identity verification all become API calls an agent can trigger mid-purchase. The same back-end BaaS infrastructure that powers today's embedded finance becomes the substrate for agent-initiated transactions. Stitch's analysis of how embedded finance is transforming online retail points to this convergence of payments, lending, and data into a single programmable layer.
What this means for merchants
You don't need to build agent infrastructure yourself. But you should make sure your store is structured so embedded, programmatic checkout can function — clean product data, standard payment methods, and platform-native flows. Merchants who fight the embedded model with bolted-on, redirect-heavy workarounds will be hardest for agents to transact with. Keep an eye on our AI and emerging tech coverage as this space matures.
The Risks and Tradeoffs Merchants Should Weigh
The embedded model is convenient, but convenience has a price. Treating it with clear eyes means naming its downsides as plainly as its benefits.
Platform dependency and lock-in
When your payments, your business account, your financing, and your storefront all live inside one platform, switching costs compound. The same integration that makes everything seamless also makes leaving expensive and operationally painful. Concentration is a real strategic risk — your cash flow, payouts, and credit can all hinge on a single provider's decisions.
Take-rate and margin compression
Platforms monetize the payment rail through a take-rate on every transaction, plus margins on lending and accounts. That's the business model. For a high-volume merchant, fractions of a percent on processing add up to meaningful money — which is exactly why comparing your blended cost against alternatives still matters. Our comparison of Shopify Payments vs. Stripe is the right place to pressure-test gateway-level economics if you're weighing the setup decision.
Compliance and risk you don't see
Because the PayFac carries underwriting and compliance risk, it also enforces it — which means holds, reserves, and account reviews can hit you with little warning. The convenience of instant onboarding is matched by the platform's right to pause or restrict your account if its risk models flag you. You're operating under someone else's risk appetite.
Here's a quick framework for weighing the tradeoff:
| If you value... | The embedded model is... |
|---|---|
| Speed to launch and zero setup overhead | A strong fit |
| Native conversion and unified data | A strong fit |
| Maximum negotiating leverage on rates | A weaker fit at low volume |
| Independence from any single platform | A real risk to manage |
| Programmatic, agent-ready checkout | Increasingly essential |
What Merchants and Operators Should Actually Do
Understanding this model is only useful if it changes a decision. Here's how to convert the knowledge into action depending on who you are.
If you run a store
Don't treat your payment stack as set-and-forget. Audit your blended processing cost at least annually, know which embedded financial products you're paying for, and read your take-rate the way you'd read any other line item. Lean into the conversion benefits — native checkout, installments where they fit your average order value — but keep a clear-eyed inventory of your platform dependency. Diversification doesn't have to mean leaving; it can mean keeping a secondary processor relationship warm.
If you build or advise on Shopify
The embedded model is your context for nearly every payments conversation. When a client asks whether to add financing, you're really advising on embedded consumer lending. When they ask about payout speed, you're discussing embedded banking. Frame recommendations around the layers — payments, finance, BaaS — so clients understand what they're actually buying. The Shopify experts and operators in our community trade exactly these judgment calls daily.
If you're choosing a platform or PayFac provider
Compare on the things the layers expose: who holds funds, who carries compliance risk, what the take-rate is across payments and financing, and how programmable the checkout is for the agentic future. Bain's research on embedded finance is a strong primer on where the value is migrating across the chain — read it before signing a multi-year payments deal.
Decision box — Should you lean into embedded payments? Lean in if: you want the fastest setup, the highest native conversion, unified transaction data, and a checkout that's ready for AI agents. The embedded model is the default for a reason. Proceed with caution if: you're high-volume and want maximum rate leverage, you need independence from any single platform, or your business model depends on owning the direct processor relationship. In those cases, weigh the take-rate and lock-in against the convenience, and benchmark against alternatives before committing.
Want to pressure-test your own payment strategy against other operators? The Shopify growth community is where merchants and experts compare take-rates, financing offers, and platform tradeoffs in real time.
Frequently Asked Questions
What is the difference between embedded payments and embedded finance?
Embedded payments are one specific financial function — accepting payments — built directly into a non-financial platform. Embedded finance is the broader category that also includes lending, insurance, and banking integrated into that same platform. In short, accepting payments natively is a subset of embedded finance.
Is Shopify Payments an example of embedded payments?
Yes. Shopify Payments lets merchants accept cards natively inside Shopify without redirecting customers to an external gateway, and onboards merchants as sub-merchants under Shopify's payment-facilitator structure. That's a textbook embedded payments setup, and it's the foundation Shopify built embedded finance products like Capital and Balance on top of.
How big is the embedded finance market?
Bain & Company projects financial services embedded into ecommerce and software platforms will exceed $7 trillion in US transaction value by 2026, up from $2.6 trillion in 2021. Consumer payments make up the majority of that volume, which is why payment-centric platforms are so central to the trend.
Do embedded payments cost merchants more?
It depends on volume. Platforms monetize the embedded model through a take-rate on each transaction plus margins on financing and accounts. For lower-volume stores, the convenience and conversion benefits usually outweigh the cost. For high-volume merchants, even small rate differences add up, so it's worth benchmarking your blended cost against alternative processors.
The Takeaway
Embedded payments aren't a feature you turn on — they're the architecture you're already operating inside every time a customer checks out without leaving your store. The model collapses the old gateway redirect into an invisible, on-platform flow, and it's the launchpad for embedded finance: the lending, banking, and installment products that platforms like Shopify layer on to deepen merchant relationships and capture margin at every step.
The strategic move isn't to resist this — it's to understand it. Know the difference between embedded payments, embedded finance, and the BaaS infrastructure underneath. Read your take-rate clearly. Lean into the conversion and data benefits while managing the very real risks of platform dependency and lock-in. And get your store structured for the agentic future, where AI agents will transact through exactly these embedded rails.
What's your experience been with the embedded financial products on your platform — has Capital, Balance, or Installments actually moved the needle for your store, or does the take-rate sting? Bring your numbers and your hard-won opinions to the Talk Shop Discord community and compare notes with other operators figuring out the same tradeoffs.
About Talk Shop
The Talk Shop team — insights from our community of Shopify developers, merchants, and experts.