Confluent Financial Services global

SumUp

Application Refactoring · Real-time Analytics

SumUp's centralized data platform had become a bottleneck, leaving teams waiting for pipelines, reports, and analytics while siloed systems made it difficult to provide merchants with better real-time products and decisions at global scale.

36 markets worldwide
Over the last two years
a handful of projects per quarter
more than 20 teams

Reported impact

Business outcome

SumUp reduced data-team bottlenecks, gave more than 20 internal teams self-service access to trusted streams, and accelerated customer-facing analytics, CRM, and machine-learning work without growing infrastructure overhead.

  • Customer Experience
  • Productivity Improvement
  • Scalability
  • Speed to Market

Solution

SumUp used Confluent Cloud to implement a data-mesh-oriented event architecture that decentralizes data ownership and turns siloed operational information into reusable streaming data products. The managed platform lets teams publish and consume standardized streams without waiting on a central platform group to build every new pipeline. Kafka Connect and Schema Registry support consistent interfaces and data quality, while Confluent Cloud runs across on-premises and AWS-hosted environments and fits into SumUp's microservices architecture backed by Amazon RDS for PostgreSQL. Internal teams now publish streams directly to the shared platform, and downstream groups use them for reporting, CRM, analytics, banking services, and machine learning use cases. This shifted the platform team away from pipeline firefighting toward governance, self-service enablement, and higher-value data product work.

Data flow

Teams publish transaction, CRM, analytics, and operational data streams into Confluent Cloud, where standardized contracts and pipelines make the data reusable for downstream reporting, customer-facing applications, risk models, and other self-service consumers across the business.

Solution architecture

3 components · 3 layers
  1. Ingest
    • Kafka Connect Helps SumUp standardize streaming data pipelines between source systems and downstream end systems.
  2. Governance
    • Schema Registry Maintains consistent event contracts and data quality across independently owned streams.
  3. Uncategorized
    • Confluent Cloud Provides SumUp's shared managed streaming platform for publishing, governing, and consuming data products.

Architecture clues

  • Risk, CRM, banking, and analytics teams publish and consume streams independently on the shared Confluent backbone.
  • SumUp applies data mesh principles including federated governance, self-service infrastructure, and domain ownership.
  • The managed platform spans on-premises and AWS-hosted environments.

Evidence from the source

"Migrating to Confluent Cloud allowed the data platform team to make significant strides in implementing data mesh principles."
"Now, more than 20 teams across SumUp use Confluent Cloud to pursue advanced, mission-critical use cases."
"Over the last two years, Confluent Cloud has become integral to provide internal teams with the trusted, shareable data products they need to accelerate innovation and business growth."
"Today, individual teams at SumUp independently publish streaming data directly to Confluent Cloud."
Transparency Evidence & methodology 70/100 reference value · 77% 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 value70/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 scale5/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence77%
  • 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
    4 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • 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. Confluent

    SumUp customer story

    First-party
    https://www.confluent.io/customers/sumup/
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • First archived Mar 3, 2024 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
  • Sitemap last modified Oct 11, 2026 · Confluent · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.