Backend middleware
Laravel
Service-provider registration, environment configuration, and fail-closed route middleware.
sdk/frameworks/laravelOfficial integration references
Framework adapters that preserve server-side trust boundaries.
Use maintained reference packages to mount browser experiences, validate response tokens privately, and authenticate webhook events before business logic runs.
Backend bundle
Symfony
Request verifier service for controllers, event subscribers, and form workflows.
sdk/frameworks/symfonyPlugin reference
WordPress
Widget rendering and private verification helpers for forms and custom actions.
sdk/frameworks/wordpressBrowser component
React
Lifecycle-safe widget mounting with verification, expiry, and error callbacks.
sdk/frameworks/reactBrowser component
Vue
Vue 3 component with emitted verification events and automatic cleanup.
sdk/frameworks/vueRoute helpers
Next.js
Server verification and exact-raw-body webhook verification for route handlers.
sdk/frameworks/nextjsGateway references
Edge & Ozibus
Nginx, Apache, edge-runtime, pre-clearance, and signed Ozibus risk-signal references.
sdk/frameworks/edgePhase 54
Stop abusive traffic before application business logic runs.
Use the edge decision endpoint from a trusted reverse proxy, gateway, serverless worker, or server adapter. Ozibus handles communications delivery while VettiGuard provides customer-context risk and enforcement.
Reverse proxies
Nginx and Apache references demonstrate internal decision adapters, status mapping, and safe fail behaviour.
sdk/frameworks/edge/Pre-clearance
Issue short-lived, signed clearance after successful verification and bind it to site, host, action, path, subject, or device.
POST /v1/edge/preclearance/issueOzibus signals
Signed preflight and delivery-event APIs combine Ozibus provider intelligence with VettiGuard policy and cross-module correlation.
POST /v1/integrations/ozibus/preflightBoundary of responsibility
Ozibus generates and delivers OTP, SMS, and email and reports provider outcomes. VettiGuard does not replace the transport; it evaluates whether a customer request should be allowed, challenged, delayed, or blocked.
No OTP values or message bodies are requiredSafe implementation pattern
Collect in the client. Decide on the server.
1 Mount widget2 Receive response token3 Verify privately4 Validate action and context
Backend adapters
Laravel, Symfony, WordPress, Next.js, PHP, and Node integrations keep secrets server-side and fail closed on invalid, expired, or unavailable verification.
Frontend adapters
React and Vue wrappers manage SDK loading and component lifecycle. They do not treat a browser callback as authorisation.
Webhook receivers
PHP and Node helpers authenticate the exact raw request body, enforce timestamp tolerance, and use constant-time signature comparison.