# Setup

Secutix is your ticketing backend. The Wallet Crew adds the wallet layer on top. This setup is about getting a reliable, real-time pipe between both systems. You configure credentials in Wallet Crew. Your Secutix CSM enables the Secutix side.

### What you need

You need a Secutix environment that can expose ticket data over web services. You also need a technical user that Wallet Crew can use to read that data.

* A Secutix instance with **web services** enabled.
* A **technical user** (operator) for API calls.
* Your Secutix CSM to enable the connector and configure webhooks.

{% hint style="info" %}
Ask your secutix CSM to get and validate these values.
{% endhint %}

### Who does what

Wallet Crew teams usually handle tenant-side enablement. Secutix teams usually handle webhook activation and shop/email changes.

* **You / your integrator**: choose the distribution pattern and validate end-to-end flows.
* **The Wallet Crew**: enable the connector, help validate mapping and pass behavior.
* **Secutix CSM**: enable webhooks and assist with ticket shop and email templates.

### Setup steps

{% stepper %}
{% step %}
**Enable the connector**

Ask The Wallet Crew team to enable the **Secutix connector** for your tenant.
{% endstep %}

{% step %}
**Configure the connector in Wallet Crew**

Open the Secutix integration settings in the admin console. These values define how Wallet Crew authenticates and which Secutix environment it calls.

<p align="center"><a href="https://admin.thewalletcrew.io/tenant/~/integrations/secutix" class="button secondary" data-icon="chevrons-right">Open Secutix General settings page</a></p>

<figure><img src="/files/7rHpO3ztocuyvUvFOJWj" alt="Secutix Wallet Crew Integration configuration screen"><figcaption></figcaption></figure>

* **Secutix URL**: web services endpoint
* **Operator**: technical user
* **Institution**: your institution identifier
* **Partner**: keep `Neostore`
* **Secret**: operator password

{% hint style="info" %}
Confirm these values with your Secutix CSM.
{% endhint %}

**Typical URL formats**

* Production: `https://xxx.ws.secutix.com`
* Test: `https://xxx.pp-ws.secutix.com`

When you click **Save**, Wallet Crew tests the connection to **Secutix**. If the test fails, an error message is shown.
{% endstep %}

{% step %}
**Enable the integration in Secutix**

Ask your Secutix CSM to handle the Secutix-side work.

* Validate configuration.
* Configure the **webhook** that notifies Wallet Crew of ticket changes.
* Enable / deploy the **ticket shop** integration.
* Add the **“Add to Wallet”** link in order confirmation emails.
  {% endstep %}
  {% endstepper %}

If you haven’t configured your ticket layout yet, start with [Wallet pass template & field mapping](/connect/ticketing/secutix/wallet-pass-template-and-field-mapping.md). If you’re ready to ship the end-user flow, go to [Distribution](/connect/ticketing/secutix/distribution.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.thewalletcrew.io/connect/ticketing/secutix/setup.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.