A customer verifying in person at a METAiD terminal beside a bank ATM
Solutions/In-Person Authorization

In-Person
Authorization

Presence verification for high-value actions.

Remote approval is convenient.
For high-value actions, it is no longer enough.

Remote factors prove an approval arrived — not that the account holder was there.

Phone Approval

Approves from whichever device holds the account.

OTP / PIN

Codes can be phished, intercepted, or shared.

Remote Biometric

A face or voice check over a camera can be replayed or synthesized.

Account Takeover

Attackers approve actions from the victim’s own account.

Credential Compromise

Stolen factors look exactly like legitimate ones.

AI-Assisted Impersonation

Synthetic faces and voices pass remote checks.

Approval accepted
No proof the person was there

Move high-value authorization
into the physical world.

Everyday actions stay remote. High-value actions require the person to be there.

A customer verified in person at a METAiD terminal before a high-value ATM transaction
Standard action
Digital approvalAction proceeds

Low-risk actions keep the convenience of remote approval.

High-value action
Authorized personPhysical presenceAction released

The person verifies at a METAiD terminal at a controlled location before the action is released.

The action proceeds because the authorized person is physically there.

Physical presence becomes part of the authorization policy.

Required by Policy

Presence is required only for the actions your policy marks high-value.

Person Present

Confirms the authorized person is physically at the point of approval.

Independent Evidence

A presence record, separate from the account credential, is attached to the action.

Depth, Not Images

No RGB camera. METAiD senses depth — no face photos or video.

METAiD C4U terminal

Works with your
authorization workflow.

Existing systems stay. METAiD adds physical presence when policy requires it.

  1. RequestA high-value action is initiated in your business system.
  2. FlagYour authorization policy marks it as in-person required.
  3. VerifyThe authorized person confirms physical presence at a METAiD terminal.
  4. ReleaseThe action is released, with a presence record attached.

Approve remotely when you can.Require presence when it matters.