Contact us
/// PoS · In-person Payments

The counter is where crypto gets practical

A terminal that treats a USDC scan exactly like a card tap: same charge, same receipt, same nightly settlement to the merchant's IBAN.

Contact usAll products
3
Ways to pay — tap · insert · scan
USDC-QR
On the terminal
Nightly
Settles to IBAN
Live
Card vs crypto split
/// 01

Every way a customer pays

Tap and insert work the way merchants expect. The addition is scan: the terminal renders a USDC QR for the exact charge, the customer pays from any wallet, and the sale closes on the spot — no separate device, no manual address copying.

/// 02

The merchant sees one business

The companion app shows takings as one stream with a card-versus-crypto split, live. At night, everything — card and crypto alike — settles to the merchant's IBAN, so the accountant never learns which customers scanned.

  • [ 01 ]One daily total, split by method
  • [ 02 ]Per-order drill-down with receipts
  • [ 03 ]Nightly settlement to IBAN, one line to reconcile
/// Integration

Counter to IBAN, five steps.

  1. [ 01 ]

    PRESENT

    Tap, insert, or USDC QR at the terminal.

  2. [ 02 ]

    AUTHORIZE

    Approved on the spot; offline payments queue as deferred authorizations.

  3. [ 03 ]

    CLOSE

    The day's payments close into a named batch.

  4. [ 04 ]

    SETTLE

    The batch settles overnight to the merchant's IBAN as one line.

  5. [ 05 ]

    TRACE

    Any payout question starts from the batch ID, not a search.

/// Features
Ref 9F21-0716 on the terminal — tap, insert, or scan.
/// 01

A terminal that acts like a terminal

The charge screen shows what every merchant expects: the total, €49.00, and the contactless zone. Tap and insert work exactly as they do everywhere else. The only new word on the screen is scan — and the reference, 9F21-0716, is the same order format the rest of the platform uses.

The exact charge as a USDC QR on Base — waiting for payment.
/// 02

USDC at the counter

Choose scan and the terminal renders a QR for the exact charge: the €49.00 order priced in USDC on Base at the rate on screen. The customer pays from any wallet while the terminal waits, then the sale closes on the spot. No separate device, no address copying, no mental arithmetic at the till.

  • [ 01 ]The QR encodes the precise USDC amount for the charge
  • [ 02 ]Rate stated on screen while the customer decides
  • [ 03 ]The terminal waits, confirms, and closes the sale itself
€1,284.50 across 32 payments — split by method, settling at 23:00.
/// 03

The merchant app

The companion app is the day at a glance: €1,284.50 across 32 payments, last one at 14:02. A single bar splits it — card 68%, crypto 22%, cash 10% — and the settlement banner says where it all lands: tonight at 23:00, RO49 •••• 0421. New charge and refund sit at the bottom, one tap away.

  • [ 01 ]Live method split as payments land
  • [ 02 ]Recent payments with per-order status
  • [ 03 ]Settlement time and destination stated plainly
Seven terminals, one screen — the offline one found before the shift notices.
/// 04

The fleet on one screen

Seven terminals under one merchant, read at a glance: 5 online, 1 offline, 1 deactivated, with €4,182.30 taken today across 104 payments and the next batch at 23:00. Each row carries location, status, today's takings, and last-seen; selecting the offline studio-bar terminal shows its device ID, firmware, network, and battery — with ping, reassign, and deactivate one click away.

  • [ 01 ]Online, offline, and deactivated visible per terminal
  • [ 02 ]Takings and payment counts per device, live
  • [ 03 ]Ping, reassign location, deactivate from the detail panel
One €49.00 sale — items, entry, auth code, batch, and refund on one screen.
/// 05

Every sale, fully told

A payment opens into its whole story: €49.00 approved at 14:02 on T-01, the three line items, the €0.50 processing fee, card ••4417 by contactless with auth code 00A712, the customer's name, and the settlement batch it will ride tonight. Refund and send receipt sit at the bottom of the same screen.

