Process Controls

    Content of this article

    1. Preliminary remarks
    2. Manage the Process Control
    3. Use Case

    1. Preliminary remarks

    In the process control settings, it can be set how the system should react in the event of a failed or revoked payment. Depending on the trigger, additional available system mails are sent to the customer.
    Failed payment attempts are displayed in the transactions.
    The timing of payment attempts can be set for three different accounting periods.
    How the settings behave is explained in point 3 Use Case.

    2. Manage the Process Control

    Select the desired accounting period for which the settings should apply.
    • more than 1 month, up to 1 month, up to 1 week
    Set the interval at which a payment attempt should be made.
    • Payment attempt when due
    • Payment attempt after X day(s)
    • Payment attempt after X further day(s)
    • Click on + to add more payment attempts. Click on - to delete payment attempts.

    Note: Each time a payment attempt fails, the Notification of a failed payment attempt email template is sent. If all payment attempts fail, the email template Notification of a failed recurring payment will be sent. If the subscription is canceled according to the settings, no additional cancellation email will be sent.

    What should happen afterwards?

    •  What happens to the invoice?
      • Nothing
      • Switch to invoice payment
    •  What should happen to the subscription?
      • Nothing
      • Cancel
    • Block access?
      • No
      • Yes, block product access.
      • Yes, block customer access.
    • When will product/customer access be granted again?
      • Manually
      • After changing the payment method
      • After payment

    Note on blocking access: If the selection is made that the subscription is to be canceled, the selection for blocking and renewed product access is obsolete.

    If customer access is to be blocked, the customer can no longer change their payment method via Self Service. The payment method can only be changed by an employee in the merchant backend.

    Payments revoked by customers

    The same settings can be made as in What should happen afterwards?.

    3. Use Case

    The following settings were made:
    • Payment attempt should be made 
      • when due
      • after 2 days
      • after 4 further days and
      • after 6 further days.
    If no payment has been received by then, the following should happen:
    • Payment method is switched to invoice payment. The subscription will not be canceled. The product access will be blocked. As soon as payment has been received, product access will be granted again. 
    Payment is due on June 1st. The first payment attempt is on June 1st.
    A further payment attempt is on June 3rd (2 days later).
    A further payment attempt is on June 7th (another 4 days later).
    The last payment attempt is on June 13th (another 6 days later).
    Transaction data still show that payment has failed.
    The settings which have been made in What should happen afterwards? now take effect. 

    Published