New : Pradeo recognized Company of the Year 2026 by Frost & SullivanRead the announcement

Use case

Anti-fraud for mobile applications

A banking, payment or healthcare application runs on a device the organization does not control. Alongside it may sit a keylogger, a one-time-code interceptor or an overlay that captures credentials the moment they are typed.

Strong authentication is not enough if the runtime environment is already compromised: a code received by SMS and then intercepted remains valid in the eyes of the server. The application must therefore assess the reliability of the device itself before opening a session.

Talk to an expertDiscover In-App Protection
User making a payment from their mobile application

The context

Why fraud is moving to mobile

Mobile now concentrates a large share of transactional journeys, and fraudsters are adapting their techniques to it.

Modern banking malware combines several vectors: overlaying a fake login screen, reading notifications to capture validation codes, and remote access to initiate transfers without the account holder knowing.

Rooting or jailbreaking the device, sometimes done by the user themselves, disables system partitioning and makes all these attacks markedly easier to carry out.

PSD2 requires payment service providers to take measures to limit the risk of a compromised device, including mechanisms that check the software or device has not been altered. It is being replaced by PSD3 and a European regulation on payment services. PCI MPoC and EMV mobile set comparable requirements for payment applications.

Fraud techniques

Three techniques that target mobile applications

Credential capture

Keyloggers, automatic screen captures and fake overlaid windows intercept usernames and passwords the moment they are entered.

Authentication hijacking

Reading SMS and notifications to retrieve one-time codes, which bypasses two-factor authentication.

Application tampering

Reverse engineering, binary modification and redistribution of a cloned version that keeps the look of the original while diverting transactions.

The solution

How Pradeo protects your applications

Pradeo combines two protections. Shielding hardens the application's binary before release: the code becomes hard to analyse, modify and clone. RASP, embedded in the application as an SDK (Android) or framework (iOS), continuously monitors the runtime environment: malicious applications, rigged networks, altered systems.

When facing a threat, the application triggers the configured responses. Security events are reported from devices and help adjust the strategy.

The benefits

What In-App Protection changes

The application protects itself, with no user intervention.

Risky transactions blocked

Transactions initiated from an untrusted device or application can be blocked.

Support for compliance

Verifying the application and the device helps meet the requirements of PSD2, PCI MPoC and EMV mobile.

A preserved experience

A lightweight module with negligible battery impact, no data collection and minimal permissions.

Talk to an expertDiscover In-App Protection