Developer Docs

Introduction for Developers

PeakCommerce is designed to give developers flexibility and control while abstracting away the heavy lifting of modern commerce—subscriptions, checkout, entitlements, payments, and identity handoffs—so you can focus on building great product experiences.

Developers typically interact with PeakCommerce differently than business or operations users. While non-technical users configure products, pricing, and workflows through the admin UI, developers integrate PeakCommerce directly into their applications and customer journeys.

At a high level, developers use PeakCommerce to:

• Create custom commerce experiences using Templates built with standard HTML, CSS, and JavaScript.

• Pass contextual data into PeakCommerce checkout flows to enable seamless handoffs between your application and PeakCommerce.

• Integrate authentication and identity flows, including scenarios like free-trial conversion, account activation, and entitlement enforcement.

• Embed PeakCommerce components directly into your product, reducing redirects and preserving a native user experience.

• Orchestrate commerce events across systems, connecting PeakCommerce with platforms like Salesforce, Zuora, NetSuite, and custom backends.

PeakCommerce is intentionally platform-agnostic, allowing it to fit cleanly into both greenfield applications and complex enterprise ecosystems.

How Developers Create Experiences with PeakCommerce

PeakCommerce commerce experiences are composed using three core concepts:

• Journeys – Define the logical flow of a commerce experience (e.g., signup → checkout → confirmation).

• Templates – Control the presentation layer using standard web technologies.

• Pages – Individual steps or views within a journey.

This approach gives developers the freedom to fully control UX and behavior while relying on PeakCommerce to manage commerce logic behind the scenes.

Templates: Full Control with Familiar Tools

Templates are authored using standard HTML, CSS, and JavaScript—no proprietary templating language required. This allows you to:

• Match your brand and product UI exactly

• Implement custom client-side logic

• Reuse existing frontend patterns and components

• Iterate quickly without platform lock-in

PeakCommerce injects the necessary commerce context (products, pricing, customer state, entitlements, etc.) into the template at runtime.

---

Passing Context into PeakCommerce

Developers can pass data into PeakCommerce at runtime to personalize and contextualize the commerce experience. Common use cases include:

• Identifying the current user or account

• Passing plan or offer selections from your app

• Preserving return URLs and application state

• Coordinating checkout completion events

This enables PeakCommerce to act as a seamless extension of your application rather than a disconnected checkout system.

---

Authentication and Identity Integration

PeakCommerce integrates cleanly with modern authentication systems and identity providers.

Typical patterns include:

• Handing off authenticated users into PeakCommerce

• Converting free or trial users into paid customers

• Delegating password management and identity policies to your IdP

• Syncing entitlements back to your application in real time

PeakCommerce works alongside providers like Auth0 and custom IdPs without forcing you to change your existing authentication architecture.

---

Embedded and Headless Use Cases

In addition to hosted experiences, PeakCommerce supports embedded and headless patterns where specific components or flows are instantiated directly inside your application.

This allows you to:

• Reduce full-page redirects

• Maintain application routing and state

• Deliver commerce experiences that feel truly native

• Gradually adopt PeakCommerce without a full frontend migration

---

What You’ll Find in These Docs

The PeakCommerce Developer Docs are organized to help you:

• Understand core platform concepts

• Build and customize Templates

• Integrate APIs and webhooks

• Embed commerce experiences

• Secure and scale your integrations

Whether you’re building a simple checkout flow or deeply integrating PeakCommerce into a multi-system enterprise architecture, these docs are designed to meet you where you are.