Payments / Transactions brings together configured transaction reporting and a separate Card authorizations section. A reported approval, pending transaction, authorization hold, captured payment and bank settlement are different states. The reporting rows provide receipt actions; a Refund or Void transaction type describes reported activity rather than an immediate refund/void button on that row.

Before you beginConfirm the business, configured location, store timezone, amount and safe processor/receipt reference. Financial changes require the appropriate role, enabled runtime and original payment evidence. Keep card data, private customer details and internal credentials out of support requests.

Step by step

  1. Open Money → Payments, or CentriPay → Transactions in the POS workspace. Confirm the intended business and the configured-location selection. These entry points share the current Transactions panel; separate reporting/deposit views and direct gateway activity can have their own coverage.
  2. Choose All configured locations or the exact configured location. The location choice affects transaction reporting and the Card authorizations section. It does not grant access to another business or prove that every location/provider has been configured.
  3. Review the date picker. Its default is Year to date. Choose the intended preset or custom period and verify the store timezone before comparing transaction dates with a register closure, processor report or bank deposit. The panel waits for a usable timezone and valid date bounds before loading reporting.
  4. Wait for loading to finish. Transactions could not load is an error, while No transactions were found for this period means the configured reporting response was empty for the selected period/location. Neither result proves that another source, provider or unreturned historical record has no activity.
  5. Use Search TXN ID, sale, name… to match the returned processor ID, invoice reference, sale ID, customer name, location name or card last four. Search is applied to returned rows in the browser; it does not search amounts, authorization codes, arbitrary receipt notes or unloaded transaction history.
  6. Choose All statuses, Approved, Declined or Pending and All types, Sale, Refund, Void or Auth. Read Showing X of Y transactions returned for this period. The panel requests a bounded reporting response with count 500; client filters cannot find rows the service did not return. Narrow the period or location when investigating a missing record.
  7. Read the date/time, type, location/customer, masked card/funding detail, amount, status, payment-receipt action, POS receipt and transaction ID. The phone layout presents the same returned rows as cards. A blank card field or missing POS link is an information gap, not proof that no payment occurred.
  8. Open the POS receipt link when present and compare the exact sale/customer, payment amount/reference, original register session and invoice/return state. Keep payment reporting and receipt history distinct: a processor-only transaction may need investigation before it can be tied to a POS sale.
  9. Choose Payment receipt when offered to preview the receipt for that exact processor transaction. Review its merchant, amount, status and reference before sharing. This is the payment receipt, which can differ from the merchandise/tax/fulfillment detail on the POS receipt.
  10. Use the payment-receipt Print control only after checking the intended document and printer destination. Printing re-reads the transaction so a recent refund can be reflected. A printed receipt is a document copy, not confirmation of bank settlement.
  11. To email that payment receipt, enter the one intended Email receipt to address, review it and choose Email receipt once. This compact action uses a server-built receipt and the configured sending service; it is separate from the full POS receipt email composer. If delivery is uncertain, retain the original context and check available communication evidence before starting another send.
  12. For a product return, partial refund, exchange, inventory/tax adjustment or correction to a completed payment, open the originating POS receipt and use its eligible return or original-payment controls. Do not follow older instructions to click an immediate full-amount Refund or Void button in this reporting table; those buttons are not part of the current Transactions rows.
  13. Read Card authorizations separately when that section appears. Authorized · unpaid means funds were reserved, not collected. Capture in progress, Release in progress, Captured, Released and Review required describe different lifecycle states. Report date/status/type/text filters do not filter this separate authorization list; use its location scope and Refresh.
  14. Before Capture payment, confirm the exact receipt, held amount, customer authorization and capture deadline. The action captures the full retained hold amount shown here; this compact panel has no partial-capture amount editor. Capture before is a maximum workflow window, and the issuing bank may release funds earlier.
  15. Before Release authorization, confirm that the original hold should be released without collecting payment. Review the displayed capture/release question, then choose Confirm capture or Confirm release once. Use Cancel to leave the review without dispatching the action. An enabled button still requires the backend to accept the original payment scope, role and lifecycle.
  16. If the action is pending or its outcome is uncertain, use Check saved result for the retained original action. Do not start the opposite action, open another tab to bypass the saved attempt, or take a second payment. If the browser cannot retain the action, stop before submission and follow the message. A declined or unresolved action needs review of the original authorization.
  17. Some explicitly enabled accounts have a checkout-hold recovery panel under Alerts. It is not a general action in the transaction rows. An expired checkout window can still retain a payment hold. Inspect the original processor outcome and follow the separately authorized recovery procedure; inspection alone does not release a hold, collect money or refund a payment.
  18. After a confirmed capture, release, refund or other authorized financial action, reopen the same payment and POS receipt. Reconcile the actual processor outcome, receipt/invoice balance, register/closure evidence, batch/deposit, bank settlement and accounting state as applicable. A success message or changed reporting row does not establish every downstream result. Escalate uncertainty with safe references before another financial action.

