v2.17.1 (Autumn '21)

new features asperato customers can now accept instant bank payments asperato have added a new ‘payment route’ that allows collection of one off bank to bank payments, powered by open banking in the uk and europe why this feature is so important? manual bank transfer is inconvenient sharing bank details is time consuming, causes payment friction, and can cause late payments credit cards come with high fees card payments typically come with high fees and higher failure rates slower payout timings for bank debit in some cases you can’t wait 3 5 days for funds to land in your account how it works send a payment request create payment record as normal in asperato with ‘payment route’ set to open banking send your customer the ecommerce link, which asks them to make an instant bank to bank payment customer completes payment after your customer opens the link, we’ll connect them to their bank once everything looks good, they simply authorise and confirm payment confirmation and funds transferred confirmation to the customer is immediate asperato will record the outcome of the payment in salesforce as normal it is also possible to collect an instant bank to bank payment and set up a direct debit mandate for future payments in one step just select open banking as the payment route for both the payment and the authorisation to enable this feature add ‘open banking’ as a new payment service provider connection on your asperato setup page in salesforce currently gocardless is the only psp to support this feature update “picklist value set” for “payment route options” from setup add “open banking” in the values select the checkbox “add the new picklist values to all record types that use this global value set ” enhancements cancel pending direct debit payments it is now possible to cancel a pending payment from within salesforce https //asperato github io/userdocs/docs/payments#cancellations https //asperato github io/userdocs/docs/payments#cancellations to enable add mobile and lightning actions (for lightning page) and buttons (for classic page) cancel payment on page layout add “pending cancellation” and “cancelled” picklist value in status field from fields and relationships view next retry date for gocardless success+ customers it is now possible to see the date on which gc will re attempt to collect a payment to enable add “next retry date” on asperato payment page layout from the salesforce setup view ‘payout date’ it is now possible to see when funds are disbursed to you, the merchant by your payment service provider this is known as a ‘payout date’ this feature is currently only supported by gocardless asperato will be adding other psps as they introduce this service via their api to enable add “payout date” on the payment page layout from the salesforce setup security token added to ecommerce url we have added a new security feature to the ecommerce url full details on how to enable and use this feature described below what has changed? on creation of a new payment or authorisation object, a unique data integrity token (dit) is created against that object this dit value will be added to the payment url to add additional security the data integrity of the payment or authorisation is protected by ensuring that the url will only show the details for that specific payment or authorisation how is it enabled? this feature can be enabled in the salesforce custom settings ”enable pay/auth url data integrity” this feature will be enabled by default for any clients who are installing the package as new for existing clients, who are upgrading, this feature will be disabled by default but we strongly recommend that this feature is enabled to provide the additional security who is impacted? if you use the asperato generated ecommerce url, no further configuration is required if you generate your own payment urls you need to update your logic to include the new dit parameter in the url impact on existing ecommerce links there is no impact on previously generated ecommerce urls, these will still work as expected impact on paypage overlays if you use paypage overlays, a change is required the input data for this javascript class now needs to include the dit https //asperato github io/userdocs/docs/paypage#using the paypage template as an overlay https //asperato github io/userdocs/docs/paypage#using the paypage template as an overlay https //asperato github io/userdocs/docs/paypage#using the paypage template in a lightning component https //asperato github io/userdocs/docs/paypage#using the paypage template in a lightning component self manage courtesy notification recipients when asperato cannot insert data into your org, we send you a “courtesy notification” it is now possible to update the email addresses that courtesy notifications are sent to, direct from the asperato setup page immediate payments against an “in force” authorisation this change enables you to process an immediate payment against an “inforce” authorisation and instantly see the outcome prior to this release, the initial payment had to wait for the scheduled batch job better data visibility between payments and linked authorisations previously when linking an authorisation to a payment there was very little detail to provide assurance that the correct authorisation was being selected we have increased the level of data available to make this process easier and more reliable raw psp response messages now added to asperato records asperato now passes through the raw response message from connected payment service providers this provides further detail in understanding the outcome of payments / authorisations this is not seen as a replacement for our sanitised error codes and responses to enable update the payment object > page layout add field “raw error message from psp” update the authorisation object > page layout add field “raw error message from psp” update the refund object > page layout add field “raw error message from psp” ability to suppress direct debit notifications sent by psp it is now possible to request the suppression of direct debit notifications (gocardless only) please contact support to request this suppression if you would like to send your own direct debit messaging \ bug fixes payment value decimal places fix to resolve issues created when payment amount is defined to greater than 2 decimal places this was causing payment processing batch failures “process payment using authorisation” functionality this feature released in version 2 16 was not working for echeck payments this issue has now been resolved paypal added validation to restrict paypal processing in moto mode other minor bug fixes \ how to upgrade to v2 17 upgrade to the latest version 2 17 1 with link here https //login salesforce com/packaging/installpackage apexp?p0=04t1n000002ae4k https //login salesforce com/packaging/installpackage apexp?p0=04t1n000002ae4k other considerations if you are running a package older than 2 16 then refer release notes for all the releases in between to know the configurations for features released in between upto release 2 17