Microsoft Financial Services Global

Swift

Fraud Detection · Risk Management

Swift needed to improve fraud and anomaly detection for global financial transactions without copying or moving sensitive member data out of secure locations.

More than nine billion financial messages a year
Over 11,500 financial institutions worldwide
Products and services delivered in over 200 countries

Reported impact

Business outcome

Swift is creating a privacy-preserving fraud-detection approach that can improve financial-crime prevention while keeping member data confidential and operationally distributed.

  • Compliance
  • Cost Reduction
  • Risk Reduction

Solution

Swift and Microsoft are building a federated anomaly-detection platform for financial crime on Azure Machine Learning and Azure confidential computing. Rather than moving member data to a central repository, Swift sends models to participants’ local compute environments, trains against distributed datasets at the edge, and then fuses the training results into a shared model. Confidential computing and supporting governance controls keep data protected during collaboration, while the Azure ML environment manages the training workflows required for the anomaly-detection use case. The design lets more than 11,500 financial institutions contribute insights without copying transactional data out of secure locations, preserving privacy while improving pattern detection. For Swift, the architecture creates a path to detect fraudulent transactions more accurately, with stronger security, privacy, and cost efficiency than traditional centralized approaches.

Data flow

Transactional data stays in participants’ secure environments, Azure Machine Learning sends models to local compute for training, Azure confidential computing protects execution, and the resulting training outputs are fused into a shared anomaly-detection model.

Solution architecture

3 components · 2 layers
  1. Compute
    • Azure Machine Learning Orchestrates federated model training and the anomaly-detection workflow across distributed participants.
    • Azure confidential computing Protects data and model execution while training occurs at secure participant locations.
  2. Governance
    • Microsoft Purview Supports the governance and policy framework around sensitive financial data collaboration.

Architecture clues

  • Federated learning sends the model to the data instead of moving the data to the model
  • Participants’ data remains confidential during collaborative model building
  • Zero Trust based policy framework is part of the design

Evidence from the source

Rather than bringing the data to a central point, we do the opposite. We send the model for training to the participants’ local compute and datasets at the edge and fuse the training results in a foundation model.
Swift’s network and platform is trusted to provide seamless automated transmission, receipt, and processing of more than nine billion financial messages a year.
Using federated learning techniques along with Azure Machine Learning and Azure confidential computing, Swift and Microsoft are building an anomaly detection model for transactional data—all without copying or moving data from secure locations.
Transparency Evidence & methodology 75/100 reference value · 82% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value75/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence82%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence15/20
    3 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Microsoft

    Swift customer story

    First-party
    https://www.microsoft.com/en/customers/story/1637929534319366070-swift-banking-capital-markets-azure-machine-learning
    Source type
    Vendor-published customer story
    Published
    May 23, 2023
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page May 23, 2023 · Microsoft · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.