Pulse
Add one small widget before submit. Pulse checks continuity instead of snapshots, corroborates the action instead of inheriting trust, and gives your server a result it can enforce. It is not a one-time code, push approval, credit-file score, or GPS check.
The missing check
Document checks, phone codes, device fingerprints, face checks, phone numbers, bureau files, and old sessions can all pass while the real applicant remains unproven. Pulse asks for live corroboration before the file moves forward.
A document, code, device, number, face image, login, or record match can pass while the person behind the application stays unproven — and a one-time proof can decay into a loose credential that keeps moving after the proof is over.
Pulse reads signs of ordinary phone use — movement, device state, signal changes, and daily rhythm — and looks for a pattern that agrees over time. A static profile, script, or document image is not enough.
Your server receives the pass, review, or stop result it needs. Raw motion readings, location trails, and day-by-day details stay on the phone, out of the lender’s website.
Synthetic fraud gets easier when files, codes, and sessions can be copied. Pulse raises the cost by asking for the real phone at the moment risk is accepted, refusing to let an old proof stand in for a current action, and doing it without exposing raw location history. Read the threat glossary or the engineering matrix.
Form check
Pulse belongs at the decision point — submit, approve, recover, transfer, or claim. Add it before that action, mint a short-lived session from your backend, and check the returned result on your server. Your team does not build the phone flow, waiting state, timeout handling, or result check.
<script src="https://kenshiki-pulse-worker-production.pulsekenshikilabscom.workers.dev/v1/pulse.js"></script>
<div id="pulse-trust-gate"></div>
<script type="module">
const session = await fetch("/api/pulse/sessions", { method: "POST" }).then((r) => r.json());
const pulse = KenshikiPulse.init({ publishableKey: "pk_live_customer_123", workflow: "credit_application", containerId: "pulse-trust-gate" });
const bond = await pulse.requireBond({ session: session.session, action: "submit_application" });
</script>Desktop applicants scan a short-lived QR code with the Pulse app; mobile applicants open Pulse directly. The page waits, then returns to the form with a pass or block. Your form stays intact.
Pulse checks whether the phone looks current, carried, and tied to normal use.
The submit includes a Pulse result id. Your server checks it before accepting the action.
Mobile SDK
The browser gate starts the action. The Pulse iOS app and KenshikiPulseSDK perform the phone-side check: bounded device evidence, signed receipts, App Attest where available, and a result the server can verify before the action is accepted.
Private-beta iOS package for the app surface that collects derived device-physics evidence and submits it to the Pulse verification endpoint.
Evidence is reduced on-device, hashed, and signed with an integrity receipt before it leaves the phone.
The lender page receives the pass, review, or stop result it needs. Raw sensor streams and location trails stay out of the web form.
Architecture
Pulse does the hard work on the phone before the browser action continues, and governance is part of the runtime path, not a document beside it.
Private beta
Start with a credit application submit, account opening, account recovery, benefits claim, job application, wire approval, or dealership finance application. Pulse brings the phone check to that moment and gives your team a clear pass, review, or stop result.