This documentation is currently under development. Certain sections are not yet complete and will be added shortly.
Ctrlk
HomeDocumentationRessources
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Setup

Enable The Wallet Crew Secutix connector, configure Secutix web services access, and activate webhooks + email/shop distribution.

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

What is needed

The setup requires a Secutix environment that can expose ticket data over web services, and a technical user that The Wallet Crew can use to read that data.

  • A Secutix instance with web services enabled.

  • A technical user (operator) for API calls.

  • The Secutix CSM, to enable the connector and configure webhooks.

Ask the Secutix CSM to provide and validate these values.

Who does what

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

  • The brand or its 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

1

Enable the connector

Ask The Wallet Crew team to enable the Secutix connector for the tenant.

2

Configure the connector in The Wallet Crew

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

Open Secutix General settings page

Secutix connector configuration screen in The Wallet Crew, with URL, operator, institution, partner, and secret fields
Check every field against the values supplied by the Secutix CSM before saving.

  • Secutix URL: web services endpoint

  • Operator: technical user

  • Institution: the institution identifier

  • Partner: keep Neostore

  • Secret: operator password

Confirm these values with the Secutix CSM.

Typical URL formats

  • Production: https://xxx.ws.secutix.com

  • Test: https://xxx.pp-ws.secutix.com

On Save, The Wallet Crew tests the connection to Secutix. If the test fails, an error message is shown.

3

Enable the integration in Secutix

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

  • Validate configuration.

  • Configure the webhook that notifies The Wallet Crew of ticket changes.

  • Enable / deploy the ticket shop integration.

  • Add the “Add to Wallet” link in order confirmation emails.

When the ticket layout is not configured yet, start with Wallet pass template & field mapping. When the end-user flow is ready to ship, go to Distribution.

Last updated