IBM Financial Services Czech Republic

Flowpay

Risk Management

Flowpay needed to speed expansion into new countries and improve lending efficiency because metadata generation for PSD2 transaction categorization and underwriting report preparation were manual, slow, and difficult to scale across markets.

100% time savings for new market research and metadata creation
pilot built and tested by seven users over four weeks
~20% speed increase in loan approval process by under-writer
~50% time savings per country for metadata error correction, monthly

Reported impact

Business outcome

Flowpay reduced the time needed to research and launch into new markets, cut recurring metadata cleanup work, and sped up underwriting so its small team can expand internationally with less manual effort.

  • Productivity Improvement
  • Revenue Growth
  • Speed to Market

Solution

Through IBM Client Engineering and the Fintechx program, Flowpay built two generative-AI-assisted workflows on IBM watsonx.ai to accelerate both market entry and underwriting. The first uses large language models plus internet search results to assemble an initial metadata dataset for each new country, helping Flowpay categorize PSD2 transaction data from prospective customers faster as it enters new markets. The second uses raw PSD2 bank-account transactions and calculated data points to generate a plain-language underwriting summary that describes an applicant’s financial health and lending risk, giving human underwriters a faster starting point. Both workflows were piloted with seven users over four weeks and run within an IBM Cloud-based data environment using supporting services such as object storage, Watson Studio, and PostgreSQL. Because the outputs are intended to be refined and exposed through APIs, Flowpay turned generative AI into a reusable part of its cross-market risk and operations stack rather than a one-off proof of concept.

Data flow

Public web information and PSD2 transaction data flow into watsonx.ai-powered processes, one generates market metadata for new-country onboarding and the other produces underwriting summaries from bank transactions and calculated features, and the resulting outputs are refined for API delivery inside Flowpay’s lending platform.

Solution architecture

5 components · 3 layers
  1. Compute
    • IBM watsonx.ai Runs the large language model workflows that generate market metadata and underwriting summaries.
    • IBM Watson Studio Supports the collaborative development and testing of the AI-assisted process flows.
  2. Storage
    • IBM Cloud Object Storage Stores the data used to assemble metadata and underwriting assets during the AI workflows.
    • IBM Cloud Databases for PostgreSQL Persists the structured application and metadata information used by the lending workflows.
  3. Serving
    • IBM Cloud Hosts the pilot environment and related services for Flowpay’s AI-assisted processes.

Architecture clues

  • Flowpay plans to expose the underwriting report through API calls inside its main product.
  • One workflow generates metadata for new-country onboarding and another generates underwriting reports from PSD2 transactions.
  • The system was first piloted before market rollouts such as Slovakia.

Evidence from the source

“100% time savings for new market research and metadata creation”
“Both processes rely on IBM watsonx.ai”
“The first solution uses large language models (LLMs) to generate completely new content, and to process internet-based search results.”
“The second solution is designed to significantly speed up Flowpay‘s underwriting process.”
“~20% speed increase in loan approval process by under-writer”
Transparency Evidence & methodology 100/100 reference value · 89% 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 value100/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 impact25/25
    3 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • 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
    5 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 specificity10/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. IBM

    Flowpay customer story

    First-party
    https://www.ibm.com/case-studies/flowpay-watsonx
    Source type
    Vendor-published customer story
    Published
    Apr 4, 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.