This is a restricted administrative surface containing merchant identifiers and secret-bearing controls. Never place a private key, API password, MID, developer key, webhook signing material, or full terminal identifier in screenshots, tickets, chat, email, public documentation, or CentriAI prompts. The approved Harbor & Hearth capture policy rejected this screen, so this guide intentionally has no screenshot. Work with the merchant account owner and an authorized CentriPOS administrator.

Before you beginConfirm the register, amount, processor or terminal, and customer-safe transaction reference. Never copy card credentials into a support request.

Step by step

  1. Go to Payanywhere Suite → Settings, identified by the Settings icon. Wait for Loading settings… to finish. Confirm the CentriPOS business first; then use each section’s own location/routing selector instead of assuming the top-bar register scopes it.
  2. Read the four cards before editing. In-Person Payments reports Ready or Needs Credentials; Online Payments can report Verified, Retest Needed, Saved, or Not Connected; Billing-Link Fees reports On/Off; Register Rules is labeled Register Level. Some Payments Connected means at least one online or in-person configuration exists—not that all channels or locations are ready.
  3. Create a change record before touching credentials: business, affected location/register/channel, current environment, current non-secret status, requested outcome, processor owner/approver, test plan, rollback plan, and maintenance window. Never copy existing masked/secret fields into the record.
  4. For In-Person Payments, choose the exact Location. Each location can have a different Payments Hub/Payanywhere merchant route, environment, MID, credentials, application-source header, public gateway key, webhook status, and terminal assignments.
  5. Choose Production only for approved live merchant credentials, Sandbox for test credentials and non-live transactions, or Beta / pilot only when the processor explicitly provisions it. Environment and credentials must belong together. Never test with a live customer card in a sandbox/pilot route.
  6. Enter or verify Display Name, MID, Developer Key, API Password, App Source Header, Gateway Public Key, and the branded webhook URL supplied by CentriPOS. A blank API Password on an existing record preserves the saved password; do not enter a placeholder. Public keys are not card data, but still treat merchant configuration as internal.
  7. Choose Save CentriPay™ Cloud only for the selected location. MID and Developer Key are required by the visible control; API Password is required for a new working connection even when the button state cannot prove it. Saving marks an approved branded webhook as approved or another nonempty webhook as pending approval.
  8. Review Selected location, Cloud config, and Paired terminals after save. Configured · webhook approved is configuration evidence, not proof of processor delivery. The reporting panel depends on this location record; an unconfigured location cannot contribute its Payanywhere reporting through this connection.
  9. Review Location Terminal Devices. A terminal can be available to the whole location or assigned to one register and can show Active/Inactive, device type, and account identifier. Use Open Location Terminals to manage pairing from the location record; saving merchant credentials does not pair a terminal.
  10. Tap to Pay on iPhone appears only in the native iPhone app. Save Environment, MID, Developer Key, and API Password for the location first. Activate Tap to Pay launches native enrollment; Check status reports eligibility, authentication, settings load, and environment; Setup info opens Apple/provider education when available. A successful enrollment is device/location evidence, not proof every register can accept a payment.
  11. Use Reset SI Details only as a controlled recovery/decommission action. Confirm the exact location in the browser warning. It clears saved Payanywhere/North credentials for that location and deactivates paired semi-integrated terminals while preserving historical payments. It is destructive operationally even though history remains; reconfiguration and re-pairing may be required.
  12. For Online Payments, treat North embedded checkout and NMI Gateway as separate routes. North can be stored at Universal tenant scope or for one selected settlement location. A missing, inactive, or Standby North route falls back to the current NMI flow where supported.
  13. For North Online, choose routing scope and location when applicable; enter Display Name, Checkout Mode, Checkout ID, Profile ID, private API key, and environment. Choose Standby only during configuration/certification. North-first routing can affect e-cart, online store, and Woo-style checkout only when the corresponding Use toggle is enabled.
  14. Configure North capabilities deliberately: Cards, ACH / Pay-by-Bank, Apple Pay / Google Pay, reusable-token default, and channel toggles are independent. The saved policy requires supported card-not-present authentication/fraud controls. Do not enable wallets, ACH, reusable tokens, or a channel until processor certification, customer consent, legal disclosure, and controlled tests are complete.
  15. Choose Save North Online to persist only the selected tenant/location North route; an entered private key is cleared from the visible field after success. Choose Check North Readiness only when Checkout ID, Profile ID, and a saved/new private key make the route ready. Readiness is not a completed charge or settlement test.
  16. For NMI Gateway (Collect.js), understand the two credentials: Security Key is private and stored encrypted; Tokenization Key is public and used client-side. When a private key is already saved, leave the field blank to keep it or enter a replacement. Changing either credential makes the prior Verified status stale until a new test succeeds.
  17. Choose Test Gateway Connection after entering the intended credentials. Verified and Last tested prove that authentication succeeded at that time. They do not prove e-cart, storefront, billing links, keyed entry, ACH, 3DS, refunds, webhooks, settlement, or every register override. Save Online Payment Settings after the intended test and review the resulting status.
  18. Configure Gateway Risk & Capture only under processor/risk approval. Auto-Capture captures rather than authorizes only; AVS requests address verification; Require CVV requires the security code for supported gateway card transactions; 3D Secure is a tenant-level gateway switch. When 3DS is off here, a register override cannot force it on.
  19. Treat Processing Rate and Per-Transaction Fee as manual reference values only. CentriPOS does not currently synchronize processor pricing into them, and in-person Payanywhere terminal pricing is not separately stored here. They do not add a customer surcharge or determine processor billing.
  20. Enable PaymentsHub Reporting Add-On only for an NMI Gateway merchant that has the approved CentriPay reporting MID. Environment, Developer Key, Auth Password, App Source, and fee-collection mode must match that reporting account. CentriPOS caches the returned account identity internally and keeps NMI deposits classified separately from Payanywhere deposits.
  21. For Billing-Link Fees, understand the narrow scope: the Credit Card and ACH / Bank toggles add percentage or flat convenience fees only to the public franchise billing-link flow. They do not configure terminal surcharge/edge pricing, e-cart fees, storefront fees, processor pricing, or ordinary register payments.
  22. Before Save Billing-Link Fees, confirm the screen finished loading the existing online gateway settings. This control uses the same tenant gateway-settings save payload as the Online Payments form, so avoid changing unrelated online fields in the same session. Enter a reviewed nonnegative percentage or flat value and verify legal/card-network disclosure rules.
  23. Open Register Rules for a read-only inventory. Review Total registers, Custom gateway / 3DS, and ACH enabled; filter by location or search register/location. Rows can show Custom gateway keys, 3DS forced on/off, ACH enabled, or Uses storefront defaults. These counts and badges are configuration indicators, not transaction-success evidence.
  24. Choose Edit register settings or Open Locations & Registers to change one register. Register-specific NMI keys, 3DS behavior, and ACH availability live on the register record. A register with no custom gateway/3DS and ACH off is counted as using storefront defaults. Tenant 3DS off remains a kill switch even if a register says forced on.
  25. Run a controlled test matrix after an approved save: each affected location/register; PAX or semi-integrated terminal; Tap to Pay iPhone; keyed card; ACH; e-cart; online store; Woo-style route; billing link; authorization/capture; AVS/CVV/3DS; approved and declined callbacks; receipt match; refund/void; batch; deposit; register closure; and reporting source classification. Use test credentials/data where appropriate.
  26. For a failed or misrouted payment, stop retries until checking the CentriPOS payment intent/transaction, processor portal, configured location/register route, environment, terminal assignment, gateway test state, webhook delivery, batch, and deposit. Preserve only safe references. Never switch to another tenant’s MID or credentials as a shortcut.
  27. The screenshot boundary is intentional: the Amelia Grant Harbor & Hearth manifest records this route as rejected-sensitive-credentials because it contains MID, developer key, API password, public key, webhook, terminal pairing, and destructive reset controls. No screenshot was retained, and this guide does not invent or expose one.

