One build. Every device.

One certified application across twelve device families, with the certification carried all the way through the acquirer and the scheme.

Start a project See how we work

Certify once.

A hardware abstraction layer sits between the application and the terminal, so one certified build runs across device families. A new terminal becomes a configuration rather than another certification.

Hardware

Change the maker. Keep the build.

A manufacturer change is a commercial decision, not an engineering programme.

One applicationWritten once, against one interface.

Hardware abstraction layerCard reader, printer, PIN entry, keys and peripherals: the same calls on every device below.

Verifone
Ingenico
PAX
Sunmi
iMin
Datecs
Dspread
Any Android

A new manufacturer is a configuration in the layer. The certified build above it does not change.

Software

Written to be certified.

The device is locked down, and the examiner is outside the building.

Terminal applications
Payment applications for attended, unattended, and mobile terminals, written against the manufacturer’s own SDK.
EMV Level 3
Transaction analysis, test case preparation, and certification carried through the acquirer and the scheme.
Semi‑integration
An existing point of sale drives the terminal, and the card data never enters it.
Unattended
Kiosks and vending, with MDB and Executive support and a defined answer for a link that drops mid‑sale.
Edge and offline
Local processing with a queue that reconciles when the connection comes back.
Intelligence
Forecasting and analytics computed on the counter’s own data, where that data is generated.

Certification

Inside a certification.

Five steps to a letter of approval.

certification · scope

Acquirer       North American processor
Region         US · Canada
Device         Attended, PIN on glass
Kernels        Visa · Mastercard · Amex · Discover
Entry modes    Contact · Contactless · Mag stripe

Four answers before anything is built. Get one wrong and the test scripts that arrive are the wrong test scripts.

We take all five.

Or the parts you choose to hand over.

Talk to engineering

Identifiers, test cases and tag values are illustrative.

Design

The last second of a transaction.

Instant, impossible to misread, and identical every single time. Designed, built and certified here.

Amount, card and authorisation shown are test values.

Deliverables

Certified in your name.

The approved application, the letter that approves it, and the evidence behind both.

The approved application
Running on every device family that was in scope, from one build.
The letter of approval
Issued against that application on that hardware, by the acquirer and the scheme.
The evidence behind it
Every test case and every log, in the package that was submitted.
The configuration
What was set and why, so the next device family is a change of parameters, not another programme.

Industries

Eleven rooms. One certification.

The certification does not change. The room it runs in does.

Delivery

Seven stages. One team.

Scoped, certified and maintained by the same engineers, with over 30 years in payments behind them. Nothing is handed to a group that was not in the room.

01Discovery
What is already running, what it runs on, and which parts cannot be touched.
02Consultation
What has to be built, and what does not, settled before anyone prices it.
03Design
Screens, flows and failure states, signed off before code depends on them.
04Development
Terminal, gateway and back office built together, so integration is not the last step.
05Quality
The acquirer’s own test scripts, run on the real hardware until they pass clean.
06Deployment
Certification filed, then a pilot estate before the fleet.
07Maintenance
Updates, and re‑certification each time the specification moves under you.

30 to 50% under in‑house.

Measured against building the same capability in‑house. The difference is not in the code. It is in the certification, where a first attempt costs the most and takes the longest.

Three ways to start. The work decides the contract.

Embedded

Dedicated team

Engineers assigned to the estate, for as long as the roadmap runs.

Engineers inside your team
Roadmap work, not tickets
Re‑certification as specifications move

Billed

Monthly

Rolling term. Scales by headcount.

Talk to engineering

Defined

Project

One scope, carried from specification through to certification.

Specification through to approval
Scope agreed before it starts
Paid by milestone

Billed

Fixed

Priced per scope. Paid by milestone.

Talk to engineering

On demand

Advisory

Certification and architecture judgement, without a build attached.

Architecture and certification review
Test failures read with you
No build attached

Billed

Hourly

No term. Scales by the call.

Talk to engineering

Start here

The platform is already built.

Atom, Proton, Mirillium and the Ops Center. A project can begin from working software.

See the platform

A Payrillium terminal held up to camera, greeting in eight languages.

Bring us the certification.

Talk to engineering Get pricing ›