Courtesy Notifications

after a payment or authorisation transaction is processed by the psp, asperato 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, asperato 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 asperato 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 customizations within your salesforce org might prevent payment and authorisation records from being updated asperato integration configuration issues with the configuration of your asperato 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 from noreply\@asperato com to support\@asperato com subject courtesy notification from asperato salesforce failed to accept data from asperato body asperato 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\@asperato 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 asperato and salesforce issues with processing refunds other problems related to affected payments asperato 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 payment record (asp04 payment c object) field mappings are based on customers using asperato and gocardless as their psp field names may vary based on your specific psp and asperato 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 managing courtesy notification email addresses you can update the email addresses that receive courtesy notifications directly within asperato setup go to the asperato setup tab in salesforce scroll down to the error notification section review the existing email addresses list, which displays current recipients click new email address enter the desired email address in the provided field click add email to save the new address