v2.16.1 (Spring '21)

internal reference type title customer facing notes md 279 usability correct use payor and payee corrected terminology to clarify the difference between a payor and payee the update has been applied to the user documentation and product interface, i e payment record details payor a person who pays payee one to whom money is or is to be paid md 280 bug classic platform on asperato setup page "reconnect salesforce" option should be present “reconnect salesforce” option has been added to the asperato setup page for salesforce classic ui previously customers had to switch to lightning in order to reconnect the connection/configuration md 429 new feature gocardless success+ feature support the package now supports gocardless success+ which is inactive by default certain steps must be taken to enable this feature package changes new field on payment object, retry attempt new status on payment "retry in progress" md 458 new feature ability to withhold gocardless messaging on "subscription or instalment" transactions allow customers to limit the email notifications that are sent for subscription or instalment payments by optimising the use of gocardless api package changes custom setting changes new field on payment object , suppress psp notification new field on process payment screen md 487 new feature gocardless support for pad pre authorized debit (pad) scheme support has been added and is now available via gocardless md 498 new feature gocardless support for ach gocardless ach / echeck support has been added by updating the api, statuses, fields, webhooks etc md 94 new feature internationalisation for french the package ui is now able to run in french on salesforce orgs where this language has been configured accordingly the translation workbench compatibility allows the customer to adapt the translation as required md 105 new feature customization for english language the translation workbench support has been added to allow the customer to adapt the translation for the package ui on salesforce orgs that are configured to run in english md 404 new feature package changes ability to cancel a gocardless mandate the ability to cancel gocardless mandates from within the package has been added previously this was only possible from the gocardless dashboard package changes quick action button on authorisation status on authorisation "submitted for cancellation" md 430 new feature different pay page template configuration for each merchant group multi merchant integrations now support different paypage templates for merchant groups customisation options include paypage logos, colours, styles etc md 437 new feature package changes ability to view gocardless mandate from salesforce gocardless mandates are now available to view on authorisation records by using the “view mandate” quick action button package changes quick action button on authorisation md 442 new feature package changes add a payout reference number on the payment record payment records now reflect the payout reference number that is generated by gocardless when a payment has been completed package changes field on payment object md 147 usability inconsistent behavior of payment and authorisation record, after they get processed individually payee details get updated in payment but not in authorisation a fix to address the issue where payment and authorisation records were not updated correctly after individual processing md 273 bug setup page issue on reconnecting salesforce connection with different users fixed the issue where merchant groups / psp connections were incorrectly displayed after salesforce org was reconnected to asperato via a different user account md 275 bug in classic blank setup page appears on setup configuration with 2 different users fixed the issue where asperato setup appeared as a blank page in salesforce classic after the configuration was initially completed by a different user md 306 usability immediate data does not get update after processing authorisation and payment using process button fixed the issue where the data was not updated immediately on authorisation and payment records after “process authorisation” and “process payment” buttons were used previously the page had to be refreshed manually in order to see the details for each record md 317 bug inconsistency behavior of refund in classic and lightning platform fixed the issue where the default amount was not correctly displayed for the refund page/pop up on a successful payment in classic & lightning md 318 bug in lightning, payment value does not round off when record gets created through payment using authorisation fixed the issue in lightning ui where payment value does not round off correctly when a record gets created through the 'payment using authorisation' button md 329 bug source does not appear when payment gets failed through batch process fixed the issue where source field is not being populated when a payment that was created through payment schedule (batch process) has failed