Payments
Recording payments against each order
Cash, card on your own terminal, Fonepay, eSewa, Khalti and bank transfer. Each payment is recorded against the order it settles, so closing the day is a matter of matching totals.
DataRestro records payments; it does not process them. Cards run on the terminal you already have. Sample data.
- ORD-0133auth 004417004417Rs 2,860Rs 2,860
- ORD-0137auth 004512004512Rs 1,240Rs 1,420
- ORD-0139auth 004538004538Rs 4,150Rs 4,150
- ORD-0144auth 004561004561Rs 980Rs 980
- ORD-0146auth 004602004602Rs 3,300Rs 3,300
POS card total
Rs 12,530
Terminal batch
Rs 12,710
Out by Rs 180. Somewhere in today’s card lines.
Where it works: Counter
Walk the whole restaurantRecording a card payment
The cashier runs the card on the terminal, then records it in DataRestro with the approval code. The POS never sees a card number and does not approve or decline cards. It keeps a record of what happened at the terminal.
The button says “Record” rather than “Charge” so cashiers know the card still has to be run on the terminal.
Record payment
Recorded, not processed. Run the card on your card terminal first.
Terminal reference / approval code (optional)
auth 004512
Record Rs 1,240.00 payment
The dialog, as it ships · wording deliberate
Split payments without duplicates
Split a bill across cash and a wallet, or between guests. If a button is tapped twice or a request is retried on a poor connection, the payment is still recorded only once.
- 1If two terminals take payment on the same bill, the second is refused once the balance is paid.
- 2Even and proportional splits add up exactly, down to the paisa.
- 3The amount paid is always recalculated from the recorded payments.
Table 9 · Rs 2,450
Illustrative data- 21:14:02Cash Rs 1,000Balance Rs 1,450Idempotency-Key pay-9a1ePartially paid
- 21:14:40Fonepay Rs 1,450 · txn 7731…Balance Rs 0Idempotency-Key pay-c04bPaid
- 21:14:41Same request again (double tap)First response returned, nothing new writtenIdempotency-Key pay-c04bReplayed
- 21:15:10Card Rs 500 on another terminalBill already settled, no overpaymentIdempotency-Key pay-11d7Refused
Refunds
A refund can’t exceed the amount paid minus earlier refunds. It requires the refund permission and a reason, and it is written to the audit log. Voids, which cancel items before payment, are a separate action.
Refund · ORD-0128 · cash
Illustrative data- Taken
- Rs 1,240
- Already refunded
- − Rs 360
- Most you can refund
- Rs 880
Refused
Refund of Rs 1,000 exceeds what remains on this payment.
Cash comes out of the drawer that took it, while that shift is open. The refund is logged with who issued it and why.
Choose your own card provider
Card fees are a cost you can negotiate, so DataRestro doesn't tie you to a card processor. Several large POS platforms bundle processing with the POS; DataRestro keeps them separate.
Processing tied to the POS
Toast
“Card transactions must run through Toast POS.”
Toast Card Payments FAQ
Clover
Part of Fiserv’s payment platform.
SkyTab & Revel
POS software owned by Shift4, a payment processor.
DataRestro
We record. Your terminal processes.
- Keep the acquirer with the best rate, and switch without touching the POS.
- No card number ever reaches this system.
- Integrated processing can be added behind the same ledger when it earns its place.
Competitor statements are from vendor documentation and press releases (Toast Card Payments FAQ; Clover restaurant POS page; Shift4 SkyTab and Revel press releases), accessed 27 Sep 2026. Terms change; check current vendor terms before relying on them.
How it connects
How payments connect to orders and shifts
Each payment is recorded against an order and a cash shift, so the drawer count, the reports and loyalty points use the same figures.
Feeds in
- POSThe order and its balance
- QR table ordersSettled at the counter
- LoyaltyPoints as tender, in tender mode
- Online checkoutPartialKhalti, eSewa and Stripe, verified with the provider
Payments
Records each tender with method, reference, cashier and shift. Guards against duplicates and overpayment.
What payments do today
Partial means it works now, with the limit stated next to it.
- Available
- Available
- Partial
- Partial
- Planned
- Planned
Tender types
AvailableCash, card, bank transfer, digital wallet, loyalty and other, enabled per restaurant.
Local wallets
AvailableFonepay, eSewa and Khalti recorded as wallet payments with their transaction ID.
Card on your terminal
AvailableRecorded with the approval code. Processing stays with your acquirer.
Split & partial payments
AvailableAcross tenders and guests; remainder allocated so shares sum exactly.
Duplicate protection
AvailableIdempotency keys, order locks, overpayment refused.
Refunds
AvailableCapped at what remains, permission-gated, reasoned, audited, attributed to the right drawer.
Reconciliation
PartialCard totals vs terminal batch, by approval code. Manual matching.
Online checkout for QR orders
PartialKhalti, eSewa and Stripe with your own merchant account; recorded only after a server-to-server check of the amount. Not yet verified against live merchant accounts.
Fonepay dynamic QR
PlannedA QR per bill, confirmed by callback. Needs a Fonepay partner agreement.
Integrated card terminal
PlannedBehind the same provider seam, when processing is wanted.
Gift cards
PlannedStored value on the payment ledger.
Accounting journal export
PlannedPayments as journal entries for accounting software. CSV export works today.
Payment questions
Does DataRestro process card payments?
How do Fonepay, eSewa and Khalti work today?
How do I reconcile at close?
Can I switch acquirer later?
Try the demo
A sample restaurant in your browser. Take an order, send it to the kitchen, mark it ready and take payment. No account needed.