Ticketing

Roles: Super Admin

In the Ticketing section in the management settings of a product, you can configure the product’s ticketing.

If the product feature ticketing is not activated, the following warning message is displayed below the title of this section in Control Center:

Feature not enabled: Changes to the setting(s) below will not take effect unless this feature is enabled

The following fields can be configured.

Adapter for Ticketing

A suitable ticket adapter must be chosen from one of the following options:

• Ticketing Failure Adapter. Fails and does not issue a ticket.
• None. No ticketing.
• Developer Test Adapter. This adapter does not connect to a third-party backend, but instead issues a ticket (120 per adult, 50 per child, 0 per infant) in the name of ACME Corp. This is useful for client developers and for tests on staging.
• VHH Hochbahn Adapter. Ticketing adapter for VHH Hochbahn. It connects to the eos B2B API and issues tickets through that system. See eos.uptrade.

Require passenger names for all passengers

If this setting is enabled, each passenger on a ride must either:

• have a selected public transport ticket passenger option, or
• have both a first name and a last name.

If a passenger does not have the public transport ticket passenger option selected, the ride can only be created when both names are provided.

The public transport ticket option is identified by the passenger option slug public_transport_ticket.