Cibuscibus.
Payments & Receipts

Payment records connected to the order.

Take card, wallet, cash, Stripe Terminal, voucher, split and tip payments from one connected flow. Receipts, tax, service charges, refunds, shifts and end-of-day reports stay attached to the original order record.

Illustrative payment workflow
Order record
Table, counter, QR or Storefront
Subtotal calculated
Tax calculated
Service charge calculated
Tip recorded
Amount due
Payment methods
Card-present
Wallet
Cash
Voucher
Split
Manual card
Pay at counter
Promo code
Receipt
Digital receipt issued
Email receipt
Thermal receipt
Reprint available
Attached to order
Reconciliation
Payment status
Shift record
Cash variance review
End-of-day report
Admin visibility
Order recordPayment capturedReceipt issuedShift updatedEOD reportAdmin payment record
Methodspayment options

Card, supported wallets, cash, Stripe Terminal, vouchers and split payment.

Digitalreceipt formats

Digital and thermal receipts tied to the order record.

Linkedorder record

Recorded payment rows remain attached to the original order.

Shiftreconciliation

Shift and end-of-day review use the connected payment records.

Why this matters

Payments become messy when they live outside the order.

Restaurants do not just need to take payment. They need to know which order was paid, which staff member handled it, which method was used, which tips and service charges applied, which receipts were issued and whether the shift reconciled at close. Cibus keeps the payment trail attached to the original order.

Without a connected payment layer
  • Separate card terminal sitting next to the POS
  • Cash drawer reconciled with a spreadsheet
  • Split-bill calculation done manually
  • Vouchers noted by hand
  • Receipt reprints cause confusion
  • End-of-day stitched together by export
With Cibus Payments & Receipts
  • One order record per table or channel
  • Multiple payment methods on the same bill
  • Split rows linked to the order
  • Tips and service charges captured in flow
  • Digital and printed receipts attached to the order
  • Shift and EOD reporting connected to payments
  • Review records for supported refunds, voids and adjustments
Payment methods

Cards, cash, wallets, vouchers and splits in one flow.

Cibus supports the ways restaurants actually get paid: card-present through Stripe Terminal, online card and wallet payments, cash, manual card recording, vouchers, promo codes, tips and split payments. The method can vary, but the record stays connected.

01
Card & wallet
  • Stripe Terminal
    Card-present chip, contactless and wallet payments paired to POS terminals.
  • Online card and wallet
    Card and wallet checkout for QR Order & Pay and Storefront flows.
  • Manual card recording
    Record external card-reader payments for reconciliation without claiming Cibus processed them.
02
Cash & alternatives
  • Cash
    Tender, change due and denomination-aware cash handling where configured.
  • Pay at counter
    Support customers who prefer settling with staff.
  • Voucher and promo redemption
    Apply gift vouchers and campaign codes at checkout.
03
Splits, tips, service
  • Split payments
    Split one bill across people, methods or payment rows.
  • Tips and service charges
    Capture tips and configured service charges in the payment flow.
  • Per-row receipts
    Issue per-person receipts while retaining the order-level payment history.
Payment drawer
Illustrative payment workflow
Split row · Card-present
Split row · Wallet
Split row · Cash
Split row · Voucher redemption
Tip selector
Custom
Voucher / promo code
Enter code
Receipt preference
EmailPrintBoth
Stripe & terminal integrity

Stripe payments connected to the order record.

Cibus uses Stripe for online and card-present payment flows. POS terminals can pair with assigned Stripe Terminal readers. Server-derived amounts check the payment request against the order, while idempotency keys identify repeated requests.

Stripe online payments
Stripe Terminal card-present
One reader paired to one terminal
Server-derived amount
Idempotency on retries
Stripe-managed payment components
Payment confirmation attached to the order
Receipt issued after success
Stripe Terminal pairing
Paired
1POS terminal selected
2Reader paired
3Amount derived from order
4Payment intent created
5Customer taps or inserts card
6Confirmation received
7Receipt issued
Server-derived amount · Retry key · Stripe payment component
Split payments

One bill can have many payment rows.

Groups can combine multiple payment methods. A table might split by diner, split equally, combine cash and card, use a voucher for part of the bill or settle some amount at the counter. Cibus keeps each payment row linked to the same order.

Split equally
Split by item
One pays
Multiple payment methods
Voucher plus remaining balance
Cash plus card
Per-person receipt
One order-level payment history
Order record · Split builder
Illustrative payment workflow
Amount due
Payment row · Card-presentCaptured
Payment row · CashRecorded
Payment row · Voucher redemptionApplied
Payment row · WalletCaptured
StatusReady for reconciliation
Receipt lifecycle

