Ceramic instructor and collaborator recording a digital lesson together
Growth systems · Payhip Operator

Payhip Collaboration Revenue Sharing: Agree on the Terms Before You Invite a Co-Creator

Payhip can send a portion of a digital product’s sales to a collaborator through PayPal. The tool handles a defined payment step; the people making the product still need to agree on the work, the percentage, access, refunds, and rights.

A specialist records a lesson. A collaborator demonstrates a technique on camera, edits the footage, or builds the workbook. They decide to sell the finished product together. The question is not only whether they trust one another. It is whether they have described the arrangement clearly enough that each person understands what the percentage means after the first sale, the first update, or a customer refund.

Payhip’s Collaborations feature can automate a product-level payment share. It cannot decide what is fair, establish ownership of the work, or write the agreement between the people involved. Treat the percentage setting as the last step of the conversation, not the conversation itself.

What Payhip’s current documentation says

Payhip’s Help Center says Collaborations are available for digital products. The primary creator can assign up to three collaborators to a product, set each collaborator’s share between 10% and 90%, and must retain at least 10%. The primary creator and each collaborator need a Payhip account and a connected PayPal account. The current page was last updated April 16, 2026. (Payhip Help Center — Collaborations)

The primary creator is responsible for the Payhip fee and sales taxes on each sale, according to the same page. PayPal charges its usual transaction fee to the primary creator and collaborators. These details affect what each person takes home, so do not negotiate a percentage as if every party receives that share without any other deductions.

When a product is purchased, the primary creator is paid through PayPal in the usual way. Payhip says the collaborator’s payment is sent roughly ten minutes after the primary creator has been paid. The first collaborator payment may take up to 24 hours for approval; future payments are described as instant. That is the published process, not a guarantee about a bank withdrawal or every payment-provider review.

The feature lets the primary creator choose specific products, set a collaborator’s cut, and assign selected permissions. These can include permission to edit assigned products and administrative actions such as resending email receipts or resetting download credits. A “Show as co-creator” option can add a badge to the product sales page. Use only the access needed for the person’s role, and agree on whether public credit is wanted. (Payhip Help Center — Collaborations)

Decide what the percentage is paying for

Avoid borrowing a percentage from an unrelated partnership or assuming that a particular job title has a standard rate. A useful discussion starts with the actual contribution:

  • Who develops the expertise, lesson, template, or other material?
  • Who produces, edits, tests, and maintains the digital product?
  • Who pays for contractors, equipment, or other direct costs?
  • Who handles the product page, customer questions, and updates?
  • What marketing work is each person committing to, and what happens if those commitments change?
  • Is the share tied only to this product, or does either person expect it to cover future products or services?

For example, an instructor and a videographer might agree that the videographer receives a percentage of one course because both want that compensation to rise or fall with sales. That is a possible design choice, not a default rate or a claim that revenue sharing is better than paying a fixed production fee. A fixed fee, a product-level share, or a combination each allocates risk differently. Both people should compare the options against their contribution, costs, and capacity before deciding.

Write down the product’s name and scope. Payhip assigns collaborators to individual products; the Help Center does not describe the feature as a store-wide compensation agreement. If the arrangement covers a bundle, future releases, marketing services, or other parts of a business, confirm that the current interface supports the exact scope you need and put the wider terms in a separate written agreement.

Agree before setting permissions

A share percentage answers one question: what portion of a product’s sales is assigned to a collaborator in the Payhip setup? It does not answer who owns the underlying content, who can make editorial decisions, who approves discounts, or what happens if someone leaves. Record those decisions separately.

At minimum, both parties should be able to refer to the same written terms for:

  1. The product and contribution. Identify the digital product, each person’s tasks, deadlines, and what counts as a completed contribution.
  2. The share and cost responsibility. State the agreed percentages and confirm how Payhip’s fee, sales taxes, and each person’s PayPal transaction fee affect the arrangement.
  3. Permissions and public credit. Choose whether the collaborator can edit the assigned product or use the listed administrative permissions. Decide whether to display the co-creator badge.
  4. Changes and ongoing work. Set expectations for updates, customer support, replacing files, and promotion. Define how you will approve a change to the product or percentage.
  5. Refunds and disputes. Agree on how you will handle customer refunds and keep records. Payhip’s refund guidance says PayPal refunds are reflected in Payhip’s sales reports and analytics, but the public collaboration page does not explain how a refund is reconciled after a collaborator has already been paid. Ask Payhip support how the current system handles that case before relying on a specific accounting method. (Payhip Help Center — How Do I Refund a Transaction?)
  6. Exit and rights. Decide what happens to the product, each party’s access, and the contributed material if the collaboration ends. The dashboard’s collaborator setting is not a substitute for deciding who may keep, revise, or license the work.

Two digital-product collaborators reviewing their written terms before setting up revenue sharing

This is a planning checklist, not legal or tax advice. Copyright, tax, and contract rules vary by product and jurisdiction; seek professional advice for a material or ongoing arrangement.

Configure the product only after the terms are clear

To set it up, the collaborator needs a Payhip account and connected PayPal. The primary creator selects the product, share, and permissions; the collaborator receives an email and can see the assignment in the Collaborations area. Payhip also sends notices when a collaboration changes or ends. (Payhip Help Center — Collaborations)

Before launch, review the assigned product, percentages, and permissions together. Ask Payhip how discounts, partial refunds, taxes, or later payouts affect a share if that behavior matters; do not infer it from the word “automatic.”

Keep the agreement with the product’s sales reports. Payhip reports platform and processor fees, taxes, product sales, and affiliate information; these records help reconciliation but do not define responsibilities or rights. (Payhip Help Center — Sales Report)

When the built-in split fits — and when to pause

The feature may fit a digital product with up to three collaborators, connected PayPal accounts, and product-level terms. It can reduce manual collaborator payments after the primary creator receives a sale.

Pause if the arrangement involves physical goods, more than three collaborators, store-wide compensation, or terms the documented settings cannot express. Public documentation does not settle every bundle, refund, termination, or intellectual-property scenario. Confirm consequential feature behavior with Payhip and document the business terms separately.

Revenue sharing can connect compensation to product sales. Set the percentage only after agreeing on contributions, expenses, permissions, rights, and edge cases.

Continue exploring

Back to the library