Payments

Protect every payment session, not just the login

Add continuous identity assurance to mobile wallets and payment apps. YEO’s CFR SDK helps confirm that the authorised customer remains present during higher-risk actions, without replacing your existing authentication or fraud controls.
Compatible SOLUTIONS:

YEO CFR SDK

The problem

Authentication establishes trust. The session can outlive it.

SCA, MFA, device binding and biometric login make it harder to get in. They don't prove the same person stays in control.

scenario

Handed over

A customer authenticates, then passes their unlocked phone to someone else, who approves a payment.

scenario

Left unlocked

An active session is left open, and a beneficiary is changed while the customer is away.

scenario

Accessed remotely

A fraudster takes control of the session and triggers account recovery.

Where does identity certainty disappear in your payment journey?

  • New-device enrolment

    Link the verified customer and their biometric identity to a newly registered device.

  • Account recovery

    Add assurance when passwords, devices or credentials are reset.

  • Wallet provisioning

    Confirm the authorised customer is present when a card or account is added.

  • High-value payment approval

    A live identity signal alongside transaction risk controls.

  • Beneficiary and profile changes

    Extra assurance before changes that could redirect funds.

  • Remote support journeys

    Tell the verified customer apart from someone else in an active session.

How YEO helps payment platforms protect customers & markets

The YEO CFR SDK works alongside your KYC, SCA, MFA, device intelligence and transaction monitoring. It adds the one signal they can't provide: whether the authorised person is still present.

The YEO CFR SDK works alongside your KYC, SCA, MFA, device intelligence and transaction monitoring. It adds the one signal they can't provide: whether the authorised person is still present.

Continuous verification without a central biometric database

Biometric processing happens on the user's device. Facial images and templates are never sent to YEO's servers, reducing the privacy, security and infrastructure risk of centralised storage.

On-device biometric processing

No central YEO biometric database

No repeated selfie or identity-document journey

Run continuously or only at selected risk events

Continuous verification without a central biometric database

Biometric processing happens on the user's device. Facial images and templates are never sent to YEO's servers, reducing the privacy, security and infrastructure risk of centralised storage.

On-device biometric processing

No central YEO biometric database

No repeated selfie or identity-document journey

Run continuously or only at selected risk events

Continuous verification without a central biometric database

Biometric processing happens on the user's device. Facial images and templates are never sent to YEO's servers, reducing the privacy, security and infrastructure risk of centralised storage.

On-device biometric processing

No central YEO biometric database

No repeated selfie or identity-document journey

Run continuously or only at selected risk events

Passive for your customers. Configurable for your team.

YEO runs in the background during normal use, so genuine customers keep a fast and familiar journey. The SDK integrates at the application layer, so no rebuild of your stack.

Your team controls

Where verification is active

The response to a failed or uncertain match

Which events need more assurance

How it looks in your product

Who benefits

One additional signal. Multiple teams benefit.

Fraud & risk

Add evidence of authorised presence to investigations, payment decisions and higher-risk account actions.

Who benefits

One additional signal. Multiple teams benefit.

Fraud & risk

Add evidence of authorised presence to investigations, payment decisions and higher-risk account actions.

Identity & security

Extend identity assurance beyond onboarding and login without displacing the existing stack.

Product

Apply additional assurance proportionately, rather than adding the same authentication friction to every journey.

Compliance

Create a clearer record of the identity controls applied during sensitive actions.

Engineering

Integrate an application-level SDK while retaining control over policy, thresholds and customer response.

Who benefits

One additional signal. Multiple teams benefit.

Fraud & risk

Add evidence of authorised presence to investigations, payment decisions and higher-risk account actions.

Presence is one part of payment risk

YEO confirms the authorised customer is present. It doesn't on its own determine whether they're being manipulated or whether a transaction is legitimate — so it's built to complement your other controls.

Frequently asked questions

Which platforms are supported?

YEO supports mobile application integrations. Contact the team to confirm compatibility with your operating systems, frameworks and deployment model.

Can the experience match our brand?

Yes. The SDK operates within your application and can be configured to match your customer experience and design system.

Does it replace our fraud engine?

No. YEO provides an identity-presence signal designed to strengthen the information available to your existing fraud and risk controls.

Can we use YEO only for selected payment actions?

Yes. Verification can run throughout the session or at configured events such as device enrolment, account recovery, beneficiary changes or high-value payments.

What happens when verification fails?

Your platform determines the response: re-verification, restricting a sensitive action, flagging the session for review or ending the session.

Is biometric data sent to YEO?

No. Biometric processing takes place on the user’s device. YEO does not maintain a central biometric database.

Does YEO replace SCA or MFA?

No. YEO works alongside SCA, MFA, KYC, device intelligence and transaction monitoring. It adds identity assurance during the session.

Book a 20-minute session-risk review

We'll cover

How the customer is verified today

Where trust is inherited from an earlier check

Which actions carry the greatest fraud or account-takeover risk

Where continuous or event-based verification may add value

Explore SOLUTIONS:

YEO CFR SDK

Certified for trust

Currently in the process of also acquiring the following certifications:

  • ISO 27001

  • Fido

HIPAA Badge

Cyber Essentials

Certified for trust

Currently in the process of also acquiring the following certifications:

  • ISO 27001

  • Fido

HIPAA Badge

Cyber Essentials

Certified for trust

Currently in the process of also acquiring the following certifications:

  • ISO 27001

  • Fido

HIPAA Badge

Cyber Essentials

Next industry

Slide 1 of 1
Slide 1 of 1
Gavel icon
Lock icon
Shield icon
Message icon

See continuous identity verification in action

See continuous identity verification in action
See continuous identity verification in action
See how YEO's continuous facial recognition technology works, and what it can do for your platform or team.
YEO CFR SDK
YEO for Business

See continuous identity verification in action

See continuous identity verification in action
See continuous identity verification in action
See how YEO's continuous facial recognition technology works, and what it can do for your platform or team.
YEO CFR SDK
YEO for Business

See continuous identity verification in action

See continuous identity verification in action
See continuous identity verification in action
See how YEO's continuous facial recognition technology works, and what it can do for your platform or team.
YEO CFR SDK
YEO for Business
Certifications

© 2026 YEO messaging Ltd is registered in England and Wales 10785061.

🇺🇸 US patent No: 10,607,035
🇬🇧 GB patent No: 1713943.7
🇨🇳 Chinese patent No: 201880071020.4
🇪🇺 EU patent No: 3676738

Certifications

© 2026 YEO messaging Ltd is registered in England and Wales 10785061.

🇺🇸 US patent No: 10,607,035
🇬🇧 GB patent No: 1713943.7
🇨🇳 Chinese patent No: 201880071020.4
🇪🇺 EU patent No: 3676738

Certifications

© 2026 YEO messaging Ltd is registered in England and Wales 10785061.

🇺🇸 US patent No: 10,607,035
🇬🇧 GB patent No: 1713943.7
🇨🇳 Chinese patent No: 201880071020.4
🇪🇺 EU patent No: 3676738