Reader
The verification device
Device posture and integration availability are confirmed per pilot. The Laurel application contract is intentionally narrow and outbound-only.
Integrations
A verification layer, not another platform.
Laurel answers one question inside an operation that already has a POS, a device fleet, and a management stack. The design goal is coexistence: add the age boundary without asking you to replace, re-platform, or re-train around anything else.
01 · The stack around Laurel
What stays yours, and how Laurel sits next to it.
| Your system | Its job | How Laurel relates |
|---|---|---|
| Point of sale | Transactions, catalog, payments | Laurel integration may sit beside a lane or inside a checkout moment only after the specific pilot path is reviewed and approved. It never becomes the POS. |
| Existing device management | Managing your device estate | Device-management compatibility is confirmed during qualification. Laurel is not an MDM and does not replace yours. |
| Ticketing & entry | Admission, capacity, access | The age check runs at the same threshold without joining your entry system or its data. |
| Compliance record-keeping | Your obligations of record | Aggregate outcome counts support operational reporting. Laurel is not a legal authority and does not certify compliance on your behalf. |
Specific product-to-product connectors are scoped during pilot qualification against your actual stack — we publish coexistence design, not a logo wall.
02 · Integration surfaces
Three places systems meet Laurel.
Portal
The operations surface
Locations, devices, fleet health, and aggregate reporting, with role-scoped team access — the place your operators actually work.
API
The typed contract
Every boundary is a strict, versioned schema. What the API accepts is the allowlist; what it never accepts is the privacy model.
03 · A boundary, on purpose
What Laurel deliberately is not.
Laurel Secure is not an MDM, not a POS, not an identity database, and not a legal authority. It does not build patron profiles for marketing, does not track individuals across locations, and does not replace the physical-ID fallback your staff already know.
That restraint is what makes the integration story simple: a system that only answers an age question has very few ways to conflict with the systems that do everything else.
Building where age needs an answer?
POS vendors, kiosk manufacturers, and platform teams: the partner page covers how the verification boundary composes with your product.