Go to Admin → Payment types only with settings.payment_types authority. Credentials, merchant IDs, API keys, terminal identifiers, and connection details are sensitive. The attached Harbor & Hearth screenshot is a real read-only capture showing provider names and not-configured states only; it exposes no credentials or transactions.

Harbor & Hearth Payment Types screen showing available payment providers and safe configuration status in CentriPOS
Harbor & Hearth live CentriPOS demo
Before you beginUse an authorized administrator account and confirm the business shown in the top bar. Record the previous value before changing a live operational setting.

Step by step

  1. Open Admin → Payment types. Read the page’s central distinction: Integrated Payment Types are managed by connected services; Custom Payment Types are manual methods that are not driven by an integrated service.
  2. Review each integrated provider card: Payanywhere for connected terminals/card-present payments, NMI Gateway for gateway/ecommerce processing, PayTomorrow for financing reporting, and Katapult for lease-to-own reporting.
  3. For each card, compare Reporting payment type, Status, and Active connections. A provider is Active only when an active connection and an enabled matching reporting payment type both exist. The reporting row alone does not mean processing is connected.
  4. Interpret nonactive states precisely: Needs attention means saved/active service details are incomplete or its reporting row is disabled; Needs reporting type means a connection exists without an enabled matching row; Payment type only means the row exists without active connections; Disabled means the row exists disabled with no active connection; Not configured means neither was detected.
  5. Open Active connections only to inspect the location-level connection summary. Payanywhere derives it from active terminal devices; NMI uses master gateway settings or register overrides; financing uses provider settings on registers. Do not copy identifiers or credentials into support material.
  6. Use Credentials to open the provider’s dedicated secure setup page: in-store CentriPay for Payanywhere, online CentriPay for NMI, or Financing Apps for PayTomorrow/Katapult. Use Method to open the mapped payment-type detail. These are separate controls because a processor connection and reporting row solve different problems.
  7. Under Custom Payment Types, review the name, System status, POS/WEB badges, description, enabled switch, and row menu. An enabled custom row is still manual unless another documented integration actually invokes a processor.
  8. Choose Add type to select a preset or create a custom method. Presets include Cash, card labels, BNPL, digital wallets, Gift Card, Store Credit, Bank Transfer, QR Code, and Other, but choosing a preset creates a payment-type definition—not the third-party integration named by its label.
  9. Enter a unique, cashier-readable Name and optional Description. Choose POS and/or WEB channels, then choose at least one active location when locations exist. If every active location is selected, CentriPOS stores it as unrestricted; a subset becomes an explicit location list.
  10. Choose Add payment type. Success reports Payment type added and opens its detail page. If the new name overlaps an integrated alias such as CentriPay Cloud/Gateway, PayTomorrow, or Katapult, it can be classified into the integrated section; use the canonical reporting name intentionally.
  11. On the detail page, verify Payment information: name, immutable underlying type label, description, POS/WEB channels, and Locations. A Pay-screen method requires enabled status, POS support, current-location assignment, and—when noncash—Show in manual payment list.
  12. For noncash types, set Sell screen visibility. Keep manual exposure off for integrated/reporting/import-only rows unless cashiers truly need to record an already-completed outside transaction. Turning it on does not make CentriPOS call that provider.
  13. Configure Payment reference when the cashier must enter an external ID. Check forces reference collection. For other custom types, enable Collect a payment ID at checkout and set the exact Field label, Placeholder, and Instruction line staff can verify.
  14. For Cash, choose the rounding increment used when cash finishes a balance and decide whether to Conceal totals during register review. Conceal totals hides cash takings until the register is closed; it is not a substitute for permissions or reconciliation.
  15. For a noncash type, treat Gateway URL as an optional external-system endpoint field, not proof that a complete authenticated processor flow exists. Use the supported CentriPay/financing configuration for those named integrations. Terminal pairing for PAX/CentriPay/EPX-like rows is managed per register in Locations & registers.
  16. Use Enabled to make the type eligible under its other filters, then Save payment type. Success reports Payment type saved and refreshes POS/refund choice caches. Test from each allowed and disallowed location/channel; verify checkout visibility, reference requirement, receipt label, reports, refunds, register closure, and accounting export.
  17. Disable a custom type when it should stop appearing while preserving the definition/history. Edit can update name, description, channels, and locations. Delete is unavailable for system rows and permanently removes a custom row after confirmation; prefer disable when historical/reporting continuity is uncertain.

Screen and contract reference

Control or areaWhat it means
Integrated Payment TypesConnected-service cards for Payanywhere, NMI Gateway, PayTomorrow, and Katapult.
Reporting payment typeCentriPOS row used to label/report the service’s transactions.
ActiveBoth an active service connection and enabled matching reporting row exist.
Needs attentionSaved or active service setup exists but required activation/credentials or enabled reporting row is missing.
Needs reporting typeActive connections exist without an enabled matching payment row.
Payment type onlyEnabled reporting row exists without an active service connection.
DisabledMatching payment row exists disabled with no active service connection.
Not configuredNo active connection or matching reporting row detected.
Active connectionsLocation summaries derived from terminals, gateway master/overrides, or register financing settings.
CredentialsNavigates to the provider-specific secure setup; never expose the values.
MethodOpens the mapped reporting payment-type detail.
Custom Payment TypesManual definitions not currently classified as integrated provider rows.
Add typePreset search or custom-definition entry point.
PresetSeeds name/description only; it does not connect the named processor.
POS / WEBChannel filters; empty/unrestricted behavior differs from explicitly excluding POS.
LocationsAll active locations stores no restriction; a subset stores explicit IDs; zero is rejected when locations exist.
SystemProtected row whose delete control is unavailable.
EnabledMaster eligibility switch; other channel/location/manual-list filters still apply.
Show in manual payment listNoncash control exposing a manual cashier record option.
Collect a payment IDAdds an amount/reference step at checkout; Check forces it.
Field label / Placeholder / Instruction lineCashier-facing reference guidance.
RoundingCash increment applied when cash completes the balance.
Conceal totalsHides cash takings during open-register report review until closure.
Gateway URLOptional external URL field; not evidence of credentials, authentication, or successful processing.
Terminal integrationDirects pairing to Locations & registers.
Save payment typePersists configuration and refreshes payment/refund choice queries.
Disable vs deleteDisable preserves the definition; delete permanently removes a non-system row.
Real Harbor & Hearth screenshotRead-only Admin → Payment types capture with unconfigured provider statuses and no sensitive credentials, identifiers, or transactions.

Expected result

The payment type appears only at its allowed locations and channels, collects the intended reference information, and completes the controlled test correctly.

Troubleshooting

  • Confirm you are changing the intended business and location before saving.
  • Record the previous setting when a change affects live selling, payments, tax, or integrations.
  • Use a controlled test record after saving before rolling the setting out broadly.

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.