Tips, receipts, language, firmware — the counter configures itself.
/// 06

Tips and receipts, set at the counter

The terminal's own settings cover what a counter actually argues about: tip prompts on or off with 5%, 10%, 15%, or a custom value — tips post as tip adjustments before the batch closes — and printed customer receipts, a merchant copy, and a QR receipt each behind their own toggle. Below that, the device states its identity — terminal, device ID, firmware, network.

  • [ 01 ]Tip presets or a custom prompt, per terminal
  • [ 02 ]Paper, QR, or no receipt — the merchant chooses
  • [ 03 ]Language, firmware, and network visible on-device
One fee schedule — what it says is what the app shows, changes audited.
/// 07

Fees the merchant can read

The fees behind the fleet live in one audited schedule: free card issuing and inbound SEPA, €0.50 plus 1.5% on ATM withdrawals, a 0.5% FX markup, €15.00 SWIFT outbound, a 0.75% crypto buy-sell spread. What the schedule says is what the app discloses — and every change to it is diffed, reasoned, and audited.

/// And more

Nightly settlement to IBAN

At 23:00 the day's takings — card and crypto alike — settle to the merchant's IBAN as one line. RO49 •••• 0421 in the demo. The accountant reconciles one number and never learns which customers scanned.

Settlement batches as records

Every settlement is a batch with a name: tonight's sales ride B-0717-A, and each terminal shows its last batch and amount — B-0715-A at €312.40 on the studio-bar unit. A question about a payout starts from a batch ID, not a guess.

Card versus crypto, live

The split updates as payments land, so the day reads as one business with a method breakdown — not two revenue streams in two systems. When the crypto share moves, the merchant sees it the same afternoon, not in a month-end export.

The same order model as Gateway

The reference on the terminal is the same order format the hosted checkout uses, and the receipts match. A business running Gateway online and PoS at the counter runs one system with two surfaces, not two products.

Charges and refunds from the phone

New charge and refund live in the companion app, and the refund button sits on the sale itself. A refund points at the order — the same rule Gateway follows — so the merchant never has to remember how the customer paid before making it right.

Built to clear offline

Real venues lose connectivity at the worst moment. The terminals keep accepting offline — payments queue as deferred authorizations and submit with the next batch, deduplicated so reconnection never double-charges or loses a tap. A dead router is an inconvenience, not a closed till.

Terminal provisioning

A new terminal is registered from the fleet view, assigned a location, and retired the same way — the demo keeps a deactivated spare on the shelf. Devices carry their own IDs, so swapping hardware never confuses the books.

Remote diagnostics

Every terminal reports firmware, network, battery, and last-seen — and the fleet view can ping a device on demand. The studio-bar unit that went quiet on Jul 15 is diagnosed from a desk, not a drive across town.

Locations and pop-ups

Terminals carry locations — a front counter, a back office, a stand at Piața Amzei, two event kits marked on location. Reassigning a device to a weekend market is one action, and its takings still roll up to the same merchant.

Receipts three ways

Printed at the terminal, offered as a QR the customer scans, or sent from the app after the fact. The merchant copy has its own toggle, so the drawer does not fill with paper nobody asked for.

Cash in the picture

The split bar has a third segment: cash, 10% of the demo day. Cash sales are recorded alongside card and crypto, so today's €1,284.50 is actually today — not today minus the drawer.

Takings analytics

The fleet view keeps score beyond the total: 104 payments, an average ticket of €40.21 against €38.12 last week, takings per terminal. The merchant sees which counter earns before the month closes.

Staff accounts

The people behind the counter get their own accounts under the merchant, managed from the staff section. Who took a payment is a fact on the record, not a memory.

Customers on the sale

When the payer is known, the sale says so — A. Ionescu on the demo receipt. Payments connect to customers, so a regular's history is a lookup instead of a stack of anonymous tickets.

