Software for the systems
people rely on.
Protocore is a software company. We design, build and operate software for payment companies, public institutions and product teams — web and mobile apps, back-office platforms, payment integrations, and the design system underneath. We build and license the software; our clients run their services on it.
METROPOLITAN POLICE
LUXOFT
ENDAVA
ANIFThree services, one standard.
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
Payments
Gateways, PSP integrations, and cashless systems that clear at scale.
- Payment gateways
- PSP integration
- Cashless & NFC
- Settlement & ledgers
- PCI compliance
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
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.
Software we license to banks, payment companies and merchants — one core under all of it. Protocore Pay is a whitelabel banking app platform shaped into any brand: three example directions below, one platform underneath. Hosted checkout, card programmes, and the operator console are their own surfaces on the same ledger. Every screen here is the actual product UI, shown with demo data.
One banking core. Any app you can imagine on top.
A whitelabel banking platform — ledger, accounts, and cards in one core, with an app layer shaped to your brand.
6 products on one coreThe back office behind every front end
Customer 360s, ops queues, and every payment rail on one surface — every privileged action reason-required and audited.
One console, the whole operationCards, Apple Pay, and Google Pay — one payment page
A hosted checkout that puts every method on the same page, with one receipt and one reference per order.
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 five 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.
- ISSUECONTROL
Issuing puts a card in Apple Pay or Google Pay — virtual first, push-provisioned as a device token. Every authorization then checks balance and per-card controls on Pay's ledger, and freezes, limit changes, and reissues run through Center, reason-required and audited.
- DISPUTERESOLVE
When a cardholder disputes a charge, the Gateway order is the evidence file: authorization result, receipt, refunds, and webhook history against one reference. Center is where operators work it — queues with the clock visible, every action on the record.
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 · documents · automation[ 06 ]Manufacturing
IoT · monitoring · OEE[ 07 ]Energy & utilities
Sensors · metering · control[ 08 ]Healthcare
Devices · compliance · dataWe build the devices, too.
When off-the-shelf doesn't fit, we design the electronics, firmware, and cloud — through to OEM production.
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