Setup

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

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.

Ask your secutix CSM to get and validate these values.

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

1

Enable the connector

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

2

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.

Open Secutix General settings page

• Secutix URL: web services endpoint

• Operator: technical user

• Institution: your institution identifier

• Partner: keep Neostore

• Secret: operator password

Confirm these values with your Secutix CSM.

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.

3

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.

If you haven’t configured your ticket layout yet, start with Wallet pass template & field mapping. If you’re ready to ship the end-user flow, go to Distribution.