Payrillium

Chat to it. It checks out.

One Android application. Six ways in. One of them takes an instruction in plain language.

Talk to sales

Write it once.

Standalone, POS, semi‑integrated, cloud, app‑to‑app and MCP all resolve to the same API. Move between them without touching the payment logic.

Deployment

Six ways in.

Six transports. One application. The choice is where the caller runs, not what to buy.

  • Standalone. The whole lifecycle on the terminal (sale, refund, void, capture, split) with staff profiles and reporting in the same place.

    On the terminal

  • POS Mode. A focused catalogue built into the terminal. No point of sale to buy, and no second box on the counter.

    On the terminal

  • Semi‑integrated. An existing point of sale drives the terminal across the local network, and the card data never reaches it.

    HTTPS POST on the LAN

  • Cloud. Transactions created, routed, watched and finished from a central platform, with no server on the site.

    HTTPS · no local server

  • App‑to‑app. Another application on the device calls Atom over localhost. Atom surfaces for the payment, then hands control back.

    HTTP on localhost

  • MCP server. A chat client starts, follows and finishes a card‑present sale on the terminal itself.

    Model Context ProtocolFirst to publish

Architecture

One API underneath.

Different above the line. Identical below it. Write the integration once, run it on any transport.

  • Standalone
  • POS
  • Semi‑integrated
  • Cloud
  • App‑to‑app
  • MCP
Session ManagerAll six modes land here.
One APIWrite the integration once, run it on any transport.

Different above the line. Identical below it.

  1. 01Session Manager

    The single entry point. All six modes land here, and an MCP request resolves to the same interface a POS on the local network uses.

  2. 02Ops Center

    Every transport is published as its own project, documented, with runnable requests and no proprietary SDK to adopt.

  3. 03Acquirer‑agnostic routing

    The processor sits behind the application rather than inside it, so changing one does not change the other.

Standalone

All of it, on the terminal.

01

Sale, refund, void, authorisation, capture, and split payments, end to end.

02

Role‑based profiles for clerks, servers, and administrators.

03

Logos, colour themes, receipt layouts, and on‑screen messaging, set per merchant.

POS Mode

A POS without the POS.

Items, prices and images, built on the terminal itself. Daily totals, item performance and payment activity, with no POS hardware behind it.

The POS Mode grid on an ATOM terminal, with categories across the top and priced items below
An item sheet on an ATOM terminal, choosing a size and an extra before adding to the bag

PayLove

Add a reason to come back.

A preset, an emoji, or a line typed at the counter. Printed with the payment. The last thing they are handed is an invitation, not a total.

The PayLove message picker on an ATOM terminal, with six preset messages to choose from
A custom PayLove message being typed at the counter: ten per cent off your next visit
The message picker again, with the new offer saved as the first preset

Configuration

Nothing is set on the terminal.

Every button and flow is set in Mirillium, not on the device. One terminal or the whole estate. Never at the counter.

See Mirillium
The Atom home screen, with the buttons a member of staff can reach

Multi‑merchant

One terminal. More than one merchant.

Each merchant keeps its own profile, and the device moves between them at the counter rather than going back for re‑provisioning.

Its own MID

Transactions settle to the merchant that took them.

Its own look

Logo, colours, receipt layout and on‑screen messaging, per merchant.

Its own reporting

Totals and activity stay separated by merchant, not by device.

Every payment revolution so far changed how the card reaches the terminal. The agentic revolution changes how everything else reaches it.

Meet your newest employee.

The first card‑present terminal that speaks MCP.

Just say

  • Charge $115 and email the receipt
  • How did we do yesterday?
  • Turn on 20% tipping everywhere
Talk to salesSee the protocol
A Payrillium terminal beside a counter display: the instruction on one screen, the approved sale on the other.

The standard

The protocol already won.

Model Context Protocol went from proposal to standard in under two years. A terminal that speaks it is reachable by tools that already exist. No SDK to adopt.

97M

Monthly MCP SDK downloads by March 2026.1

28%

Of the Fortune 500 with MCP already deployed.1

10,000+

Public MCP servers live by early 2026, with 41% of software organisations in production.2

75%

Of API gateway vendors expected to add MCP during 2026.3

These are the market’s numbers, not Payrillium’s. 1 - Digital Applied / Nevermined, MCP Adoption Statistics 2026. 2 - Stacklok, State of MCP in Financial Services 2026. 3 - CData vendor survey. Visa Intelligent Commerce and Mastercard Agent Pay are both published agent‑payment frameworks; neither covers the card‑present counter, which is the gap Atom is built for.

Inside Atom. A closer look.

Loyalty

PAYLOVE

The receipt, working harder.

Turns every payment into a reason to come back.

A Payrillium receipt carrying a PayLove offer
PayLove

Checkout

APPROVED

Even the confetti is a setting.

Switched on or off in Mirillium, like every other button on this screen. Never on the terminal.

When a card fails

HMM…

It doesn’t say DECLINED.

No red, no capitals, nothing for the queue behind them to read. Just a way forward.

Customization

BUILD YOUR ATOM

Your color. Your logo.

Every Atom arrives in your brand, Any screen color. Your logo, front and center.

See it on a counter.

Talk to sales