Signal slots

Signals

Signals are currently only used in the actions of the payment controller to control the behavior of the output and the processing of the payment of a registration.

Controller:	Action:	Signal:	Description:
Payment	redirect	‘redirectActionBeforeRedirect’ + ucfirst($paymentMethod)	Signal is called before rendering the redirect view. Use this signal to create the views HTML content, that redirects the user to the payment providers payment page.
Payment	success	‘successActionProcessSuccess’ + ucfirst($paymentMethod)	Signal is called before rendering the success view. Use this signal to create the views HTML content and also use this signal to modify the payment status of the registration after a successful payment.
Payment	failure	‘failureActionProcessFailure’ + ucfirst($paymentMethod)	Signal is called before rendering the failure view. Use this signal to create the views HTML content and also use this signal to modify/delete the registration after a failed payment.
Payment	failure	‘cancelActionProcessCancel’ + ucfirst($paymentMethod)	Signal is called before rendering the cancel view. Use this signal to create the views HTML content and also use this signal to modify/delete the registration after a cancelled payment.
Payment	notify	‘notifyActionProcessNotify’ + ucfirst($paymentMethod)	Signal is called before rendering the notify view. Use this signal to create the views HTML content and also use this signal to modify the registration when the payment provider supports a server to server nofitication URL.