Open the intended customer’s Payment methods tab. It can combine NMI Gateway vault cards, CentriPay Online card or ACH tokens, and Payanywhere terminal tokens. The row identifies a reusable token; it is not proof of current authorization, available funds, ownership, or successful future payment. Never put a full card number, bank account, CVV, PIN, password, or processor credential in customer notes or support screenshots.
Step by step
- Open the exact Customer Profile and choose Payment methods. Confirm the customer name and at least one independent identity field before reviewing or charging any saved method. A merge can reassign token rows to the surviving customer, so re-verify identity after duplicate cleanup.
- Read the Payment Methods source label. NMI Gateway Vault is a gateway vault card. CentriPay Online Card Token and CentriPay Online ACH Token come from supported online checkout. Payanywhere Terminal Token comes from an eligible in-person terminal save. One customer can have tokens from more than one connected provider.
- Identify a row by safe evidence: card brand or generic Card, last four digits when returned, expiration month/year when returned, provider label, and saved origin. “Card details pending” means the token row lacks last-four display data; do not guess which physical card it represents.
- Read origin text for CentriPay Online and Payanywhere tokens. It can show the source sale number and saved date, online-checkout date, or terminal-save date. NMI Gateway rows do not currently show equivalent origin text in this panel. Origin is audit context, not cardholder authentication.
- Understand connection states. With no active CentriPay payment connection and no saved rows, the panel says No CentriPay payment connection is active and offers Open CentriPay Hub. With connected providers but no customer tokens, it identifies NMI Gateway, Payanywhere, and/or CentriPay Online as active and explains what will appear after a method is saved.
- Choose Open CentriPay Hub or Review CentriPay setup only to inspect provider configuration. A visible saved token can outlive a current connection state; do not interpret a row by itself as proof that the provider is ready to process a new payment.
- Use Add Card only when it appears. This button is tied specifically to an NMI Gateway tokenization key; it does not manually create a Payanywhere or CentriPay Online token. The embedded Collect.js fields are supplied from secure.nmi.com for Card Number, Expiration, and CVV, then return a one-time token to the NMI vault workflow.
- Ask the customer for permission before collecting a new card. Enter Card Number, Expiration, and CVV only in the embedded provider fields and choose Save Card once. CentriPOS sends the returned token with the selected customer ID; it should not receive or display the full card credentials. Cancel closes the form without intentionally saving a method.
- Wait for Card saved to vault and reopen Payment methods. Verify brand, last four, expiration, NMI Gateway Vault label, and the correct customer. If tokenization or vault creation fails, read the error and retry only after correcting the provider or card-entry issue; never paste credentials into another field.
- Choose Make primary on the intended nonprimary row to set its is_default state. The filled star marks the current primary token. Primary is a CentriPOS preference for supported payment selection; it does not charge the method, move funds, make it valid, or override a workflow’s provider compatibility.
- At checkout or another authorized payment workflow, select the exact customer and supported saved payment method. Compare provider, brand/type, last four, expiration, amount, sale, and customer authorization before submitting. Follow every gateway, terminal, ACH, verification, or decline prompt; a saved token does not bypass processor controls.
- Do not assume every token works in every channel. NMI Gateway, CentriPay Online, and Payanywhere tokens have different providers and token types. The payment screen must explicitly offer the row for that transaction; otherwise use the supported provider path instead of copying or transforming the token.
- To remove a method, choose its trash icon and read Remove saved card?. The dialog names the provider and last four. For an NMI row, CentriPOS requests removal from the NMI Gateway vault. For a Payanywhere row, it removes the local reusable terminal token through the Cloud token workflow. Other non-NMI token rows use the gateway deletion workflow and should be verified after removal.
- Choose Remove only when the customer or authorized business process requires the token to stop being available. Removing a token does not void, refund, reverse, or erase prior payments, receipts, processor transactions, chargebacks, or accounting records. It also does not prove the underlying physical card or bank account was closed.
- After removal, wait for success and refresh the profile. Confirm the exact row is absent and that another intended primary token is marked when applicable. If removal fails, leave the row in place, capture only safe provider/last-four/error context, and resolve the provider connection; do not repeatedly submit destructive requests.
- After any save, primary change, customer merge, or removal, test only through an authorized controlled payment or the provider’s supported verification path. Confirm the resulting receipt and processor transaction reference without exposing full payment credentials.
- No exact safe Harbor & Hearth Payment methods screenshot is currently assigned to this article. The help center intentionally uses no screenshot rather than an invented card, fake last four, another tenant’s payment token, or a mismatched CentriPay screen.
Screen and contract reference
| Control or area | What it means |
|---|---|
| Payment methods tab | Customer Profile section listing safe reusable payment-token references. |
| NMI Gateway Vault | NMI customer-vault token created through gateway tokenization. |
| CentriPay Online Card Token | Saved online-checkout card token from the North/CentriPay Online provider. |
| CentriPay Online ACH Token | Saved online-checkout bank token; it is not a card. |
| Payanywhere Terminal Token | Reusable local reference captured from a supported in-person terminal payment. |
| Brand / Card | Safe card-type label returned with the token. |
| Last four | Safe identifying digits when returned; insufficient by itself to establish ownership. |
| Card details pending | No usable last-four display value is stored on the token row. |
| Expiration | Month and year shown only when returned with the saved method. |
| Saved origin | Available sale/date or provider/date context for Payanywhere and CentriPay Online tokens. |
| Provider-active badge | Indicates a configured active connection, not a successful future charge. |
| Open CentriPay Hub | Opens payment-provider setup when no connection is active. |
| Review CentriPay setup | Opens configuration when an additional or missing provider needs review. |
| Add Card | Shown only when an NMI tokenization key exists. |
| Collect.js fields | NMI-hosted embedded Card Number, Expiration, and CVV inputs that return a token. |
| Save Card | Submits the NMI token for vault creation against the current customer. |
| Make primary | Sets the selected token as CentriPOS’s preferred saved method. |
| Primary star | Marks the row whose is_default state is true. |
| Payment compatibility | A token is usable only where the active payment workflow supports its provider and token type. |
| Trash | Opens provider-aware removal confirmation for the exact token row. |
| Remove NMI card | Requests deletion from the NMI Gateway vault. |
| Remove Payanywhere token | Removes the local reusable terminal token through the Cloud workflow. |
| Remove other token | Uses the configured gateway deletion workflow; verify the row disappears and provider state is consistent. |
| Removal boundary | Does not refund, void, reverse, delete receipts, or erase processor/accounting history. |
| No active connection | Empty state when no supported provider connection and no saved token rows exist. |
| No saved methods | Connected provider state with no customer token rows yet. |
| Security boundary | Full card/bank credentials and CVV belong only in secure provider fields, never CentriPOS notes, screenshots, or support messages. |
| No exact screenshot | The article remains text-only until a safe screen-matched Harbor & Hearth capture exists. |
Expected result
The token row belongs to the verified customer and shows only safe provider, type/brand, last-four, expiration, origin, and primary state; NMI collection occurs only in provider-hosted fields; an authorized controlled payment uses a compatible provider path; removal deletes only the intended reusable token without implying a refund or history deletion; and no protected credential appears in CentriPOS notes, screenshots, or support content.
Troubleshooting
- Search by more than one identity field before creating or merging a customer.
- Confirm the selected customer, company, or household before changing balances or associations.
- Do not place payment credentials or unnecessary private information in notes.
CentriPOS API explorer · API Center administration