Screen and contract reference

Control or areaWhat it means
Settings navigation iconExact Payanywhere Suite icon for Payment Settings.
Some Payments ConnectedAt least one stored online or in-person configuration exists; not full readiness.
In-Person PaymentsLocation-scoped Payments Hub/Payanywhere credentials, webhook, reporting eligibility, terminals, and Tap to Pay.
LocationExplicit merchant-routing scope for in-person settings; independent from the top-bar context.
EnvironmentProduction, Sandbox, or Beta / pilot; must match the credential set.
MID / Developer Key / API PasswordRestricted merchant authentication values; never expose them.
App Source HeaderProcessor-provided application identity used by semi-integrated flows.
Gateway Public KeyPublic tokenization/configuration key stored on the selected location.
Webhook statusApproved, pending, or unconfigured configuration evidence; not delivery proof.
Location Terminal DevicesRead-only summary with link to pairing in Locations & Registers.
Tap to Pay on iPhoneNative-only enrollment/status/education surface using selected location credentials.
Reset SI DetailsConfirmed destructive location reset that clears credentials and deactivates paired SI terminals while preserving history.
North routing scopeUniversal tenant route or one selected settlement location.
StandbySaved North configuration that should not take first routing priority.
North-firstActive priority route for explicitly enabled online channels.
North readinessRequired route identifiers plus saved/new private key; not charge proof.
NMI Security KeyPrivate encrypted credential; blank preserves an existing saved value.
NMI Tokenization KeyPublic Collect.js key used for client-side tokenization.
Retest NeededPreviously verified credentials changed in the current form.
Test Gateway ConnectionAuthentication check for the supplied NMI credentials.
Auto-CaptureCapture immediately instead of authorization-only behavior.
AVS / CVV / 3DSGateway card-not-present risk controls; tenant 3DS off blocks register forcing.
PaymentsHub Reporting Add-OnOptional NMI reporting/deposit link for an approved reporting MID.
Gateway Fee ReferenceManually entered processor-cost reference; not a customer fee.
Billing-Link FeesFranchise public billing-link convenience fees only.
Save Billing-Link FeesUses the shared tenant gateway-settings payload, so unrelated online fields must remain unchanged.
Register RulesRead-only tenant inventory of register gateway/3DS/ACH overrides.
Uses storefront defaultsNo custom gateway keys, no explicit 3DS override, and ACH off for that register.
No screenshotExact route intentionally rejected by the Harbor & Hearth safe-capture policy because secrets and destructive controls are present.

Expected result

The intended merchant, location, terminal, and processing options report a healthy connection and a controlled payment follows the new mapping.

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.

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.