Payhip vs Gumroad: Fees, Storefronts and Seller Control Compared

A creator selling a $29 Notion template can list the exact same file on Payhip or Gumroad. The customer sees a checkout button, taps it, pays, and downloads. From the outside, the two experiences look almost interchangeable.

Behind that checkout button, the seller has made a very different set of decisions — about who touches the money first, who is responsible for sales tax in forty different countries, how much of the storefront actually belongs to them, and what happens if they ever want to leave. That is the real substance of Payhip vs Gumroad, and it’s a comparison most existing guides reduce to a single number: 5% versus 10%.

Fees matter, but they’re the smallest part of the decision. The bigger question is which platform lets an independent seller keep more control over the business they’re building — the storefront, the checkout, the payment rail, the tax relationship, the customer list — and what that control costs in dollars, complexity, or both.

Quick answer: Payhip is the stronger default when a seller wants lower direct-sale platform costs, an easier no-code branded storefront, customizable checkout styling and a payment relationship that normally sits with the seller’s chosen processor. Gumroad is stronger when Merchant-of-Record tax coverage, a centralized commerce stack, Discover, advanced team permissions or multi-seat software licensing matter more. Gumroad’s storefront is no longer simply a fixed creator profile: it can now be replaced with fully custom HTML, but that freedom comes through an agent/CLI workflow rather than a conventional visual store builder.

The short version

Payhip tends to be the stronger fit when a seller wants:

• Lower platform costs on ordinary direct sales
• A visual store builder that does not require coding or an AI-agent publishing workflow
• A custom domain, branded store pages and increasingly customizable checkout styling
• A payment stack that normally connects directly to the seller’s own Stripe, PayPal or regional gateway
• Marketplace exposure without a separate marketplace commission
• A free starting tier with no monthly platform charge

Gumroad tends to be the stronger fit when a seller wants:

• Global Merchant-of-Record tax handling
• No monthly platform subscription
• Gumroad Discover as an additional acquisition channel
• A storefront that can now be replaced with fully custom HTML when the seller is comfortable using Gumroad’s agent/CLI workflow
• Unlimited account team members with role-based permissions
• Multi-seat software licensing and a mature creator-commerce back end

The most important update is that this is no longer a comparison between a "customizable Payhip store" and a "fixed Gumroad profile." Gumroad has changed materially. Its storefront can now be fully custom HTML. Payhip still has the accessibility advantage for sellers who want to design and maintain a branded store through a conventional interface rather than through code or an agent.

So the comparison has become more interesting: Payhip offers easier storefront control; Gumroad can offer deeper technical storefront control. The decision then shifts to fees, checkout, payment flow, tax responsibility and how much of the commerce stack the seller wants to operate directly.

Same product, two different business architectures

Once you strip away the marketing language, both platforms can host products, take payments, deliver content and report sales. The meaningful differences show up in what sits around the transaction.

Payhip functions primarily as commerce software connected to payment processors the seller chooses. Its current payment setup supports Stripe, PayPal and a growing list of regional gateways. That means the storefront and checkout layer can sit on Payhip while the seller maintains a separate relationship with the processor that moves and settles the money.

Gumroad is more centralized, but describing it as completely closed is no longer accurate. For standard card sales, Gumroad sits deeply in the transaction and settlement process as Merchant of Record. However, eligible sellers can connect PayPal through PayPal Connect, and the net amount from those PayPal sales goes directly to the seller’s PayPal account. Gumroad also documents Stripe Connect for legacy connected accounts and certain eligible cases, including Brazil.

That distinction matters because the phrase "Gumroad controls the payment rail" is only fully true for the standard Gumroad-settled flow. The modern platform now mixes two architectures: a centralized Merchant-of-Record system for its standard transactions and direct connected-account flows for some supported payment methods.

Neither structure is objectively superior. Payhip gives a seller a more conventional independent-merchant setup. Gumroad removes more compliance and settlement work from the seller by default, while still allowing some direct connected-account flows. The question is not simply who "owns" checkout; it is which responsibilities remain portable outside the platform and which are delegated to it.

