Take payments on the POS

Open the intended bill and verify its current amount before Pay. Available tenders depend on the restaurant and device configuration. The full-screen progress and automatic post-payment return described below require the matching POS version; an API update alone does not change the installed payment UI. To name a check from Continue/Send before collecting payment, follow custom check creation.

Refund or void a Verifone online payment

The Admin order payment section supports total or partial matched refunds and total VOID for an eligible single Verifone online payment, for owners/managers with payments.manage. Provider state, captured amount and verified history govern eligibility, not a fixed 24-hour rule. This does not cancel preparation or fulfillment and does not add a POS terminal refund button. Unknown results stay reserved and must be checked, never resubmitted. Invoice4U credit/cancellation documents require a separate check. See the online payment procedure.

A captured ABS sale still AUTHORISED/AUTHORIZED or SETTLEMENT_REQUESTED is not settled: Admin shows Available to void and only Void entire payment, with no prior refund. Refund payment and Available to refund require an explicit settled state or verified partially-refunded history. Generic APPROVED/COMPLETED, contradictory states or missing evidence offer neither action. A state change before confirmation rejects the stale action; it never switches VOID to REFUND automatically. Request rejected by Verifone means no return of funds is confirmed, not necessarily an issuer decline.

After a full return verified against matched Verifone history, the summary keeps the original amount, shows the full amount returned and zero remaining, and offers no further refund or VOID. A cleared capture balance after that return is not an uncaptured hold to release. Missing or inconsistent evidence still requires verification without resubmission.

Keep the hosted payment form readable

When Foody enables a restaurant-branded Verifone hosted checkout, the payment page uses light surfaces and dark text, even if the restaurant website is dark. The published logo is kept and the brand/button accent is adapted when needed for readable contrast. This concerns online hosted payments, not POS terminals or native Apple Pay/Google Pay sheets. If an older page is unreadable, contact the Foody team to resynchronize its payment theme. The update applies to newly issued Checkout links, not the page already open. Check the current payment status before requesting another link; never repeat a debit because of a display problem.

Review the by-weight authorization ceiling

For online by-weight orders, open Settings → Payments & VAT with settings.edit. Set Weight hold buffer % from 0 to 100 and save; the default for new restaurants is 20. A failed save keeps the draft. Zero still authorizes the estimate. Only the weight-priced subtotal gets a margin: 100 weighted + 50 fixed at 20% authorizes 170; delivery has no extra margin. Checkout shows the estimate, temporary ceiling and Confirm and authorize, in the restaurant theme. A changed ceiling requires customer review and another confirmation before payment; unknown policy blocks authorization. Existing reviewed checkouts and holds keep their ceiling. Staff confirm measured weights before capture and progression; excess beyond the hold is flagged for a separate payment, never automatically charged. Cash/pay-later makes no hold promise. Requires a configured authorize/capture provider, with partial capture, release and expiry validated before production. This neither changes the catering deposit/balance policy nor enables new-card saving with a CST weighted hold.

Record cash

On an enrolled POS with an active PIN shift, first open More → Reports → Cash drawer balance and enter the physical opening float. Then choose cash on the intended order or financial bill, enter the amount received and check the change before confirming. Only record money actually received. A pending cash collection must be retried with its existing identity, not recreated as another sale. Split bills keep their own receipt and paid status. A Pending payment state can simply mean payment is expected before any attempt; it does not prove an operation is in progress. Existing payment actions retain their conditions and permissions. A card authorization or an actual operation with an uncertain result must instead be resolved through its existing flow, without creating a replacement collection. Unknown kitchen progress does not authorize payment.

Retry an unconfirmed cash-drawer read

If Cash drawer balance or Cash movements cannot be read, do not infer that no drawer is open. Retry reads the state on the same device without a cash movement or Verifone deposit. New operations stay unavailable until the state is confirmed. Preserve pending operations with their identifiers and do not erase local data. Specific messages need compatible POS and API versions; this guide does not confirm installation. See cash-access diagnostics for refusals and safe recovery.

