A hosted checkout is a payment page run by someone else, so card details never touch your server. What matters is who runs that page and who takes a cut. A processor-hosted page charges you card rates, usually around 4% on a small sale. A marketplace-hosted page adds its own commission on top, which can double or triple that cost.
TL;DR:
- A hosted checkout keeps card data off your server, which shrinks your PCI burden to the lightest questionnaire (SAQ A) in most setups.
- "Hosted" describes who runs the page. It says nothing about who takes a commission, and that gap is where most sellers lose money.
- On a $25 sale, a standard US Stripe charge costs about $1.03 (4.1%). A 10% all-in marketplace fee costs $2.50.
- A $299 one-time license pays for itself after about 203 sales of a $25 product, if your current platform keeps 10% all-in. At a 5% all-in fee, it takes about 1,330 sales.
- Leaving a marketplace also means you handle sales tax and VAT yourself, so settle that before you switch.
Table of Contents
- Hosted Checkout Explained: Three Different Things People Call It
- Hosted Checkout vs. Iframe vs. Embedded Fields: What Changes
- What a Hosted Checkout Costs, Down to the Cent
- When a Hosted Checkout Is the Wrong Choice, and When the Marketplace Wins
- The Tax Question a Hosted Checkout Does Not Answer
- A Hosted Checkout Example: One $25 Template Pack, Start to Finish
- Conversion: Why Page Design Still Matters
- How to Choose: Four Rules You Can Apply Today
- Get a Self-Hosted Checkout That Pays Into Your Own Stripe and Wallet
- Frequently Asked Questions
- Sources
Hosted Checkout Explained: Three Different Things People Call It
Search results for this term mix up three setups, and they have different economics.
- Processor-hosted. Your payment processor serves the page, and you redirect customers to it. Stripe Checkout is the best-known example: you create a session through the API, send the buyer to a Stripe-hosted URL, and Stripe handles card entry, 3D Secure challenges and wallets like Apple Pay. You pay card processing fees and nothing else.
- Platform-hosted. A marketplace serves the page, owns the customer relationship at checkout, and often acts as the seller of record. You pay processing plus a commission, typically a percentage of every sale for as long as you use it.
- Self-hosted. You run the checkout software on your own domain and server. The processor still serves the card fields, but the page, the URL and the sales flow belong to you.
All three are "hosted" in the sense that matters for security: someone other than you handles raw card numbers. They differ in who gets paid, who sees your customer's email, and who can freeze your funds.
Hosted Checkout vs. Iframe vs. Embedded Fields: What Changes
Most readers ask about hosted payment pages versus iframes right after the definition. The practical difference is where the card number is typed and how much of the page you control.
| Approach | Where card data is typed | Typical PCI path | Branding control | Extra fee layer |
|---|---|---|---|---|
| Platform-hosted page | Marketplace domain | Handled by platform | Low | Commission on every sale |
| Processor-hosted redirect | Processor domain | SAQ A | Medium (logo, colors) | None |
| Iframe or embedded fields on your page | Processor iframe inside your page | SAQ A in most cases | High | None |
| Direct post or fully custom form | Your own page | SAQ A-EP or SAQ D | Total | None, but heavy compliance work |
The PCI Security Standards Council publishes the self-assessment questionnaires. SAQ A is the shortest and applies to merchants who fully outsource cardholder data handling. Redirect pages and properly implemented iframes generally qualify. Once your own page code touches the card data flow, you move to longer questionnaires. Confirm your exact eligibility with your processor or acquirer, because the rules change between PCI DSS versions.
For most small sellers I'd pick the iframe or embedded-fields route on a page you control. It keeps the lighter compliance path of a redirect and gives you a checkout that looks like your brand. A full redirect is fine if you want zero maintenance.
What a Hosted Checkout Costs, Down to the Cent
Take a $25 digital product. Stripe's published US pricing is 2.9% plus 30 cents per successful domestic card charge. That works out to $1.025 on a $25 sale, or 4.1% of the price. You keep $23.98. International cards and currency conversion add more, so check the current pricing page for your country.
A platform that keeps 10% all-in takes $2.50 on the same sale. The gap is $1.475 per sale.
At a 10% all-in marketplace fee and a $25 product, a $299 one-time license pays for itself on sale number 203.
Here is how the payback shifts with volume, using the same 10% versus 4.1% comparison:
| Sales per month | Monthly savings | Months to recover $299 |
|---|---|---|
| 50 | $73.75 | 4.1 |
| 100 | $147.50 | 2.0 |
| 300 | $442.50 | 0.7 |
| 1,000 | $1,475.00 | 0.2 |
Price changes the result too. A $100 product at a 10% all-in fee costs $10 against roughly $3.20 through Stripe, a saving of $6.80 per sale. The longer breakdown of how percentage cuts compound is in why you're losing money to platform fees.
When a Hosted Checkout Is the Wrong Choice, and When the Marketplace Wins

