Skip to main content

Dev Station Technology

Banking

Banking software where a claim has a clock on it

Case handling, deadline tracking and the migration of sensitive records. We moved a national platform with zero downtime.

£85,000Maximum APP reimbursement per claim
35Business days to reach an outcome
13Months a customer has to claim
0Downtime in our platform migration
What this is

The deadline is in the rules, so it has to be in the system

Since 7 October 2024 payment firms on Faster Payments and CHAPS have had to reimburse authorised push payment fraud within set limits. That puts a clock on every claim and a record behind every decision.

Where we have proof

a national platform migration with zero downtime, penetration testing and static analysis during delivery

Where we have not yet

We have no published banking case. We say so on the first call and show the closest work.

Services

What we build for banks and payment firms

Claim and case management

Each claim with its deadline, its evidence and the decision recorded.

Deadline tracking

Business days counted from the right start, with the late ones at the top.

Data migration

Years of sensitive records moved by a team that does nothing else.

Security testing during delivery

Penetration testing and static analysis run alongside the build.

Integration with core banking

The case record joined to the account and the payment it concerns.

Reporting for the regulator

Counts, outcomes and times in one export.

Rules

What the APP reimbursement rules set out

These come from the Payment Systems Regulator, psr.org.uk.

In force from 7 October 2024Reimbursement requirements cover authorised push payments sent over Faster Payments and CHAPS. Source: Payment Systems Regulator.
Up to £85,000 per claimThe maximum level of reimbursement is £85,000. Source: same PSR pages.
Five business days, or 35 with more informationReimbursement is expected within 5 business days. Where more information is needed, the outcome is due within 35 business days. Source: same PSR pages.
13 months to claimA customer has 13 months to make a claim. Source: same PSR pages.
Case study

The nearest build we can show you

National education analytics platform rebuilt by Dev Station
Education technology, Norway

National education analytics platform

Different sector, same discipline. A Norwegian technology company needed its national education analytics platform modernised after a previous vendor missed the deadline. A dedicated team moved years of sensitive records, with penetration testing, static analysis and network assessment during delivery.

0Downtime during the migration
Technologies in the build above.NETAngularXamarin and .NET MAUIAWSPower BI
Who we build for

The teams who call us

Banks and building societies

Fraud and disputes teams with a case system near its limits.

Payment firms and e-money issuers

Where reimbursement rules arrive faster than the tooling.

Core banking vendors

Product teams who need a case module beside the core.

Banks mid-migration

Teams moving a platform without stopping the service.

Related reading: financial services software, fintech software, finance software and insurance software.

FAQs

What buyers ask first

Do you have a banking case?

Not yet published. We say so on the first call and show the closest work, which is a national platform migration delivered with zero downtime.

Do you give advice on the reimbursement rules?

No. That advice comes from your compliance team and the Payment Systems Regulator. We build the case tracking they specify.

Can you work with a legacy core?

Usually. The first step is documenting what exists so you own it again, then we integrate or replace in stages.

Who owns the code and the cloud accounts?

You do, from the first commit. Repositories and cloud accounts stay in your name.

Send us one case workflow

Thirty minutes with the engineers on how a claim moves, where the clock starts and who decides.

Let's Talk