Email/SMS notifications

Notifications can be sent based on events related to certain API objects:

• Payment request (paymentRequest)
• Card dispute (dispute)
• Installment payment (installment)
• Card transaction (transaction)
• Outgoing payout (payout)
• Card refund (refund)
• Subscription (subscription)
• Card credit (credit)
• SEPA Direct Debit transaction (sddTransaction)
• Reversed SEPA Direct Debit transaction (sddTransactionReversal)
• Mandate (mandate)

1. Notification scenario types

Automatically notify your customers and alert your colleagues when certain events occur on your CentralPay Merchant profile: receipt of a transfer, customer dispute, payment failure, etc.

You control the content of each notification using custom templates and define a delivery method by email, by SMS, or by JSON. This automates the reconciliation of your collections, customer notifications, and even updates to your information system.

2. Configuring notification templates

2.1. Template configuration

To start configuring your notifications, you must create your communication templates (email, SMS, or hook) by filling in the requested elements, such as the email subject, the sender name and email address, the message body, etc.

You can insert dynamic elements (tags) into the message body by typing the “#” character, which will display the list of tags available for the selected notification scenario type.

Please note: if you use email notifications, please ask us to provide our SPF and DKIM keys so that you can authorize CentralPay to send emails from your domain.

For SMS, please calculate the number of characters: you will be billed for one SMS per 160 characters (including spaces).

Access to email template settings:

Access to SMS template settings:

Access to hook template settings:

2.2. Configuring the header and footer for email templates

When creating an email template, a “header” and a “footer” must be created. For example, you can add your logo in the header and your contact details or legal notices in the footer.

Access to email header settings:

Access to email footer settings:

3. Configuring notification scenarios

To specify to the platform the sending conditions and recipients for your notifications, you must create a scenario that includes one or more sending rules.

After choosing the desired scenario type, you can create a sending rule. This rule is split into two parts: “WHEN” defines the event that triggers the notification, while “THEN” lets you choose the actions that will be performed when the event occurs.

Access to notification scenario settings:

3.1. In the “WHEN” section:

• Type “#” to view all attributes available for your scenario
• Use logical operators to build your rule:
  • For strings (must be enclosed in quotation marks “”):
    • = (equals)
    • != (not equal to)
    • in (in the following)
    • not in (not in the following)
  • For numbers (note: amounts must be entered in cents):
    • = (equals)
    • != (not equal to)
    • < (less than)
    • <= (less than or equal to)
    • in (in the following)
    • not in (not in the following)
  • For booleans (true/false statements):
    • = (equals)
    • != (not equal to)
• You can use conditions to complete your rule:
  • AND (to add another activation condition)
  • OR (to add another activation possibility)

It is possible to set priorities by placing parentheses around conditions. If you use AND and OR in the same rule, you must set priorities. If you use AND multiple times or OR multiple times, you must also prioritize each part.

Rule examples:

#end_user_country in ('FRA', 'BE')

#authorisation_status = 'FAILURE' or (#transaction_amount > 100000 and #context = 'TRANSACTION_RISKY' )

#transaction_amount > 100000 and ( #authorisation_status = 'FAILURE' or #context = 'TRANSACTION_RISKY' )

((#transaction_amount > 100000 and #context = 'TRANSACTION_RISKY') or ( #authorisation_status = 'FAILURE' and #transaction_amount < 100000 )) and (#card_product_type = 'Consumer')

Before you can save a rule, you must first test it using the “test” button. This verifies that your rule is grammatically correct. Please note: this does not guarantee that your rule matches what you intended to do.

3.2. In the “THEN” section:

“THEN” lets you choose the recipient and the template used for the notification. You only have access to templates that match the required template type (SMS, Email, Hook) and that match the selected scenario type (card transaction, payment request, refund, etc.).