> 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/integrations/plugins/hospitality-plugins.md).

# Hospitality Plugins

### Introduction

{inject-platform-name} is seamlessly integrated into a variety of leading hospitality systems.\
The key advantage: **a complete omni-channel payment solution** that connects in-person payments, e-commerce channels, and tokenized transactions across all platforms.

This enables merchants to deliver a unified guest experience — whether payments occur at the front desk, in a restaurant, at the bar, or online.

***

### Integrated hospitality systems

| Hospitality System                                                                                                          | Integration Type       | Supported Channels                                       |
| --------------------------------------------------------------------------------------------------------------------------- | ---------------------- | -------------------------------------------------------- |
| [Opera Cloud](/documentation/payments/integrations/plugins/hospitality-plugins/opera-cloud.md)                              | Cloud-based PMS        | <ul><li>E-Commerce,</li><li>POS,</li><li>Token</li></ul> |
| **Oracle Opera On-Premise**                                                                                                 | On-premise PMS         | <ul><li>E-Commerce,</li><li>POS</li><li>Token</li></ul>  |
| [Oracle Symphony Order @Table Service](/documentation/payments/integrations/plugins/hospitality-plugins/oracle-symphony.md) | POS for F\&B           | <ul><li>POS</li><li>Token</li></ul>                      |
| [Oracle Symphony Counter](/documentation/payments/integrations/plugins/hospitality-plugins/oracle-symphony.md)              | POS for Quick Service  | <ul><li>E-Commerce,</li><li>POS</li><li>Token</li></ul>  |
| [Protel (Air)](/documentation/payments/integrations/plugins/hospitality-plugins/protel.md)                                  | PMS & POS combinations | <ul><li>E-Commerce,</li><li>POS</li><li>Token</li></ul>  |
| [Protel On-Premise](/documentation/payments/integrations/plugins/hospitality-plugins/protel.md)                             | PMS & POS combinations | <ul><li>E-Commerce,</li><li>POS</li><li>Token</li></ul>  |

***

### Why omni-channel matters

In hospitality, guest interactions span multiple touchpoints:

* **Booking & reservations** online or via call center (e-commerce channel)
* **On-site spending** at restaurants, bars, or outlets (POS transactions)
* **Post-stay charges** (tokenized follow-up transactions)

With {inject-platform-name}, all these flows are connected — ensuring consistent reporting, a single reconciliation process, and a smooth guest experience.

### Connecting Oracle systems

Oracle Opera and Simphony connect through the OPI interface. See [Hosted OPI / OPI on Premise](/documentation/payments/integrations/plugins/hospitality-plugins/hosted-opi-opi-on-premise.md) for the certificate, chain code and interface configuration that both share.

### Related topics

* [Terminal Configuration](/documentation/payments/in-store-payments/terminal-configuration.md) — setting up the terminals used at the front desk and in outlets.
* [Tokenization](/documentation/payments/integrations/features/tokenization.md) — how the tokens behind post-stay charges work.