Count and close the cash drawer

On the same enrolled POS with an active PIN shift, open More → Reports → Cash drawer balance. Review the opening float, cash sales and refunds, paid in/out and expected cash. The optional description is copied to the closing note, without automatic saving. With payments.manage, open Paid in/out, enter a positive amount and mandatory reason, then choose Pay in cash or Pay out cash. A payout cannot exceed the expected balance. With orders.manage, choose Close cash session, count physical cash, enter that amount and confirm; any discrepancy is preserved. Dismissing the modal without confirming records nothing. Cash movements lists only the session loaded on this device, not past sessions. Resume any uncertain operation using its existing identity before another action. Cards are excluded: closing cash does not start a Verifone deposit, and a Verifone deposit does not close cash. Never use a cash adjustment to disguise a card refund.

To bring together the end-of-day steps, use the combined closing flow.

Collect a connected payment

On an ordinary counter or table check on the updated handheld terminal, Pay opens a black customer review with the selected check’s lines, modifiers and confirmed amount. Review it before Confirm and pay. The ⋯ menu offers cash; the language selector changes only this review, without changing the device language. Dismissing the review collects nothing. Tablets retain the full-screen Card/Cash tender choice. Choose Pay by card. Foody keeps a full-screen progress view during preparation, terminal connection, reported login/session/parameter stages, the terminal instructions, payment recording and the counter order's kitchen send. Only stages actually reported are shown; not every payment needs every stage. Card reading and PIN entry remain on the secure Verifone terminal. The displayed kitchen send confirms order submission, not physical paper output: only categories selected in the assigned kitchen profile print. The screen closes on refusal or cancellation without marking the bill paid; review the displayed error before retrying. Wait for Foody’s verified final status; browser return alone is insufficient. If the result is pending/uncertain, refresh and review the provider transaction with an authorized operator before any retry. Never ask the help assistant to inspect card details. Before collection, Foody checks the bill data again. A change to lines, amount, paid state or restaurant/account context stops the flow: reopen Pay and confirm the updated review. The same check protects cash confirmation. An interrupted review does not establish a charge; if the provider has already returned an uncertain result, use the reconciliation procedure below. A new item or kitchen batch added to the check during review or cash entry also requires fresh confirmation; it must not be ignored when collecting. This Victa checkout uses ILS; changing language does not convert currency.

Find a completed payment in Transactions

Open Transactions in the iPad POS navigation, in More on compact terminals, or in the Admin sidebar, with payments.view or payments.manage. All three screens read the same restaurant-scoped confirmed payment history. In Admin choose a date range, source and method; search by item, reference or order number, then select a payment for its amount, method and linked orders. On the POS, selecting a linked order opens its saved read-only detail without leaving Transactions; if it cannot load, refresh and retry. The source follows the linked order: a provider-processed payment for a POS-created order appears under POS, not Online. Totals cover all matching payments, not just the visible page, and keep currencies separate. One order can have several tenders and one tender can cover several orders; Orders remains the place to follow fulfillment. Pending terminal attempts are not completed sales. History does not issue new receipts. Authorized owners and managers may see server-verified cash refunds or Verifone Checkout original-card returns for eligible payments; see the refund procedure before acting. If a result is missing, check restaurant, date and filters, then reconcile uncertain terminal payments before another charge.

Understand payment origin

Open a transaction on POS or Admin and read Payment origin separately from Source. Source identifies where the linked order was created; origin identifies cash, Verifone Checkout, another provider, or a recorded card payment. Victa (recorded payment) and Card (origin unverified) mean Foody recorded a result; they do not prove that a refund can be sent to the terminal. Older grouped payments can show Origin not attributed. For a return, confirm the original tender and use its authorized refund workflow; never substitute cash for a card payment.

Search every item and retry the history