Screen and contract reference

Control or areaWhat it means
All configured locationsSelects configured reporting scope; the same location is passed to Card authorizations.
Date range / store timezoneDefault Year to date, with presets/custom bounds interpreted for the selected business location.
Search TXN ID, sale, name…Client-side match across returned processor ID, invoice/sale reference, customer/location name and last four.
Status / TypeApproved, Declined, Pending and Sale, Refund, Void, Auth, plus All choices.
Showing X of YFiltered count versus returned reporting rows, not a complete unlimited ledger.
Payment receiptProcessor-transaction receipt preview, print and one-recipient email when an exact reference is available.
POS receiptLinked CentriPOS sale context when the report supplies a sale ID.
Card authorizationsSeparate held-funds lifecycle list, scoped by location rather than report date/search filters.
Capture payment / Release authorizationReviewed full-hold financial action, offered only when the returned capability allows it.
Confirm capture / Confirm release / CancelExplicit review before dispatching a capture/release; cancel leaves the review.
Check saved resultChecks the retained original action after pending or uncertain outcomes.
Capture beforeLatest supported capture window; the issuing bank may release earlier.
Alerts checkout holdsSeparately gated recovery surface available only to explicit rollout accounts; not a universal Transactions tool.
Return/refund boundaryUse the originating receipt’s authorized return/payment workflow rather than treating a reported type badge as an action.

Expected result

The intended reported transaction is traced to its payment receipt and linked POS receipt when available. Any authorization action has the reviewed original scope and a confirmed result, while settlement, receipt balance and accounting outcomes are checked separately without duplicate payment attempts.

Troubleshooting

  • For a missing payment, check business, configured location, store timezone, date range and active client filters. Narrow the scope before concluding that the payment is absent; investigate another source separately when needed.
  • If reporting cannot load or the authorization runtime is unavailable, preserve the error and ask authorized support to inspect configuration. Do not change a provider, tenant route or permission to bypass the failure.
  • After an uncertain capture, release or payment, keep the original attempt and use its saved-result path. Do not create an offsetting charge, new payment, new refund or replacement invoice without reconciliation.
  • For support, provide the safe transaction/receipt reference, amount, time/timezone, visible state and exact action/message. Redact private customer and payment data; no transaction screenshot is published by this guide.

More guides

Build an itemized payment in MoneyUse Products or Amount & description to build one receipt, attach the customer, and follow the appropriate payment or service-estimate workflow.
Take a one-time payment in Virtual TerminalReview a one-time amount, tax and contact at the correct payment station, use its verified secure checkout, and recover the original receipt after an uncertain result.
Review booking payments, refunds and earned careKeep a booking’s customer payments, unused advances, completed care, cancellation fees and refunds distinct, then read a correctly scoped accrual report.
Configure booking properties and customer pagesSet accommodations, service packages, availability, required intake and payment terms, then review the correctly branded booking page before sharing it.