Cibuscibus.
Payment architecture & governance

How payment, adjustment, receipt and close records connect.

See the control layer behind Cibus payments: minor-unit calculations, order-linked allocations, role-aware adjustments, receipt records and end-of-day reconciliation across configured methods.

Discuss paymentsPayments & Receipts product
Payment drawer
Table T12 · 4 guests · Bill ready to pay
Illustrative
Subtotal£144.00
Service (12.5%)£18.00
Tip£10.00
Total£172.00
Visa
Card ****4242
Stripe Terminal · authorised
£86.00
Mast
Card ****1881
Stripe Terminal · authorised
£86.00
EOD reconciliation
Reconciliation · balanced sample
Cash
Card
Terminal
Online
Multipleways to pay

Cash, Stripe Terminal, manual card, voucher, coupon, split.

1reconciled record

Supported payments retain their relevant order, staff and shift context.

2receipt formats

Digital and thermal, issued from the same record.

1end-of-day

Cash, card, terminal and online records compared at close.

The pain

What disconnected money costs a restaurant

Payments live outside the order
POS and payment provider don't agree on what was paid for, so refunds become a mystery.
Split bills break the flow
Splitting by item across two cards requires a calculator and a side app.
Tips and service charge handled by hand
End-of-shift maths happens in a notebook, not a report.
Cash reconciliation done after midnight
Float, variance and EOD totals stitched together at closing time.
Audit gaps on refunds and voids
Disconnected adjustments can make actor, time, reason and affected order difficult to reconstruct.
Old way vs. Cibus

From spreadsheets to one reconciled record

Disconnected money
  • POS and payment provider don't agree
  • Splits handled on a calculator
  • Tips and service charge tracked by hand
  • Cash reconciled at midnight in a notebook
  • Refunds and voids hard to trace
With Cibus
  • Payments tied to the order line item
  • Splits by item, share or method in one drawer
  • Tips and service charge reportable per shift
  • EOD reconciliation across cash, card and online in one report
  • Supported refunds, voids and corrections retain actor and time context
Workflow

What happens at the moment of payment

  1. 01Capture
    Payment captured against the order record
    Card, terminal, wallet, cash or voucher — same drawer.
  2. 02Split
    Splits by item, share or method
    Mid-payment, without leaving the drawer or restarting.
  3. 03Tip
    Tips and service charge handled at point of payment
    Captured per line and reportable per shift.
  4. 04Receipt
    Digital or printed receipt issued
    Linked back to the order line item for audit.
  5. 05Reconcile
    EOD reconciliation across configured channels
    Cash, card, terminal and online totals tied to orders.
  6. 06Audit
    Refunds and voids traceable to actor and time
    Supported actions remain associated with the affected payment and order context.
Capabilities

What's in the money layer

•
Card and wallet payments
Online and in-person payments through Stripe — wallets included.
•
Stripe Terminal
Card-present payments paired to POS, Staff Mobile and Storefront.
•
Cash and tills
Cash float, shift open/close and variance reporting built in.
•
Split payments
Split by item, share or payment method inside the same drawer.
•
Tips and service charges
Captured at the moment of payment and reportable per shift.
•
Digital and printed receipts
Digital and thermal receipt paths use the order and payment record; delivery depends on configuration.
•
EOD reconciliation
Cash, card, terminal and online totals reconciled against the order record.
•
Adjustment records
Supported refunds, voids and corrections retain actor, time and affected-order context.
•
Exact-cent calculation
Integer minor-unit arithmetic avoids floating-point drift; configured tax rules still require review.
Controls

Payment integrity, not just payment capture

✓
PCI scope kept narrow
Card data stays with Stripe; Cibus never stores raw card numbers.
✓
Idempotent payment intents
Supported Stripe payment writes use idempotency keys so a retried request can be recognised.
✓
Role-aware refunds and voids
Sensitive actions gated by role; managers approve where required.
Example shift end

One service, one clean reconciliation

  1. 21:12
    Server opens the payment drawer for the table
    Subtotal £144.00, service charge £18.00 (12.5%).
  2. 21:13
    Bill split across two cards
    £86.00 on Visa ****4242 and £86.00 on Mastercard ****1881.
  3. 21:14
    Tips captured per payment, recorded against the shift
    The supported tip record remains associated with the payment and shift.
  4. 21:15
    Digital receipts issued from the payment record
    Receipt delivery and any separate marketing preference are recorded for their own purposes.
  5. 23:30
    EOD reconciliation runs
    The reconciliation view compares cash, card, terminal and online records against orders.
The money layer

Not payment capture in isolation. Payment records connected through the shift.

Supported cash, card, wallet, voucher, tip and service-charge workflows connect order, receipt and end-of-day context.

Connected platform

Where the money layer shows up

Payments & Receipts
The product surface for operators: split bills, tips, receipts and EOD flows.
Service ops
POS
The card-present payment surface, using the same order and adjustment context.
Service ops
Security & compliance
Role-aware refunds, tenant isolation and the supported payment activity records.
Platform
FAQ

Money questions

Which payment providers are supported?

Cibus supports Stripe and Stripe Terminal for configured online and card-present workflows. Exact providers, wallet methods, reader hardware and availability are confirmed for the restaurant's market.

Tie every payment back to the order that produced it.

See how Cibus connects service, kitchen operations, payments, reporting, customer engagement and delivery into one restaurant operating system.

Book a DemoExplore Payments