> For the complete documentation index, see [llms.txt](https://help.urbanpiper.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.urbanpiper.com/pos-integrations/foodics/configuring-payment-methods.md).

# Configuring payment methods

Payment methods created in **Foodics** can be **mapped to specific delivery channels** on **UrbanPiper**. For example, you can associate all orders coming from platforms like **Talabat** or **Careem** with a designated payment method (e.g., *Talabat Cash*, *Careem Online*). This helps in **accurate sales reporting and reconciliation**.

***

**How to Create Payment Methods in Foodics**

Follow these steps to create and configure payment methods in the Foodics console:

1. **Login to your Foodics Web Console**.
2. Click on **Manage** from the main navigation.
3. Click on **More**.
4. Select **Payment Methods**.
5. Click on **Add Payment Method**.

A pop-up window will appear with the following fields:

* **Name**: Enter a descriptive name (e.g., *Talabat Cash*).
* **Name Localized (Optional)**: Add a localized name for multi-language support.
* **Type**: Choose **Cash** or **Card** based on how the payment is collected.
* **Code (Optional)**: Input an internal reference code if required.
* **Auto Open Cash Drawer**: Enable this option if you want the cash drawer to open automatically when this method is used at the POS.

6. Click on **Save** to finalize.

{% hint style="info" %}
Once the payment methods are created in Foodics, coordinate with your **UrbanPiper account manager or support team** to **map these methods** correctly to the respective aggregator channels. This ensures proper payment attribution in reporting and analytics.
{% endhint %}


---

# 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.urbanpiper.com/pos-integrations/foodics/configuring-payment-methods.md?ask=<question>&goal=<user_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.