Make backdated payments
Last updated
Last updated
A change to the booking may result in the participant having to make an additional payment. If this is not to be done by invoice/bank transfer, there is also the option of making an online payment in the personal login area C3. The payment collection takes place independently of the registration process.
We currently offer this PSD-2-compatible (current Payment Services Directive) payment function for our standard payment interfaces via Computop (for credit cards).
In order for participants to be able to make payments at the frontend, a few requirements must be met at the backend.
1. Payment of outstanding invoices at the front end must be activated in the participant registration configuration (Fig. 1).
2. A “Payment” page must be created in the page structure of the CMS.
Create the page in the C3 folder in the page structure.
The page template is usually “FrontendModulFullWidth” (Fig. 2, point 1).
Set the action name “show_payment” (Fig. 2, point 2).
The page must be active, but will not be displayed as a separate menu item (visibility settings)
In the Contents tab, the module type “Payment Frontend” must be added using the Add Module button (Fig. 3).
3. The payment methods credit card and/or bank transfer must be active and visible at the frontend.
Subsequent payment is only possible for the credit card (Converia standard payment interfaces via Computop) and bank transfer payment methods. This means that at least one of these payment methods must be active and visible for the participant on the frontend (Fig. 4). Activating a hidden payment method via voucher codes is not possible for subsequent payment.
An invoice with an outstanding amount must be available for the participant (Fig. 5). The original payment method is irrelevant.
As soon as the participant logs in with the outstanding invoice amount in the C3 area on the front end, she sees a note about the open invoice (Fig. 6) and has the option to check it and make a payment (Fig. 7).
