Fintech

The parts of a fintech that partner banks and regulators check

We build ledgers and reconciliation, KYC/KYB onboarding, digital-asset custody and banking-as-a-service integrations, and the evidence that they work. We are the team behind a banking orchestration platform that ties Sumsub, Fireblocks, a ledger and BaaS partners together, in production for a European payment platform.

Built onSumsub, Fireblocks, BaaS
Rules we build forFCA, DORA, US partner banks
First stepfrom €4,900

Why now

Deadlines that are creating the work

Each of these rules is written for compliance teams, but most of the work lands on engineering: the ledger, the reconciliation, the records and the contracts with suppliers.

UK · since 7 May 2026

FCA safeguarding rules

Payment and e-money firms must reconcile safeguarded funds every day, file a monthly safeguarding return and have the arrangements audited every year. That only works if the ledger can say, for any day, whose money is where.

Ledger and reconciliation →
US · since 2022

Sponsor-bank enforcement

US regulators have put several sponsor banks under enforcement orders since 2022. The banks pass the fixes down to their fintech partners: tighter onboarding and monitoring, proof that the fintech's ledger matches the bank's, and closer checks on the fintech's own suppliers.

Banking-as-a-service integration →
EU · since 17 Jan 2025

DORA Article 30

EU financial entities must put specific terms into their contracts with technology suppliers: where services run and data is kept, help during incidents, audit and inspection rights, and an exit plan. If you are regulated in the EU, your developers are such a supplier.

Our supplier terms →
Cards · since 31 Mar 2025

PCI DSS 4.0.1

Where you take card payments, every script on the payment page must be authorised and listed, and changes to the page must be detected (requirements 6.4.3 and 11.6.1). We check these in a Readiness Review and build to your own card controls; we don't certify.

Readiness Review →

What we build

Fintech systems we build and integrate

Fintech

Ledger & reconciliation

Double-entry ledgers and daily reconciliation against every bank and provider, built for FCA safeguarding rules and sponsor-bank reviews.

Fintech

KYC & KYB onboarding

Sumsub KYC, KYB and AML screening built into your customer lifecycle, so accounts open and stay open only in states your compliance team approved.

Fintech

Digital-asset custody

Fireblocks digital-asset custody wired into your platform: transfers started under your rules, callbacks matched to requests, balances reconciled to the ledger.

Fintech

Banking-as-a-service

Accounts, IBANs and payments from banking-as-a-service partners, orchestrated across providers and reconciled, with the evidence a partner bank asks for.

Fintech

Readiness Review

Technical due diligence before your partner bank, buyer or investor runs theirs: a fixed-price, 7-day review with every fix priced. Credited to the build.

Case study · client under NDA

Banking orchestration for a European payment platform

Read the case

Why a small team abroad is a safe choice

What goes wrong with agencies, and what our contract says instead

All contract and security terms
The seniors pitch, juniors build

The people you meet are the people who build

Your proposal names the engineers who will do the work, and you meet them before you sign. A key-person clause means nobody is swapped without your written consent.

The agency keeps the code

Your repository and accounts from the first commit

Code, cloud, app-store and domain accounts are in your name, and we work inside them from day one. The contract assigns the IP to you in the present tense ("hereby assigns"), so there is no later transfer to wait for. Portuguese law (Decree-Law 252/94) also treats commissioned software as the client's by default. lawyer to confirm DL 252/94

The agency disappears

Nothing depends on us staying

You pay per milestone, for work you have seen running. Everything lives in your accounts, and every milestone ends with a written handover: architecture notes and runbooks your next engineer can follow without us.

Code nobody can maintain

Reviewed work, under a 90-day warranty

A second engineer reviews every change before it merges, and code written with AI tools is read line by line (our AI-use policy). Paths that touch money and data have automated tests. A written 90-day warranty covers defects in our work.

Supplier terms

Ready for your bank's vendor questionnaire

Your partner bank, your auditor or your own compliance team will check the contract with us, not only the code. We sign a supplier annex written against the FCA's outsourcing rules (SYSC 8), DORA Article 30 and the US interagency guidance on third-party risk.

It gives you and your regulator audit and information rights, lets us use subcontractors only with your written consent, states where work is done and data is kept, commits us to help during incidents and sets out how we hand everything over if you leave.

Supplier terms for regulated clients

Questions

Fintech questions

Are you regulated yourselves?

No. We are a software supplier to regulated firms: we don't hold customer money or offer financial services. We accept the terms a regulated client has to put in a supplier contract, including audit rights, subcontracting only with consent, incident help and exit support. A compliance specialist works with the team on every project, but we don't give legal advice and we don't act as your auditor; your compliance team and your lawyers keep those decisions.

Will our partner bank accept a small vendor?

Banks look at what a vendor can control and what happens if it goes away. We answer their questionnaire in writing and show the terms behind each answer: named engineers with a key-person clause, code and cloud accounts in your name from the first commit, a second engineer reviewing every change, and the supplier annex above. We don't hold ISO 27001 or SOC 2 certification; we say so up front and work inside your environment under your controls. Where your bank requires background checks for people with production access, we agree them in the contract. insurance cover we hold

Who owns the code and the IP?

You do, from the first commit. We work in your repository and your accounts, and the contract assigns the IP to you in the present tense, not at some later date.

Who will actually work on our project?

The engineers named in the proposal, and you meet them before you sign. A key-person clause means nobody is swapped without your written consent.

How do time zones work for a UK or US team?

We work on Lisbon time, which is the same clock as London: Mon–Fri, 08:00–18:00 UK time. That leaves about four working hours a day in common with the US East Coast. You get a demo of working software every week and a short written update every working day.

What contracts do you sign?

A master services agreement with a statement of work for each project, or your own paper if you prefer. A mutual NDA before we see anything, and a GDPR data processing agreement. US clients get a W-8BEN-E from us. Which law governs the contract is answered on Contracts & security.

How do we pay?

The fixed-price first step is paid upfront. Builds are billed by milestone, after you have seen the work running. Monthly care, if you want it, is billed at the start of each month. We invoice in euros, pounds or dollars.

Free 30-minute call

Tell us what has to work, and by when

You talk to an engineer who would work on it, not a salesperson. You leave the call knowing what it would take and what the first step costs, or we tell you that you don't need us.

Or write to us
info@jobsdone.pro
Lisbon time: the same clock as London, 4–5 hours ahead of New York

We answer within one working day. We sign an NDA before seeing any code.

Thank you, it's with us

An engineer will reply within one working day with a few times for the call. If it's urgent, email info@jobsdone.pro.