Secure short links
Links do not need to expose full purchase state directly in the browser.
Security and architecture
Secure purchase sessions.
Built like commerce infrastructure, not a link shortener. Ocliby keeps session state, timing, offer logic, and validation server-side.
Routing architecturelive_env
01
Surface
02
Claim
03
Session engine
04
Commerce connector
Browser-facing links initiate a server-side claim path. The session engine remains the source of truth for validity, timing, offer rules, and journey state. Connectors execute platform-native order and payment behavior where supported.
Server-side session claims
Purchase sessions are validated through backend-controlled claim and exchange logic.
Time-limited windows
Sessions can expire automatically based on strict server-enforced timing.
Connector execution
Your commerce platform still handles native order and payment behavior where supported.
Plain-language trust model
What this means for merchants
Links do not need to expose the full purchase payload.
Sessions can expire automatically and be validated server-side.
Native platform fallback remains available where instant repeat purchase is not 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.