Fraud Detection Software Philippines: How to Choose

Fraud detection software spots and stops suspicious users and transactions before money moves. In the Philippines, a complete setup covers four layers: identity at onboarding, device risk, session behavior, and transaction monitoring. Under AFASA, banks and e-wallets also need real-time systems that can block disputed transfers. So choose tools by the layer you lack, not by the longest feature list.

Four Layers Fraud Detection Software Should Cover

Most fraud does not start with the transfer. Instead, it starts with a fake or borrowed identity, a tampered phone, or a hijacked session. That is why buyers who only look at transaction rules often miss the cheapest place to stop an attack.

Layer	Question it answers	Example signals
Identity	Is this a real person who owns this ID?	Government record match, liveness, face match, duplicate faces
Device	Can we trust the phone or browser?	Emulator, rooted phone, hooking tools, one device with many accounts
Session	Is the account owner the one using it now?	New device, unusual location, rapid changes to phone or email
Transaction	Does this payment fit the customer’s pattern?	Velocity, new payees, transfers to known mule accounts

Each layer catches a different stage. For example, identity checks block mule accounts before they open, while transaction monitoring catches a takeover after it happens. Our guide to transaction monitoring rules covers the last layer in depth.

What AFASA Expects From Fraud Systems

AFASA turned fraud tooling from a choice into a duty. Its Section 6 makes institutions guard client accounts with controls such as multi-factor authentication and fraud management systems. The law describes those systems as automated tools that spot and stop disputed, suspicious, or other online transactions in real time.

The stakes are financial. Under the text of RA 12010, institutions that fail to use adequate controls must restore funds that account owners lose to scams. On the other hand, institutions the BSP finds compliant are not liable for those losses.

BSP has since added detail. BSP Circular 1213 updated the IT risk management rules so they carry out Section 6, building on the 2022 framework in Circular 1140. For a control-by-control view, see our AFASA compliance checklist.

Build, Buy, or Combine Fraud Tools

Still, few institutions buy one product for all four layers. More often, they combine a core banking or payments rules engine with specialist tools. The table shows the usual trade-offs.

Approach	Strength	Weak spot
Build in-house rules	Full control, tuned to your products	No access to government records or device intelligence
Single fraud platform	One dashboard and one contract	Often weak on local ID checks and biometrics
Specialist APIs plus your rules engine	Best tool per layer, easier to swap	Needs integration work and one owner for decisions

In practice, Philippine lenders and e-wallets lean toward the third option. Their rules engine stays in place, while identity and device checks come from APIs that already reach local records.

How to Compare Fraud Detection Vendors

Vendor demos rarely fail. So make every vendor answer the same questions, in writing, before any pilot.

Local Coverage for Philippine Users

Ask which Philippine records the vendor can check, for example the PhilSys registry or LTO, SSS, and NBI data. Also ask whether it reads local IDs reliably from phone photos. A global tool that cannot validate a PhilID only does half the job here.

Speed That Fits Real-Time Blocking

AFASA expects real-time blocking, so latency is a compliance issue as well. Ask for response times at your peak volume, not at demo load. Then check what happens when the vendor’s service is down.

Reasons Behind Every Decision

Your team must explain blocks to customers, auditors, and the BSP. Therefore, prefer tools that return reason codes or signals with each score. A score without reasons makes disputes slow and tuning almost impossible.

Fit With Your Case Workflow

After all, alerts need an owner. Check whether results flow into your case management tool, or whether staff must copy them across by hand. Also confirm that every decision carries a timestamp, since that record is your evidence under AFASA.

Data Privacy and Contract Terms

Fraud tools process IDs, faces, and device details. Even so, the Data Privacy Act keeps you accountable for how vendors handle them. So agree on processing location, retention, and breach notice before go-live, and read our note on privacy duties in KYC.

Three Fraud Scenarios to Test Before You Buy

Meanwhile, feature lists blur together. Real scenarios do not, so ask each vendor to walk through these three.

• Promo abuse at an e-wallet. One phone opens twenty accounts to claim sign-up bonuses. Device checks should link the accounts before any bonus pays out.
• Borrowed IDs at a lending app. A ring applies for loans with real IDs bought from their owners. Here, liveness and face match should show that the applicant is not the ID owner.
• Takeover at a bank. A scammer convinces a customer to share access, then registers a new device. In this case, a selfie step-up on device change should stop the transfer that follows.

The second scenario is how most money mule schemes start. So a vendor that cannot handle it will leave your mule risk untouched.

Where Verihubs Fits in Your Fraud Stack

Verihubs covers the identity and device layers. Its ID verification that checks PhilSys and other agency records confirms that applicant details match official data. Face recognition and liveness then confirm that the applicant is present and owns the ID.

On the device side, device intelligence that flags emulators and rooted phones also detects app hooking and many accounts on one device. However, Verihubs does not run transaction monitoring. Instead, its signals feed the rules engine or monitoring system you already use.

Frequently Asked Questions

What is fraud detection software?

Put simply, it flags or blocks suspicious users, devices, sessions, or transactions. Most setups combine several tools, each covering one layer of the customer journey.

Does AFASA require fraud detection software?

Yes, in effect. RA 12010 requires institutions to use adequate controls, including real-time fraud management systems that spot and stop suspicious online transfers.

What is the difference between fraud detection and transaction monitoring?

Transaction monitoring is one part of fraud detection. It reviews payments, while fraud detection also covers identity checks at onboarding, device risk, and session behavior.

How much does fraud detection software cost?

Pricing varies by model. Identity and device APIs usually charge per check, while platforms often add a monthly fee for dashboards and case tools.

Can small lenders use fraud detection software?

Yes. Pay-per-check APIs let smaller lenders start with identity and device checks, then add more layers as volume grows.

Choosing Fraud Detection Software That Closes Your Gaps

Start with the layer where your losses begin, not with the biggest platform. For most Philippine lenders and e-wallets, that means identity and device checks at onboarding, linked to the rules engine they already run. Then test vendors on real scenarios and demand reasons with every score. That way, your fraud stack also becomes the evidence AFASA asks you to keep.

Mapping your fraud layers this quarter? Talk to Verihubs about identity and device checks for your onboarding flow.