> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/feature-references/features-and-products-references/cullinan-financial-transaction-services/configuring-cullinan-financial-transaction-interface/configuring-the-cullinan-financial-transaction-interface-feature.md).

# Configuring the Cullinan Financial Transaction Interface Feature

Configuring the Cullinan Financial Transaction Interface feature encompasses:

* Enter the sales mode in the User Panel Function to scan or manually enter the third party product provider information.
* Enter the sales mode in the Soft Key Function to scan or manually enter the third party product provider information.
* In Config Client (Configuration Client), under Payment Controller in the Third Party Product Configuration menu on the POS side configure the connectivity to Cullinan.
* Enabling or disabling the Third Party Product Provider feature.
* The URL populates with default data. Create a OTP (one-time password) to setup or change the URL.
* Create a custom error instruction message to print on receipts for customers.
* Create a custom error instruction message to display on the POS for the cashier.
* Configure one or more Cullinan product ID ranges along with a field to assign a department to each range. There are no reserved Conexxus Product Codes for third party products, so list all departments.
* Determine if the user can view or edit the configuration.


---

# 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://commanderhelp.verifone.com/feature-references/features-and-products-references/cullinan-financial-transaction-services/configuring-cullinan-financial-transaction-interface/configuring-the-cullinan-financial-transaction-interface-feature.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.
