LicenseChain

Pay checkout & payment providers

LicenseChain Pay (https://pay.licensechain.app) hosts seller checkout pages, issues licenses, and delivers signed redirects or merchant webhooks. The Core API (/v1/products) defines product metadata; Pay executes payment and fulfillment.

Checkout modes

  • Hosted Pay page — /checkout/{productId} with optional Mirror ?payload=... (strict mode).
  • Mirror strict mode — seller builds encrypted payload (TOKEN, CLIENT_EMAIL), redirects buyer to Pay, receives signed callback. See Mirror SDK.
  • WooCommerce — LicenseChain WC Checkout plugin automates payload + validate flow.

Payment providers on Pay

Stripe (primary)

Card payments and subscriptions. Card entry is embedded on the Pay checkout page. Recurring products require stripePriceIdRecurring on the Core API product. Renewals from seller backends use POST /api/checkout/mirror/subscription/charge.

Crypto (NOWPayments)

Optional crypto checkout when cryptoPaymentsEnabled is true on the product (Business/Enterprise tiers may apply). Validation still flows through Mirror /validate after confirmed payment.

Whop (external / alternative storefront)

Whop is a creator/SaaS checkout platform. It is not embedded inside Pay checkout today — Whop acts as an alternative storefront alongside LicenseChain, not a drop-in processor like Stripe (see Pay docs/payment-provider-expansion-analysis.md).

Typical pattern: sell access on Whop, then issue or verify LicenseChain licenses via Core API (POST /v1/licenses/verify) or Pay merchant webhooks when you bridge orders manually or via automation. For native hosted checkout on your domain, use Mirror + Stripe on Pay instead.

Post-checkout verification

  1. Verify Mirror redirect signature (if using strict mode).
  2. Call POST /api/checkout/mirror/validate with license + email.
  3. Optionally consume Pay merchant webhooks (x-lc-pay-signature) for async fulfillment — see signing models.

API reference