Twelve fintech products,
one banking core.
Protocore is the product studio behind them — one banking core, twelve products, one design system. A whitelabel neo-bank, hosted checkout, card issuing, fiat ramps, and custody. Accept cards, wallets, and USDC — online and at the counter.
METROPOLITAN POLICE
LUXOFT
ENDAVA
ANIFSix services, one standard.
Artificial Intelligence
LLM applications, retrieval, and ML pipelines that ship to production — not demos.
- LLM & agent apps
- RAG & search
- ML pipelines
- Computer vision
- MLOps & evals
Blockchain
Smart contracts, wallets, and tokenization — audited, gas-aware, and built to last.
- Smart contracts
- Wallets & custody
- Tokenization
- Cross-chain
- Audits & security
Payments
Gateways, PSP integrations, and cashless systems that clear at scale.
- Payment gateways
- PSP integration
- Cashless & NFC
- Settlement & ledgers
- PCI compliance
Software engineering
Web platforms, mobile apps, and the back office behind them — built to be operated, not just launched.
- Web applications
- Mobile apps
- APIs & integrations
- Cloud & DevOps
- Legacy modernisation
Digital public services
Citizen portals, electronic registries, and signed records a public institution can answer for.
- Citizen portals
- Registry & case management
- Qualified e-signatures
- Electronic archive
- Fee reconciliation
Hardware & IoT
Custom electronics, firmware, and the cloud behind them — the devices our software runs on.
- Access control
- NFC & credentials
- Kiosks & terminals
- IoT & sensors
- PCB & firmware
From problem to operated system.
- [ 01 ]
Discover
We map the problem, constraints, and the smallest valuable slice to ship first.
- [ 02 ]
Design
Architecture, interfaces, and a build plan your team can ship and operate.
- [ 03 ]
Build
Production code in tight increments, instrumented and tested from day one.
- [ 04 ]
Operate
We ship, monitor, and harden — then hand over, or run it with you.
Built as products.
One core runs all of it. Protocore Pay is a whitelabel neo-bank you shape into any app — five example directions below, one platform underneath. The other products — hosted checkout, card issuing, fiat ramps, self-custody wallets, agent payments — are their own surfaces on the same ledger, all run from one operator console. Every screen here is the actual product UI, shown with demo data.
One banking core. Any app you can imagine on top.
A whitelabel neo-bank platform — ledger, accounts, cards, and crypto in one core, with an app layer shaped to your brand.
12 products on one coreThe back office behind every front end
Customer 360s, ops queues, and both money rails on one surface — every privileged action reason-required and audited.
One console, the whole operationCards, wallets, and USDC — one payment page
A hosted checkout that puts every method on the same page, with one receipt and crypto settled to EUR.
Every method, one receiptOne payment, end to end.
Each product is the software for one stage of a payment, handing off to the next over one core ledger. Three of the eight flows:
- ACCEPTSETTLE
Gateway authorizes and captures the payment; settlement pays out in EUR against one order reference. Bank-transfer orders carry vIBAN references so incoming SEPA credits identify their orders by construction — and whatever doesn't match lands in Center's reconciliation queue as a counted exception.
- FIATCRYPTO
Ramp and ATM are the doors between euros and crypto — card or Apple Pay in, cash in hand at a kiosk, and both ways back out. Chain carries the on-chain leg; Wallets holds the result inside whatever app the user is already in.
- POLICYPAY
Agents lets software spend under written policy — budgets, merchant allowlists, human approval above a threshold. Approved payments settle as ordinary SEPA transfers on Pay's core, and every decision lands in the same hash-chained audit trail Center reads.
Digital services for public institutions.
A public institution needs software it can answer for: every request registered, every statutory deadline tracked, every act signed by the official the law names, and every record kept for as long as it must be. We build that software — and when citizens pay local taxes and fees, the money settles to the institution's own treasury accounts, never through us.
- [ 01 ]Citizen portals — national e-ID sign-in, guided forms, request tracking
- [ 02 ]Electronic registry — numbering, routing, and a deadline on every case
- [ 03 ]Qualified e-signatures and seals — officials sign with their own certificates
- [ 04 ]Electronic archive — PDF/A, qualified timestamps, retention schedules
- [ 05 ]Local taxes and fees — reconciled against treasury statements
- [ 06 ]Migration from legacy systems — imported, reconciled, signed off
Where our systems run.
Fintech & banking
Payments · ledgers · KYC[ 02 ]Public sector
Portals · registries · e-signatures[ 03 ]Events & venues
Ticketing · cashless · access[ 04 ]Retail & hospitality
POS · loyalty · kiosks[ 05 ]Transport & logistics
Tracking · automation · AI[ 06 ]Manufacturing
IoT · monitoring · OEE[ 07 ]Energy & utilities
Sensors · metering · control[ 08 ]Healthcare
Devices · compliance · data[ 09 ]Gaming & esports
Wallets · payments · anti-fraudWe build the devices, too.
A closer look at the devices: gates and validators, wristbands, kiosks, and sensors — with the firmware, cloud, and prototyping behind them, from first board to OEM volume.
Ticketing & Access Control
Turnstiles, gates, QR/NFC validators.
Wristbands & Credentials
NFC wristbands, RFID cards, cashless.
Self-Service Kiosks
Ordering terminals, check-in, payment.
IoT & Sensors
Environmental sensors, gateways, monitoring.
Custom Electronics
PCB design, embedded, firmware.
Software & Cloud
Dashboards, APIs, mobile apps.
Consulting & Prototyping
Discovery, prototypes, OEM production.
And the everyday work that ships alongside.
- Websites
- Web applications
- Mobile apps
- UX/UI design
- Branding
- E-commerce
Everything renders on PDS.
Protocore Design System 4.0 is the foundation under every screen above — and under this site. Dark-first, token-driven, radius zero: 207 design tokens across three planes and 1,010 utility classes shared by the web products, with the same tokens shipped for web, .NET, and native through @protocore/pds-css.
- [ 01 ]One doctrine across the whole family — hairlines, mono labels, one green accent
- [ 02 ]Tokens for web, .NET, and native from a single source
- [ 03 ]Proprietary and licensed per team, served from our private registry
We treat infrastructure as a product — instrumented, documented, and built to be operated. Not handed over and forgotten.
From the workshop.
Have a system to build?
Tell us the problem. We'll come back with an architecture and a plan.
Contact us