E-mail sent to the merchant

The table below lists the default existing e-mail notifications and the events that trigger them.

You can create a custom e-mail notification and choose your trigger event.

Confirmation e-mail of recurring payment sent to the merchant (disabled by default)

Trigger event(s):

Creation of a recurring payment.

Condition(s):

None.

Example(s) of use cases:

You want to be notified by by e-mail when a subscription is created.

Activation/deactivation of the rule

All you need to do it make a right click on the rule and choose Enable the rule/Disable the rule.
This action will trigger/stop the notification.

Refusal e-mail of payment in installments (disabled by default)

Trigger event(s):

Transaction declined during the automatic authorization process.

Condition(s):

Payment in installments set to Yes.

Example(s) of use cases:

You want to be notified by e-mail when one of the installments is refused.

Activation/deactivation of the rule

All you need to do it make a right click on the rule and choose Enable the rule/Disable the rule.
This action will trigger/stop the notification.

Refusal e-mail of deferred payment (disabled by default)

Trigger event(s):

Transaction declined during the automatic authorization process.

Condition(s):

Payment in installments set to Yes.

Example(s) of use cases:

You want to be notified by e-mail when the deferred payment authorization request is refused.

Activation/deactivation of the rule

All you need to do it make a right click on the rule and choose Enable the rule/Disable the rule.
This action will trigger/stop the notification.

Payment confirmation e-mail sent to the merchant (disabled by default)

Trigger event(s):

Payment accepted.

Condition(s):

The event source is not on a “Processing by file” list.

Example(s) of use cases:

You want to be notified by by e-mail when a payment is accepted.

Activation/deactivation of the rule

All you need to do it make a right click on the rule and choose Enable the rule/Disable the rule.
This action will trigger/stop the notification.

Key regeneration e-mail (disabled by default)

Triggering event(s):

Regeneration of the key.

Condition(s):

None.

Example(s) of use cases:

You want to be notified by e-mail when the PRODUCTION key has been re-generated via the Back Office.

Activation/deactivation of the rule

All you need to do it make a right click on the rule and choose Enable the rule/Disable the rule.
This action will trigger/stop the notification.

E-mail delivery confirmation of a direct debit/credit transfer file. (disabled by default)

Trigger event(s):

Capture sent to the acquirer.

Condition(s):

Network is on the SEPA list.

Example(s) of use cases:

You want to be notified by e-mail when a SEPA capture file is sent to the bank. Remember to confirm this with your bank.

Activation/deactivation of the rule

All you need to do it make a right click on the rule and choose Enable the rule/Disable the rule.
This action will trigger/stop the notification.

Registration confirmation e-mail sent to the merchant

Trigger event(s):

Token creation
Token update.

Condition(s):

None.

Example(s) of use cases:

You want to be notified by e-mail when a token is created or updated.

Activation/deactivation of the rule

All you need to do it make a right click on the rule and choose Enable the rule/Disable the rule.
This action will trigger/stop the notification.

Categories

Tags

E-mail sent to the merchant