Search Transactions by any item in a linked order, including items after the first four. Open a payment to review the available linked item names. On the POS, if loading more results fails, the payments already shown remain visible; choose Try again under the list to continue. This retries only the history request, not a card charge.

Read refunds and payment voids in Transactions

A successful Verifone Checkout refund or void initiated in Foody appears as its own return transaction, linked to the original payment. A confirmed cash return also appears separately, linked to its original cash tender. On the POS, an owner or manager with payments.manage can open an eligible payment in Transactions. For a journaled cash sale, choose Issue refund only when the server confirms an exact refundable portion and an open enrolled drawer. Select the order or check portion, enter an amount within the limit and a reason, then hand over cash only after Foody confirms. For one captured Verifone Checkout card payment linked to one exact order allocation, choose Refund to original card or Cancel card payment if offered. Enter a reason and, for a refund, an amount within the displayed limit. Foody sends the return to the original card, never to the cash drawer. An uncertain card result must be rechecked using the same saved request before another return; do not issue cash instead. Legacy unattributed, split/multi-order and Victa card payments do not offer this card action. Admin shows gross collections separately from returns recorded in Foody; neither figure is net revenue. Returns made directly in Verifone Central or on Victa are not included automatically. Also review recorded net and balance.

Read the transaction total correctly

The Admin date range and displayed times use the restaurant’s timezone. The total sums all confirmed payment records matching the selected filters, even across several pages. Currencies remain separate. It is a gross payment total, not net sales: refunds, processing fees, cash-drawer movements and terminal end-of-day deposits are not subtracted here. Use the appropriate provider and accounting reports before reconciling a day.

Close and deposit a Verifone terminal batch

To close cash and card activity in one flow, use End of day and the Foody Z report. Staff clock-out remains separate. On older versions, Terminal deposits offers a separate Verifone transmission with payments.manage: check the terminal, confirm once at end of day and wait for final confirmation. An uncertain result blocks repetition before verification. Unsupported totals commands remain unavailable. Numerical results and the batch reference are shown only when actually supplied. Never share terminal credentials or card details in support chat. Hardware compatibility must be checked on the relevant Mini or Portable. If context changes, reopen confirmation.

Read totals or use advanced terminal actions

In More → Reports → Terminal deposits, View current totals reads the active batch without closing or transmitting it. Advanced actions are shown only when supported by the terminal: Close batch only closes the reporting period without transmission; Transmit only requests acquirer reconciliation without explicitly closing it. Neither advanced action alone is the standard end-of-day flow. Use either only on your payment provider's instruction, confirm once and wait for the terminal's final result. If unsupported or uncertain, do not assume success; check the terminal or ask the provider before retrying.

Verify payment for one QR order

From Orders → Menu → Actions → Manage this order, offered actions affect the selected number only, never the combined value of the table’s QR orders. Collection is offered only for an eligible unpaid order in its workflow and with payments.manage; pending, partial or already-paid states do not permit charging the full total again. Verify number, state and amount before confirming. Changing restaurant or operator, or losing permission, invalidates the open action. A terminal approval arriving after that change remains to be reconciled: do not repeat the charge. View table is separate navigation that neither pays nor closes anything. Existing Verifone rules, journals and final terminal confirmation remain in place.

Review tips and receipt

Review any supported tip step before collection and confirm the total; availability depends on configuration. After confirmed payment for an ordinary check on the updated terminal, the receipt page offers Print when a printing action is available, or No receipt. Print requests an additional copy through the existing printing service; configured automatic receipt output may already have been requested. Email and SMS remain disabled when no sending service is supplied; they do not establish delivery. After the choice, You’re all set appears; New sale explicitly finishes the flow. For cash, the receipt shows known change, or No change for exact payment; missing or invalid values are omitted. Card receipts show no cash change. A fully paid table returns to the floor only after server-confirmed closure; an Open checks home configuration can retain its list. If restaurant, bill or permissions changed during receipt choice, Foody does not automatically close the old context. If closure fails after recorded payment, resume closure of that same check without collecting again. On a failed or uncertain print result, inspect history and jobs before another copy; never repeat payment. Per-check refunds are not established for every advanced split flow: use an authorized manager rather than assuming a refund button exists.