The seller-control comparison

Nobody wins every row. Payhip’s advantages cluster around accessible control and direct-merchant economics: the seller can build a branded store without code, connect a processor they already use and move from 5% to 2% to 0% Payhip fees as revenue grows.

Gumroad’s strengths cluster around delegation plus technical depth. It can assume global Merchant-of-Record duties, operate a marketplace, support sophisticated account roles, handle multi-seat licenses and now publish a fully custom HTML storefront. The trade-off is that its standard direct-sale fee remains materially higher than Payhip’s at most sales levels, even after allowing for the new high-volume discount.

Fees: not a calculator, a pricing philosophy

This section is deliberately not another five-tier revenue calculator. The useful difference is the shape of the cost model and what happens to seller control as revenue increases.

Payhip’s three-way trade

Payhip’s pricing page lists three tiers, and the core feature set is broadly shared across them:

• Free Forever — $0/month, 5% Payhip transaction fee
• Plus — $29/month, 2% Payhip transaction fee
• Pro — $99/month, 0% Payhip transaction fee

Processor fees still apply. The important part is that Payhip lets a seller exchange a fixed monthly cost for a lower platform percentage without moving to a different product ecosystem.

That gives the seller a simple progression. Early on, fixed cost can stay at zero. Once sales become predictable, the seller can pay $29 to reduce Payhip’s percentage. At a larger scale, $99/month removes Payhip’s own transaction fee. The platform is effectively letting the seller buy back margin as the business matures.

That pricing architecture is one reason our full Payhip review scores the platform strongly on value. The point is not that the Free plan is always cheapest. It is that the seller has several economically different ways to run the same basic commerce stack.

Gumroad’s direct-sale model — including the new volume discount

Gumroad’s current official fee documentation lists 10% + $0.50 on direct/profile sales, with credit-card processing currently listed separately at 2.9% + $0.30 and PayPal fees separate where PayPal is used. Discover-sourced marketplace sales are charged 30%, which includes processing.

The important 2026 update is the high-volume discount. Once a seller reaches $20,000 in paid sales during a calendar month, new direct sales for the rest of that month are charged 5% + $0.50 instead of 10% + $0.50. The counter resets on the first day of the next month. A refund can push the seller back below the threshold, in which case new direct sales return to the standard rate until the threshold is crossed again.

That materially improves Gumroad’s economics for high-volume sellers, but it does not turn the platform into a flat 5% service. The first $20,000 of qualifying paid sales in a new calendar month still occurs before the lower rate is triggered, and the $0.50 fixed component remains.

The fixed component matters disproportionately on low-priced products. On a $100 product, $0.50 is minor. On a $5 download, it represents another 10% of the product price before processor charges are considered. That is why "10% versus 5%" is too crude: unit price and sales source matter.

Our Gumroad review goes deeper into its payout architecture and account-level controls. For this comparison, the essential point is simpler: Gumroad has improved its high-volume pricing, but Payhip still gives sellers more ways to deliberately trade monthly cost against transaction percentage.

The storefront: who owns the destination?

This is the section that changed most dramatically.

Payhip’s store builder remains the more conventional option. A seller can choose themes, edit sections, create pages, connect a custom domain and use custom CSS. Payhip also supports embedded HTML/JavaScript blocks on stores using a custom domain. For a creator who wants to sign in, visually edit a store and publish without adopting a developer workflow, that remains a meaningful advantage.

Gumroad, however, can no longer be described as a fixed profile template with a custom domain pasted on top. Its current documentation says the profile page can be replaced with fully custom HTML with no fixed layouts, blocks or sections. Gumroad expects that page to be built and maintained through its Agent or another coding agent, then previewed and published with Gumroad’s CLI workflow. The custom page can replace the entire profile at the normal Gumroad subdomain or a connected custom domain.

That changes the comparison completely.

If the question is "which platform gives me the easiest no-code way to make a branded store?", Payhip has the cleaner answer.

If the question is "which platform lets me replace the storefront with arbitrary custom HTML?", Gumroad now has a surprisingly powerful answer — potentially more flexible than a conventional section-based builder, provided the seller is comfortable working through an agent or code-oriented workflow.

