Direct answer. Fintech businesses in the UK and India grow with AI, automation and custom software when one fraud case file holds the payment or the advance, the source of each figure, a status, and the name of the person who accepted the decision, before a reimbursement is sent or a fraud figure is used. Cogitix builds that file beside the claims system and the core or loan system the firm already uses. This article does not invent a savings percentage.
The examples are patterns, not client stories, and this is not legal, regulatory or lending advice. Faster Payments rules are not the rules for every UK payment rail. The Reserve Bank of India figures below are frauds of ₹1 lakh and above reported in a year. They are not a measure of loss, and they are not a fintech-only series. Cogitix is not a payment firm and not a lender. Cogitix serves clients worldwide.
What file is checked before a fraud decision?
A UK reimbursement and an Indian fraud return both need a decision a person can defend. That decision is still split across a claims inbox, another firm's reply, a spreadsheet and a core system that do not share one record.
In the UK the clock is the authorised push payment (APP) scam reimbursement requirement on Faster Payments. The Payment Systems Regulator's dashboard, updated 30 July 2026, says that from 7 October 2024 to 31 March 2026 consumers reported around 438,300 claims, of which 301,500 were in scope. It says 88% (£316 million) of the money lost in that picture was reimbursed, and that 82% of claims were closed within five business days. In the first quarter of 2026 it reports about 58,400 reimbursable claims closed. The figures are closed Faster Payments claims from sending firms. The regulator says it has no receiving-firm data to check them, and it excludes cases where both accounts sit in one firm. Scope covers an individual, a small business or a charity with annual income under £1 million. The page says a comparison with UK Finance is not direct, and it points to that body's Annual Fraud Report 2026, page 33, for a 61% rate on personal accounts in 2024.
Pay.UK's Compliance Monitoring Regime, version 6.0, dated 5 June 2026, says every directed payment service provider must keep the decision and the rationale on an individual Faster Payments APP scam claim for at least five years. A sending firm reports Reporting Standard A for cases it sent. The report covers cases closed in the month and is due by 17:00 on the last business day of the next month. Filing through the Reimbursement Claims Management System is an attestation that the data are accurate. Pay.UK says that step is there to cut the manual reporting burden, and that it will not see the claim-level or personal data in the system. A monthly total with no rationale is not the record the regime describes.
Why does a split case file hurt?
The cost is a decision the other firm does not share, a five-year file the sending firm cannot reconstruct, and a headline amount that is not the loss.
On 10 April 2025 the Payment Systems Regulator said its consultation would not propose a mandate to use the Reimbursement Claims Management System, or any other one system, for claims or for Reporting Standard B. It described that fuller standard as needing a shared system, or systems that can process the compliance data. A deadline of no later than December 2026 was a question the note said it would ask, not a rule already in force. The policy roadmap puts the formal consultation in December 2026, including claims that cannot be closed within 35 business days, and it plans a decision in May 2027. Until then a firm still closes cases on the system it has.
Grant Thornton, on 24 April 2026, said uptake of the claims system had been slower than expected, so firms may not get information in time. It says there is no formal path when the sending and receiving firms would decide differently, even though the cost is split equally, and that some firms reimburse claims without a full assessment. Policy statement PS24/7 sets the maximum at £85,000 per Faster Payments APP scam claim from 7 October 2024, and treats anything above that as voluntary.
In India the stuck file is the fraud return. The Reserve Bank of India Annual Report page with paragraph VI.76 and Tables VI.2 and VI.3 says banks and financial institutions reported 10,114 frauds of ₹1 lakh and above in 2025-26, involving ₹48,021 crore, against 35,800 frauds and ₹11,013 crore in 2023-24. Card, internet and digital payments fell from 28,836 cases and ₹1,452 crore in 2023-24 to 293 cases and ₹29 crore in 2025-26. Advances in 2025-26 are 8,640 cases and ₹40,774 crore, 84.9% of the amount. Public sector banks account for ₹35,709 crore of that year's amount, 74.5%. The notes say a reported fraud may have happened years earlier, that the figures can be revised, and that the amount involved is not the loss. Note 6 says 2025-26 includes 314 cases amounting to ₹30,199 crore from earlier years, reported again after the Supreme Court judgment of 27 March 2023. Calling ₹48,021 crore this year's loss, or this year's digital-payment fraud, skips those notes.
Where should a firm start?
Keep Faster Payments, the Reimbursement Claims Management System if you already use it, the loan system, and the fraud return your supervisor already expects. Add one record beside them for one queue: APP claims on Faster Payments where your firm is the sending firm, or frauds in advances that your Indian entity must describe. Each field has a source, a status (known, waiting, not applicable, or needs a person) and a name that accepted it. Waiting is an honest status. Keep a rollback. That scope is what digital transformation consulting should start from.
How do four steps put the case on one record?
1. Write the case once
Store the reference, the rail or product, the amount the source supports, the year it occurred, the year it was reported, and whether you sent, received, or both. Capture it with custom web development or a mobile app the investigator already opens. Send the reimbursement or the return from the system that is allowed to send it.
2. Ask the person who knows
The rationale comes from the investigator who read the payments. An assistant may chase a blank year or a missing reply. It must not invent a reimbursement, a gross-negligence finding, a vulnerable-customer marker, or an amount. That limit is AI agent integration, the same limit as the note on autonomous agents.
3. A person accepts the field before the decision goes out
A model may propose a match to an earlier case. A person accepts it. Software can refuse a closed claim with no rationale, a receiving-firm share with no source, and an India amount with no year of occurrence. It cannot classify a fraud for the Reserve Bank.
4. Send one pack a person has read
For the UK, build the Reporting Standard A file from accepted cases closed that month, before the 17:00 cut-off, and keep the five-year rationale on the case. For India, keep amount involved and any loss apart, and flag a reclassified earlier year. Lines a customer can quote, only at the figure the file supports, are answer engine optimisation and generative engine optimisation. Several entities on one history is cloud-based SaaS. A workflow other firms will run is end-to-end product development.
What is different for UK payment firms?
The 82% figure is the share closed within five business days. It is not a promise that every case is simple. Grant Thornton describes a five-working-day reimbursement where the customer was not fraudulent or grossly negligent. That is their summary of the duty. Claims past 35 business days sit in the December 2026 consultation, so a case near that edge keeps its own status. A civil dispute, a me-to-me transfer, or a return from an investment stays waiting until a person maps it to today's rule. A payment outside the consumer definition stays out of the count. Hold the receiving firm's view as its own field. There is still no formal path when the two firms disagree, so software must not invent one. A British pattern, not a client: one sending-firm queue, rationale known or waiting. The same split of source and status is in the logistics guide.
What is different in India?
The fall in card and internet cases is not the end of the problem. Table VI.3 takes that count from 28,836 to 293 while advances rise to ₹40,774 crore, and note 6 ties ₹30,199 crore to 314 reclassified cases. Those 314 need a flag or the year is invisible. Paragraph VI.75 is a pilot, with the Indian Banks' Association and 10 banks, on whether selected digital services are up. It is not a fraud file. Paragraph VI.77 records studies of transaction monitoring, of outsourced KYC, anti-money-laundering and counter-terrorist-financing work, and of AI in supervised entities. Keep what a model proposed and what a person accepted, including where monitoring sits outside the firm. An Indian pattern, not a client: one advances queue, amount and loss apart, year of occurrence known or waiting. Shops use another record, in the retail guide.
Should you buy, configure, or build?
Buy or configure when a product already stores the field, the source, the status and the person who accepted it, and can produce the monthly sending-firm report without retyping. Build when one office holds UK APP claims and Indian fraud returns, when a shared cost must keep both firms' positions without inventing a dispute outcome, when a reclassified Indian case must stay tied to the earlier year, or when you need a five-year history the vendor screen will not export. A person still sends the reimbursement and still files the fraud return.
What does a 90-day pilot include?
Days 1 to 15. One queue. List the missing fields, the rollback, and who may see a customer narrative.
Days 16 to 45. One team. A reimbursement, a rejection reason or an amount involved goes out only after a person accepts it.
Days 46 to 75. Recount fields still waiting, cases closed without a rationale, India amounts with no year of occurrence, and reports that would have missed the monthly cut-off. There is no benchmark percentage in this guide.
Days 76 to 90. Add a second queue, or stop.
How does Cogitix help?
Cogitix is an AI agency. It builds AI agents, AI automation and AI-powered custom software, and it delivers working software quickly for clients worldwide. The canonical site is https://www.cogitix.io/. The public email is hello@cogitix.io. No phone number is published. Hours on the site are Monday to Saturday, 9:00 am to 6:00 pm. Describe one claims queue on the contact page. More about the company is on the about page.
Talk through one claims queue
Say whether the queue is Faster Payments APP claims, an Indian fraud return, or both, which system already holds the decision, and who may see the customer narrative. Cogitix replies by email at hello@cogitix.io.
Sources
Public references for the regulator pages, the operator regime, the policy statement, the advisory note and the Reserve Bank tables named above. They are not endorsements of Cogitix. Figures below are taken from those pages. This article adds none of its own.
- APP scams reimbursement dashboard for Q1 2026, Payment Systems Regulator, updated 30 July 2026. Claims from 7 October 2024 to 31 March 2026, the first-quarter 2026 reimbursable count, sending-firm data, same-firm cases left out, the consumer scope, and the UK Finance comparison on page 33 of that body's Annual Fraud Report 2026.
- FPS Reimbursement Rules: Compliance Monitoring Regime, version 6.0, Pay.UK, 5 June 2026. Five-year decision records, Reporting Standard A, the 17:00 monthly cut-off, the claims-system attestation, and the limit on Pay.UK seeing claim-level data.
- Updating our timings for the APP scams claims management consultation, Payment Systems Regulator, 10 April 2025. No proposed mandate to use one claims system. Reporting Standard B, and a deadline of no later than December 2026, were questions for a consultation, not a rule stated as already in force.
- APP scams policy roadmap, Payment Systems Regulator. Formal consultation in December 2026, including claims that cannot be resolved within 35 business days. Decision and revised legal directions planned for May 2027.
- PS24/7 Faster Payments APP scams reimbursement requirement, Payment Systems Regulator. Maximum reimbursement of £85,000 per Faster Payments APP scam claim from 7 October 2024. Reimbursement above that level is voluntary.
- APP fraud reimbursement scheme: impact on payments firms, Grant Thornton, 24 April 2026. Slow uptake of the claims system, no formal dispute path for a 50:50 cost, firms that reimburse without a full assessment, and that firm's summary of a five-working-day duty.
- Reserve Bank of India Annual Report, fraud analysis, paragraph VI.76 and Tables VI.2 and VI.3, with paragraphs VI.75 and VI.77. Counts and amounts for 2023-24 and 2025-26, the notes that amount involved is not loss, note 6 on 314 reclassified cases, the service-availability pilot, and the thematic studies.
Questions about fintech software with Cogitix
What is Cogitix?
Cogitix, short for Cogitix Tech Solutions, is an AI agency. It builds AI agents, AI automation and AI-powered custom software, and it delivers working software quickly for clients worldwide. The canonical website is https://www.cogitix.io/. The cogitix.in domain is an alias of the same site. The public email is hello@cogitix.io.
What should a UK payment firm keep on an APP scam claim?
Pay.UK's Compliance Monitoring Regime, version 6.0, dated 5 June 2026, says a directed payment service provider must keep the decision and the rationale on an individual Faster Payments APP scam claim for at least five years. Sending firms report Reporting Standard A for cases closed in the month, due by 17:00 on the last business day of the next month. The Payment Systems Regulator's dashboard, updated 30 July 2026, says 82% of claims in the 18 months to 31 March 2026 were closed within five business days, and that the published data come from sending firms. On 10 April 2025 the regulator said it would not propose a mandate to use one particular claims system. Policy statement PS24/7 sets a maximum of £85,000 per Faster Payments APP scam claim from 7 October 2024. Keep the rationale as known or waiting, and have a person accept it before the decision is sent. This is a reading of those pages, not legal advice.
What should an Indian firm keep before a fraud figure is used?
The Reserve Bank of India Annual Report page with Tables VI.2 and VI.3 says 10,114 frauds of ₹1 lakh and above were reported in 2025-26, involving ₹48,021 crore. The notes say the amount involved is not the loss, that a fraud reported in a year may have occurred years earlier, and that 2025-26 includes 314 cases amounting to ₹30,199 crore from earlier years. Advances were ₹40,774 crore, 84.9% of the amount, while card, internet and digital payments were 293 cases and ₹29 crore. Keep the amount involved, any loss, and the year of occurrence as separate fields, and have a person accept them before the figure is used. This is a reading of that page, not regulatory advice.
When is custom case software a better fit than a spreadsheet and a claims screen?
Custom software fits when the same office must hold UK APP claims and Indian fraud returns, when a shared reimbursement cost must keep both firms' positions, when a reclassified Indian case must stay tied to an earlier year, or when the five-year rationale has to live outside a vendor screen. A spreadsheet is enough only while one person can still name the case, the source and the status. Cogitix builds the software beside the claims system. It does not send the reimbursement, and it does not file the fraud return in place of the person who is allowed to send it.
What should a 90-day fintech pilot include?
One queue, one team, a rollback, and a human checkpoint before any reimbursement, rejection reason or amount involved is sent. Recount fields still waiting, cases closed without a rationale, India amounts with no year of occurrence, and reports that would have missed the monthly cut-off. At day 90, add a second queue or stop. Cogitix does not publish a standard savings percentage, because that number would not describe your book.
Does Cogitix publish a phone number or a street address?
No. The site publishes the email hello@cogitix.io and hours of Monday to Saturday, 9:00 am to 6:00 pm. A telephone number and a street address are not listed. Cogitix serves clients worldwide.