Check an itemized Invoice4U invoice

This concerns online orders, not a new POS terminal integration. When Invoice4U issuance and an invoice document type are enabled by the Foody team for the merchant, ordinary immediate Verifone order payments send the saved order lines: items and quantities, selected variants/options, combo base and included components, order discount and delivery fee. Frozen prices already include VAT; it is not added again. The line total must equal the payment amount or payment initiation is blocked. The same detail is sent for a later saved-card sale. Legacy orders without catalogue lines and catering/table/capture operations keep their existing document behavior. An approved payment is not proof that Invoice4U issued a fiscal document: check the document in Verifone Central/Invoice4U and customer delivery. Do not create another payment to obtain a missing invoice.

Wait for counter card payment before kitchen preparation

For a new counter pickup order paid by card, choose Pay, then Pay by card. Wait for terminal approval and for Foody to record the payment before preparation and the kitchen ticket start. During collection the payment remains pending and is excluded from the live order board. After a refusal or cancellation, keep the same checkout and retry there; do not send it to the kitchen to bypass payment. If approval succeeded but synchronization failed, reconcile the existing payment before starting another charge. Orders deliberately sent for table service before collection keep their existing send-then-pay flow.

Confirm a paid counter takeaway sale

After collecting a counter takeaway sale and confirming its kitchen send, the updated handheld terminal opens receipt choice; choose an available receipt action or No receipt, then New sale. Tablets retain the brief Payment recorded confirmation and automatic return after about two seconds. The tablet header shows the tender and sale amount; on the handheld, the receipt retains known cash change, or No change for exact payment. Unknown or invalid change stays unspecified. Use Transactions, available in More on the handheld, to consult the collection with the required payment-read permission. This confirmation never charges, reprints or pretends that a pending result succeeded. The paid order remains active while it is being prepared: payment does not mark it ready or handed over. Orders and Transactions refresh when reopened. If payment is recorded but the kitchen send is unconfirmed, keep the existing bill and retry only its send; never charge again. Kitchen tickets and customer receipts are separate. Automatic kitchen output requires an enabled printer profile with In-person order tickets, the item's categories selected and the printer associated with the current POS installation. This includes manually entered takeaway sales, not just table service. Configure profiles in FoodyAdmin or More → Settings → Hardware → Printers → Profiles on the POS. Reinstalling or using another POS installation can require discovering the printer and assigning the existing profile again. A successful payment or a queued print job does not prove paper was printed. Check the printer's history and queued/uncertain jobs before reconnecting or reprinting; pending documents can print after reconnection. If a confirmed paid takeaway bill remains before kitchen dispatch, Send to kitchen resumes only that send, even with a customized preparation workflow. It never requests a tender or another charge. If the original tender is absent, confirmation uses a neutral Payment heading, not an invented card payment. Before reassigning a printer, review its pending-document warning and routing.

Find Pay on mobile

On an ordinary check on the updated terminal, open Check then Pay at the bottom. It stays unavailable until the workflow permits collection. Review the customer summary, lines and amount before Confirm and pay; use ⋯ for cash. Card and PIN entry stay on Verifone’s secure screen. Only a confirmed, recorded result opens receipt choice and New sale. Neither a tab change nor an animation confirms payment. Never repeat collection with an unknown result. Other check commands, including permitted prepayment printing, remain in the check’s ⋯ menu.

Read transactions and reports on mobile

Transactions uses the full width for its list; tap a row to open details and use Back to return to the list. Filters, pagination and access permissions remain those of the journal. On compact screens, details and the cash-drawer report use terminal-sized insets. The visual change starts no collection, refund or deposit.

Sumit in Admin

For Admin Sumit payments, see the dedicated procedure.