DEV Community

PermitCore
PermitCore

Posted on

Sell software through your own Paddle or Lemon Squeezy account—with licensing connected

You want to sell your app, not spend every release maintaining a second product made of checkout pages, tax settings, invoice links and license-delivery scripts.

A merchant of record can take on the payment, tax and receipt side of eligible software sales under your agreement with it. But a successful checkout still needs to become something your customer can actually use: the right license, for the right product, in an account they can return to.

PermitCore Store now connects those steps with Stripe, Paddle and Lemon Squeezy. Choose one payment provider for your branded Store, connect your own account, and link verified payments to automatic software license delivery.

Choose your payment relationship. Keep your own brand.

Your payment account should fit how you sell.

If you want to use Paddle or Lemon Squeezy as merchant of record, you can connect your own provider account to PermitCore Store. The selected provider handles checkout, tax and its receipts under your merchant-of-record agreement. PermitCore handles the licensing and fulfillment side.

Stripe remains supported for your Store. If you sell directly through your own Stripe account, you remain responsible for your applicable tax obligations; the Store setup guide explains the available tax configuration.

The important distinction is ownership of the relationship: this is your provider account for your customers' purchases, not the account used to pay for your own PermitCore subscription.

PermitCore takes 0% sales commission. Your selected provider's fees, payout terms and account requirements still apply.

A storefront that looks like your software belongs there

The Store is more than a payment link.

Use your logo, colors and product imagery. Organize products into collections, add a featured spotlight, and build product pages with descriptions, feature lists and price choices. Offer one-time purchases or recurring products according to your sales model.

The same product and license settings connect the storefront to what your app enforces: features, device limits and access rules.

That gives the sale a continuous path:

  1. Create the product and the license settings your customer should receive.
  2. Implement licensing in your app through the REST API or an official SDK.
  3. Sell through your branded Store and selected payment account.
  4. Deliver access after payment is verified, with purchase history available in the customer's account.

Connect payment to access—not just a success page

A browser landing on a thank-you page is useful feedback. It is not the authority for issuing a paid license.

PermitCore verifies provider payment notifications and payment evidence before fulfillment. A completed purchase creates the appropriate order and license; the customer receives an email linking to their account rather than a license key exposed in the message.

For recurring products, paid renewals extend the existing key. Failed payments follow the Store's configured payment-grace policy. Cancellation and refunds follow their respective access rules, while customers retain their purchase history and provider documents.

That connection matters after the first sale as much as during checkout. You should not need a separate manual process to reconcile a renewed subscription with a customer's software access.

Paddle and Lemon Squeezy: same goal, different setup

With Paddle, the Store can create or update the connected provider catalog from your Store products and prices. Review the resulting mappings and provider tax categories as part of setup.

With Lemon Squeezy, create products and variants in its dashboard, then connect the matching variants in PermitCore. A multi-product cart uses an aggregate provider line while PermitCore preserves the individual purchase shares. Different recurring intervals use separate checkouts.

Both routes connect your provider account to the same branded storefront and licensing workflow. The Store setup guide walks through account configuration, product mappings, payment notifications and going live.

Less glue between selling and shipping

For an indie developer, reducing tax and invoicing administration is only part of the benefit. The other part is keeping the sale connected to the software you ship.

Your Store presents the product. Your selected provider handles the payment relationship. PermitCore delivers and manages the license.

Explore PermitCore Store, or follow the setup guide to connect your account.

Which part of selling software takes more of your time today: tax and invoices, storefront setup, or keeping paid access synchronized?

Top comments (0)