...
| Excerpt |
|---|
Available shipment modes are currently defined at sales channel level. However, you may wish to reserve a shipment mode for specific products. For example, postal mail should only be used for season tickets or memberships loaded on cards and single tickets should only use electronic shipment modes. This feature provides you a convenient and user friendly way to define such flexible set-up. |
Solution
Solution overview
- A set of shipment modes are still defined at sales channel level. A shipment mode will only be proposed to the user if it's allowed by the current sales channel.
- Define a For each shipment mode, define the list of shipment modes available for each product family,product families for which it is allowed
- You may override the list defined above by defining some shipment modes at product level. For example, you could decide that postal mail isn't allowed for single tickets except for a special event.
- SecuTix will propose the list of shipment modes common to the whole order, i.e. allowed for all items belonging to the order. If there is no such shipment mode, the end user will be able to select a shipment mode for each item of his order.
- As currently, SecuTix will only propose shipment modes that are compatible with the ticket model (example: not propose any e-ticket if only a thermal ticket template has been set-up for a given product)
Set-up
...
the list of product families for a given shipment mode
For each shipment mode, you can define for which product families it should be authorized.
...
For example, you could define that standard (postal) mail and registered email are only used for memberships (because single tickets are using electronic shipment modes and goods are shipped by some external shipping provider).
Set-up allowed shipment modes at product level
The set-up defined above can be overridden for a given product. For example, you've got one very expensive membership providing many privileges and you want to provide it only by registered mail.
Selection of shipment modes on Ticket Shop
Case 1: There exists
...
one (or several) common shipment mode(s) allowed for all items of the cart
...
The table below compares the three available direct debit payment methods:
- Bank withdrawal: the first direct debit payment method provided by SecuTix
- Slimpay direct debit: the direct debit payment method based on pending account and using Slimpay (for bank file generation and automatic mandate creation for on-line sales)
- SEPA direct debit: the new direct debit bank payment method also based on pending account
...
The Ticket Shop will only propose this (or these) common shipment mode(s).
This approach allows to minimise the number of shipments, thus reducing shipment costs and fees for you and your customers.
Case 2: There doesn't exist any common shipment mode for all items of the cart
The internet user will be invited to select one shipment mode for each item in the cart. When the page is displayed, the list of shipment modes available for the first item is expanded while the list for the other ones are closed. The internet user may at each moment view or hide the details of the shipment modes available for one product.
The file detail displays the different shipments created:
Getting started
Create a ticket to our service team to enable the feature. The service team will:
- Set the feature flag SHIPMENT_MODE_PER_PRODUCT
Current restrictions
Scenario | Status |
Ticket Shop | |
Direct sale on Ticket Shop (no creation of options or reservations) | Shipment mode set-up per product is taken into account Internet user may select multiple shipment modes if needed The file detail mentions all the shipments with their respective cost but doesn’t mention which products belong to which shipment → not a big issue For postal shipment modes, the internet user cannot create a new shipment address with a different first name and last name (business case: an internet user wants to make a present and wants the tickets to be shipped directly to the beneficiary) The flag only immediate shipment mode if available is ignored if the shipment modes per product feature is enabled. |
Online exchange | OK (same as above) |
Reservation on Ticket Shop | Shipment mode set-up per product is ignored → a reservation order may be created with a reference shipment which shipment mode is inconsistent with the shipment mode set-up per product |
Ticket Shop sale converted to reservation:
| High risk of technical error if the sales order has multiple shipments → currently, shipment mode per product isn’t compatible with order amount limit or prepayment |
Pay online a reservation order created on-line | The reference shipment (which shipment mode may be inconsistent with the shipment mode set-up per product) is ignored, allowing the internet user to use the new feature → Only consequence:
|
Box Office | |
Reservation and sales | The behaviour is the same for reservation and sales orders: the shipment mode per product set-up is taken into account but the order may contain only one shipment. The operator needs to split the order if there is no shipment mode common to the whole order. |
Payment of a reservation performed on BO | No problem since reservation and sales handle the shipments in the same way. |
Hybrid scenarios | |
Payment of an online reservation at the Box Office | Because the online reservation doesn’t take into account the shipment mode set-up per product, the BO operator may need to split the order, i.e. create 2 sales orders for one reservation order. |
Payment of a BO reservation online | No problem |
| Fixed price season tickets | No shipment mode can be selected if the season ticket is defined as "ticket only" and no performance has been selected yet |
| Info | ||
|---|---|---|
| ||
SEPA allows to withdraw money from a bank account with or without a mandate. In absence of a mandate, the debtor will be allowed to refuse this bank withdrawal more easily and during a longer period of time. Concretely, you may have to credit a bank account several months after having performed a debit on it. As a result, establishing a signed mandate before the first bank withdrawal is a matter of financial risk, not a technical matter of failed or succeeded payments. |
Which direct debit payment method should I use?
- If you want to be sure that tickets are paid before the corresponding event or visit, use the bank withdrawal payment method.
- If you want an automated mandate generation during on-line sales, use the direct debit payment method based on our Slimpay partner.
- If you want a flexible and easy to use solution, however providing a lower level of "built-in" security, use the new direct debit payment method described in the next sections.
Use of the new payment method
Scope
The new payment method is available for the following cases
- Sales on box office
- Sales on Ticket Shop (without automated on-line mandate generation)
Membership renewalStatus colour Blue title UPCOMING
Season ticket renewalStatus colour Blue title UPCOMING
Sales on box office
The operator first enters the mandate information from the contact detail screen (tab Management)
If the end customer has signed a mandate, the operator may enter the mandate reference and mandate signature date. Otherwise, the operator may click on the Generate mandate button. The system will then generate a mandate reference (based on the contact number) and consider it as valid from today.
The operator can revoke the consent by removing the mandate reference.
The operator chooses the created payment method (see Getting started section)
As for any installment based payment method, he may choose the number of installments within the configured range. He may then modify the mandate information if needed:
If the operator modifies the mandate information, a message will inform him that the mandate information stored at contact level will be updated accordingly.
Sales on Ticket Shop
When the internet user chooses the new direct debit payment method, the Ticket Shop displays the installments and the bank account information.
If the internet user has already given his consent, the check-box concerning the consent is checked and cannot be modified at this step (see below how to revoke the consent). However, the internet user may modify the bank account information.
The internet user may revoke or add his consent from profile page:
| Warning | ||
|---|---|---|
| ||
You should not allow your internet users to revoke or enable consents on the Ticket Shop if you are managing signed mandates. Indeed, the internet user may modify the mandate reference entered by the box office operator (by removing it and replacing it by the automatically generated mandate reference). Such inconsistencies should be avoided. The Getting started section describes how to enable or disable this possibility. |
Membership renewal
...
- The memberships paid by direct debit will be renewed by direct debit
- The renewal function will reuse the number of installments that were used to pay the initial membership
- The due dates and installment amounts are computed based on the current definition of the payment method (and, of course, the price of the new membership)
- The system will create a reservation (instead of a sales order) if the direct debit method can't be used for some reason, for example:
- The end user has revoked his consent (no mandate reference and signature date are available anymore in SecuTix)
- The current definition of the payment method doesn't allow the payment, for example:
- The maximum number of installments has been lowered from 3 to 2 and the initial membership was paid in 3 installments
- The minimum amount accepted for this payment method has been increased from 50€ to 100€ and the price of the new membership is 80€
Season ticket renewal
...
- The renewal function tries only to create a payment (whatever the payment method) if the automatic renewal flag is set. If the flag isn't set, it will only create reservations.
- If the automatic renewal flag is set but a given end customer has requested to stop the renewal (criterion STOP_AUTOMATIC_ST_RENEWAL is set to yes), the renewal function won't create any order for this contact.
Send the payment file to the bank
- The payment file is generated by the function Direct debit bank file generation of the batch of type Instalment management (see getting started section below for more information on how to set-up the batch).
- The file is available on the specified FTP server (URL defined at batch level)
- If no FTP server has been specified or the file couldn't be stored on the FTP server, the file can be downloaded by clicking on the link displayed in the execution log.
Import the payment status file from the bank
- The function Confirm debit bank file of the batch of type Instalment management allows to import the payment status file either automatically from a FTP server or by uploading it manually (see getting started section below for more information on how to set-up the batch).
Direct debits and refunds
Once an installment has been sent to the bank, any subsequent order cancellation (entire order or a part of it) cannot cancel the concerned installment. More generally, in case of partial order cancellation, SecuTix will cancel the installments not sent yet to the bank and with the most distant deadline.
Storage of end customer's consent
If you don't manage mandates signed by your end customers (either manually or through Slimpay), the end user just has to click on a check box in order to accept direct debit. You can view the history of customer's consent in the new screen Audit contact available from the contact detail screen.
This screen also shows marketing and communication consents provided by the end customer.
Payment information to end user
| Status | ||||
|---|---|---|---|---|
|
- The payment purpose is based on the first product of the order related to the installment (that hasn't been refunded in the meantime)
- If the product is a competition , the payment purpose will contain the competition name, the opponent team and the match date-time
- If the product is an event, the payment purpose will contain the event name and the performance date-time
- For any other product (including composed products), the payment purpose will contain the product name
- Note that the payment purpose will be truncated if it exceeds the maximum length of 140 characters allowed by the SEPA standard. In that case, the competition name and event name will be removed first.
Getting started
Set-up the payment methods
You have first to create a payment method of type direct debit. This payment method will be used when performing the actual direct debit.
You have to define a payment method of type pending account with follow-up. This payment method will be used when creating the sales order.
Make sure to select Contact's mandate as the direct debit authorization type. This means that the bank information (IBAN, BIC. etc..) have to be entered in SecuTix since they aren't managed by an external system (like Slimpay).
All other parameters used to configure the installment creation process (number of installments, dates, amount) are identical to the other pending account based payment methods provided in SecuTix.
Allow the usage of the payment methods
- The pending account payment method must be authorised for the concerned point of sales
- The contact must be authorised to use a pending account payment method and the maximum balance of the pending account must not be reached
Allow (or not) the internet user to grant or revoke a payment mandate from his user account
In the menu Institution > Organisation > Screen configuration, configure the field bank_AcceptDDebitFromOrg to be displayed (or not) in screens B2C_INTERNET_CONTACT_FORM and B2B_INTERNET_CONTACT_FORM.
Set-up of administrative numbers
In order to generate the installment files, Secutix needs the following 4 administrative numbers :
If you don't see them, you'll have to ask for them to be activated in the DB.
As described in more detail below, you may override the IBAN and BIC numbers in the batch parameters.
Set-up the batch to generate the payment file
- Create a batch of type Instalment management if it doesn't exist yet.
- Schedule the function Direct debit bank file generation.
- The main batch parameters are described below:
- File sales channels: consider the files created on the selected sales channels
- Payment method(s): consider only the installments belonging to orders paid by one of the specified pending account payment methods
- Instalment due in:consider only installments due in the next N days (example: current date is 01.07.2021. If the parameter equals to 10, all the installments still not processed and which deadline is the 11.07.2021 or before will be taken into account)
- Minimum remaining amount: Ignore installments which amount (that remains to pay) is less than the entered amount
- IBAN: You may either use the organisation's IBAN or another IBAN defined in the batch parameters. This allows you to use several bank accounts to gather the money debited from the end customer's account, for example, depending on the sales channel or the product family.
Set-up the batch to Import the payment status file
- Schedule the function Confirm debit bank file of batch Instalment management.
- The main batch parameters are described below:
- Bank file: you can either let the import function get the file from the FTP server (which URL is defined at batch level) or upload it manually
- Email configuration: you can decide to send an email (or not) to the end customer in order to inform him about the performed direct debit (click No to send an email). If you decide to send an email, following information must be provided:
- The email may be sent to the purchase contact or payment contact
- The email's origin (i.e. the sales channel and point of sales from which the email is sent).
- The email's template in case of success. It must be a document type of document class instalment payment success email
- The email's template in case of failure. It must be a document type of document class instalment payment failure email. Note that the current bank file won't provide any information about failed payments. However, this parameter has already been foreseen in case of future ease.
- The document template. It's a document type belonging to document class file recap (file summary)
...
| title | Management of BIC codes |
|---|
By default, the internet users or operators have to enter the BIC code of the end customer's bank account. You can request a SecuTix service to make the BIC optional for a list of countries. For example, you can decide that end customer residing in the same country as your institution don't have to enter the BIC code but still require the BIC for end customers living abroad.
...
| . |