Ocliby
Open menu

Category explainer

What are purchase sessions in ecommerce?

Purchase sessions are portable, stateful transaction windows. They bind a customer moment to products, rules, timing, and connector execution without forcing every customer back through a storefront-first path.

The stateful flow

Surface to session to order

STEP_01

Create a scoped purchase session

Define customer, product, offer, timing, and connector context for a specific transaction moment.

STEP_02

Place the link anywhere intent exists

Use the secure link in email, SMS, ads, QR codes, chat, support, or future AI surfaces.

STEP_03

Execute through the commerce connector

When clicked, the session opens a focused buying window and finalizes through the native platform path where supported.

Transaction surfaces

The channel does not need to own checkout.

A purchase session can be launched wherever a secure link can live.

Email
SMS
Paid social
QR codes
Support
AI agents

Structural comparison

Purchase sessions are not static payment links.

Capability layer
Standard payment links
Purchase sessions
Orchestration
Static links route shoppers to a generic checkout or payment page.
Scoped sessions carry product context, timing, offer rules, and connector behavior.
Surfaces
Most tools assume email, ads, or SMS should send traffic back to the store.
Any high-intent surface can launch a secure purchase session.
State and expiration
Expiration and offer context are often separate from the destination page.
Session validity and timing are governed server-side.
Commerce execution
The link usually owns the checkout destination.
Commerce connectors execute native order and payment behavior where supported.

Purchase Session Infrastructure

If intent is already distributed, buying should be too.

Request pilot access to see how purchase sessions can work on your store, channels, and connector roadmap.