Payments

Every charge is one connected record from charge to invoice to settlement

Quivi payments live inside the POS — Quivi and Paybyrd share the same infrastructure, so there's no card machine bolted on the side. One charge produces one persisted Transaction, one compliant fiscal document, and a settlement record you can trace back to it. It reconciles because it was never separate.

Transaction $55.60
  1. Charged · Card (Paybyrd) 19:42
  2. Invoice FT 2026/418 issued
  3. Settles · payout batch Tue
One record, reconciled to Cash Management

The reseller's terminal

A card machine sold next to your POS will never reconcile with it

Charges land in one system, invoices in another, payouts in a third — and month-end becomes a spreadsheet forcing three exports to agree.

POS Terminal Bank

Three exports, forced to agree at month-end.

Two systems, one sale

The terminal takes the money while the POS records the order — nothing ties the charge to the ticket.

Invoices bolted on later

Fiscal documents get generated in a separate tool, so a refund or a tip breaks the paper trail.

Payouts you can't trace

A lump settlement lands in the bank with no line back to the method or the transaction that earned it.

Every tender

Every way they pay, on one payment layer

Card, mobile wallet, cash, or a method you define yourself — staff take it at the POS and guests get the same breadth in the QR app.

Paybyrd card terminal (TPA)

Native tap-and-chip at the counter or tableside — the terminal is part of Quivi, not a separate device to reconcile.

Card hosted page

Paybyrd or Revolut hosted checkout for online, kiosk, and QR — the guest pays by card without staff handling it.

Apple Pay

The mobile wallet your guests already carry, built in for staff and guests alike.

Revolut Pay

One-tap checkout for guests who already pay with Revolut — no card entry, at the POS or in the QR app.

Cash

Recorded as a tender like any other, so it reconciles in Cash Management instead of falling off the ledger.

Custom Charge Methods

Define your own — think house account or voucher — and it flows through the same Transaction, invoice, and settlement path.

The life of a payment

Four steps, one record, nothing to re-key

From the charge at the table to the line on your payout, a single payment carries its own history. No export, no matching, no second system.

  1. 01 Choose

    Pick the tender

    Staff or guest select a method — terminal, hosted card, Apple Pay, Revolut Pay, cash, or a custom method — against the open Session, and choose how to split.

  2. 02 Charge

    Persist the Transaction

    Every charge is stored as a Transaction tied to the order. Split it, tip on it, or refund it later — each refund references its original.

  3. 03 Invoice

    Issue the fiscal document

    The transaction produces an itemized, sales-tax-ready receipt via Quivi-native invoicing, with the guest's EIN if they gave one — and can print over ESC/POS.

  4. 04 Settle

    Land the payout

    The platform aggregates settlement records per charge method and itemises them on the Payouts screen, so every euro traces back to a method and a charge.

Split the bill

Five ways to split, no math at the table

Pay the whole bill, split it evenly, pick your own items, name an amount, or leave a tip — every path settles against the same Session.

Pick how the table pays

Bill · Table 12 $55.60
The whole bill, one tap.

Pay

$55.60

Pay $55.60

Fiscal-native

Sales-tax-ready receipts and invoices, out of the box

Quivi is live in both markets, so every transaction issues the right fiscal document for the right country — no add-on, no accountant's export.

🇵🇹 NIF 🇩🇰 CVR

Auto-issued

Each transaction produces an itemized, sales-tax-ready receipt via Quivi-native invoicing as the transaction is recorded.

EIN

Tax IDs — like a customer's EIN — captured on the document where they belong.

Your rules

Set your invoice prefix, choose whether tips are included, and print the document over ESC/POS right after payment.

The back office

Every transaction, refundable, filterable, traceable

The finance work you do after close — refunds, reconciliation, payouts — lives in the same system that took the money.

Refunds with a trail

Refund fully or partially; each refund references its original transaction, so nothing goes untied.

Filterable transactions

Filter the list by date, method, has-refunds, has-discounts, over-paid, or Quivi-only to find exactly the charge you need.

Settlements per method

Settlement records aggregate per charge method, with itemised payout detail on the Payouts screen.

Customer & tax-ID capture

Before paying, a guest can add a tax ID (EIN), name, and email so the invoice is right the first time.

Prepaid or post-paid

Take pay-before-order checkout for Kiosk and Online, or settle the Session at the end — both flow the same way.

Custom methods

Merchant-defined Custom Charge Methods sit alongside cards and cash and reconcile through the same spine.

Paybyrd-native — a reseller of a terminal cannot match this

Because Quivi and Paybyrd share infrastructure, the charge, the fiscal document, and the settlement record are one connected chain, not three integrations. A generic terminal takes the money and leaves you to reconcile the rest.

One payment layer, in the POS

The reconciliation spine

The numbers line up because they never split apart

Cash tenders reconcile in Cash Management while sales break down by charge method in Insights — and because every payment is one persisted record, per-method totals line up end to end. Nothing to match, because nothing was ever separated.

See one payment travel the whole way

Watch a charge become a fiscal invoice and a traceable line on your payout — reconciled against cash, reported by method, in the same POS your staff already use.