SecBriefs
← All briefs

A Metro Bank customer lost £14,244 after the bank flagged—but did not stop—the fraud

The customer rejected a suspicious payment, yet further transactions were processed before the card was fully blocked.

Hand-drawn SecBriefs editorial illustration: A Metro Bank customer lost £14,244 after the bank flagged—but did not stop—the fraudSOURCE · The Guardian
© 2026 SecBriefs · Original illustration

THE BRIEF

A Metro Bank customer reported £14,244 in unauthorized payments used to buy AI-service credits. The bank had asked whether an early transaction was legitimate and received a ‘no’, but additional payments continued before the card was fully frozen.

WHY IT MATTERS

The case shows a control gap between detecting suspicion and stopping loss. Repeated smaller transactions can continue while systems treat a previously used merchant as familiar.

WHO SHOULD CARE

Bank customers, card issuers, fraud operations teams and AI-service providers accepting high-volume credit purchases.

WHAT TO DO NOW

  • Call the bank immediately and request a full card and token block.
  • Remove stored payment methods from affected services.
  • Banks should test whether a customer rejection blocks related follow-on attempts.

VERIFICATION NOTE

Source basis: The Guardian’s account and responses from Metro Bank and Anthropic.

Read original at The Guardian

SecBriefs adds context and practical guidance. Reporting remains credited and linked to the original publisher.