MétaCan
Menu
Back to cohort
Record W4382677794 · doi:10.1109/emr.2023.3288432

Considerations for Using Artificial Intelligence to Manage Authorized Push Payment (APP) Scams

2023· article· en· W4382677794 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueIEEE Engineering Management Review · 2023
Typearticle
Languageen
FieldComputer Science
TopicBlockchain Technology Applications and Security
Canadian institutionsTD Bank GroupYork University
Fundersnot available
KeywordsPaymentLiabilityBusinessSociotechnical systemComputer securityService providerInvestment (military)Identity theftService (business)Computer scienceMarketingKnowledge managementFinanceLaw

Abstract

fetched live from OpenAlex

Artificial Intelligence (AI)-based security intelligence modeling can be used to prevent, detect, and manage cyber threats. Data-driven AI solutions are currently undergoing rigorous research and design changes in their own field, but few scholars or practitioners frame authorized push payment (APP) scams as a unique cybersecurity concern, or tailor technical solutions based on local regulatory contexts. Drawing on a recent consultation publication by the UK Payment Systems Regulator on APP scams (November 2021), this article shows how AI can be leveraged to manage APP scams and explores some of the opportunities and risks one should consider when adopting such an approach. We highlight three scenarios: 1) Liability on payment service provider; 2) Liability on payor; and 3) Liability on payor with substantial public sector involvement. These examples illustrate how sociotechnical systems can play a design role, and consequently assist industry leaders and engineering management in prioritizing investment focus, strategic approaches, and technical solutions.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.821
Threshold uncertainty score0.709

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.059
GPT teacher head0.307
Teacher spread0.248 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it