Additional Configuration

custom references some psps allow you to specify a custom reference attached to an authorisation you can specify this by using the "custom reference" field available on the authorisation object however, note that not all psps or psp account types support custom references, and some often have restrictions on the maximum length of a reference you should check your psps documentation for any rules around specifying custom references note that setting a custom reference where they are not supported, or setting an invalid custom reference, may cause a transaction to fail custom fields via field sets the authorisation custom page has been updated to support custom fields through field sets, offering greater flexibility and customization for outbound (supplier/vendor) payments also, if you need to link each authorisation to specific account or contact records, you can now add those lookup fields directly to the page to add custom fields in salesforce, navigate to setup > object manager locate and select the authorisation object in the left hand navigation menu, click field sets choose the field set used by the custom authorisation page (the name may vary; consult your administrator if you're unsure) drag your desired custom field from the palette onto the field set click save to apply the changes your custom field will now be displayed on the authorisation custom page, making it readily available for use import authorisations to salesforce import existing authorizations from your psp into salesforce this process involves transferring psp data into salesforce and preparing it for use with asperato data import is a complex process that's best to be carried on tailored to your specific requirements as such, if you require existing authorisations from your psp to be populated in salesforce, contact support\@asperato com mailto\ support\@asperato com with details of your requirements prerequisites before you start importing authorisations, ensure you have the following in place access to psp data you need the ability to export customer and token data from your psp (e g , gocardless or authorize net) contact your psp or the asperato team for support salesforce permissions you must have sufficient permissions in your salesforce org to create and update records in the authorisation object how it works export data from your psp retrieve customer and token information from your psp this process varies from psp to psp prepare the data format and map the data to the authorisation object fields import the data insert data into the authorisation object from a csv file that you create from the psp data using the salesforce data import tool link authorisations connect the imported records to related salesforce objects export for asperato once you have created all the authorisation rows and ensured that the fields ‘asperato repeat token’ and ‘payment service provider repeat token’ contain data then create a csv file using data loader containing the content of the authorisation object (including the salesforce record ids) and send that to asperato asperato will then sanity check the object content and import relevant data to our database prepare the data this section is for guidance only contact the asperato support team, for assistance during data import to import the data, you will need to format it into a csv file and map it to the fields in the authorisation object below are the key fields and their data sources asperato repeat token (asp04 asperato repeat token c) generate a unique token in the format cccc aconvnnnnnnn, where cccc is your asperato customer id (found in asperato one settings or provided by asperato) aconv is a fixed constant nnnnnnn is a unique identifier (e g , a number or string without spaces) ensure uniqueness across all imports to avoid overlaps payment service provider repeat token (asp04 psp repeat token c) for gocardless use the mandate id (typically starts with “md”) for authorize net combine the customer profile id and customer payment profile id as customer profile id|customer payment profile id customer id (asp04 customer id c) obtain this from the customer id field in asperato one settings in multi merchant setups, you may need to hard code this value—contact asperato if unsure billing address fields (e g , asp04 billing address city c, asp04 billing address street c) map these from the psp’s customer data (e g , gocardless’s city, address line1; authorize net’s equivalent fields) cpa granted (asp04 cpa granted c) set to “true” payment route options (asp04 payment route options c) and payment route selected (asp04 payment route selected c) for gocardless set both to “direct debit” for authorize net set both to “card” status (asp04 status c) set to “in force” currency (currencyisocode) if your org uses multi currency, set the correct iso code (e g , “usd”, “gbp”) troubleshooting for persistent issues during this process, refer to salesforce data import documentation or contact asperato support for assistance if issues arise during the import, consider these solutions data format mismatches double check that token fields and ids match the required formats (e g , gocardless mandate ids start with “md”, authorize net uses id|id) duplicate records review the csv for duplicate asperato repeat tokens and adjust the unique identifier as needed missing links ensure all linking fields (e g , account lookups) are populated correctly—re run the update if necessary csv errors verify the exported csv includes all required fields and matches asperato’s specifications before submission