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

Compare with Current View Page History

« Previous Version 2 Next »


Parameters defining the reservation payment deadline can already be defined at product level for some product families. This improvement allows you to define also these parameters at season level. This brings you following advantages:

  • If you always use the same parameters (for example, reservations have to be paid within 10 days after purchase), you can define them only once
  • The parameters at season level will also be taken into account for some product families for which no parameter can be defined at product level, thus allowing you to define a reservation payment deadline that suits your needs

Solution

Defining the number of days at season level

You will be able to define the number of days in the season detail screen (menu organisation context > Initialisation > Seasons):

Compute the reservation deadline

The number of days at season level are default values that may be overridden at product level

If the number of days has been set-up (either at season level, at product level, or both)

If the confirmation delay after reservation has been set, compute a reservation deadline DL1 by adding the confirmation delay after reservation to the reservation date

If the confirmation delay before start time has been set, compute a reservation deadline DL2 by substracting the confirmation delay before start time from the product validity start dat

Consider the minimum of DL 1 and DL 2

If the computed reservation deadline is before the reservation date, consider the reservation date as the deadline

The list of payments screen has been extended in order to display the group to which a payment method belongs:

A payment method doesn't need to be assigned to a group. It can't be assigned to multiple groups.

Display on the Ticket Shop

As before, the selection of the payment method occurs in two steps:

On the first page, the internet user chooses between the on-line payment methods (handled by the SecuTix payment gateway that will call external payment service providers) and the methods managed internally by SecuTix.

If the internet user selects the on-line payment methods (first option on page above), the new payment method selection page will be displayed.

The page displays:

  • The groups of payment methods sorted by the rank of the group
  • The payment methods that don't belong to a group sorted by the rank stored in the additional information list defined at payment method level
  • For a given group, the page displays:
    • The external name of the group
    • The description of the group
    • The list of payment methods belonging to the group. The payments are sorted according to their order in the group (see Define groups of payment methods section above).
    • If the additional information list contains multiple entries, each entry will be displayed as if it was a separate payment method.

The internet user selects a payment method by clicking on its logo. He can then enter the details of the selected payment method:

This detail will depend on the payment method. The internet user may close a payment method group at any moment by clicking on the arrow in the upper right corner.


Grouping payment methods directly managed by SecuTix

The payment method selection page described here concerns only the on-line payment methods (handled by the SecuTix payment gateway that will call external payment service providers). As a result, setting-up groups containing other payment methods, like payment by pending account or direct debit won't have any impact on the page layout.

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:

  • No labels