Unfortunately, you cannot really "force" someone to pay in ConfTool.
But overall it’s just a question of whom the organizers consider as fully registered participants, therefore you can still represent this requirement in ConfTool.
There are several reasons why the online payment cannot be fully embedded as a step of the registration process:
- With offline payment methods such as bank transfer and checks, it will take some days before incoming payments are recorded in the organizer’s account.
- Many people need to first present an invoice (and an invitation) to their administration before they get a payment release. It may take from some days to several weeks in order to receive this approval. For this (usually relatively large) group of participants, a payment process is necessary that is separate from the registration process.
- Please note that a registration with all details (participant data, status, booked items or events, confirmation of the registration terms etc.) is required for a legally valid purchase. The data is needed to calculate the total fee, to generate the invoice for the participant and to create the data required to call most payment systems.
- Many payment systems providers also obligate their merchants (in the terms of their merchant agreement) to provide such a process including a confirmation of the registration terms, before users may proceed with the payment. They want to avoid that credit card holders complain later that they were not aware of the full costs and obligations, as credit card chargebacks cause considerable costs and work.
- German customers must press a button with the inscription "zahlungspflichtig bestellen" ("order with obligation" to pay or comparable) before a payment can be made (see §312j BGB).
- Most payment systems today use their own secure pages, the process runs outside of ConfTool. Furthermore, the ConfTool system often does not receive any message if the user does not complete the payment.Therefore, it cannot be avoided that individual payments are not made after successful booking (e.g. when customers close their browser windows).
- Cross-border online payments (even of smaller amounts) quite often fail for security reasons, and the bank of the client has to clear the payment first. This happens much more often when compared to national online payments (e.g. to your favorite online stores).
In theory, we could automatically cancel a registration if the payment is not completed within a certain time. However, an automatic cancellation would force all users to start over with their registration process each time a payment problem occurs or if they, for instance, need the invoice and a release for payment first. For offline payment methods (like bank transfer or check), an automatic cancellation is not an option anyway, as many organizations need 2 to 4 weeks to transfer the payment. That is why we decided against an automatic cancellation of registrations.