02Industries · Payments
When your risk engine escalates a transaction, the challenge should be stronger than a typed code. SenseCrypt turns approval into a live-face ceremony bound to the exact merchant and amount.
01The ceremony
Your policy decides when to ask
Merchant, amount, action, expiry
Live face plus intent, on their own phone
Approval or denial, plus an audit reference
02The outcomes
Each prompt shows the verified app and the exact action being approved. Only the enrolled person's live face can grant it.
Your server starts the approval over CIBA. The customer confirms on their own device while checkout waits for the signed result.
Interception is an attack on things in transit, and nothing secret is in transit. The code was never sent.
Keep low-risk payments one-step. Escalation stays your call, and SenseCrypt supplies the strong step.
Buyers approve in the authenticator app on the phone they already carry, or inside your own app with the embedded SDK. The device at checkout needs no enrollment.
Your internal consoles ride the same IdP, with roles, scopes, and every action on the audit trail.
Each merchant gets an isolated tenant with its own users and branding: SSO you offer, not build.
03The failure modes
SMS and email one-time codes are phished, SIM-swapped, and relayed at scale. They are still the default step-up.
Every extra code typed at checkout costs completed payments; every reset costs a returning customer.
Users tap Approve to make prompts go away. Attackers count on exactly that.
Challenge flows bolted onto checkout cut completion. The customer blames your brand, not the issuer.
Stored cards make every account worth taking over, and stuffed passwords are the cheapest way in.
Web, app, and in-store each authenticate differently. Users feel the inconsistency, and fraud exploits it.
04The compliance map
Possession of the enrolled device plus a live face gives you two independent factors, a strong foundation for SCA step-up, without an OTP in sight.
Each approval names the amount and the payee, and the signed result is specific to both. That supports the dynamic-linking requirement in Article 5 of the EBA's technical standards for strong customer authentication.
Read the sourceA code the customer types can be relayed, which is why NIST SP 800-63B excludes manually entered one-time codes from phishing resistance. SenseCrypt replaces the typed code with a live-face approval bound to the enrolled device.
Read the sourceFace matching in SenseCrypt is independently evaluated in the Face Recognition Technology Evaluation under Seventh Sense's own name, with results anyone can inspect. See the NIST report card (seventhsense-000)
Passwordless, phishing-resistant confirmation, wired in through CIBA.