v2.18.1 (Spring '22)

release features take payments using qr code asperato have added an out of the box payment and authorisation qr code why this feature is so important send your customers a qr code for them to scan to make payment, or capture their bank details for future payments make it as easy as possible for them to pay you how it works add field ‘qr code’ to the payment & authorisation page layouts in salesforce create your payment record as normal in asperato, you’ll see a qr code available which you can expose to your customers in a variety of ways scanning this qr code will take you to the payment or authorisation page in order for the customer to enter their details set up add field ‘qr code’ to the payment & authorisation page layouts in salesforce ‘pay now’ button image included on payments to make setting up asperato easier, we have added an out of the box payment button image which you can use out of the box, rather than create your own this pay now image is displayed on the payment record in the field ‘payment image’ simply decide how you want to expose this image to your end customers for them to pay you with minimal clicks amending the pay now image in this release, you can create a custom field for your own pay now image, to do this you need to upload your custom image into static resources select 'use custom pay now image' in the asperato one settings in custom settings create a custom field on the payment object of type formula the formula should go something like the following as rough guidance but please feel free to use your own depending on your requirements if( asp04 ecommerce url c != null, hyperlink("https //" + $setup asp04 asperatoonesettings c asp04 server url c + "/pmweb1?pmref=" + asp04 customer id c + "\&aid=" + id + "\&locale=" + text(asp04 language c) +"\&dit=" + asp04 data integrity token c , if( $setup asp04 asperatoonesettings c asp04 use custom pay now image c , image("/resource/paynowimage1", 'auth online', 1,150) , image(" https //live protectedpayments net/donationline/images/auth img png",'pay https //live protectedpayments net/donationline/images/auth img png%22,'pay online', 1,150)) ), null ) gocardless store bank name on payment in order to be compliant with the gocardless scheme rules (when not using standard gocardless notifications), we now store the bank name on the payment record when direct debits are processed via gocardless so that they can be confirmed to the customer to enable add ‘bank name’ field to the payment page layout outbound (supplier/vendor) payments asperato have built an outbound payments feature in conjunction with financialforce for version 2 18 1, this is only available to financialforce customers using the financialforce and asperato integration package, however keep up to date with our product news to hear more about when this will be available to a wider audience this feature needs to be enabled by our support team even in the free trial if you are interested in understanding what this feature entails contact support\@asperato com mailto\ support\@asperato com for financialforce customers go to our getting started guide https //docs google com/document/u/0/d/1fdonmk6kvpmogvkhabckwjaqvc38zurgfm4rccx8hee/edit for help and guidance \ bug fixes other minor bug fixes \ upgrade considerations upgrade to the latest version 2 18 1 from appexchange https //appexchange salesforce com/appxlistingdetail?listingid=a0n3a00000ecronuaj or with link here https //login salesforce com/packaging/installpackage apexp?p0=04t1n000001ph2r https //login salesforce com/packaging/installpackage apexp?p0=04t1n000001ph2r https //login salesforce com/packaging/installpackage apexp?p0=04t1n000002dfuv as part of our outbound payments work, we have made a change to the payment and authorisation objects to introduce two new record types the current collections functionality is now classed as a record type of inbound you must add the correct record type to existing asperato user’s profiles upon upgrade to this version important information please contact asperato support on support\@asperato com when you upgrade any sandbox or production environments to ensure that your asperato environment is correctly configured we are making some changes on our side to automate this process in the next 2 19 release, but for 2 18 1 it is key that you contact our support team to make sure you have no processing issues if you are running a package older than 2 17 then refer release notes for all the releases in between to know the configurations for features released in between earlier versions