Manage Terminals

The Terminal Settings module under Settings is where you configure the operational rules that drive in-person and terminal-based payments. It’s split into three sub-pages: Set Tax Amount for regional tax rates that auto-apply to transactions, Device Management for pairing and configuring cloud-based card terminals, and Defined Fields for adding custom data-capture fields to your payment workflows. This guide covers each sub-page in detail, including how Ecrypt’s cloud terminals pair with your dashboard.

---

​

Navigation

From the left sidebar: Settings → Terminal Settings, then expand to reveal:

• Set Tax Amount
• Device Management
• Defined Fields

---

​

Set Tax Amount

A library of tax rates that can be attached to transactions by region. Each tax record is region-tagged so you can apply the right rate based on where the customer is located.

​

Tax Rate List

Top toolbar:

• +TAX button — opens the Add Tax Rate panel.
• FILTERS / CLEAR FILTERS — filter the list.
• Rows per page with pagination.

​

Add Tax Rate

Click ADD TAX RATE to save. Tip: Use Exclusive rates when you want the customer to see “Subtotal + Tax = Total” math on receipts (typical for U.S. sales tax). Use Inclusive when the displayed price already contains the tax, and you just need Ecrypt to report the tax portion separately (typical for VAT/GST-style regions).

---

​

Device Management

This is where you pair, configure, and manage Ecrypt’s cloud-based card terminals. Once paired, a terminal accepts card-present payments triggered from the POS quick action in the sidebar.

​

How Ecrypt Cloud Terminals Work

Ecrypt terminals are cloud-based. After powering on the device and connecting it to either ethernet or WiFi, the terminal displays a 6-digit registration code on its screen. You enter that code into the Ecrypt dashboard when pairing a new device — that’s how the physical terminal is linked to your merchant account in the cloud. Once a terminal is paired, you use the POS button in the sidebar (under ACTIONS) to push card-present transactions to that device. The terminal prompts the customer to tap, dip, or swipe — and the resulting transaction flows back into the dashboard like any other payment.

​

Device List

Top right: +TERMINAL button — opens the New Terminal pairing panel.

​

New Terminal (Pairing a Device)

Header text: “Please have the terminal in front of you to complete this process.” Device Default Configuration — checkboxes that govern how the terminal behaves out of the box. These can be edited later: Enter Tip Amount to Display on Terminal (Converted to dollar amount) — four percentage suggestion buttons that the customer sees if Tip at Time of Sale is enabled: Click ADD TERMINAL to complete pairing. Once added, the terminal is ready to accept card-present transactions from the POS quick action.

​

Edit Terminal

The Edit panel has the same default configuration toggles and tip amount fields as the New Terminal panel. Differences:

• The Terminal Name is shown as read-only at the top — you can’t rename a terminal after pairing.
• There’s no Device Registration Code field — pairing is one-time.
• The save button reads UPDATE TERMINAL.

​

Deleting a Terminal

Click Delete in the Action column to unpair a device. After deletion, the terminal stops responding to POS pushes from your account. To use the device again, power-cycle it, retrieve a fresh 6-digit code, and pair it as a new terminal.

---

​

Defined Fields

Defined Fields let you add custom data-capture inputs to your payment flows — useful for collecting things like invoice numbers, slip numbers, order types, dock locations, or any other custom information that isn’t part of the standard payment form. Once defined, these fields show up wherever payments are taken.

​

Field List

The Add Field form sits to the right of the list and dynamically changes based on the Field Type you pick.

​

Add Field — Common Inputs

​

Field Type Behaviors

Text Adds a free-text input. Shows a Validation Rule dropdown that controls what’s accepted: Checkbox Replaces Validation Rule with a Checkbox fields input where you type labels for each checkbox. Helper text: “You can add up to a maximum of 10 checkbox fields.” Radio Replaces Validation Rule with a Radio fields input where you type labels for each radio option. Helper text: “You can add up to a maximum of 10 radio fields.” Select Replaces Validation Rule with a Select option fields textarea. Helper text: “To add multiple entries, separate each word with a comma. You can add up to a maximum of 50 options.” Click ADD FIELD to save the new field, which then appears in your payment workflows.

---

​

Tips & Best Practices

Tax rates can’t be edited after creation — only deleted. If you need to change a rate, delete the old one and add a new one with the corrected value. Existing transactions that already used the old rate keep their historical tax record intact. Keep the Region label short and consistent (state abbreviations work well) so your staff can quickly pick the right rate at the point of sale. For the cloud-terminal pairing flow, the order matters: power on the terminal first, let it connect to your network, then start the +TERMINAL panel in the dashboard. The 6-digit code is short-lived — if the terminal sits idle on the code screen too long it may refresh, so don’t start the pairing dialog until the code is on the screen in front of you. Be deliberate about the Default Configuration toggles when pairing a terminal. Turning on Default Amount Confirmation and Default Enter Postal Code improves fraud signals (better AVS coverage) but adds friction to every transaction. For high-volume environments (restaurants, retail counters), you may prefer to leave those off and rely on tap/EMV liability shift instead. Default Tip at Time of Sale is essential for service businesses but should be off for retail. The tip percentages you enter for Tip Amount 1–4 are the suggestions the customer sees on the terminal screen. Industry-typical values are 15 / 18 / 20 / 25, but tune these to your business — quick-service often uses 10 / 15 / 20 / 25, while fine dining might use 18 / 20 / 22 / 25. The terminal converts each percent into the equivalent dollar amount for the specific sale. For Defined Fields, pick the field type that minimizes data entry errors. Use Select or Radio whenever the answer comes from a known set of options (e.g., department, dock number, route) so staff aren’t free-typing values that won’t aggregate cleanly in reports. Reserve Text with validation rules (especially Numeric only, Currency, Phone Number) for cases where the value is genuinely free-form. Checkbox is best for multi-select tags like “Curbside / Tip Included / Customer Pickup.” Once a terminal is paired and Defined Fields are set up, in-person sales become a tight workflow: open POS from the sidebar, enter the amount, fill any defined fields, push to the terminal, and let the customer complete payment on the device. The transaction lands in Credit Cards → Transactions like any other payment, with its full audit trail.