You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »


Currently, when a ticket is delivered as mobile ticket, the end customer may reprint it as e-tickets. However, this operation invalidates the initial mobile ticket and this may disrupt the inflow of your visitors. A new flag allows you to prevent this reprint.

Solution

In order to illustrate the solution, let's consider the following example. The customer has bought 3 tickets. The on-line shop allows mobile ticket and print@home shipment mode. He selects the mobile ticket shipment mode and pays the order. No tickets have been downloaded or printed yet. The end customer has still the choice between downloading a ticket on his mobile or printing an e-ticket.

The end customer decides to download the first ticket on his mobile. He can't get an e-ticket anymore to prevent the invalidation of the mobile ticket:

The restriction works similarly in the other way. If the end customer prints the second ticket as a print@home, he won't be able anymore to download it as a mobile ticket. Clicking several times on the printable ticket link will open exactly the same PDF file (without invalidating previous tickets).

Getting started

You have to create a service request to enable the feature. The service team will enable the feature flag PAY_PAGE_GROUP_MODE. This will allow you to set-up the groups of payment methods.

You can enable the new payment mode selection page on a given point of sale by enabling the following parameter:

Use of customised payment pages

If you have enabled some customisation, for example through CSS, this customisation may not be compatible with this new feature. Check first on a test environment (using the same customisation) that the layout is OK and, if not, adapt your customisation accordingly.


  • No labels