v2.31 (Spring '25)

new features ach payments via cybersource ach payments through cybersource (bank of america) to collect payments directly from u s customer bank accounts how to set up create a psp connection on the asperato setup page under your chosen merchant group for echeck and cybersource (bank of america) enter your cybersource credentials and click create psp connection create your payment and/or authorisation records with echeck included in the payment route options cybersource (bank of america) requires a telephone number and this field must be added to salesforce on both the authorisation and payment page layouts manually payments are set to collected from customer once they are successfully sent from asperato, however, webhooks are unsupported for this payment gateway for information about late failures, you will need to check your cybersource account cybersource (bank of america) does not support standalone for recurring payments, you will need to combine authorisations and payment records when the first payment record is processed, it will set the authorisation to an in force status and assign repeat tokens to allow future payments to be collected automatically refunds are processed by asperato adhering to cybersource timelines for transactions klarna integration offer flexible payment options via klarna pay in 3 split into three interest free installments pay in 30 pay the full amount 30 days post purchase pay in full standard checkout how to set up create a psp connection navigate to asperato setup page and connect klarna for required currencies update picklist values (if upgrading) if you are upgrading from a previous version of asperato, you need to manually add buy now pay later to the picklist value set go to setup > objects and fields > picklist value sets > payment route options add buy now pay later as a new value assign it to inbound record type picklists for both payment route options and payment route selected create payment records select buy now pay later in payment route options when a customer chooses pay in 3 or pay in 30 , your payment record will display the full payment amount klarna manages installment arrangements directly with customers klarna does not support authorised recurring payments via our authorisation object bank details validation validate uk bank details for customers and suppliers to reduce processing errors asperato validates key fields such as account number with account name and sort codes at the point of entry once the authorisation has been validated, the validation status and validation status description fields are populated on the record with the outcome the user entering the details on the paypage will also see the outcome of the validation responses for validation are pass details matched successfully caution possible typo the response will suggest a close match fail validation unsuccessful contact support to enable this feature at support\@asperato com for this release, the validation service is only applicable for uk bank accounts should you wish to validate other countries, please contact support\@asperato com and request this for consideration by our product team bank details are returned to salesforce unmasked , so if you use them with another psp they are available for use however you may want to add your own masking or encryption on the page to prevent the details being visible to users how to set up update page layouts add the validation status and validation status description fields to your authorisation page layout ensure the process authorisation button is on the page layout add the account validation value to the payment route options global value set and ensure add the new picklist values to all record types that use this global value set is checked prepare for validation in order to submit records for validation, you will need to enter a united kingdom as bank country in the authorisation record page if this field is not on your page layout, you must add it (the field is bank country and it is the free text field, not the picklist field) to validate personal details, ensure the first name and last name fields are populated on the authorisation record; to validate company details, ensure that the company name field is populated submit for validation option 1 send the paypage link to customers to enter their details directly option 2 have an internal agent input details over the phone ( contact the customer success team for paypage setup guidance ) upgrade to asperato 2 31 prerequisites we recommend following salesforce best practices on app upgrades by installing the package for admins only and in sandbox orgs first before deploying to production if you are upgrading from asperato versions prior to 2 22, ensure you follow the steps in the release notes of each version in particular, v2 21 (spring '23) docid\ og4dwtzvblnxdaurqpica documentation around the merchant group fields this is critical to the smooth running of this version from v2 18 1 (spring '22) docid\ pgmo23zmidwh w9m3q sq , two new record types ( inbound and outbound ) were added to payment and authorisation objects you will need to add the inbound record type to all asperato user profiles if outbound payments are unused, remove them from the aforementioned objects following the instructions at additional options docid\ myxfi9eel8vla5wlo2 hi to avoid issues with the update, make sure the salesforce notifications setting enable notifications in lightning experience and salesforce mobile app is set as follows installation steps install the package sandbox/test org install asperato 2 31 in sandbox production org install asperato 2 31 in production alternatively, install directly from the salesforce app exchange post installation configuration assign the asperato full admin permission set to the connected user (the user who clicks connect on the asperato setup tab) ensure the connected user remains active in your salesforce org changes to this user may disrupt payment processing you must ensure that the connected user, the person who clicks connect on the asperato setup tab, has the asperato full admin permission set applied to them this person needs to be an active user at all times in the org any changes to this user will affect how your payment records are processed troubleshooting if issues arise post upgrade, cross reference the v2 21 (spring '23) docid\ og4dwtzvblnxdaurqpica release notes for merchant group field updates contact mailto\ support\@asperato com for unresolved issues