Where automated Asperato payment record updates have failed and courtesy notifications are generated, manual Salesforce record updates need to be performed by the customer or SI.


If manual record updates are not performed based on the data in Asperato courtesy notifications, users can later face various issues with affected payments, i.e. data inconsistencies, refund processing failures etc.


Asperato courtesy notifications typically contain all required values for manual record updates and these just have to be populated in the correct fields for each payment record.


The field mappings between payment records and courtesy notifications are as follows


ParameterSalesforce field mapping for the Payment record
Emailasp04__Email__c
AsperatoRepeatReferenceasp04__Asperato_Repeat_Token__c
PaymentDateasp04__Payment_Date__c
FirstNameasp04__First_Name__c
Amountasp04__Amount__c
SalesforceId (Repeat Ref)Salesforce Id of the payment record
DonationId
Salesforce Id of the authorisation record
TransactionGroupasp04__Transaction_Group__c
AddressCountryasp04__Billing_Address_Country__c
AsperatoReference (Order ID)asp04__Asperato_Reference__c
AddressPostalCodeasp04__Billing_Address_PostalCode__c
Sourceasp04__Source__c
Successif True and Payment Route = Card then set "asp04__Payment_Stage__c" as "collected from customer".
if false, set "asp04__Payment_Stage__c" as "Failed"
CurrencyCodeCurrencyIsoCode
PaymentRouteasp04__Payment_Route_Selected__c
GiftCardasp04__Is_Gift_Card__c
PSPReference (Cross Ref)asp04__PSP_Reference__c
AddressCityasp04__Billing_Address_City__c
AddressStreetasp04__Billing_Address_Street__c
CardTypeasp04__Card_Type__c
StatusDescription (MessageText)asp04__Payment_Stage_Description__c
LastNameasp04__Last_Name__c
AccountReferenceasp04__Account_Reference__c
AddressStateasp04__Billing_Address_State__c
AccountNameasp04__Account_Name__c