Receipts are issued, attached and recoverable.

A receipt is part of the order record. Cibus supports digital receipt issuance, email delivery, receipt access, thermal printing, reprints and receipt history.

  1. 01
    Payment succeeds
  2. 02
    Receipt generated
  3. 03
    Digital copy issued
  4. 04
    Thermal receipt printed where configured
  5. 05
    Receipt attached to order
  6. 06
    Reprint or resend available
  7. 07
    Receipt available for review and support
Receipt preview
Illustrative receipt
RECEIPT
Order record
Item
Item
Item
Subtotal
Tax
Service charge
Tip
Total
Payment method
Receipt attached to order
Email sent
Print job queued
Reprint available
Minor-unit calculations

Money calculations designed to reconcile.

Payments, discounts, taxes, service charges, tips and split rows need consistent rounding. Cibus calculates money in integer minor units and tests balancing behaviour across receipts, payment rows and reporting.

01
Money engine
  • Integer minor-unit calculations
    Minor-unit arithmetic across items, discounts, tax and tips.
  • Multi-currency support
    Configurable currency per location.
  • Tax handling
    Inclusive, exclusive and compound tax support.
  • Service charge handling
    Configurable service charge rules.
02
Allocation
  • Sequential discounts
    Discounts applied in defined order.
  • Split payment allocation
    Allocate amounts across payment rows cleanly.
  • Tip capture
    Tips captured per payment, attributed per shift.
  • Receipt total balancing
    Receipt totals are checked against payment records and reporting.
Integer minor-unit calculation
Calculation stack
Items
Discounts
+Tax
+Service charge
+Tip
=Amount due
Payment rows
Receipt total
EOD report
Shift & end of day

Shift and end-of-day payment review.

Payments feed into shifts and end-of-day reporting. Managers can review payment mix, cash handling, tips, refunds, voids, vouchers, print jobs and variance from the same connected system.

End-of-day report
Payments reconciled to orders
Illustrative
Payment mix
Tracked
Cash variance
Review queue
Card-present payments
Logged
Online payments
Logged
Wallet payments
Logged
Voucher redemptions
Recorded
Tips
Recorded
Refunds and voids
With reasons
Receipts issued
Per order
Orders reconciled
End of shift
Audit & exceptions

Refunds, voids and adjustments need a trail.

Sensitive money actions need reviewable records. Cibus connects supported refund, void and adjustment workflows with order detail, status history and, where configured, staff attribution, approval and reason capture.

01
Controls
  • Refund visibility
    Supported refund records link to the original payment and order.
  • Void visibility
    Supported void workflows can retain actor and reason details.
  • Manager approval
    Configured approval steps for sensitive actions.
  • Reason capture
    Supported exception workflows can retain a reason.
02
Trail
  • Staff attribution
    Supported sensitive actions can retain staff attribution.
  • Order detail timeline
    Order-level timeline of payment events.
  • Payment status history
    Status transitions kept for review.
  • Admin payment overview
    Visibility for managers and owners across locations.
Exception · Refund or void
Illustrative exception record
Action requestedRefund
Staff roleCashier
Manager approvalRequired
Reason capturedLogged
StatusUpdated
Exception historyVisible
Payment flow

Not a terminal beside the till. A payment record that reconciles.

Recorded card, wallet, cash, voucher, tip and split rows stay connected to their order and feed the relevant shift and end-of-day records.

In service

A mixed-payment table, one connected record.

A table orders through a mix of staff-entered and QR-originated items. At checkout, the bill is split across card-present, wallet, cash and a voucher. Cibus attaches each recorded payment row to the order, issues receipts, updates the shift and makes the record visible in Admin for end-of-day review.

Mixed-payment table · One order record
Illustrative scenario
  1. 1Order opened
  2. 2Items added
  3. 3Payment drawer opened
  4. 4Split rows selected
  5. 5Voucher applied
  6. 6Card-present payment confirmed
  7. 7Cash recorded
  8. 8Receipt issued
  9. 9Shift updated
  10. 10EOD report ready

The cashier opens the payment drawer, builds split rows, captures the card-present payment through the paired reader, records cash for one diner and applies a voucher for another. Each recorded row stays attached to the same order record.

Illustrative scenario
FAQ

Payments questions, answered.

Does Cibus support card, cash and wallet payments?

Yes. Cibus supports card-present, online card, supported wallets, cash, vouchers and split payments. Each recorded payment row remains connected to the order.

Keep payment records connected to the order.

Connect payments, receipts, tips, vouchers, splits, cash handling, printing and reconciliation inside the same platform that runs service.