> For the complete documentation index, see [llms.txt](https://docs.saferpay.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.saferpay.com/home/master/web-shop-plug-ins/opera-pms.md).

# Opera PMS

Saferpay offers a connection towards the Opera cloud PMS. This connection is handled in part through our partner [Gustaffo](https://gustaffo.com/), to enable a seamless integration of E Commerce through Saferpay and also POS transactions through Worldline acquiring via the TIM API.

## Requirements

{% hint style="info" %}
Please [contact our sales team](/home/integration-guide/support.md#worldline-sales-team), or your account manager for the Opera PMS onboarding and setup.
{% endhint %}

In order to use this solution, you need access to the following things:

* Worldline
  * Access to [Secure Card Data](/home/integration-guide/licences-and-interfaces/secure-card-data.md)
  * Access to [Omnichannel](/home/integration-guide/licences-and-interfaces/omni-channel.md) with a corresponding setup
  * Access to the [Saferpay Management API](/home/interfaces/management-api.md)
  * A Saferpay MOTO terminal
  * A Saferpay Secure PayGate terminal
  * Worldline or Payone Acquiring for cards
  * Access to the Worldline TIM API
    * An EP2 terminal via TIM API
* Gustaffo middleware
* An Opera license with OPI access

## Available functions

| Opera                             | Saferpay                                                                                                        |
| --------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| Pre-Authorization Transaction     | [Pre-Authorization](/home/integration-guide/payment-methods/general-and-special-cases.md#pre-authorizations)    |
| Authorization Release             | [Cancel](/home/integration-guide/licences-and-interfaces/capture-and-daily-closing.md#cancel)                   |
| Sales Completion Transaction      | [Capture](/home/integration-guide/licences-and-interfaces/capture-and-daily-closing.md)                         |
| Sale/Purchase Transaction PMS     | --                                                                                                              |
| Refund Transaction                | [Refund](/home/integration-guide/licences-and-interfaces/transaction-interface/refunds.md)                      |
| Void Transaction                  | --                                                                                                              |
| Void of Refund Transaction        | --                                                                                                              |
| End-Of-Day Settlement             | [Daily batch close](/home/integration-guide/licences-and-interfaces/capture-and-daily-closing.md#daily-closing) |
| GetToken Transaction              | --                                                                                                              |
| GetToken (Bulk)                   | --                                                                                                              |
| Request PayByLink URL             | [Secure PayGate via Management API](/home/interfaces/management-api.md)                                         |
| Request PayByLink Payment Details | [Secure PayGate via Management API](/home/interfaces/management-api.md)                                         |


---

# 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://docs.saferpay.com/home/master/web-shop-plug-ins/opera-pms.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.
