Fintech

Software that moves money and can prove where it went

We build payment flows, ledgers, lending workflows and wallet apps for fintech teams, with reconciliation and audit trails designed in from the first commit, and voice agents that work from the same records.

Start a project
The sector

The hard part is not the feature

Fintech software carries a burden ordinary software does not. A double charge, a ledger entry that does not balance, a payout sent twice: each one is money in the wrong place, and a support case that has to be answered with evidence. The interesting engineering in this industry is rarely the feature. It is the accounting behind it.

Most fintech products are also assemblies of other people's systems. A card processor, a banking partner, an identity vendor, a credit bureau, a core ledger. They fail in different ways, retry at different times and disagree about what happened. A payments platform is largely the work of holding those disagreements together and resolving them into one truthful record.

Villaex holds PCI DSS compliance, so the handling of cardholder data is a practice we already run rather than something we learn on your project. We work the same way on the rest of the money path: double entry ledgers, idempotent calls to the rails, and an audit trail an examiner can follow without asking us questions.

What makes it hard

The constraints that shape fintech systems

Money moves before the record does

Payments settle on the rail's schedule, not yours. A charge can authorise, capture, reverse and dispute across days, and a repayment can fail on collection day and retry later, so the system must hold a transaction unresolved without losing it.

The books rarely agree first time

The processor statement, the bank file and your own ledger rarely agree on the first pass. Somebody has to find the missing cents, and if that somebody is a person with a spreadsheet, it does not scale.

KYC turns signups into a funnel

Identity checks fail for honest reasons: a blurred document photo, a name spelled differently on two records, an address that moved. Every extra step loses real customers, and skipping steps loses the banking partner.

Card data leaks into logs

A card number that reaches an application log, a support ticket or an analytics event has widened your PCI scope and your risk. Keeping it out takes tokenisation and discipline in every service that touches a payment.

What we build

Systems we ship for fintech teams

Payment flows and rail integrations

Card, bank transfer and wallet payments wired to processors and banking partners, with idempotency keys, retry handling and webhook processing that survives duplicate and out of order delivery from the provider.

Double entry ledgers and reconciliation

An immutable ledger where every movement has a matching pair, plus a nightly job that pulls the processor and bank files, matches them against internal records and files the breaks for an analyst to clear.

Onboarding and KYC workflows

Signup journeys that call identity, document and sanctions providers, then route the cases those providers cannot decide to a review queue where an analyst sees the evidence and the reason for the flag.

Lending, from application to arrears

An application flow that calls bureau and affordability data, a decision the underwriter can explain, disbursement to the borrower's account, and an amortisation schedule the ledger enforces, including what happens when an instalment fails: retry, arrears status, collections queue.

Voice agents on the money path

Agents that call on a failed payment, verify a flagged card transaction with the cardholder or chase the document that failed a KYC check, with no card number spoken or stored and every outcome written back to the account record.

Proof

Screens from systems in production

9:41
DL

Good morning

Dana Lynch

Available balance

$4,182.60

Ledger settled · 2 min ago

Vaultpay

•••• •••• •••• 4471

D. LYNCH09/29
Send
Request
Top up

Recent activity

All
BBBlue Bottle CoffeeCafés · card ••4471−$6.40Today 08:12
KLPayroll · Kestrel LtdDeposit · direct credit+$3,240.00Today 06:00
TATransit AuthorityTravel · card ••4471−$2.75Yest. 18:44
NRNadia RahimiSent · split dinner−$48.00Yest. 20:31
Wallet
Cards
Activity
Settings
FinTech App · Consumer Finance

A wallet app shipped in 12 weeks, secure to the core

A fintech startup needed a consumer wallet that handled real money correctly and felt effortless. We built it end to end: payments, a ledger with transaction integrity, KYC, and a polished mobile experience, all engineered to the security and correctness bar finance demands.

app.conveyor.dev/payments-api/runs/4821

payments-api

mainDeploying
RollbackPromote to prod
Pipeline run#48219c4e1f7DODara Okafor pushed to mainelapsed 8m 47sView logs
1m 42s

