Independent business · Payments, Gatekeeper, and updates

How to Sell a Mac App Outside the App Store

Selling a Mac app directly is more than adding a checkout button beside a ZIP. Customers need a trusted download, a clear purchase promise, a working license, and a reliable way to receive updates. You also need a plan for taxes, refunds, and support. Treat those as separate responsibilities, then choose tools for each one.

By Francisco Cantu ·

1. Define what the customer is buying

Decide whether you sell a perpetual license, a subscription, or access to a specific major version. A one-time price does not automatically promise every future major upgrade. State update eligibility, supported macOS versions, device limits, transfer rules, and trial behavior before checkout.

  • Trial: when does it begin, what is limited, and what happens when it ends?
  • License: is it per person, per device, or per organization?
  • Updates: are maintenance releases included, and are future major versions paid upgrades?
  • Offline use: does activation need the network, and how does the app behave during an outage?
  • Refunds and support: where can customers contact you, and which policy and statutory rights apply?

HarborPilot’s current offer is an example, not a required model for your app: a $49 beta price instead of the regular $99, a one-time payment with no subscription required, and a 14-day trial. Its beta discount ends when 1.0 is released. Your product’s terms should reflect your own promise, not copy another app’s pricing.

2. Choose a payment role, not just a checkout design

A payment processor moves money; a merchant of record generally acts as the seller of record for the covered transaction and takes on specified transaction responsibilities. The exact scope comes from the provider’s contract, supported countries, and product eligibility.

Polar
Describes its offering as merchant of record and provides software-selling features including license-key benefits. Verify current eligibility, transaction-tax handling, fees, payouts, and refund terms. HarborPilot’s checkout uses Polar; that is not an endorsement of a universal fit.
Lemon Squeezy
Also describes a merchant-of-record model and offers licensing and webhook features. Check country coverage, approval requirements, and the agreement governing your product.
Stripe
Ordinary Stripe payment processing does not automatically make Stripe your merchant of record or transfer all tax and seller obligations. Evaluate the specific product and contract you use; tax tools are not the same as outsourcing every responsibility.

Calculate net revenue after the provider’s current fees, refunds, chargebacks, currency conversion, and any other applicable charges. Don’t choose a service on an outdated percentage quoted in a blog post.

Direct Mac distribution through your own website is a different channel from an App Store transaction. It is not useful to frame it as a guaranteed “zero-fee” business: developer program membership and your chosen services still cost money. Check the agreements applicable to your channel rather than importing rules for iOS alternative distribution into a Mac app launch.

3. Make purchase fulfillment and licensing reliable

Decide whether your provider’s built-in license system is enough or you need your own entitlement service. Keep the model as simple as your requirements allow. Build in lost-key recovery, activation transfer, and an explanation of what happens if a customer cannot reach the license service.

Do not grant permanent paid access just because the browser lands on a success URL. Verify the purchase with the provider or use a documented provider-managed license flow. A desktop app cannot keep a private administrative API key secret: never embed one in the bundle.

If you operate a fulfillment service, its event handling should:

  • Verify webhook authenticity using the provider’s current signature scheme.
  • Use event and order identifiers to process repeated deliveries idempotently.
  • Handle delayed and out-of-order events without granting conflicting access.
  • Reconcile refunds, disputes, cancellations, and license status according to your published terms.
  • Provide recovery when an email or event delivery fails.

Client-side licensing discourages casual misuse; it is not unbreakable DRM. Balance enforcement against legitimate customers’ ability to use the software they bought.

4. Deliver a signed, notarized download

For the standard direct-distribution path, use Developer ID signing, Hardened Runtime, and Apple notarization. Staple the accepted ticket to a supported artifact and validate the final release. Notarization is not App Store review, and it does not guarantee that your app is bug-free.

Host the completed archive over HTTPS and make the download version and system requirements clear. Test the public browser download, not just a build on your development Mac. A ZIP is not itself staplable; if you distribute a ZIP, staple the app before making the final archive.

Do not make bypassing Gatekeeper part of the onboarding experience. If a customer sees a damaged-app warning, use the damaged-app troubleshooting guide to investigate the exact release.

Keep download trust separate from payment entitlement. A signed app can offer a trial to anyone while requiring a valid license for paid features; signing is not proof of purchase.

5. Plan updates before your first sale

Sparkle lets the installed app discover updates from an appcast and verify signed update archives. Your update-signing private key must stay secure; the app embeds the corresponding public key. This is a different trust mechanism from Developer ID signing.

Publish a versioned archive first, then the feed referencing it. Keep the feed and archives reachable, with a deliberate cache policy. Test an upgrade from an already-installed older release and confirm licenses, user data, and preferences survive.

If a license includes only a particular major version, design and test update eligibility before you publish a paid upgrade. Do not push an update that unexpectedly removes access without explaining the entitlement rules. Licensing and update discovery need to agree, but they are not the same system.

Use the Sparkle setup guide and the R2 hosting guide for implementation details. HarborPilot prepares and can help publish release files; the files remain on your chosen host.

6. Cover taxes, refunds, privacy, and support

A merchant of record can reduce covered transaction-tax work, but it does not automatically handle your business registration, income tax, bookkeeping, or every local obligation. Confirm what the contract covers and get qualified legal or tax advice for your situation.

Publish terms, a truthful privacy policy, and a support address. Disclose the services receiving customer or app data. Collect the minimum diagnostic information needed, and never ask a customer to email payment credentials or private license-service tokens.

Your refund policy must fit applicable consumer rights and the provider’s agreement. Providers can have their own refund or dispute handling powers. Explain what a refund does to the license without inventing a blanket “no refunds” rule that your contract cannot support.

Keep purchase records and release records separate, with appropriate access controls and retention. Plan what happens when you stop supporting a macOS version or discontinue the app; customers should not discover that only when an activation service disappears.

7. Rehearse the entire purchase-to-update journey

  1. Use the provider’s documented test mode to complete checkout.
  2. Verify purchase confirmation and license fulfillment, including a delayed or repeated event.
  3. Download the app from the public URL on a clean Mac.
  4. Test trial use, activation, an invalid key, and the documented offline behavior.
  5. Install an older build and perform a real Sparkle update.
  6. Exercise refunds, activation recovery, and support using safe test data.
  7. Before accepting public sales, confirm live checkout settings and payout readiness with the provider.

A checkout screenshot alone is not a successful launch rehearsal. The result should be a customer who can pay, receive access, launch a trusted app, and update it under the terms you promised.

Simplify your next release with HarborPilot.

Keep your storefront and licensing choices independent from release preparation. HarborPilot can handle the repeated build, signing, Apple notarization, stapling, and Sparkle packaging work on your Mac, while you run the customer relationship and host your own downloads.

Sources and further reading

Service limits and Apple requirements can change. Check the linked documentation before publishing. HarborPilot is not affiliated with Apple, Cloudflare, or the Sparkle project.