hub.xt
Back to works

Case study

Payments AI

How Huboxt built an internal tool that uses an AI agent to read payment confirmations — PDFs and images from banks across many countries — match them against client and credit configurations, flag fraud, and keep operators in control, cutting manual processing work and saving the company around €100,000 a year.

Tech stack

  • Python
  • Next.js
  • OpenAI
  • Docker
payments-ai.huboxt.com
Client
Financial services (confidential)
Engagement
Internal tool, end to end
Services
AI agent, document processing, full-stack
Industry
Fintech / internal automation

Product preview

Payments AI payment confirmation processing dashboard

The challenge

Payment confirmations arrive from all over — different banks, in different countries, in whatever format each bank happens to use. They come as PDFs and images, with no common structure. Someone has to read each one, pull out the details, match it against the right client and credit configuration, and confirm the payment is valid before it's reconciled.

Done manually, that's slow, repetitive and error-prone, and it doesn't scale as volume grows. It's also genuinely hard: payments span multiple currencies, value dating depends on public holidays that differ from country to country, and timezones shift when a payment actually counts. On top of that, manual review across many sources makes fraud easier to miss.

The goal was to automate the reading and matching wherever possible, keep people in control where judgment is needed, and handle the cross-border details — currencies, holidays, timezones, fraud — correctly.

Goals

01

Read any confirmation

Automatically read payment confirmations from any bank, in PDF or image form.

02

Match to configs

Match payments against internal client and credit configurations.

03

Operator oversight

Keep operators able to review and correct everything.

04

Cross-border correctness

Handle multiple currencies, country-specific public holidays and timezones correctly.

05

Fraud detection

Detect potential fraud.

06

Access control

Control who can access and act on what.

Our approach

We built an OpenAI-based agent for document reading, kept operators in the loop for judgment calls, made per-bank prompts tunable, and handled currencies, holidays and timezones properly — with monitoring, fraud detection and access control built in.

01

AI agent for reading

An OpenAI API agent reads payment confirmations directly from PDFs and images, extracting the data needed regardless of the bank's format — removing the manual data-entry step that ate the most time.

02

People in the loop

Operators can review all extracted data and modify it where needed. The tool assists the team rather than replacing their judgment.

03

Tunable per-bank prompts

Configurable prompts for specific banks whose documents weren't processed automatically — improving coverage without code changes.

04

Cross-border & security

Proper handling of currencies, country-specific holidays and timezones, plus a monitoring dashboard, anti-fraud detection and role-based access control.

What we built

An end-to-end internal tool — AI document reading, matching dashboard, operator workflows, and cross-border payment correctness.

  1. 01

    AI document-reading agent

    An OpenAI-API-based agent that reads payment confirmations from PDFs and images across many banks and countries, extracting the data needed to process each payment.

  2. 02

    Monitoring dashboard

    A dashboard for tracking payment statuses, integrated with the company's internal client and credit configurations so payments are matched against the right records.

  3. 03

    Operator review & editing

    Tools for operators to review all data and modify it where required — full human oversight over the automated output.

  4. 04

    Per-bank prompt configuration

    Tunable prompts for specific banks whose documents weren't handled automatically, so coverage can be improved source by source.

  5. 05

    Cross-border correctness

    Handling for multiple currencies, country-specific public holidays and timezones.

  6. 06

    Anti-fraud & access control

    Detection of suspicious activity surfaced for review, plus role-based control over who can access and act on payment data.

Results

01

~€100k saved per year

By automating the reading and matching of payment confirmations, the tool removed a large amount of manual processing work.

02

Faster processing

Payment confirmations from any bank are read and matched automatically, instead of keyed in by hand.

03

People still in control

Operators review and correct everything, so automation speeds the work without removing oversight.

04

Correct across borders

Multiple currencies, country-specific holidays and timezones are handled properly, not approximated.

05

Safer operations

Anti-fraud detection and access controls reduce risk across a process that spans many sources.

The design got the division of labor right: let the AI agent handle the slow, repetitive reading and matching, and keep people in control of the judgment calls. Making the per-bank prompts tunable meant coverage could keep improving without engineering work, and handling currencies, holidays and timezones properly meant the automation could be trusted rather than second-guessed. The payoff was concrete — roughly €100,000 a year in saved manual effort — alongside faster processing, fewer errors, and built-in fraud detection and access control.

Why it worked

Let's talk

Get in touch

Contact us if you have any projects in mind

Tell us about your idea, expected budget, and timeline. We usually reply within one business day.

Please complete the captcha to submit the form.