Build

image 212 MB

1m 58s

Unit tests

1,284 passed

2m 06s

Integration

3 services

41s

Security scan

0 critical

2m 14s

Canary 10%

64%
queued

Full rollout

after canary

Deploy historyAll environments
VersionCommitAuthorEnvStartedDurationResult
v2.41.49c4e1f7DODara O.production9m ago8m 47sDeploying
v2.41.49c4e1f7DODara O.staging2h ago5m 31sSucceeded
v2.41.35a7d2b0LSLuca S.production1d ago7m 48sSucceeded
v2.41.2c91e0adMHMei H.production4d ago9m 04sRolled back
v2.41.2c91e0adMHMei H.staging4d ago5m 12sSucceeded
v2.41.1e7b3f52LSLuca S.staging6d ago2m 58sFailed
6 of 212 deploysView all
Environments
production1d ago
v2.41.3canary v2.41.4
staging2h ago
v2.41.49c4e1f7
preview38m ago
pr-4183 open
Rollback

Rollback to v2.41.3

5a7d2b0 · last healthy

Confirm rollback
CI/CD Automation · Fintech Payments

Every release rolls through canary to production with one click back

Conveyor is the delivery console a payments platform team watches on every push. Each run moves through build, unit and integration tests, a security scan and a 10% canary before full rollout, with a deploy history per environment and a rollback to the last healthy version that takes one confirmation instead of a war room.

The services behind this work

FinTech PlatformsPayments, lending, wallets, and financial products engineered to the standard finance requires: secure, compliant, reliable, and auditable from the first commit, because in fintech the margin for error is zero.
Custom SoftwareOff-the-shelf tools force your processes into someone else's mold.
AI Voice AgentsWe build real-time conversational voice AI that answers, qualifies, books, and resolves, across inbound and outbound calls, in multiple languages, with the sub-second responsiveness that keeps a conversation feeling natural.
Outbound Voice AgentsReminders, follow-ups, surveys, and qualification campaigns run by AI agents: consistent, on-brand, and tireless, with the pacing and compliance controls outbound calling demands.
Enterprise IntegrationsYour business runs on a dozen systems that don't talk to each other.
Cloud & DevOpsWe design cloud architecture and DevOps practices that make deployment effortless and reliability boring: CI/CD, infrastructure as code, observability, and the operational discipline that keeps production healthy as you grow.
What we engineer around

PCI DSS rules on cardholder data, which decide what a system may store and how wide the assessed scope becomes. KYC, AML and sanctions screening, and the audit record a banking partner asks to see. Data residency rules that decide where account and transaction records are allowed to live. Strong customer authentication and consent requirements that change the shape of a checkout flow.

FAQ

Questions we get before we start

Still unresolved? A 30-minute conversation with an engineer usually settles it faster than another page of copy.

Yes, and we start by reading the ledger and the reconciliation process, because that is where the truth about a payments system lives. Changes go out behind feature flags and a canary stage, we do not touch a money path without a rollback plan, and the money paths are the parts we test and document hardest, since you own the code and your engineers inherit it.

It means the practices are already in place on our side: how we handle cardholder data, how access is granted and logged, and how environments are separated. On your product we design to keep card data out of your systems where a processor can hold it, so your own assessed scope stays as narrow as possible.

Both, depending on the product. A ledger service can be the right answer when the money model is standard. When the product has its own accounting, fee splits, multi currency holdings or lending schedules, we build a double entry ledger against your rules and test it against real statement files before it goes near a customer.

Named engineers on our team, working from our office in Albany, New York. Production access is granted for a task and a window, logged, and removed after. Development and test environments carry synthetic data, never cardholder data or live customer records. Releases go through a pipeline with a rollback one engineer can run with a confirmation. We answer banking partner questionnaires, and PCI DSS compliance means those controls were assessed rather than described.

Building something for fintech?

A 30 minute conversation with an engineer is usually enough to scope it honestly.

Start a project