A terminal payment is an integrated CentriPay Cloud intent plus a device transaction, not a manual card notation. Keep the Pay screen and physical terminal visible until CentriPOS reaches a confirmed final state. Never refresh, clear the cart, close the register, remove the allocation, or send again while the first result is uncertain.
Before you beginConfirm the business, location, and register in the top bar. Finish or park any active cart before changing register context.
Step by step
- On the completed cart, choose Pay and verify Total, Balance, customer when attached, business/location/register, and open session. Expand Integrated Payments if needed.
- Choose Payanywhere. If it says No terminals paired — add in Admin → Locations, stop and have an administrator configure the current context. Do not substitute a manual payment type just to finish the receipt.
- When multiple devices appear, choose the intended terminal from the picker and verify its physical name. The resolved assignment is labeled default. Confirm the customer-facing amount before sending.
- Enter or keep the amount, which cannot exceed Remaining. Choose Send [amount] to CentriPay Cloud once. CentriPOS first creates a payment intent, then sends it to the terminal and displays Sending request to terminal.
- When the terminal acknowledges the request, CentriPOS shows Waiting for customer card and a Terminal transaction reference. Wake a sleeping PAX, then ask the customer to follow the device prompts for dip, tap, swipe, or keyed entry on the terminal.
- Wait while CentriPOS polls and listens for realtime updates. Do not use Complete manually during its initial 10-second safety delay. The terminal and CentriPOS can update at slightly different moments.
- On Approved, CentriPOS records a single CentriPay Cloud allocation with the processor or terminal reference. When that allocation reaches the full total, the sale normally closes automatically. If the screen says payment approved but the receipt did not finish closing, review and tap Pay to retry receipt closure only.
- On Declined or Failed, read the response code/message. No successful allocation is added. Resolve the card, customer, device, or provider issue, then choose another tender or send a genuinely new request only after the first is conclusively failed.
- On timeout/Expired or lost response, do not assume the card was not charged. Check the physical terminal and CentriPay/Payanywhere transaction history using amount, time, terminal transaction, and payment-intent reference. Follow Fix a payment terminal problem before clearing, stopping, manually completing, or resending.
- Use Complete manually only when the physical terminal clearly shows the exact amount approved and the POS is still waiting. CentriPOS checks status once more, then if still unresolved records payment pending processor confirmation. Verify later processor detail on the receipt.
- After the receipt closes, verify sale number, card brand/last four when returned, approval/response, terminal and processor references, amount, other split tenders, balance, and receipt delivery. A successful terminal screen alone is not the final bookkeeping check.
Screen and contract reference
| Control or area | What it means |
|---|---|
| Integrated Payments | Expandable Pay area containing supported Tap to Pay, saved/original card, and Payanywhere paths. |
| Payanywhere | Terminal path using a CentriPay Cloud payment intent and paired device. |
| No terminals paired | No device is usable in the active context; configure under Admin → Locations. |
| Terminal picker | Device selector shown with multiple location terminals; the resolved assignment can be labeled default. |
| Amount | Requested integrated payment amount, capped at the remaining balance. |
| Send to CentriPay Cloud | Creates the intent and sends it to the selected terminal once. |
| Sending request to terminal | Request creation/delivery is in progress; do not submit again. |
| Waiting for customer card | Device acknowledged the request and awaits/works the customer card interaction. |
| Terminal transaction | Reference used for status, reconciliation, and safe support evidence. |
| Approved | Confirmed success added once to the payment allocation. |
| Approved but receipt not closed | Retry receipt closure through Pay; never send another card request. |
| Declined / Failed | Confirmed unsuccessful result with response evidence; no successful payment allocation. |
| Expired / timeout | POS wait ended after a final lookup, but processor reconciliation may still be required. |
| Complete manually | Delayed recovery for a payment visibly approved on the terminal while POS confirmation is still missing. |
| Pending processor confirmation | Manually recorded paid state whose detailed processor result should arrive later and must be reconciled. |
| Split tender | Terminal allocation can cover part of Remaining, after which another method completes the sale. |
| Final receipt verification | Confirms one payment, correct amount, references, card metadata, other tenders, and zero/expected balance. |
| No exact screenshot | The approved Harbor & Hearth manifest has no safe exact terminal checkout capture, so this article has no substituted image. |
Expected result
The terminal and CentriPOS agree on Approved, Declined, or Canceled. Only an approved transaction is attached to the completed sale.
Troubleshooting
- Confirm the active location, register, and register-session status before repeating the action.
- Do not refresh or retry while a card terminal shows a payment in progress.
- If totals differ, review every cart line, discount, fulfillment charge, and tax before payment.
CentriPOS API explorer · API Center administration
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.