> For the complete documentation index, see [llms.txt](https://wallee.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wallee.gitbook.io/documentation/payments/in-store-payments/terminal-configuration.md). # Terminal Configuration Every setting in a terminal configuration, explained in the same order as in the {inject-platform-name} portal. A terminal configuration holds all the settings for your terminals: which payment methods they accept, how receipts work, whether customers can tip, and more. {% hint style="info" %} **One configuration, many terminals:** Several terminals can share the same configuration. Any change you make applies to every terminal that uses it. {% endhint %} ### Find and edit a configuration Go to **Space → Terminals → Configurations** and open a configuration. The overview shows its current settings and the terminals that use it. Click **Edit** to change the settings, then **Save**. You can delete a configuration, but only if no active terminal is using it. ### Configuration Details * **Name:** a name to recognize the configuration (required). * **Time Zone:** the time zone your terminals operate in. * **Default Currency:** by default, the currency comes from the terminal's location. Set a currency here only if you want to override it. ### Maintenance Window The maintenance window is a daily time slot in which your terminals install updates, restart and, if **Automatic Submission** is enabled, send their final balance. * **Maintenance Window Start:** the time the maintenance window begins, in hours and minutes with AM/PM (required). * **Maintenance Window Duration:** how long the maintenance window lasts, for example 2 hours. {% hint style="info" %} Choose a time outside your opening hours, for example at night, so maintenance doesn't interrupt your business. {% endhint %} ### Connectors * **Connector Configurations:** the payment methods your terminals accept, for example Visa, Mastercard or TWINT (required). Only connectors from the processors you configured in your space settings appear here. ### Receipt Sending * **Email Customer Receipt:** sends the receipt to the customer by email. This only works if the transaction includes the customer's email address. * **Terminal Receipt Email Template:** the email template used for these receipts. ### Transaction Configuration * **Automatic Submission:** the terminal automatically sends its final balance during the maintenance window. * **Refunds:** allows refunds directly on the terminal. * **Mail and Phone Orders:** allows mail and phone orders (MOTO) on the terminal. #### Features your acquirer needs to activate **Additional Supported Currencies**, **Dynamic Currency Conversion (DCC)**, **Gift Card** and **Deferred Completion** only work if your acquirer supports them. {% hint style="warning" %} Ask your acquirer to activate the feature **first**, then enable it here. {% endhint %} * **Additional Supported Currencies:** other currencies your terminals can accept. * **Dynamic Currency Conversion (DCC):** lets customers pay in their card's currency. * **Gift Card:** allows gift card transactions such as activation, loading and balance inquiries. * **Deferred Completion:** allows transactions to be completed at a later time. ### Test Mode Acquirer Setup Only needed if you want to run test transactions. You can leave this setting as it is. ### Terminal Configuration * **Language:** by default, the language comes from the terminal's location. Set a language here only if you want to override it. * **Merchant Password:** a 4–15 digit password that protects merchant-only operations on the terminal. ### Terminal API * **API Access:** allows your own applications, such as a cash register system, to start transactions on the terminal. When API Access is enabled, you'll also see: * **Transaction Result Screen:** shows the transaction result on the terminal. * **Active Interfaces:** how your system connects to the terminal: **Cloud API** or **Local Network API**. See Integrations for details. * **Personnel's Attendance:** * **Attended:** staff operate the terminal. * **Unattended:** no staff present, for example at vending machines. * **Attended with amount entry enabled:** staff operate the terminal and can also enter the amount on it. ### Receipt Printing * **Print Receipt:** turns receipt printing on the terminal on or off. When receipt printing is enabled, you can also choose: * **Print Additional Receipts:** * **Merchant Receipt:** prints a copy of the receipt for you. * **Failure Receipt:** prints a receipt when a transaction fails. * **Customer Receipt:** prints the customer receipt only if the customer asks for it. #### Receipt header and footer * **Receipt Address:** prints the address of the terminal's location at the top of the receipt. * **Additional Header Text:** extra text shown below the address. * **Additional Footer Text:** extra text shown at the bottom of the receipt, for example a thank-you message or your opening hours. * **Text Alignment:** the alignment of the header and footer text. {% hint style="info" %} Header and footer texts can be up to 200 characters. You can't use hashtags (#) or curly brackets ({ }). {% endhint %} ### Tip * **Tip Functionality:** asks the customer for a tip after the cashier enters the amount. {% hint style="warning" %} Tipping doesn't work on unattended terminals, such as vending machines. {% endhint %} When tipping is enabled, you can offer predefined tip amounts that the customer can choose with one tap: * **Enable Predefined Amounts:** shows predefined tip amounts on the terminal. * **Tip Amount Type:** **Percentages** (for example 5%, 10%, 15%) or **Fixed amounts**. * **Predefined Tip Amount 1–3:** up to three amounts. The first one is required. Percentages can be between 1 and 100. ### After Sales * **QR Code:** shows a QR code on the terminal after the payment. The customer can scan it to open a page with a digital receipt, which is a good alternative to a printed receipt.