Ovatic

(Discover quick explanations of all features in our general features overview)

✅ Event & production content updater ✅ Event prices updater ✅ Event availability checker ✅ Cross-sell event content updater ✅ Cross-sell event prices updater ✅ Cross-sell event availability checker ✅ Data import: Sales data + visitor accounts + visitor tags ❌ Opt-in sync

❌ SSO (log-in & sign-up via ticketing system webpage), or ✅ Peppered online accounts (log-in & sign-up via Peppered webpage) ✅ Obtain visitor tags of visitor after login ✅ Write Visitor tags to Ticketing system account ✅ My Account: Purchased events ✅ My account: Wish list ✅ My account: Cancellation from My events page ✅ Peppered E-Tickets + barcodes in My Account ✅ Peppered E-ticket sharing ✅ Peppered Secure E-tickets (visible X time before event start) ✅ Peppered Secure E-tickets (SMS verification) ✅ Peppered Secure E-tickets (Dynamic barcodes) ❌ Link to Box-office e-tickets from My Account ✅ Time slot request/handout in account

✅ Peppered purchase path ✅ Payment: personal balance ✅ Payment: Voucher (native to ticketing system) ✅ Purchase vouchers (article type in Peppered) ✅ Purchase merchandise (article type in Peppered) ✅ Purchase membership (article type in Peppered) ✅ Purchase donation (article type in Peppered) ✅ Purchase Cross-sells linked to regular events ✅ Purchase Cross-sells stand alone ✅ Handle Payment link from Box-office ✅ Waiting list ✅ Peppered Discount codes (unlocking price types) ❌ Ovatic Discount codes

After sharing an e-ticket, the information of the invitee is added to the order in Ovatic

More information about ticket sharing

It is now possible to register waiting list requests directly in Ovatic. When a performance has the status "waiting list" in Peppered, a new pop-up form can be displayed:

Requests can only be filled out after login. The visitor's account details are automatically sent along.

In version 178 we took several steps to make e-tickets more secure. We are taking this even a step further for Ovatic users: the QR code on the ticket is replaced by a new barcode every 20 seconds. In this way we prevent that a screenshot of the QR code can be made in order to pass the ticket on to someone else. Read more about it in the 'Secure e-tickets' manual.

It is now possible to configure cancellation options per event in Ovatic and offer a cancellation form in the personal My Agenda.

First activate the options in Ovatic:

Now a new button (change / cancel) will automatically show in the top right your personal Agenda:

This button will request all cancellation options for each event in your personal Agenda and display the options:

After submitting, the cancellation is inmediately processed by Ovatic.

Cancellation options:

In this first phase we support 2 options:

The option "refund to my bank account" is currently not possible, due to the fact that Ovatic doesn't have enough information to do so, since the payment was handled by Peppered.

In a future iteration, Peppered will handle a full refund using a new Mollie API procedure.

To be continued...

The "price & Halls" updater in Peppered in the event module will now also check if the event is connected to the correct hall, using the unique Ovatic seatmap ID. For this to work, make sure every hall in Peppered has the Ovatic "box office ID" of that seatmap filled in. When updating prices, Peppered will also check the seatmap ID in Ovatic and make sure the event has the same hall in Peppered.

To activate this, halls in Peppered need an Ovatic box-offie ID, and the feature needs to be switched on in the "event halls updater" in the Peppered control panel.

Regular prices and availability checks do not take into account that different price types can have different maximum amount of tickets available. It only checks the total amount of available seats per rank, so ranks can be sold out, but that does not differentiate between price types.

If you want to work with different availability for a price type, you need to do the following:

Now the maximum available amount of tickets for a specific price type will be checked, and a warning pops up when the limit is exceeded.

Cross-sell events are now synced and added to the e-tickets, ensuring that visitors receive very complete e-tickets for their night out, without having to download or open multiple e-tickets. This should also help with scanning at the door because it provides a nice overview on one single page.

The recurring payment method is a periodical direct debit (NL: doorlopende machtiging) option for visitors. During the order process the visitor can agree to a recurring payment of a special product/membership, which will trigger a special iDeal payment.

When using this payment method, the full amount of the order (including the membership and all events that might be in the order) will be paid with iDeal and after the payment the IBAN number of the bank account is retrieved from the PSP and sent to the box-office system when finalizing the order. The order will be booked as a recurring payment, and Ovatic will do the rest.

Set-up

The recurring payment method is a dynamic payment method, which means the payment option will only be shown in specific situations.

This payment method is only active when the visitor agrees to the recurring payment. This can be done by setting the toggle to "yes" in a special type of membership product.

Go to "products" in your dashboard and create a new product with type "membership with toggle". This will show the toggle when ordering the product. The "Additional description" is a new text area for the explanation next to the toggle.

When the product is made, the recurring payment method also needs to be added in

CONTROL PANEL > PAYMENT AND DELIVERY METHODS

In this example, ID 51 is used so Ovatic knows this should result in a recurring payment.

Obviously, the payment ID should also be xreated in Ovatic.

TIP: in order to test this feature, create a new page on your website, and add the "product" part to the page, and select this new product to display it on the page. Also leave the "order option" checkbox empty in the product in the Dashboard if you don't want the product to appear in the order process for everybody to see during testing.

A payment link generated in Ovatic, will open a page on the Peppered website, where the visitor can pay with all the payment options that are available. The payment is a simple amount and payment, with no other options (it’s not possible to change the order). After booking the confirmation e-mail is handled by Ovatic.

After payment:

Second time opening same payment link (already paid):

The Deferred payment method is a direct debit (NL: incasso) option for visitors. The actual payment is done later from the box-office system. What is needed for this to work is a correct IBAN bank account number of the visitor.

This is what the deferred payment method takes care of.

When using the deferred payment method, a payment of 1 cent will be started with the iDeal bank payment option.

By paying 1 cent, the bank account of the visitor is validated, and after the payment the IBAN number of the bank account is retrieved from the PSP and sent to the box-office system when finalizing the order.

The actual payment will be handled by the box-office. Peppered has no part in this phase.

Set-up

The deferred payment method is a dynamic payment method, which means the payment option will only be shown in specific situations.

This payment method is only active when configured in the control panel:

In this configuration form, one or more price types need to be entered. The deferred payment will only be shown on the website when all tickets for all events in the basket are of one of the configured price types.

This check does not include products or cross-sells. So you can always add any product with any price type to the basket. As long as all event tickets are of the specific price types, the payment option will still be shown.