Search the fleet

Terminals are searchable by name or device ID, and payments by reference. When a customer calls about a charge, the answer starts with a search box, not a spreadsheet.

Exports

The fleet view and payment lists export to CSV as displayed. End-of-month is a download; the accountant never asks for screenshots.

Localization

The terminal speaks the counter's language — the language picker sits in the on-device settings. One fleet can serve venues that do not share a tongue.

An API for the counter

The developers section covers the counter too: payments and batches are queryable by API, so PoS data flows into whatever back office the merchant already runs.

Whitelabel terminals

The demo terminals run powered-by-Protocore; yours can run fully as your own brand. The fleet, the app, and the receipts all follow — same hardware posture, your name on the screen.

/// In the product
A €49.00 charge — tap or insert, like any terminal.
Or scan — the terminal renders a USDC QR for the same order.
The companion app — today's takings, card versus crypto.
The fleet — 5 of 7 online, €4,182.30 today, one offline terminal singled out.
One sale, fully told — items, method, batch, and a refund one tap away.
Terminal settings — tips, receipts, and device details, set at the counter.
The fee schedule — fees defined once, disclosed in-app, every change audited.
/// FAQ

At the counter, answered.

  • Card payments taken offline queue as deferred authorizations and clear when the terminal reconnects — they still close into the day's batch. The fleet console flags a terminal that has dropped off, so you see it before a shift does.

  • The terminal renders a QR for the exact charge; the customer pays from any wallet, and the sale closes on the spot — no separate device, no copying an address by hand. It is treated exactly like a card tap: same order, same receipt.

  • The day's takings — card and crypto alike — close into a named batch and settle overnight to your IBAN as a single line. Any payout question starts from the batch ID, not a search through transactions.

  • No. USDC is settled to EUR, so the companion app shows one stream with a card-versus-crypto split, and your accountant reconciles euros. They never learn which customers scanned.

  • To your own named IBAN — RO49 ···· 0421 in the demo. The terminal fleet is yours to run under the Protocore brand or your own, and settlement lands where your books already are.

  • Same order and receipt model, different setting. Gateway is the hosted page for online checkout; PoS is the terminal at the counter. Counter and checkout reconcile as one business — same references, same receipts.

/// Pricing

How the terminal fleet is engaged.

[ 01 ]

Per-terminal license

Priced by the fleet in the field — the terminals you deploy — with each day's card and crypto takings settling to one IBAN line.

[ 02 ]

Transaction-based

Cost on the takings the fleet processes rather than a per-device fee, so a terminal that sits idle costs nothing to run.

[ 03 ]

Whitelabel fleet

Deploy under your own brand and we operate the fleet for you — scope follows the terminals in service and the rails they accept.

What drives cost is the fleet — how many terminals are in the field — and the takings they process. Run under the Protocore brand or fully whitelabeled as your own.

/// Evaluate

Get a terminal on your counter.

[ 01 ]

Demo terminal

A terminal to try tap, insert, and USDC-by-QR on your own counter, with a test merchant account behind it.

[ 02 ]

Fleet console access

A login to the companion app and fleet console, seeded so you can watch takings split card-versus-crypto and settle a batch.

[ 03 ]

Pilot program

A scoped pilot across a handful of locations before a wider rollout — we help set up the machines and the settlement account.

[ 04 ]

Standalone or whitelabel

Evaluate under the Protocore brand or as your own terminal fleet — the same order and receipt model as Gateway underneath.

Request a pilot
/// Further reading
Availability

Deploy under the Protocore brand or fully whitelabeled as your own terminal fleet.

In the ecosystem

PoS references use Gateway's order format, USDC scans settle over Chain, and the nightly payout lands on the merchant's IBAN — one business across counter and checkout.

Pick a product. Or take the core.

Everything above runs in production demos we can walk you through — standalone, whitelabel, or as one platform. Tell us what you're building and we'll show you the shortest path to it.

Contact us