Skip to content
Contact us

Pix Shield

Protect the payment screen, not just the login.

Device-level protection against the trojans that drain real accounts: overlays, accessibility abuse, screen capture and remote access.

Transfer, Fake overlay, Transaction blocked, Remote access, Accessibility abuse

Built for apps that move money in Brazil.

Banking trojans in Brazil rely on tricking the customer on their own device. Pix Shield detects those techniques at the moment of payment and can stop the transaction before it leaves the account.

  • Overlay and accessibility-service abuse
  • Screen capture and recording, with content hiding
  • Active remote access, with transaction blocking
  • Ready-made policies for payment screens
  • 7.37 bn

    Pix transactions in August 2026

    Banco Central do Brasil

  • R$ 200 / R$ 1,000

    Per-transaction and daily limits on new devices under BCB Resolution 403

    Banco Central do Brasil

What Pix Shield does

  • 01

    Overlay detection

    Detects fake screens drawn over your payment or login screen to harvest credentials and confirmations.

  • 02

    Accessibility-service abuse

    Detects malware that reads the screen or taps on the customer's behalf through accessibility services.

  • 03

    Screen capture and recording

    Detects capture and recording of sensitive screens and hides their content while it happens.

  • 04

    Remote access

    Detects remote-control and screen-sharing tools, and blocks the transaction while someone else is driving the device.

  • 05

    Ready-made payment policies

    Start from policies designed for payment screens and tune them in moatgator.yml.

  • 06

    Evidence for your fraud team

    Every blocked attempt reaches Pulse with context, ready for your fraud and risk teams.

From payment screen to blocked attempt

  1. 1

    Mark the sensitive screens

    Declare which screens and flows are payment-critical in moatgator.yml.

  2. 2

    Pick the policy

    Start from a ready-made payment policy, or tune the response for each threat.

  3. 3

    Stop and learn

    Blocked attempts appear in Pulse with context, and alerts reach your fraud team.

moatgator.ymlIllustrative example
screens:  - id: transfer_confirm    protect: paymentpolicy:  overlay: block  accessibility_abuse: block  screen_capture: hide_content  remote_access: block_transaction

Threats covered

Overlays

  • Fake login and confirmation screens
  • Draw-over-other-apps abuse

Accessibility abuse

  • Services reading on-screen content
  • Automated taps and gestures

Capture

  • Screenshots and screen recording
  • Screen-casting

Remote access

  • Remote-control tools
  • Screen-sharing sessions during a payment

Frequently asked questions

Which plans include Pix Shield?

Scale and Enterprise.

Is it only for Pix?

It is built around Pix flows, and it protects any payment or sensitive screen in your app.

What happens to the transaction?

Your policy decides. It can warn, block the transaction or end the session, and every attempt is reported to Pulse.

What about customers who use assistive technology?

Policies can trust specific accessibility services, so legitimate assistive tools keep working.

Does Pix Shield replace my fraud engine?

No. It adds device-level signals that your fraud engine cannot see, and feeds them to your backend through Attest and Pulse.

Ready to protect your app?

Start free, or tell us what you need.