Callback triggers
The following triggers can be used to issue a callback:
TRIGGER | MESSAGE | DESCRIPTION | PAYMENTS | MANDATES | DIRECT COLLECT |
---|---|---|---|---|---|
on link not delivered | LinkNotDelivered | Issued when a link could not be delivered by mail. | X | X | - |
on send error | SendError | Issued when there was an issue when sending the link by mail or sms. | X | X | - |
on reminder set | Reminder | Issued when a reminder is sent to the customer. | X | X | - |
on payment declined/refused | Declined | Issued when a payment is declined by the PSP. | X | - | - |
on success | Success | Issued when a payment was successfully paid or when a mandate was successfully signed. | X | X | X |
on expired | Expired | Issued when a link is expired. | X | X | - |
on aborted | Aborted | Issued when a link is aborted by the user/API). | X | X | X |
on error | Error | Issued when a (system) error occurs. | X | X | X |
on reversed payment | Reversed | Issued when a charge back occurs. | - | - | X |
on failed | Failed | Issued when the direct collect failed. | - | - | X |
on direct collect sent | DirectCollectSent | Issued when the direct collect is sent to the financial institute. | - | - | X |
The value for ‘Message’ is returned by the system parameter [*CallbackType]. The following pages describe the possible actions that can be performed. In all these callbacks, parameters within the system can be used within the message. Custom created parameters like (for instance) [FlightNumber] or [RoomType] can be used as well.
Date updated: 2019-10-29