Two creators review a printed workbook prototype and take notes at a studio table.
Growth systems · Payhip Operator

How Payhip Collaborations Work: Revenue Splits, Permissions, and PayPal

A practical guide for creators deciding whether a product partnership, an affiliate program, or a broader operating arrangement fits their work.

When two people make or sell a digital product together, the money arrangement is only one part of the setup. Each person also needs to know what they can change, what responsibilities remain with the seller, and how payments actually move.

Payhip’s Collaborations feature addresses a specific version of that problem: a seller can attach collaborators to digital products, assign a percentage of sales, and choose from certain product-editing or administrative permissions. It is useful to understand the feature on those terms before treating it as a general team workspace or confusing it with affiliate tracking. (Payhip Help Center — Collaborations)

What Payhip documents about collaborations

Payhip describes Collaborations as a way for creators who have teamed up to make a product to manage it together and automatically pay collaborators a portion of each sale. Its current help article specifies several conditions: (Payhip Help Center — Changelog)

  • Collaborations currently support digital products.
  • A product can have up to three collaborators.
  • Each collaborator’s cut can be set from 10% to 90%. The primary creator must retain at least 10%.
  • The primary creator is responsible for the Payhip fee and sales taxes on each sale; PayPal charges each party its usual transaction fee.
  • The seller selects individual products, the percentage cut, and whether to allow product editing or selected administrative actions such as resending receipts or resetting download credits.
  • Both the primary creator and collaborators need Payhip accounts and connected PayPal accounts to receive payments.

These are product-specific settings described by Payhip. They do not, on their own, establish how every kind of store access, staff account, or client-agency arrangement works. If your need is broader than collaborating on particular products, inspect the current account interface and documentation before committing to an operating model.

First decide what kind of relationship you have

People often use “collaborator,” “partner,” and “affiliate” interchangeably. Those labels can describe different work and different payment mechanics. Identify the actual relationship before selecting a setting.

Relationship What the person contributes Payhip arrangement to examine
Product co-creator Helps create a digital product and shares its commercial outcome Collaborations, if the product and payment requirements fit
Product operator or producer Builds, edits, or maintains an assigned digital product Collaborations permissions may cover some product work; confirm the exact available actions in the live settings
Affiliate promoter Refers potential buyers through tracked promotional links Payhip’s affiliate program; it tracks referred sales, but the seller handles affiliate payments
Store operator or staff member Works across a catalog, customer service, marketing, or business operations Verify the account-level access the current Payhip setup actually provides; product collaboration alone does not answer this broader requirement

A product co-creator does not necessarily do the same work as someone who refers customers or administers a store. Define the contribution before setting a revenue share, and keep tracked referral commissions separate from co-creator payouts.

A producer adjusts a camera while an instructor arranges lesson materials for a shared course recording.

How the revenue split works

The primary creator configures a percentage for each collaborator on a supported digital product, and the feature allocates each sale according to that setting. Before entering a share, agree how refunds, discounts, taxes, platform fees, payment-processing charges, production expenses, and later updates affect the arrangement. Payhip’s feature description leaves those commercial terms to the parties.

That means a percentage is not the same thing as a fully settled profit share. Before setting it, write down what the percentage applies to and how the parties will handle refunds, discounts, taxes, platform fees, payment-processing charges, production expenses, and later product updates. Payhip’s feature description does not resolve those commercial terms for you.

The payment timing also deserves a place in the agreement. Payhip says collaboration payments are processed through PayPal. The seller receives payment through PayPal in the usual way; the collaborator’s payment is sent roughly ten minutes after the seller has been paid. Payhip warns that approval of the collaborator’s first payment may take up to 24 hours; later payments are described as instant. Treat this as the platform’s stated process, not a guarantee that every bank or PayPal account will show funds at an identical moment.

Before launch, test the setup with the actual people involved. Confirm that each Payhip account is connected to the intended PayPal account, check the displayed cut for every product, and verify what each person can edit. Keep the agreed percentages and responsibilities in writing so that the settings and the business understanding match.

Permissions: grant only what the job requires

The help article lists an option to allow a collaborator to edit assigned products. It also mentions selected administrative permissions, including resending email receipts and resetting download credits. Those examples show that editing and administration are distinct choices; they do not mean every collaborator receives the same access.

Use the live permission screen as the source of truth for the particular account and product. Review the available controls together before inviting someone, then record which actions the person needs and why. If their work requires catalog-wide administration, customer management, billing, or another capability not clearly shown in the collaboration settings, do not assume the product feature covers it. Confirm the account’s actual options with Payhip or choose a workflow that does.

An educator demonstrates a tablet to three attendees gathered around printed course material.

Collaborator or affiliate?

The practical difference is the nature of the contribution and the payment flow. A collaborator is attached to a product and receives a share through the collaboration feature’s PayPal process. An affiliate promotes products with a unique tracking link; Payhip’s affiliate documentation says the seller must pay affiliates directly and provides a monthly sales report for that purpose. (Payhip Help Center — Affiliates)

If someone is creating or maintaining the product with you, discuss whether a collaboration fits. If they are promoting it to an audience, examine the affiliate program and decide how you will calculate and pay commissions. One person could perform more than one role, but each role should have a clearly defined scope and accounting method. Avoid paying twice for the same contribution simply because both features are available.

A practical setup checklist

Before enabling a collaboration, work through these questions with the other creator:

  1. What is being made? Name the exact digital product and describe its contents, audience, and intended use.
  2. Who does what? Specify creation, editing, promotion, customer questions, maintenance, and future updates.
  3. What does the share mean? Record the percentage, the product it applies to, how discounts and refunds are handled, and which costs each party bears.
  4. Are payment accounts ready? Confirm Payhip accounts and connected PayPal accounts for everyone who needs to receive money.
  5. Which permissions are necessary? Inspect the current settings and enable only the product editing or administrative actions the agreed work requires.
  6. How will changes be handled? Decide how either party can propose updates, pause sales, resolve a disagreement, or end the arrangement. Check Payhip’s current removal and notification behavior before relying on a particular process.
  7. Has the flow been checked? Review the product page, percentage allocation, checkout, delivery, and the first payout expectations before promoting the offer.

This checklist is a working agreement aid, not legal or tax advice. A written contract may be appropriate when the product, intellectual property, expected work, or financial exposure warrants it. Ask a qualified professional about questions that depend on your jurisdiction.

When the feature fits—and when to investigate further

Payhip Collaborations is a plausible fit when the work centers on a supported digital product, everyone understands the assigned percentage, the PayPal requirements are acceptable, and the available product permissions match the contribution.

Investigate further when you need a person to administer a whole store, manage multiple products, control account settings, or perform duties beyond the documented product permissions. The public help article is specific about collaborating on products; it should not be stretched into a complete description of every account-access option. Check the current dashboard and ask Payhip to confirm any capability your operating arrangement depends on.

Before using a “collaborator” setting, compare the person’s actual work with the payment terms and permissions available in the account. Resolve any gap before the product goes on sale, then revisit the setup when responsibilities change.

Continue exploring

Back to the library