Gumroad also supports standalone pages, while its custom profile can expose live product prices and catalogue data. Payhip has its own advantage in a more integrated visual store-building workflow, where homepage, product catalogue, additional pages, store styles and commerce controls live in the same editor.

So "Payhip has more customization" is no longer accurate enough. A better distinction is:

• Payhip = easier operational storefront control
• Gumroad = deeper technical frontend control, higher setup complexity

For many independent sellers, easier control will still be more useful than theoretically unlimited HTML freedom. But advanced sellers should no longer dismiss Gumroad because of an outdated assumption that every store must look like the same creator profile.

Checkout control: two different kinds of "hosted"

Storefront freedom and checkout freedom are not the same thing.

Payhip added a more customizable checkout experience in 2026. For digital and physical products, sellers can currently control branding elements such as the logo, banner image, background treatment and button colors, and Payhip documents support for custom CSS. The overall checkout structure remains fixed — sellers cannot rearrange every field or inject arbitrary JavaScript — but the visual hand-off from a branded store can be made substantially more consistent than it used to be.

For courses, memberships and coaching products, Payhip’s checkout customization is somewhat more constrained in the visual editor, though custom CSS remains part of the documented workflow.

Gumroad supports Overlay and Embed integrations on external websites. That means a seller does not have to send every visitor to a standalone Gumroad product page just to begin a purchase. The product experience can open over or inside an existing WordPress, Webflow, Squarespace or other site.

The final transaction, however, still relies on Gumroad’s hosted commerce layer. This creates an important asymmetry: Gumroad now gives advanced sellers enormous freedom over the storefront HTML, while Payhip currently gives sellers more explicit styling control over the checkout page itself.

That is a useful distinction competitors often miss. Storefront control is not checkout control. A platform can be highly flexible before the buyer clicks "buy" and still keep the payment step structurally standardized for security, compliance and payment reliability.

Payment control: the difference that most comparisons skip

This is the part of Payhip vs Gumroad that explains most of the downstream differences in settlement, disputes and portability.

Commerce software is the layer that manages products, pages, checkout logic and delivery. The payment rail is the layer that actually moves and settles the money. Payhip and Gumroad bind those layers differently.

Payhip normally asks the seller to connect a supported processor. Stripe and PayPal are the obvious examples, but Payhip has expanded support for additional regional gateways. The seller therefore maintains a merchant relationship outside Payhip. Processor-level payouts, verification, reserves and disputes are not magically removed — they are simply handled in the connected payment account rather than being entirely abstracted behind Payhip.

This creates real portability. If a seller later moves from Payhip to another commerce platform that also supports the same processor, the underlying Stripe/PayPal-style merchant account does not need to be recreated from zero.

Gumroad’s standard transaction architecture is more centralized. Gumroad acts as Merchant of Record and standard card revenue generally enters Gumroad’s settlement system before the creator is paid. For those sales, payout eligibility, account review, holding periods and payout configuration become part of the creator’s cash-flow model.

But the old absolute statement — "Gumroad never lets the seller connect a processor" — is now wrong.

Gumroad currently offers PayPal Connect in supported countries. Its documentation says the net amount from those PayPal purchases goes directly to the seller’s PayPal account at the time of sale. The seller also handles PayPal disputes on those connected transactions. Gumroad additionally documents Stripe Connect for certain existing/eligible arrangements, with connected Stripe transactions similarly moving to that account rather than waiting for the standard Gumroad payout cycle.

That means Gumroad is best understood as a hybrid:

• standardized Gumroad settlement for the default transaction path;
• direct connected-account settlement for supported PayPal Connect and certain Stripe Connect transactions.

For standard Gumroad-settled sales, creators can configure payout cadence subject to eligibility and platform rules. Gumroad’s current documentation describes daily, weekly, monthly and quarterly schedules in supported cases, with a standard minimum balance threshold and at least a seven-day holding period applying to ordinary payout-eligible sales. Connected PayPal sales are different because the net sale amount can arrive immediately in PayPal.

