--- title: Courtesy Notifications slug: payments/courtesy-notifications description: Send courtesy notifications to customers after payments, failed transactions, or refunds using Unaric Payments. docTags: createdAt: 2025-02-26T02:03:09.425Z --- After a payment or authorisation transaction is processed by the PSP, Unaric Payments automatically attempts to record the outcome in Salesforce. In cases where this update fails, a payment may have been processed successfully, but Salesforce remains unaware of the transaction's final status. To address this potential data inconsistency, Unaric Payments sends a courtesy notification email. This email informs designated recipients that there was an issue updating data in Salesforce. ## How it works - **System-generated:** These notifications are automatically generated by the Unaric Payments system. - **Sender address:** Emails are sent from noreply\@asperato.com. - **Recipient configuration:** You can configure a single email address or a list of addresses to receive these notifications. Provide the desired email address(es) to your Customer Success Manager. **We recommend using a distribution list** to ensure notifications are seen and actioned promptly. - **Action required:** Courtesy notifications indicate that manual intervention is needed to update Salesforce records. ## Reasons for update failures Payment record updates to Salesforce can fail for various reasons. The courtesy notification typically includes details about the failure. Common causes include: - **Salesforce Customisations:** Faulty flows, triggers, or other customisations within your Salesforce org might prevent payment and authorisation records from being updated. - **Unaric Payments Integration Configuration:** Issues with the configuration of your Unaric Payments integration can also lead to update failures. - **Salesforce Errors:** Temporary Salesforce issues or errors. - **Authentication Issues:** Invalid credentials or locked out user accounts as indicated by errors like "Invalid username, password, security token; or user locked out." ## Example courtesy notification email :::BlockQuote **From:** noreply\@asperato.com **To:** support\@unaric.com **Subject:** Courtesy notification from Unaric Payments: Salesforce failed to accept data from Asperato **Body:** Unaric Payments attempted to post data to your Salesforce org. Unfortunately, Salesforce was unable to accept the data. The reason text given by Salesforce was: A LoginFault error has occurred - Invalid username, password, security token; or user locked out. Raw JSON request: null **Transaction Details:** If you need help interpreting the Salesforce reason text, consult with your Salesforce consultant. To identify this transaction with your Payment Services Provider, use the Order ID or the Payment Cross Reference. Once identified, you will need to manually update Salesforce accordingly. If you have any questions regarding this email, please contact support\@unaric.com. Donation ID: \*\*\* Order ID: \*\* Cross Reference: \*\* Transaction Type: Payment Repeat Reference: \* Repeat Cross Reference: \*\* Card Type: Not applicable Repeat Transaction Reference: \*\* Account Number: Frequency: ANN Amount: 100.00 ::: ## Manual Salesforce record updates When you receive a courtesy notification, manual Salesforce record updates are necessary. These updates must be performed by your team or System Integrator (SI). Failure to perform manual updates based on the information in courtesy notifications can lead to: - Data inconsistencies between Unaric Payments and Salesforce. - Issues with processing refunds. - Other problems related to affected payments. Unaric Payments courtesy notifications contain all the necessary values to manually update Salesforce records. You simply need to populate these values into the correct fields for each payment record. ### Field mapping for manual updates The following table outlines the mapping between parameters in the courtesy notification and the corresponding Salesforce fields on the **Unaric Payment** record (**asp04\_\_Payment\_\_c** object). :::hint{type="warning"} Field mappings are based on customers using Unaric Payments and GoCardless as their PSP. Field names may vary based on your specific PSP and Unaric Payments configuration. ::: | **Parameter** | **Salesforce Field Mapping for the Payment Record** | | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | | Email | asp04\_\_Email\_\_c | | AsperatoRepeatReference | asp04\_\_Asperato\_Repeat\_Token\_\_c | | PaymentDate | asp04\_\_Payment\_Date\_\_c | | FirstName | asp04\_\_First\_Name\_\_c | | Amount | asp04\_\_Amount\_\_c | | SalesforceId (Repeat Ref) | Salesforce ID of the Payment record | | DonationId | Salesforce ID of the Authorisation record | | TransactionGroup | asp04\_\_Transaction\_Group\_\_c | | AddressCountry | asp04\_\_Billing\_Address\_Country\_\_c | | AsperatoReference (Order ID) | asp04\_\_Asperato\_Reference\_\_c | | AddressPostalCode | asp04\_\_Billing\_Address\_PostalCode\_\_c | | Source | asp04\_\_Source\_\_c | | Success | If True and Payment Route = Card, set asp04\_\_Payment\_Stage\_\_c to "Collected from customer". If False, set asp04\_\_Payment\_Stage\_\_c to "Failed" | | CurrencyCode | CurrencyIsoCode | | PaymentRoute | asp04\_\_Payment\_Route\_Selected\_\_c | | GiftCard | asp04\_\_Is\_Gift\_Card\_\_c | | PSPReference (Cross Ref) | asp04\_\_PSP\_Reference\_\_c | | AddressCity | asp04\_\_Billing\_Address\_City\_\_c | | AddressStreet | asp04\_\_Billing\_Address\_Street\_\_c | | CardType | asp04\_\_Card\_Type\_\_c | | StatusDescription (MessageText) | asp04\_\_Payment\_Stage\_Description\_\_c | | LastName | asp04\_\_Last\_Name\_\_c | | AccountReference | asp04\_\_Account\_Reference\_\_c | | AddressState | asp04\_\_Billing\_Address\_State\_\_c | | AccountName | asp04\_\_Account\_Name\_\_c | ## Manage Courtesy notification email addresses :::hint{type="danger"} Do not add email addresses that trigger automatic replies (such as shared support inboxes or ticketing systems). Auto-responses may generate repeated notification emails and interfere with notification delivery. ::: ### Add email address You can update the email addresses that receive courtesy notifications directly within Unaric Payments setup. 1. Go to the **Unaric Payments Setup** tab in Salesforce. 2. Scroll down to the **Error Notification** section. 3. Review the **Existing Email Addresses** list, which displays current recipients. 4. Click **New Email Address**. 5. Enter the desired email address in the provided field. Remember that courtesy notification emails should be sent to individual inboxes or distribution lists that do not have automatic replies enabled. 6. Click **Add Email** to save the new address. ### Remove email address To remove an email address: 1. Navigate to the **Unaric Payments Setup** tab. 2. Navigate to **Email Notification** section. 3. Click on the **Delete** link. 4. You will get a confirmation message. Click on the **Delete Email** button. This will remove the email address to receive the error and courtesy notification emails from Unaric Payments installed in your Salesforce Org. ![](https://asperato.github.io/userdocs/img/overview/DeleteConfirmationScreen.PNG)