> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/dineplan/backoffice/tickets/payment-type.md).
# Payment Type
### **Overview**
The Payment Type setting allows you to manage the different payment methods available for processing transactions. You can create payment types and configure their general settings, payment processors, and mappings based on your operational requirements. Existing payment types can also be modified, deleted, searched, or arranged in a preferred order for easier management and access.
### **Screen Elements**
#### **Payment Type List**
| **Screen Element** | **Description** |
| ------------------- | ------------------------------------------------------------------------ |
| Payment Type List | Displays the available payment types. |
| Search | Allows you to search for a specific payment type. |
| Add Payment Type | Opens the screen to create a new payment type. |
| Edit Payment Type | Allows you to modify the selected payment type. |
| Delete Payment Type | Deletes the selected payment type after confirmation. |
| Sort Payment Types | Opens the sorting window to arrange payment types in the required order. |
| Close | Closes the Payment Type screen. |
#### **General Settings**
| **Screen Element** | **Description** |
| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name | Specifies the name of the payment type. |
| Image Path | Specifies the image path associated with the payment type. |
| Account Transaction Type | Specifies the account transaction type. |
| Account | Specifies the account associated with the payment type. |
| Button Color | Specifies the color of the payment type button. |
| Font Size | Specifies the font size displayed on the payment type button. |
| Group | Specifies the group for the payment type. |
| Account Code | Specifies the account code. |
| Toggles | Allows you to configure options such as No Change Display, Display Value in Shift Close, No Refund, Auto Payment, Non Editable, Enable Tip, Requires Authentication, Allow Over Tender, and Active. |
| Tender Type | Specifies the tender type. |
| Payment Tag | Specifies the payment tag. |
| Alternate Names | Specifies alternate names for the payment type. |
| Save | Saves the payment type configuration. |
#### **Payment Processors**
| **Screen Element** | **Description** |
| ------------------ | ----------------------------------------------------- |
| Add | Adds a payment processor. |
| Remove | Removes the selected payment processor. |
| Settings | Provides settings for the selected payment processor. |
| Name | Displays the name of the payment processor. |
| Description | Displays the description of the payment processor. |
### **Working**
#### **Add a Payment Type**
1. Select "Add Payment Type".
2. Enter the required details in "Name" and configure the required settings under "General Settings".
3. Open "Payment Processors" and select "ADD" to configure the required payment processor settings.
4. Open "Mappings" and select "Add" to configure the required terminal, user role, department, and ticket type.
5. Select "Save" to create the payment type.
#### **Edit a Payment Type**
1. Select the payment type that needs to be modified.
2. Select "Edit Payment Type".
3. Update the required general settings, payment processor settings, or mappings.
4. Select "Save" to save the changes.
#### **Delete a Payment Type**
1. Select the payment type that needs to be deleted.
2. Select "Delete Payment Type".
3. In the confirmation message, select "Yes" to delete the payment type.
#### **Sort Payment Types**
1. Select "Sort Payment Types".
2. Drag the payment types to arrange them in the required order.
3. Select "OK" to apply the changes.
### **Use Case**
* Create a new payment type for an additional payment method.
* Configure the account and transaction settings associated with a payment type.
* Configure payment processors for supported payment methods.
* Map a payment type to specific terminals, user roles, departments, or ticket types.
* Modify existing payment type settings when operational requirements change.
* Delete payment types that are no longer required.
* Arrange payment types in a preferred order for easier access.
* Search for a specific payment type when managing a large list.
### **Notes**
* Enter the required "Name" before saving a new payment type.
* "Account Transaction Type" is required when creating a payment type.
* Review the configured payment processor and mappings before saving.
* Deleting a payment type requires confirmation.
* Use "Sort Payment Types" to change the display order of payment types.
* Use "Search" to quickly locate a payment type in the list.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.rbsgo.com/dineplan/backoffice/tickets/payment-type.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