Payhip still has the cleaner story if payment independence is the priority because external processing is the normal design rather than an optional branch. Gumroad has, however, narrowed that gap enough that "closed payment system" is no longer a fair description.

Tax: convenience and control aren’t the same thing

Tax handling is one of Gumroad’s clearest advantages, but Payhip’s position has strengthened significantly in 2026.

For digital EU and UK VAT, Payhip’s current documentation says Payhip acts as the reseller and takes responsibility for collecting and remitting the applicable VAT. From July 1, 2026, Payhip also states that it handles US sales tax as a marketplace facilitator.

Canada changed at the same time. Payhip now handles GST/HST and PST as a digital platform operator. There is one important exception in its latest published guidance: Quebec QST is still excluded while Payhip completes its QST registration, so sellers with an applicable Quebec obligation may still need to handle that separately.

Outside the jurisdictions Payhip explicitly takes responsibility for, sellers should not assume the platform is a universal Merchant of Record. Payhip can support tax configuration, but that is not the same as Payhip assuming every global indirect-tax obligation.

Gumroad’s model is broader. Since January 1, 2025, Gumroad has described itself as the Merchant of Record, handling applicable sales tax, VAT and GST worldwide on Gumroad transactions. For a seller with customers scattered across many jurisdictions, that is not a cosmetic feature. It can remove a substantial compliance workflow.

The trade-off is conceptual as much as financial:

• Payhip: the seller retains a more independent merchant/payment structure while Payhip takes over important tax categories and jurisdictions.
• Gumroad: more of the transaction and tax responsibility is centralized inside the platform’s Merchant-of-Record model.

A seller may rationally accept a higher platform fee because global tax delegation is worth more than the fee difference. Another seller with an accountant, a preferred processor and mostly domestic customers may prefer the control of Payhip’s architecture.

This article is not tax advice. Platform documentation can explain what the platform collects and remits; it cannot determine every filing, registration or zero-return obligation for a specific business.

Marketplace control: Payhip has one too

One of the most persistent errors in older Payhip vs Gumroad comparisons is the idea that Gumroad has discovery while Payhip has none.

Payhip now operates its own Marketplace. Current eligibility requires the store to have made at least $10 in total sales and to pass an account review. Individual digital products then go through product approval. Payhip says it aims to complete product approval within roughly ten days, though it may take longer.

The economic model is unusually seller-friendly: Payhip does not charge an additional marketplace fee. A Marketplace sale still uses the transaction fee associated with the seller’s normal Payhip plan.

For the eligibility details, see our separate guide to how the Payhip Marketplace approval process works.

Gumroad Discover has a higher threshold before platform-driven discovery becomes relevant. Current official guidance says the creator must complete payout settings, reach at least $100 in genuine sales/balance, and pass Gumroad’s risk review. A product also needs at least one successful sale and must meet Discover requirements.

Discover’s economics are also different. A Discover-sourced sale is charged 30%, including processing, rather than the normal direct-sale fee.

That does not automatically make Payhip’s Marketplace "better." Neither platform publishes enough reliable marketplace traffic and conversion data to tell a new seller how many incremental buyers to expect. A lower commission on zero marketplace sales is worth zero.

The more useful strategic question is who owns acquisition.

A seller bringing their own audience to Payhip can largely ignore the Marketplace and focus on direct economics. A seller on Gumroad can similarly treat Discover as optional upside, but when Discover actually supplies the buyer, Gumroad takes a much larger share because the platform is providing the acquisition channel.

This makes Payhip Marketplace easier to experiment with financially, while Gumroad Discover behaves more like a paid distribution channel funded through a higher success fee.

The customer relationship: whose asset is it?

The deeper question is not which platform has more marketing widgets. It is whether the seller can keep a usable customer asset outside the platform.

Both platforms provide customer data and export paths. Gumroad’s Sales dashboard supports CSV export, while its audience tools let creators export subscribers. Payhip similarly exposes customer/order information and monthly sales reporting, and it connects to external email-marketing providers.

