Topic starter
10/06/2026 10:32 pm
TL;DR: AFASA is pushing Philippine banks toward real-time fraud detection, stronger authentication, and fund-recovery workflows, while Sumsub reports a 180% year-on-year rise in multi-step coordinated fraud globally and a 61% rise in deepfake attacks in the Philippines in 2025. The governance challenge is no longer detection alone, but whether transaction monitoring can intervene fast enough to stop suspicious activity before settlement.
Editorial analysis by NHI Mgmt Group, based on content published by SumSub: “Sumsub Launches AFASA Fraud Management Bundle to Strengthen Real-Time Fraud Prevention in the Philippines”.
By the numbers:
- SumSub’s Identity Fraud Report 2025-2026 recorded a 180% year-on-year increase in multi-step coordinated fraud globally.
- Deepfake attacks in the Philippines grew 61% year on year in 2025.
Key questions
Q: What breaks when transaction monitoring cannot act before settlement?
A: When monitoring only flags fraud after a payment clears, the institution loses its best intervention window and shifts from prevention to recovery.
Q: Why do hybrid fraud controls work better than a single detection layer?
A: Hybrid controls work because fraud signals are uneven.
Q: What are the signs that transaction monitoring is too slow for modern fraud?
A: Common signals include repeated suspicious transfers reaching settlement, excessive manual review after the fact, and intervention only when customers report loss.
Practitioner guidance
- Align transaction paths to decision outcomes Map outgoing transfers to prevention actions and incoming funds to recovery actions so every suspicious transaction has a predefined response path before settlement.
- Separate hard-stop rules from scored reviews Use direct-action rules for blacklist matches, bot activity, and abnormal access, while reserving dynamic scoring for ambiguous cases that need review or extra verification.
- Unify device, KYC, and case data Feed device intelligence, customer profile data, and case management into one operating view so analysts can see why a transaction was flagged and what to do next.
Bottom line: AFASA-linked fraud controls move banks away from passive monitoring and toward transaction decisions that can stop or hold suspicious activity in flight.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 2 days ago by NHI Mgmt Group
11/06/2026 2:36 am
Real-time fraud governance is becoming an identity problem, not only a payments problem. AFASA pushes institutions to decide whether a transaction is ordinary, suspicious, or recoverable while the money is still moving. That shifts fraud control into the same operational space as identity assurance, privileged access, and step-up verification. The practitioner conclusion is clear: fraud response now depends on how fast identity and transaction signals can be joined.
A few things that frame the scale:
- Only 1.5 out of 10 organisations are highly confident in their ability to secure NHIs, compared to nearly 1 in 4 for securing human identities, according to The State of Non-Human Identity Security.
- Lack of credential rotation is cited as the top cause of NHI-related attacks by 45% of organisations, followed by inadequate monitoring and logging at 37% and over-privileged accounts at 37%.
A question worth separating out:
Q: Who is accountable when transaction monitoring decisions affect customer funds?
A: Accountability should sit with the institution that owns the payment flow, but decision rights need to be explicit across fraud, operations, and compliance. Each control path should define who can hold a transfer, who can approve release, and who can trigger recovery. Without named ownership, real-time monitoring becomes operationally ambiguous.
👉 Read our full editorial: AFASA fraud controls raise the bar for transaction monitoring
12/06/2026 4:10 am
AFASA turns transaction monitoring into a live identity decision problem, not a retrospective fraud report. The article shows that banks are being pushed to make a decision before settlement, while the underlying attack patterns are increasingly multi-step and AI-assisted. That combination means the control boundary has moved upstream into detection, authentication, and escalation logic. Practitioners should treat fraud monitoring as part of the identity decision plane, not a separate analytics layer.
A few things that frame the scale:
- Nearly 60% of companies reported that fraud losses were still increasing in 2025.
A question worth separating out:
Q: How should fraud, IAM, and case teams share responsibility for suspicious transactions?
A: Fraud operations should own the decision workflow, IAM should harden authentication and access signals, and case teams should preserve evidence and drive recovery. If those functions are split into separate queues with no shared decision model, suspicious activity moves faster than the organisation can coordinate a response.
👉 Read our full editorial: AFASA fraud controls raise the bar for transaction monitoring
This post was modified 2 days ago by NHI Mgmt Group