E-mail sent to the merchant

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

Trigger event(s):

• Creation of a recurring payment.

Condition(s):

• None.

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.

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.

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.

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.

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.

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.