Patent Pending · Provisional Applications Filed 2026

Transaction-bound authorization for high-risk payments

A complementary authorization and fraud-control layer for banks, card issuers, and payment providers.

View Live Demo Discuss a Banking Pilot
The Gap
A valid login doesn't always mean a valid payment
Attackers may exploit a stolen or unlocked phone, compromised credentials or sessions, social engineering, SIM swap, or impersonation at a branch. A valid session or plausible identity claim alone may not prove the customer knowingly approved the exact transaction.
What Makes SafeAuth Distinctive
Six properties the portfolio is built around
1

Transaction-Specific Authorization

Applies to a specific payment action and its details — not just a successful login.

2

Signed Authorization Evidence

Evidence token can bind authorization context to a canonical transaction digest for later verification.

3

SafeHold Before Release

Risk-triggered payments can be held until required release conditions are satisfied.

4

Same-Transaction Binding

If protected details change, evidence and policy can be revalidated for the changed transaction.

5

Controlled Hold Lifecycle

Review, reconfirmation, expiry, cooling-off, and authorized release can be governed by explicit policy.

6

Counterparty-Bound Policy

Recipient trust state can inform authorization/release policy, including for new or insufficiently verified payees.

How SafeAuth Fits
A concept integration, not a replacement
SafeAuth sits alongside a bank's existing authentication, risk, and execution systems. The bank always retains execution and release enforcement.

Customer + Device

May be compromised

→

Bank App / Channel

Payment request

→

Issuer Risk Engine

Risk signals

→

SafeAuth

Evidence + SafeHold

→

Issuer Decision

Payment network

Policy Outcomes
Authorized Hold Reconfirm Deny Escalate

Potential use cases

High-risk transfers · new payees · account takeover · step-up authorization · transaction-consent evidence

Complements existing controls

Bank fraud engines, authentication, case management, branch procedures, and payment controls — not replace them.

Patent-Pending Portfolio
SafeAuth Core and related concepts
Core capabilities have been prototyped and demonstrated internally with signed, independently verifiable evidence. SafeAuth Core includes transaction-specific authorization evidence — including liveness and facial verification — and SafeHold architecture. Related concepts address evidence bound to a canonical transaction digest, controlled hold/release lifecycle, and counterparty-bound policy. Patent scope depends on the filed application and claims; this summary is not a legal claim chart.
Example Scenarios
How the pipeline responds to real risk signals
Three illustrative walkthroughs of the same authorization pipeline applied to different fraud patterns.
A High-Risk Transfer to a New Payee
1 · Request

Customer requests $2,400 to a new payee

2 · Risk Flag

Bank flags new payee + unusual amount

3 · SafeHold

HOLD; fresh liveness + transaction confirmation

4 · Confirm

Customer reviews payee and amount, then confirms

5 · Bind Evidence

Liveness and facial verification captured; authorization evidence tied to this transaction

6 · Decision

Release only if policy passes; otherwise HOLD/DENY

B Suspected SIM-Swap / SMS Channel Compromise
1 · Signal

Carrier/bank signal indicates recent SIM-swap or SMS risk

2 · Risk Policy

Issuer raises risk; SMS OTP alone may be insufficient

3 · SafeHold

HOLD/RECONFIRM under issuer policy

4 · Stronger Check

Approved non-SMS verification and fresh transaction-bound challenge, if available

5 · Bind Evidence

Liveness and facial verification against enrolled reference; bind approval to payee + amount

6 · Decision

Release only if controls pass; otherwise HOLD, step up, or DENY

C Suspected Branch Impersonation / In-Person Fraud
1 · Branch Request

Person at branch requests a high-risk transfer or account change

2 · Risk Indicators

Mismatch, unusual request, new payee, or coercion concern — if detected

3 · SafeHold

HOLD; branch presence or ID presentation alone is not sufficient

4 · Step-Up Review

Independent verification and dual-control/supervisor review per bank policy

5 · Bind Evidence

Capture liveness and facial verification evidence, transaction-specific, after approved checks

6 · Decision

Authorized staff release only if policy passes; otherwise HOLD/ESCALATE/DENY

Let's discuss a banking pilot

Concept overview only. Signals depend on institution procedures and available data. SafeAuth complements — not replaces — bank controls.

✉ support@saonlinedemo.com ☎ 512-293-2243 ↗ demo.saonlinedemo.com