That matters because a custom domain by itself is not ownership. A seller can own a domain and still be dependent on a platform for every customer record, license state and transaction history.

Payhip’s normal architecture makes it relatively natural to split the stack: Payhip for storefront and delivery, a separate payment processor for settlement, and a separate email service for lifecycle marketing. If one layer changes later, the others do not necessarily have to move at the same time.

Gumroad can also export customers and subscribers, and its new custom HTML pages make the audience-facing layer more portable in concept than it used to be. The platform still mediates more of the operational relationship for standard transactions because Merchant-of-Record settlement, the customer library, Discover history and some product-specific infrastructure live inside Gumroad.

The practical takeaway is not "Payhip owns the customer." No platform can grant a seller unlimited rights to contact buyers regardless of consent. The advantage is architectural: Payhip more naturally encourages a modular stack; Gumroad more naturally encourages a consolidated stack.

Modularity is easier to replace one piece at a time. Consolidation is easier to operate day to day.

Product control: where Gumroad legitimately wins something

This section also needs an update because Payhip has closed two gaps that older comparisons still repeat.

Software licensing: both now deserve to be taken seriously

Gumroad has a mature license-key system with verification APIs and, importantly, multi-seat licensing. A software seller can let a buyer purchase several seats under one license and can manage seat counts later. That is particularly useful for plugins, developer tools and small B2B software products.

Payhip also has a real software-license system. It can automatically generate keys or accept pre-generated keys, and its current API supports verification plus enable/disable and usage operations. In 2026, Payhip expanded this further with pre-generated key support.

So it is no longer correct to say "Gumroad has licensing; Payhip does not." The real distinction is narrower: Gumroad has the stronger built-in multi-seat model, while Payhip offers a capable generated/imported-key workflow that will cover many one-user-per-license products.

Collaboration: Payhip also added it

Payhip now supports product collaborations for digital products. A primary creator can add up to three collaborators, assign revenue percentages and automatically split proceeds through PayPal, subject to Payhip’s documented requirements.

Gumroad still goes further at the account level. Its product Collaborators feature can split product economics, while its Teams system allows unlimited team members with distinct Owner, Admin, Marketing, Support and Accountant permissions. Those role boundaries are useful when a creator business grows beyond a solo operation.

That gives Gumroad a legitimate advantage for operational teams, even though the old claim that "Payhip has no collaboration feature" is obsolete.

Product breadth still favors Payhip for mixed creator businesses

Payhip supports digital downloads, courses, coaching, memberships and physical products inside the same overall account structure. Its course product includes lessons and dedicated course-management features rather than forcing the seller to simulate a course with file delivery alone.

Gumroad remains highly capable for digital products, memberships and software, and its current creator tooling is deeper than the minimalist front end suggests. But for a seller combining courses, coaching and standard downloads under one storefront, Payhip’s product model is easier to treat as a small creator-commerce suite.

The net result is more balanced than the old checklist:

• Payhip: broader creator-product mix, capable license keys, collaborations
• Gumroad: stronger team permissions, multi-seat licensing, mature centralized operations

The exit test: what can you actually take with you?

Imagine building the business for two years and then deciding to move. Which assets survive the migration?

Original product files remain the seller’s on both platforms. Custom domains also remain portable because the domain is registered independently; migration means changing DNS rather than asking the commerce platform to release ownership of the domain.

Customer and audience data can be exported from both platforms, subject to the normal legal limits around marketing consent and data use.

The more interesting differences appear one layer deeper.

Payment relationship

On Payhip, the connected payment account is normally independent of Payhip. A Stripe, PayPal or other supported processor relationship can often continue when the seller changes commerce software.

On Gumroad, standard card transactions sit within Gumroad’s Merchant-of-Record and payout architecture. There is no equivalent independent merchant account for that standard flow to "take" to the next platform.

But Gumroad’s connected-account options complicate the old story in a useful way. A seller using PayPal Connect already has those transactions moving into their own PayPal account, and certain Stripe Connect users also maintain a connected processor relationship. For those sales, payment portability is stronger than it is for the standard Gumroad balance flow.

