Fraud and scam rules, reimbursement and liability changes for banks and payment firms, with the opportunity each one opens up.
Updated monthly · Last updated: · Items leave the tracker once their month has passed.
Who sets fraud and scam rules
| Body | Rules | Payments angle | Who it applies to |
|---|---|---|---|
| UK: Payment Systems Regulator, moving to the FCA | APP scam reimbursement for Faster Payments and CHAPS | Sending and receiving banks share losses | UK payment firms |
| Australia: Treasury, ACCC, ASIC, AFCA | Scams Prevention Framework and sector codes | Prevent, detect, disrupt, respond and report | Banks, telcos, digital platforms |
| India: Reserve Bank of India | Fraud protection rules for digital payments | Liability, alerts and refunds | Banks and payment firms |
| Brazil: Banco Central do Brasil | Pix security rules | Fraud flags and refunds | Pix participants |
What changed this month
A short log of new and changed items, updated every month.
Week of Nov 16, 2026
- Tracker launched with 4 fraud and scam rule changes in India, Brazil, Australia and the UK.
- Next deadline: RBI fraud protection rules for digital payments, Jan 1, 2027.
- Moved here from the Payment Rules tracker: RBI fraud protection and Pix security rules.
Fraud and scams tracker
Soonest first. Tap a region or a status to filter; tap again to clear.
FILTER BY REGION
FILTER BY STATUS
| Region | Rule or change | What it means | Opportunity | Key date |
|---|---|---|---|---|
| India | RBI fraud protection for e-payments Our guide → · Source: Reserve Bank of India | Banks must prove liability, alert above ₹500, refund small frauds. | Real-time alerts and AI fraud detection. | Jan 1, 2027 Deadline soon |
| Brazil | Pix security and receipt rule updates Our guide → · Source: Agência Brasil (via B3 Bora Investir) | New fraud-flag rules from Feb 2027; Pix receipts lose ads and links from Mar 1. | Fraud-flag workflows, receipt redesign and Pix regression testing. | Feb–Mar 2027 Upcoming |
| Australia | Scams Prevention Framework obligations start Treasury, ACCC, ASIC, AFCA Our guide → · Source: King and Wood Mallesons | Banks, telcos and digital platforms must prevent, detect and respond to scams, with civil penalties. | Scam detection, payee warnings and complaint handling for Australian banks. | Mar 31, 2027 Upcoming |
| United Kingdom | APP scam reimbursement rules under review Payment Systems Regulator, moving to the FCA Our guide → · Source: Grant Thornton | The reimbursement cap and the 50/50 split are under review; rules may change in 2027. | Model reimbursement costs and strengthen receiving-side controls. | Review 2026/27 Change pending |
WHO OWNS THIS
Fraud and scams: roles and sign-off
Each fraud or scam rule needs a named owner. The head of fraud owns the strategy; fraud operations runs claims and reimbursement; the payments product manager builds warnings and checks; compliance confirms the rule is met; the business sponsor signs off.
1. Roles and responsibilities
- Accountable for losses and controls
- Sets detection and warning strategy
- Accepts remaining risk
- Reports to leadership
- Handles scam claims and refunds
- Tracks reimbursement deadlines
- Shares data with other banks
- Confirms operations are ready
- Builds payee checks and warnings
- Adds friction where risk is high
- Plans releases
- Writes impact assessments
- Tunes rules and models
- Monitors scam trends
- Measures false positives
- Reports fraud rates
- Trains staff on scam cases
- Handles complaints and escalations
- Works with the ombudsman
- Tracks complaint times
- Reads new fraud rules
- Approves impact assessments
- Prepares regulator reporting
- Keeps evidence
- Funds fraud controls
- Approves policy changes
- Gives final sign-off
- Reports to the board
2. Who is accountable for what (RACI)
| Activity | Head of fraud | Fraud ops | Payments PM | Fraud analytics | Support | Compliance | Sponsor |
|---|---|---|---|---|---|---|---|
| Log a new fraud rule and name an owner | R | I | I | I | I | A | I |
| Impact assessment | A | C | R | C | C | C | I |
| Payee warnings and checks | C | C | A | C | I | C | I |
| Detection rules and models | C | C | I | A | I | I | I |
| Reimbursement and claims process | C | A | I | I | R | C | I |
| Regulator reporting | C | R | I | R | I | A | I |
| Go-live sign-off | R | R | R | R | R | R | A |
A accountable (one per activity, approves) · R responsible (does the work) · C consulted · I informed.
3. From review to sign-off
4. Sign-off record
One line per rule. No signed line, no go-live.
| Item | Prepared by | Reviewed by | Signed off by | When | Evidence |
|---|---|---|---|---|---|
| RBI fraud protection rules (India) | Fraud operations lead | Compliance lead | Business sponsor | Before Jan 1, 2027 | Alert tests, refund process |
| Scams Prevention Framework (Australia) | Head of fraud | Compliance lead | Business sponsor | Before Mar 31, 2027 | Gap assessment, code mapping |
Titles differ by firm; small teams may combine roles, but the person who builds should not be the only one who signs off. General guidance, not legal advice.
Runbook: from a fraud or scam rule to sign-off
How to handle a fraud or scam rule from this tracker. Use one runbook per rule. Each phase says when, why, what, who and how, and the evidence to keep.
▸1. Plan · Decide if the item applies to you, how big the change is, and who owns it.
When: As soon as an item appears on the tracker. Target: at least 90 days before the key date (T-90). For proposed rules, inside the comment window.
Why: Late discovery is the main reason teams miss deadlines, pay fines or ship rushed changes. Early planning turns a rule into a normal roadmap item.
What: Decide if the item applies to you, how big the change is, and who owns it.
Who: Owner: Head of fraud. With: Compliance lead (reads the rule), Payments product manager (sizes the work), Fraud operations lead.
Example: a new scam reimbursement rule. Confirm which payments and customers are in scope.
How
- Open the official source linked in the tracker and read the actual text, not only the summary.
- Map it to your products, rails, systems, vendors and customers in scope.
- Run a short gap analysis: what we do today versus what the rule needs.
- Size the work (small, medium, large) and add it to the roadmap with a target date.
- Log risks, assumptions, issues and dependencies in the RAID log.
Evidence to keep
- Impact assessment (applies / does not apply, with reason)
- Gap analysis
- Epic or change request with owner and target date
- RAID log entry
▸2. Prepare · Turn the rule into requirements, a design, a test plan and a rollout plan.
When: T-90 to T-60 days.
Why: Clear requirements and a test plan stop rework and give auditors a straight line from the rule to the change.
What: Turn the rule into requirements, a design, a test plan and a rollout plan.
Who: Owner: Payments product manager. With: Fraud analytics lead, Fraud operations lead, Customer support lead.
Example: map each rule clause to a warning, check or process step.
How
- Write requirements that quote the rule clause they come from.
- Agree the design and any vendor or partner changes, with dates.
- Build a traceability matrix: rule clause, requirement, test case, evidence.
- Plan test data, environments and a rollback.
- Book change windows and tell support and operations teams.
Evidence to keep
- Requirements with rule references
- Design or configuration decision
- Traceability matrix (draft)
- Test plan and rollback plan
▸3. Execute · Build or configure, test, and release the change safely.
When: T-60 days to go-live.
Why: This is where the change is built and proven. Testing against the rule, not just the feature, is what protects you.
What: Build or configure, test, and release the change safely.
Who: Owner: Payments product manager. With: Fraud analytics lead (rules), Fraud operations lead (claims process).
Example: add a confirmation step for first-time payees above a set amount.
How
- Build or configure the change behind a flag where possible.
- Run unit, system, regression and negative tests, plus UAT with the business.
- Fix defects and re-test; keep the defect log current.
- Hold a go/no-go meeting with clear criteria.
- Release, watch live metrics and keep the rollback ready.
Evidence to keep
- Test results and defect log
- UAT sign-off
- Go/no-go record
- Change ticket and release notes
▸4. Evidence · One evidence pack that shows the rule was understood, built, tested and approved.
When: Collected all the way through; packaged by T-7 days.
Why: If it is not written down, it did not happen. Good evidence makes audits short and calm.
What: One evidence pack that shows the rule was understood, built, tested and approved.
Who: Owner: Fraud operations lead. With: Fraud analytics lead (rule logs), Customer support lead (training records).
Example: keep alert test results and claim samples.
How
- Create one folder per tracker item with a simple index.
- Store each document with date, version and owner.
- Complete the traceability matrix with links to every test and approval.
- Add screenshots or exports of live configuration where relevant.
- Record training or communications sent to staff and customers.
Evidence to keep
- Evidence index
- Final traceability matrix
- Configuration proof
- Training and communication records
▸5. Audit · Second line (Compliance or Risk) tests the control; Internal Audit may sample it later.
When: From T-7 days to 30 days after go-live.
Why: An independent check finds gaps before a regulator, scheme or customer does.
What: Second line (Compliance or Risk) tests the control; Internal Audit may sample it later.
Who: Owner: Compliance lead (control check). Independent check: Internal audit.
Example: sample ten scam claims for time to refund.
How
- Walk through the evidence pack against the rule text.
- Re-perform a sample of key tests or checks.
- Raise findings with a rating, owner and due date.
- Track findings to closure and re-test the fix.
Evidence to keep
- Control test results
- Findings log with owners and dates
- Closure evidence for each finding
▸6. Review · Post-implementation review: did it work, what broke, what we learned.
When: About 30 days after go-live.
Why: A short look back confirms the change works in real life and makes the next rule easier.
What: Post-implementation review: did it work, what broke, what we learned.
Who: Owner: Head of fraud. With: Fraud analytics lead, Customer support lead (monthly review of fraud rates and complaints).
Example: compare fraud and complaint rates before and after.
How
- Check live metrics: errors, rejects, exceptions, complaints, incidents.
- Confirm all findings and defects are closed or accepted.
- Note lessons learned and update this runbook if needed.
- Update the tracker status and any related guides.
Evidence to keep
- Post-implementation review notes
- Metrics snapshot
- Lessons learned
▸7. Sign-off · Named people confirm the item is done and the evidence is complete.
When: After the review, and before closing the item.
Why: Formal sign-off shows clear ownership and closes the loop for auditors.
What: Named people confirm the item is done and the evidence is complete.
Who: Owner: Business sponsor (approves). Signers in order: Payments product manager, Fraud analytics lead, Fraud operations lead, Customer support lead, Compliance lead, Head of fraud.
Example: close the item when every signer has signed.
How
- Share the evidence pack and review notes with the approvers.
- Each approver confirms their part in writing, with date.
- Archive the pack in your GRC tool or records system.
- Close the epic and the RAID entries.
Evidence to keep
- Signed approvals (name, role, date)
- Archived evidence pack
- Closed epic and RAID items
Sign-off
Sign in this order: Prepared, then Reviewed, then Certified, then Approved. Each signer checks the evidence of the lines above. Close the item only when every line has a name, date and evidence link. The person who prepares cannot approve.
| # | Role | Stage | Confirms | Evidence | Name and date |
|---|---|---|---|---|---|
| 1 | Payments product manager | Prepared | Impact assessment done; warnings and checks built | Impact assessment, UAT | ________________ |
| 2 | Fraud analytics lead | Reviewed | Rules and models tuned and tested | Rule change log, test results | ________________ |
| 3 | Fraud operations lead | Certified | Claims and refund steps ready | Procedures, sample claims | ________________ |
| 4 | Customer support lead | Certified | Staff trained; complaint route ready | Training records | ________________ |
| 5 | Compliance lead | Certified | Rule met; reporting ready | Control test, evidence pack | ________________ |
| 6 | Head of fraud | Approved | Fraud controls effective | Signed approval | ________________ |
| 7 | Business sponsor | Approved | Accepts remaining risk and closes the item | Signed approval | ________________ |
Tip: copy this runbook into your own tracker or GRC tool, one copy per rule. Dates are relative to the key date shown in the tracker (T-90 means 90 days before).
Risk and control self-assessment (RCSA): Fraud and scams
The main risks for this area, the controls that reduce them, and the risk left after those controls. 4 risks are specific to this area and 6 are shared by every tracker (C1 to C6). Owners match the roles in the Who owns this section above. Reviewed every quarter and checked by the second line. Preventive controls lower likelihood; detective and corrective controls lower impact. Read more in our RCSA guide.
10 risks assessed for this area. Controls bring every high inherent risk down to medium or low.
How to read the heat map: each dot is a risk. It starts at its inherent rating (no controls) and moves to its residual rating (after controls). Score = likelihood x impact: 1 to 6 Low, 8 to 12 Medium, 15 to 25 High. Mid-blue dots are this area; navy dots are shared risks.
QUARTERLY RCSA CYCLE
RISK AND CONTROL REGISTER
| ID | Type | Risk and cause | Control | Owner | Inherent | Residual |
|---|---|---|---|---|---|---|
| FR-R1 | This area | Scam losses rise after a rule change Cause: Warnings and checks not updated | Payee checks and risk-based warnings tested before each change Preventive · Per release | Payments product manager | High 16 L4 x I4 | Medium 8 L2 x I4 Control: Partly effective |
| FR-R2 | This area | Refunds miss the regulator deadline Cause: Manual claim handling; no deadline tracking | Claims system with deadline clocks and daily queue review Preventive · Daily | Fraud operations lead | Medium 12 L3 x I4 | Low 4 L1 x I4 Control: Effective |
| FR-R3 | This area | Too many good payments are blocked Cause: Rules tuned only for fraud catch | False-positive tracking and monthly rule tuning Preventive and detective · Monthly | Fraud analytics lead | Medium 9 L3 x I3 | Low 4 L2 x I2 Control: Effective |
| FR-R4 | This area | Money mule accounts receive scam funds unnoticed Cause: No inbound payment monitoring | Inbound mule detection and data sharing with sending banks Detective · Continuous | Head of fraud | High 15 L3 x I5 | Medium 9 L3 x I3 Control: Partly effective |
| C1 | Shared | A rule change is missed Cause: No owner watches the sources; news arrives late | Weekly tracker review; every new item gets a named owner within 5 days Preventive and detective · Weekly | Compliance lead | High 20 L4 x I5 | Medium 8 L2 x I4 Control: Effective |
| C2 | Shared | A rule is read the wrong way Cause: Summaries used instead of the rule text; no expert review | The impact assessment is signed against the source text Preventive · Per item | Compliance lead | High 15 L3 x I5 | Medium 10 L2 x I5 Control: Effective |
| C3 | Shared | A deadline is missed Cause: Work starts too late; dependencies not tracked | Planning starts at T-90; RAID log and go/no-go before release Preventive and detective · Per item | Payments product manager | High 16 L4 x I4 | Low 6 L2 x I3 Control: Effective |
| C4 | Shared | Testing does not cover the rule Cause: Tests check features, not rule clauses | Traceability from each rule clause to a test, with sign-off Preventive · Per release | Fraud analytics lead | Medium 12 L3 x I4 | Low 4 L1 x I4 Control: Effective |
| C5 | Shared | Evidence is missing at audit time Cause: Documents spread across tools; no index | Evidence pack with an index, checked at T-7 Preventive · Per item | Fraud operations lead | Medium 9 L3 x I3 | Low 3 L1 x I3 Control: Effective |
| C6 | Shared | Audit findings stay open Cause: No due dates or follow-up | Findings log with owner and due date; monthly review Preventive and detective · Monthly | Head of fraud | Medium 9 L3 x I3 | Low 4 L2 x I2 Control: Partly effective |
Open actions
- FR-R4: add inbound mule account monitoring. Owner: Head of fraud.
- FR-R2: add deadline alerts to the claims queue. Owner: Fraud operations lead.
- Test two controls in this area each quarter and keep the results in the evidence pack. Owner: Compliance lead.
Quarterly attestation
Head of fraud and Fraud operations lead (first line): confirm risks, controls and ratings are current. ________________
Compliance lead (second line review): confirms the review and challenge. ________________
Business sponsor: accepts residual risk. ________________
This is a sample RCSA for planning and training. Adjust risks, ratings and owners to your own organisation before use. The full cross-area register is in the monthly portfolio status report.
This tracker is a summary for planning, not legal advice. Dates can change, so always check the official source before acting. The Opportunity column is our own view. Summaries are written in our own words; linked pages remain the property of their publishers. Corrections: sp@paymentconsultant.top.
© 2026 SP Sankar · paymentconsultant.top. This tracker, its summaries, diagrams and layout are original work and are protected. Please do not copy, republish or scrape this page without written permission. You are welcome to link to it. See also Payment Rules Tracker and Payment Tech News.