AWS Financial Services Netherlands

bunq

Customer Service Automation · Document Processing

bunq was founded in 2012 to bring diversity of product, people, and business models to the traditional banking sector. Just over a decade after its launch, the neobank with a €1.65 billion valuation operates a banking license in the Netherlands and has more than 11 million users across Europe.

1.65 billion
11 million
3x

Reported impact

Business outcome

bunq has been making life easy for its users from day one, so it was quick to see the potential to improve the banking experience with generative AI. The neobank uses Amazon Bedrock —a fully managed service to build and scale generative AI applications with foundation models—for several use cases, including summarizing new user data with large language models.

  • Scalability

Solution

bunq was founded in 2012 to bring diversity of product, people, and business models to the traditional banking sector. Just over a decade after its launch, the neobank with a €1.65 billion valuation operates a banking license in the Netherlands and has more than 11 million users across Europe. Key Outcomes greater support efficiency 3x output accuracy 90% Key services included Amazon Bedrock hosts the foundation models and generative ai application logic; AWS Security Hub aggregates security checks and centralized alerts; AWS CloudHSM provides single-tenant hardware key management for regulated workloads; AWS Key Management Service manages encryption keys for protected application data. bunq has been making life easy for its users from day one, so it was quick to see the potential to improve the banking experience with generative AI.

Solution architecture

4 components · 2 layers
  1. Compute
    • Amazon Bedrock Hosts the foundation models and generative AI application logic.
  2. Governance
    • AWS Security Hub Aggregates security checks and centralized alerts.
    • AWS CloudHSM Provides single-tenant hardware key management for regulated workloads.
    • AWS Key Management Service Manages encryption keys for protected application data.

Evidence from the source

Just over a decade after its launch, the neobank with a €1.65 billion valuation operates a banking license in the Netherlands and has more than 11 million users across Europe.
Protecting data is a top priority, and using AWS helps bunq comply with GDPR and the Payment Card Industry Data Security Standard (PCI DSS).
Using managed services, bunq quickly made productivity gains, requiring fewer resources to run IT and helping the team focus on the business.
With AWS CloudHSM , which lets organizations manage single-tenant hardware security modules on AWS, bunq can control keys for card payments.
With rising demand for its digital banking offering across Europe, bunq migrated its infrastructure to AWS for increased scale and easier maintenance.
bunq was founded in 2012 to bring diversity of product, people, and business models to the traditional banking sector.
Transparency Evidence & methodology 75/100 reference value · 85% 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 depth10/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 impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence85%
  • 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 evidence20/20
    6 direct source quotes retained.
  • Date provenance8/10
    The publication date comes from publisher-controlled metadata.
  • 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. AWS

    bunq customer story

    First-party
    https://aws.amazon.com/solutions/case-studies/bunq-case-study
    Source type
    Vendor-published customer story
    Published
    Jan 1, 2024
    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

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.