The obvious advice is "stop paying commissions." It is wrong in three cases.
- Low volume. If you sell 10 items a month, the savings are about $15 and a self-hosted setup costs you attention. Stay where you are.
- Low platform fees. If your all-in fee is 5%, your saving on a $25 sale is 22.5 cents. At 100 sales a month that is $22.50, and recovering $299 takes over a year. The math still works for a long-lived product, but it is not urgent.
- You want someone else carrying tax liability. Some platforms act as the seller of record and remit VAT or sales tax on your behalf. That service has real value, and the commission partly pays for it.
Above roughly 100 sales a month at a 10% fee, I would move. Below that, I would move only if payout holds, account freezes or lack of customer data already frustrate you.
The Tax Question a Hosted Checkout Does Not Answer
Moving to your own Stripe account makes you the seller. That means you register, collect and remit sales tax or VAT where thresholds apply. For digital goods sold to EU consumers, VAT applies from the first sale regardless of where you are based, and other countries have their own digital services rules.
Before you switch, read whether you need a merchant of record to sell digital products and the sales tax rules for indie software makers. Tax software and filing services add cost. Include that in your break-even calculation, because a saving of $1.47 per sale shrinks if compliance eats $50 a month.
A Hosted Checkout Example: One $25 Template Pack, Start to Finish
Here is the flow for a seller using a processor-hosted or self-hosted setup.
- The buyer clicks a payment link on your site or in an email.
- They land on a checkout page showing the product, price and any tax line.
- They enter a card, or pay with a wallet. If their bank requires 3D Secure, the processor runs the challenge.
- The processor charges the card and sends your server a confirmation event.
- Your server delivers the file and emails a receipt.
- Funds arrive in your own processor balance and pay out to your bank on your schedule.
Pro Tip: Deliver the product from the webhook, never from the success-page redirect. Buyers close tabs, lose connection or get stuck on a slow bank challenge, and a redirect-only flow will occasionally charge a card without delivering anything. Listen for the Stripe webhook event that confirms payment (checkout.session.completed for Checkout Sessions), verify its signature, and make delivery idempotent so a retried event doesn't send two copies.
Conversion: Why Page Design Still Matters
The page you choose affects completion rates. The Baymard Institute's cart abandonment research puts average documented abandonment near 70%, and a long or complicated checkout process is among the reasons shoppers give for leaving. A one-page flow with fewer fields tends to help.
A hosted page from a major processor is already tuned for this, so I would not build a custom form for a small catalog. The gain is trust and continuity. A buyer who clicks from your site to a checkout on your own domain sees the same name and design throughout, which avoids the jolt of landing on an unfamiliar marketplace URL.
How to Choose: Four Rules You Can Apply Today
- Under about 50 sales a month. Use a processor-hosted page and keep it simple.
- 50 to 100 sales a month at a 10% fee. Run the break-even table above with your own price. If payback is under six months, move.
- Over 100 sales a month. Own the checkout. The commission is a larger line item than most hosting, tools and software combined.
- Selling to many countries. Price in the tax work before you decide, and consider keeping a merchant-of-record option for the markets where filing is hardest.
If you want the ownership model spelled out, what you pay and own with a self-hosted license covers it, and why your own Stripe account beats a reseller explains the payout and dispute differences.
Get a Self-Hosted Checkout That Pays Into Your Own Stripe and Wallet
ReplaPay is a self-hosted checkout you buy once for $299. It connects directly to your own Stripe account, so card payments settle to you with Stripe's standard fees and no commission layer on top. It also takes crypto (Bitcoin, Lightning and stablecoins) straight to your own wallet, and it generates payment links for both. The Stripe fee calculator on the site lets you run your real price and volume through the math in this article before you pay anything.
The license includes 12 months of updates and 30 days of setup support. It has limits. You become the seller, so tax registration and remittance are yours to handle, and if you sell fewer than a hundred items a month at a low platform fee, the $299 may take a long time to earn back. Check the spec sheet and run your own numbers first.
Frequently Asked Questions
What is a hosted checkout?
A hosted checkout is a payment page served by a third party, usually a payment processor or sales platform, instead of your own server. The buyer enters card details on that page, so you never handle raw card numbers. This keeps your PCI compliance burden low.
Is a hosted payment page better than an iframe?
Neither is universally better. A hosted page redirects the buyer to the processor's domain and requires almost no maintenance. An iframe embeds the processor's card fields inside your own page, which gives you more control over design while usually keeping you in the lightest PCI category (SAQ A). Confirm eligibility with your processor.
Does a Stripe-hosted payment page cost extra?
Stripe does not charge a separate fee for its hosted Checkout page in standard setups. You pay the normal card processing rate, which is 2.9% plus 30 cents for domestic US cards on the published standard plan. Optional add-ons such as tax calculation or invoicing carry their own pricing, so check Stripe's pricing page.
Can I accept crypto on a hosted checkout?
It depends on the product. Many card-focused hosted pages do not take Bitcoin or Lightning at all. A self-hosted checkout can send crypto payments straight to your own wallet alongside card payments through your processor account.
When does a self-hosted checkout beat a marketplace?
When your sales volume is high enough that the commission exceeds the cost of running your own setup. At a 10% all-in fee on $25 products, a $299 license is repaid after about 203 sales. At a 5% fee, it takes about 1,330 sales.
Sources
- Stripe Checkout documentation | Stripe
- Stripe pricing | Stripe
- Stripe webhooks documentation | Stripe
- PCI Security Standards Council document library | PCI Security Standards Council
- Cart Abandonment Rate Statistics | Baymard Institute
