Payment Notifications Suppression
GoCardless automatically sends you notifications for several events, including Payment, Mandate, and Subscription creation. You can deactivate payment notifications through Unaric Payments, which is helpful if you have your own notification system in place. Supressing these GoCardless notifications will not affect the mandatory emails which are part of the BACS Scheme rules (e.g. the emails sent following Direct Debit setup).
Notifications for Mandate Created and Subscription Created events will continue to be sent by GoCardless even if you suppress payment notifications.
How it works
The Payment object in Salesforce includes two fields related to notification suppression.
Field Name | Type | Purpose |
|---|---|---|
Suppress Notification by PSP | Standard Field | Controls notification behavior for individual payment records. |
Suppress PSP Notifications | Formula Field | Displays the calculated suppression status based on relevant settings. |
These fields are primarily for informational purposes and auditing. The actual control of notification suppression is managed by protected customer settings and custom settings.
The Suppress Notification by PSP field on a Payment record is populated automatically depending on how the payment is processed:
- Scenario 1: Scheduled Batch Processing via Unaric Payment Schedule
- When: Payment records are created through the Unaric Payment Schedule.
- Result: The field is set to true if the custom settings for suppression (detailed in Configuration Steps 1 and 2) are enabled when the payment is created by the schedule.
- Scenario 2: Manual Processing from Salesforce
- When: You click the Process Payment using Authorisation button from Salesforce, and a pop-up window with a checkbox for suppression appears.
- Result: The field's value will match the selection you make in the suppression checkbox on the processing page.
- Scenario 3: Custom Processes (Salesforce Flows or Apex code)
- When: Payment records are created using custom Salesforce Flows or Apex code.
- Result: The field defaults to false unless you explicitly set it to true in your custom Flow logic or Apex code.
Configuration steps
1. GoCardless approval
Before suppressing payment notifications, you must obtain approval from GoCardless. To this end, contact GoCardless support at [email protected]. Mention that you wish to handle “payment_created” notification for all the schemes that you intend to use (eg., SEPA, BACS, BECS, PAD, ACH, etc.). Note that to GoCardless, you will have to individually mention the schemes for which you intend to handle the notifications.
2. Unaric Payments configuration
- Contact Unaric Payments support at [email protected] and ask them to set the Protected Customer Setting Bypass Payment Notifications by PSP to true. This setting requires subscriber-level access to be modified. We are required by GoCardless to see evidence of your handling of notifications. For this purpose, our Customer Success team would ask you to complete a self-signed form and provide the confirmation email from GoCardless. Once we have these two documents our team will enable this feature for your Salesforce org.
3. Salesforce settings
- In Salesforce, go to Setup > Custom Settings.
- Open Unaric Payments settings.
- Click Manage and Edit.
- set the Suppress Notification for Payments Custom Setting to true.
- Click Save to finish.
- If you use custom Salesforce Flows or Apex code to create Payment Records, you must ensure the Suppress Notification by PSP field on each Payment record is explicitly set to True. If not set, it defaults to false in custom processes.
Suppress payment notifications in records
- Go to the Unaric Payments Authorisation tab and select the record against which to take payment.
- Click the Process Payment using Authorisation button.
- Mark the Suppress Notification by PSP checkbox.
- Click on Process Payment to finish.
Troubleshooting
If GoCardless payment notifications are still being sent after you have configured suppression:
- Verify that you have received approval from GoCardless for payment notification suppression.
- Confirm that both the Protected Customer Setting Bypass Payment Notifications by PSP (configured via Unaric Payments support) and the Custom Setting Suppress Notification for Payments (configured in Salesforce) are set to true.
- If you use custom processes (Flows or Apex) to create payments, ensure your custom code correctly sets the Suppress Notification by PSP field to true on each Payment record.