...
- 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 already existing function Season ticket renewal of the batch of subscription has been extended to allow the usage of the new payment method. The behaviour is similar to the renewal of a membership (see section above). The only difference, not related to this new payment method, is the processing of the automatic renewal flag at season ticket level. As a reminder:
- 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
...