At checkout, CentriPOS loads enabled payment types for the tenant, keeps only those supporting the POS channel and active location, and then separates integrated actions from eligible manual methods. A payment type label alone does not prove money moved through a processor. Use the separate Configure Payment Types guide for the exact Harbor & Hearth Admin screenshot.
Step by step
- Open Pay only after confirming the cart total, customer, tax, fulfillment, and register session. The Pay screen shows Total, Paid, Balance, any Payments Applied, and Amount to collect.
- Review the payment choices actually shown. An enabled type with no channel restriction or with POS enabled can appear; a location-unscoped type appears everywhere, while a scoped type appears only at an assigned active location. Disabled, WEB-only, other-location, or hidden-manual types do not belong in the manual list.
- Distinguish integrated choices from manual records. CentriPay Cloud sends a card-present request to the resolved active terminal; Tap to Pay uses the supported device plugin; Card on File charges an authorized vaulted card. A custom/manual type only records the amount under that tender unless its own connected workflow has already collected the money.
- Do not use a manual “CentriPay Terminal,” “NMI Gateway,” financing, gift, or card label as a substitute for running its integrated processor action. Manual integrated-tender options are intended only when administrators deliberately expose them for recording an already-completed outside transaction.
- Set Amount to collect before choosing a method when splitting payment. It defaults to the full remaining balance, offers Full and sometimes Half shortcuts, and caps an entered payment at the remaining balance. Selecting a method without a reference step applies that amount immediately; a positive remaining balance returns you to method selection.
- For Cash, enter the amount physically tendered or use a configured denomination preset. CentriPOS records the applied cash amount, tendered amount, and change. If this cash payment finishes the balance, the configured Cash payment type can round the remaining cash amount and store the separate cash rounding adjustment/discount on the receipt.
- For a manual method configured to collect a payment reference, enter the required searchable ID before applying it. Check always collects a reference by default; the field label, placeholder, and help text can be customized. Verify a check number, money-order number, voucher ID, authorization, or gateway transaction ID against the source document.
- For CentriPay Cloud terminal, confirm the selected terminal and amount, send once, wake the PAX if needed, and wait for an approved processor response. CentriPOS records processor/terminal IDs, approval and response details, brand/last four, entry method, device, batch/merchant/invoice/receipt references, and timestamp when returned.
- If a terminal request remains pending, use the terminal recovery guide. Manual completion becomes available only after the delay and records a pending-processor-confirmation exception; it is not equivalent to a verified approval. Never send a second request merely because the first response is slow without checking terminal/processor state.
- For Card on File, verify the attached customer and exact vaulted card. CentriPay Cloud and NMI Gateway saved cards run different connected charge paths and record their processor reference; do not describe a manual card label as a vaulted charge.
- Review Payments Applied after every tender. Each row shows method and amount; integrated rows are protected from casual removal, while a nonintegrated manual allocation can be removed before completion. Confirm Paid and Balance recalculate correctly.
- When Balance reaches zero, CentriPOS completes the sale automatically through the payment workflow. Do not click or add another method after the receipt begins completing. If a balance remains, add another valid payment, choose an approved partial-balance outcome such as layaway or Charge to Account, or correct the existing allocation.
- After completion, open the receipt and verify payment method/type, applied amount, tendered/change, reference number, processor/terminal evidence for integrated payments, cash rounding, total paid, and zero or intended remaining balance. Reconcile processor/card activity separately from the CentriPOS record.
- Administrators manage definitions at Admin → Payment types. Integrated Payment Types report the service connection plus mapped reporting row; Custom Payment Types are manual methods. Changes to enabled state, POS/WEB channels, locations, manual-list visibility, reference collection, cash rounding, conceal totals, or gateway URL affect future checkout choices and require controlled testing.
Screen and contract reference
| Control or area | What it means |
|---|---|
| Total / Paid / Balance | Current payment allocation summary. |
| Amount to collect | Draft amount capped at the remaining balance; defaults to full remaining. |
| Full / Half | Convenience allocations for the current remaining balance. |
| Payments Applied | Tender allocations already added to this checkout. |
| Enabled | Payment definition must be active before it is queried at checkout. |
| POS channel | Required explicitly when channels are restricted; no/empty channel list behaves as unrestricted. |
| Location assignment | No location list means all active locations; an explicit list limits availability. |
| Manual-list visibility | Noncash payment setting that can hide a reporting/import/integrated row from cashier selection. |
| Integrated payment | Connected action that actually requests or charges through CentriPay Cloud, Tap to Pay, or a supported saved-card provider. |
| Manual payment | Cashier-recorded tender allocation; it does not itself contact a processor. |
| Cash | Records applied amount, amount tendered, change, and completing-payment rounding. |
| Cash rounding | Configured increment/mode applied when cash finishes the current balance; the delta is retained on the receipt. |
| Payment reference | Required or optional searchable external ID; Check forces reference collection. |
| CentriPay Cloud | Integrated terminal path with payment intent, transaction polling, and processor response evidence. |
| Tap to Pay | Device-plugin card-present action shown only when available. |
| Card on File | Connected charge against the selected attached-customer vault card. |
| Manual CentriPay/NMI method | Exception record for an already completed outside transaction when explicitly exposed; not a processor send. |
| Split payment | Multiple positive allocations whose combined amount satisfies the balance. |
| Integrated-row protection | Integrated allocations are not removed with the simple X used for manual allocations. |
| Pending processor confirmation | Manual terminal exception state, not verified approval/settlement. |
| Automatic completion | Sale completes when the newly applied allocations reduce the balance to zero. |
| Processor reconciliation | Independent confirmation that the provider approved/settled the transaction represented in CentriPOS. |
| No exact Pay screenshot | The approved Harbor & Hearth manifest rejected /register/sell as rejected-loading; the real admin screenshot remains only on Configure Payment Types. |
Expected result
Only payment types allowed for the current business, location, register, channel, and role appear, and each uses its configured processing behavior.
Troubleshooting
- Check the processor transaction status before retrying an uncertain payment or refund.
- Confirm the terminal, register, amount, and transaction reference all belong together.
- Never include full card numbers or protected credentials in a support request.
CentriPOS API explorer · API Center administration