Storefront

Payhip store design itself is not portable as a one-click export. The seller keeps their brand assets, copy, domain and product files, but would need to rebuild the actual store elsewhere.

Gumroad’s new custom HTML storefront creates an interesting edge case. The underlying HTML/design logic may be easier for a technically capable seller to reproduce elsewhere than a proprietary visual-builder theme, but Gumroad-specific catalogue data, live-price attributes and publishing workflow will still need to be replaced.

Subscriptions and licenses

Neither platform should be treated as a zero-friction migration for recurring billing. Subscription payment tokens and platform-specific billing relationships can create migration work even when customer emails are exportable.

License infrastructure is similar. Payhip and Gumroad both expose license systems and APIs, but an application built around either platform’s verification endpoint will need engineering work if the seller changes licensing providers. Gumroad’s multi-seat state is especially platform-specific.

Marketplace reputation

Payhip Marketplace approval and Gumroad Discover ranking are inherently non-portable. Marketplace visibility belongs to the marketplace.

The setting I would examine first before choosing either platform is therefore not the color picker. It is the dependency map: payment processor, tax role, subscriptions, license API, customer export, custom domain and acquisition channel.

A store can be rebuilt. Rebuilding the invisible infrastructure behind it is usually the harder migration.

Which sellers fit where

Seller A — sells a $9 template to an existing audience.
Payhip is the cleaner default. The 5% Free-plan platform fee has no monthly charge, while Gumroad’s standard direct rate includes both a percentage and a fixed $0.50 platform component before processing. On a low-ticket product, fixed per-sale charges matter disproportionately.

Seller B — sells a $49 ebook plus templates and wants a polished branded store without coding.
Payhip has the advantage because its native store builder, custom domain support and checkout styling can all be managed without adopting an agent/CLI storefront workflow.

Seller C — is technical and wants a highly custom front end but does not want to operate a separate tax stack.
Gumroad becomes much more compelling than older comparisons suggest. A fully custom HTML profile combined with Merchant-of-Record tax handling is a distinctive combination. The seller gives up margin relative to Payhip in many direct-sale scenarios but gains frontend freedom plus centralized tax handling.

Seller D — sells software to teams.
This is no longer a simple Gumroad win because Payhip now supports generated and pre-generated license keys with an API. Gumroad still has the technical edge when multi-seat licensing and role-based internal teams matter. For a simple one-key-per-customer application, either platform can now work.

Seller E — co-creates digital products with partners.
Both platforms support collaborator revenue splitting. Payhip supports up to three collaborators per digital product through its documented PayPal-based workflow. Gumroad is stronger if the business also needs unlimited internal team members with different operational permissions.

Seller F — has no existing audience and wants platform discovery.
Neither marketplace comes with a reliable traffic guarantee. Payhip’s Marketplace is cheaper to experiment with because it adds no separate marketplace fee, while Gumroad Discover takes 30% on sourced transactions. Gumroad may still be worth that cost if Discover actually produces customers the seller would not have acquired independently.

Seller G — sells globally and wants the least tax-administration work possible.
Gumroad has the clearer advantage because the Merchant-of-Record model is broader than Payhip’s jurisdiction-specific tax handling. Payhip’s 2026 expansion into US and Canadian sales tax makes the gap smaller than it used to be, but it is not the same global architecture.

The verdict

Payhip is still the stronger default for an independent creator who expects to bring most of their own traffic and values direct-sale economics, an accessible branded storefront and a payment relationship that normally lives outside the commerce platform.

The reason is not that Gumroad has a weak storefront. That claim is outdated. Gumroad can now publish a fully custom HTML profile, and advanced sellers may actually prefer that technical freedom.

Payhip wins this specific comparison because its advantages line up more consistently with the three criteria in the title:

1. Fees: the seller can move from 5% to 2% to 0% Payhip platform fees by changing plans, while Gumroad’s standard direct fee is 10% + $0.50 until the seller reaches the current $20,000 monthly threshold for new qualifying direct sales.
2. Storefront operation: Payhip’s visual builder and checkout customization are easier to operate for a non-technical seller. Gumroad can be more technically flexible, but its fully custom storefront is intentionally agent/code driven.
3. Seller control: Payhip’s normal payment architecture keeps the seller connected to an external processor. That makes the commerce stack more modular.

