Never retry, clear, manually record, void, or refund an uncertain terminal payment until the physical terminal, CentriPOS payment intent/transaction status, processor activity, and receipt all agree on what happened. A POS timeout is not proof that the card was not approved. Manual completion records payment while processor details are still pending and must be used only after the cashier sees a genuine approved result on the terminal.

Before you beginRecord the exact screen, time, expected behavior, and smallest repeatable steps. Remove unnecessary customer and payment data from screenshots.

Step by step

  1. Keep the Pay screen, cart, and physical terminal visible. Confirm business, location, register, open session, amount, sale/refund mode, selected payment type, and terminal name. If No terminals paired appears, stop and have an administrator assign/pair the terminal under Admin → Locations; do not record a terminal payment as an unrelated manual type.
  2. When more than one terminal is available, choose the intended device from the terminal picker. The default label identifies the resolved terminal. Verify the physical device name/identifier before choosing Send to [terminal] or Send refund to [terminal].
  3. After sending, read both screens. CentriPOS progresses through Sending to terminal and Waiting for customer card; the terminal should show the amount and accept dip, tap, swipe, or keyed entry on the device. If the terminal screen is asleep, wake it rather than sending another request.
  4. CentriPOS creates a payment intent before sending and stores a separate terminal transaction ID after acknowledgement. Keep the displayed Terminal transaction reference and any response code. Polling checks status roughly every second and realtime updates can also finalize the same request; duplicate finalization is suppressed by intent/transaction/result keys.
  5. If the result is Approved, CentriPOS captures the intent, adds one CentriPay Cloud payment with processor or terminal reference, and closes the receipt when the balance reaches zero. If the payment is approved but receipt closing fails, the screen explicitly says to review and tap Pay to retry closing the receipt; do not send another card charge.
  6. If Declined or Failed appears, read the formatted response message and response code. CentriPOS marks the intent declined/failed and does not add the payment. Resolve card/customer/processor conditions before a new request. A confirmed decline is different from a timeout or lost response.
  7. If Terminal did not acknowledge the request or the send fails before a transaction ID exists, inspect the terminal for an old prompt and verify connectivity/assignment. Do not assume nothing happened if the device still shows a payment. Clear the blocking intent only after confirming the old request should be canceled.
  8. If the request remains waiting, allow polling to continue. The manual-completion control is intentionally delayed for 10 seconds. Do not use it merely because the customer is impatient; first wait for an approved/declined final status and check the terminal display.
  9. At the terminal timeout boundary, CentriPOS performs one final processor status lookup before marking the request Expired. When that lookup cannot prove approval or failure, the status remains operationally uncertain. Search Payanywhere/CentriPay transaction activity using amount, time, terminal, and terminal transaction/payment-intent reference before retrying.
  10. Choose Complete manually only when the physical terminal clearly shows the exact payment was approved but CentriPOS is still waiting. The control checks status again first; if approval is now available it completes normally. Otherwise it records manual_pending_processor_confirmation, closes the receipt as paid, and expects processor details to update receipt history later.
  11. After manual completion, verify the receipt contains a single CentriPay Cloud payment for the intended amount, preserves the terminal transaction/payment-intent reference, and later receives processor transaction, approval, card last four/brand, batch, and response details. Escalate if reconciliation does not arrive; never create a second payment to make the metadata appear.
  12. Use Stop waiting and send again only when CentriPOS can cancel the active payment intent and you have confirmed the old terminal prompt/result is not an approval. On success, dismiss the old prompt on the physical PAX before sending the new sale. If Failed to stop waiting appears, do not retry until the blocking request is investigated.
  13. Use Clear terminal request in CentriPOS for a known stale/blocking request. It cancels the stored intent and resets local state; it does not remotely guarantee an old prompt disappeared or reverse a processor approval. Dismiss the physical prompt and confirm transaction history before sending again.
  14. If the cart is cleared while a request is active, CentriPOS attempts to cancel that payment intent. Still inspect the terminal and processor history because clearing the cart is not a payment reversal. Likewise, closing the Pay screen or losing network does not prove a request failed.
  15. For a refund terminal problem, keep the original receipt, return/refund amount, original-card eligibility, new-card terminal choice, processor reference, and sign of the payment aligned. Do not run a sale to compensate for a failed refund or a refund to test terminal connectivity.
  16. For support, preserve amount, local timestamp/time zone, business/location/register, session, terminal name/masked ID, sale or safe receipt reference, payment intent and terminal transaction references, response code/message, what each screen showed, and whether manual completion/clear/stop was used. Never send full PAN, bank data, credentials, API keys, or an unredacted payment screen.

Screen and contract reference

Control or areaWhat it means
Terminal pickerChooses among available devices; the resolved device can be labeled default.
No terminals pairedNo usable terminal is assigned/resolved for the current context; configure it in Admin → Locations.
Send to terminalCreates a CentriPay Cloud payment intent and sends it to the selected device for the capped remaining amount.
Send refund to terminalCreates the corresponding negative/refund request for a new card in refund mode.
Sending to terminalPayment intent is being created or delivered; do not submit again.
Waiting for customer cardTerminal acknowledged the request and CentriPOS is polling for customer/processor completion.
Terminal transactionReference returned by the device send and used for polling, realtime status, support, and reconciliation.
Payment intentCentriPOS request record tracking provider, amount, terminal, state, and eventual capture/cancel/failure.
Response codeProcessor/terminal result code shown with approved, declined, or failed status when available.
ApprovedConfirmed approval; one payment is added and the receipt closes when fully allocated.
Approved but receipt did not finish closingCard payment already exists; retry receipt closure with Pay, not another terminal charge.
DeclinedConfirmed processor decline; no payment is added.
FailedConfirmed or request-level failure; read message/code and verify the terminal before resending.
Expired / timed outPOS stopped waiting after a final lookup; may still require processor reconciliation before any retry.
10-second manual delaySafety window before Complete manually is enabled.
Complete manuallyChecks processor status again, then records an observed terminal approval as pending processor confirmation only when still unresolved.
manual_pending_processor_confirmationReceipt is recorded paid while detailed processor confirmation is expected later.
Stop waiting and send againCancels the active intent before resetting POS state; dismiss the old physical prompt and verify no approval first.
Clear terminal requestCancels a known blocking intent and resets POS state; does not reverse a processor transaction or guarantee the device prompt cleared.
Cart clear cancellationBest-effort intent cancellation when the cart resets; not proof of reversal or non-approval.
Polling and realtimeParallel status sources that can finalize the same intent; the UI deduplicates repeated final results.
Duplicate-charge riskA second request can charge again when the first outcome is unresolved.
Safe reconciliation evidenceAmount, time zone, context, terminal, receipt, intent/transaction references, status and response code—never full card/bank data or credentials.
No exact screenshotThe approved Harbor & Hearth manifest contains no safe final-state payment-terminal error capture, so this guide uses no fabricated image.

Expected result

The terminal and CentriPOS agree on connection and transaction state, the device is assigned to the intended register, and a controlled payment reaches that device once.

Troubleshooting

  • Capture the exact screen, time, expected result, and smallest repeatable steps.
  • Remove unnecessary customer and payment information from screenshots.
  • Include only safe receipt, order, or record references when contacting support.

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.