Gumroad remains a strong choice when delegation is worth more than margin. Merchant-of-Record tax coverage, Discover, unlimited role-based team access and multi-seat licensing are substantial capabilities. Its PayPal Connect and certain Stripe Connect paths also make the payment architecture more flexible than the old "everything stays in Gumroad" description suggests.

Ecom Ratings currently scores Payhip at 8.7/10 and Gumroad at 8.2/10. Those ratings should not be treated as a universal winner label. The side-by-side Payhip vs Gumroad comparison is useful for the company-card data; this article addresses the narrower architectural question the cards cannot show.

For deeper platform-level analysis, see our Payhip review and Gumroad review.

FAQ

Is Payhip cheaper than Gumroad?
For many direct-sale businesses, yes. Payhip starts at 5% with no monthly fee, moves to 2% for $29/month and 0% Payhip transaction fee for $99/month, while processor fees remain separate. Gumroad’s standard direct-sale platform fee is 10% + $0.50, plus applicable processing. Gumroad now has a high-volume discount that reduces new qualifying direct sales to 5% + $0.50 after $20,000 paid sales in the same calendar month.

Does Gumroad still charge 10%?
Yes as the standard direct-sale platform rate, but that is no longer the entire story. After paid sales reach $20,000 in a calendar month, Gumroad currently reduces new direct sales for the remainder of that month to 5% + $0.50. The threshold resets monthly.

Does Payhip have a marketplace like Gumroad?
Yes. Payhip Marketplace requires eligibility and product approval, but Payhip currently charges no additional marketplace commission beyond the seller’s normal plan fee. Gumroad Discover has its own eligibility process and charges 30% on Discover-sourced sales.

Does Payhip or Gumroad give more storefront control?
It depends on what "control" means. Payhip gives non-technical sellers more accessible control through a native store builder and custom CSS. Gumroad now allows a fully custom HTML profile with no fixed layout, but it is built and maintained through Gumroad’s Agent or another coding-agent/CLI workflow.

Can I customize checkout on Payhip?
Yes. Payhip’s current checkout supports branding controls and custom CSS, although the overall checkout layout remains fixed and arbitrary JavaScript is not supported.

Can I connect my own PayPal account to Gumroad?
In supported countries, yes. Gumroad’s PayPal Connect lets eligible sellers receive the net amount from PayPal purchases directly into their PayPal account. This is an important exception to the standard Gumroad settlement flow.

Which platform handles taxes better?
Gumroad has the broader architecture because it acts as Merchant of Record and handles applicable sales tax, VAT and GST globally on Gumroad transactions. Payhip handles EU/UK digital VAT, US sales tax and Canadian GST/HST/PST under its current rules, while its latest guidance still excludes Quebec QST pending registration.

Does Payhip support software license keys?
Yes. Payhip can generate license keys or deliver pre-generated keys and provides verification/management API methods. Gumroad also supports software licensing and adds a built-in multi-seat license model.

Can Payhip split revenue with collaborators?
Yes. Payhip supports collaborators on digital products, with up to three collaborators and automatic percentage-based splitting through its documented PayPal workflow. Gumroad also supports product collaborators and additionally offers role-based account teams.

Can I move from Gumroad to Payhip later?
Products, domains and exported customer data can be moved, but the migration is not frictionless. Gumroad Discover history, standard Merchant-of-Record settlement history, subscriptions and Gumroad-specific licensing state do not simply transfer. The same principle applies in reverse to Payhip-specific store, subscription and licensing infrastructure.

Which is better for creators with their own audience?
Payhip is the stronger default in most cases because sellers who already bring their own buyers benefit more from Payhip’s lower direct-sale platform economics and modular payment setup. Gumroad can still be preferable if global Merchant-of-Record tax handling or its technical/team features save enough operational work to justify the fee difference.