Core Configuration

add new currencies asperato supports multiple currencies new currencies have to be activated from salesforce setup 1\ enable multiple currencies to learn more about the implications of enabling multiple currencies in salesforce, see considerations for enabling multiple currencies to enable multiple currencies in setup , go to company information click edit check activate multiple currencies click save to finish after enabling multiple currencies, you will see another currency field available on each salesforce object (authorisation, payment, etc ) set this currency field on your payment and authorisation objects according to the currency you wish to collect in 2\ add new currency in company information , click currency setup click new select the currency, its conversion rate from your corporate currency , and number of decimal places click save to finish create custom fields custom fields can be created for any of the asperato objects this can be used to extend the functionality of asperato and serve specific use cases, such as link payments and authorisations to other core or custom objects you may have in your org to learn how to create custom fields, see create custom fields translation workbench asperato supports salesforce translation workbench, a tool within salesforce that allows you to translate the text and labels within your organization's customizations instead of having to manually change every label, field name, or piece of text for each language, the translation workbench provides a centralized place to manage translations for more information, see translation workbench custom settings the following are the fields in the asperato one settings custom settings in the asperato package these are described in the table below these settings are not routinely changed from the default values, unless specifically instructed to do so by the asperato team changing the values could break your integration with asperato field usage bacs delay the number of days grace to allow a dd payment to be processed by bacs this is used to change a real due date to an artificial value so that the payment is collected from the bank account when it is actually due to be taken the default value is created at installation and shouldn’t need to be amended unless there is a specific reason to do so create payment schedule deprecated setting do not use customer id this value will be populated with your customer id when the connection from salesforce to asperato has been established the asperato one package will not function without this value being set enable pay/auth url data integrity when set true, an additional mechanism is used with the payment and authorisation urls to enforce the data integrity of the payments and authorisations it is recommended to enable it at all the times to maximise data protection and minimise gdpr exposure is running live the asperato team will check this box as part of the go live process server url this is the url of the server that asperato will use to process payments, refunds and authorisations at application download this is set to the test server route for a live installation this will be amended by the asperato team to point to the live server instance suppress notification for payments introduced in release 2 16 and it is currently supported only with gocardless payments if you have obtained required approvals https //asperato github io/userdocs/docs/suppressnotifications , and if this setting is set to true, the payment related notifications from psp would be suppressed this would allow you to send your custom notifications for payment enable partial payments customer can enable this flag to make a partial payment against the invoice use your own image for the pay now button introduced in release 2 20 use your own image for the pay now button see details here for using your own image https //payonomy freshdesk com/a/solutions/articles/43000688889#update authorisation cancel introduced in release 2 19 url of the endpoint navigated from the authorisation pay page in case of cancel global setting for all authorisations authorisation fail introduced in release 2 19 url of the endpoint navigated from the authorisation pay page in case of fail global setting for all authorisations authorisation success introduced in release 2 19 url of the endpoint navigated from the authorisation pay page in case of success global setting for all authorisations payment cancel introduced in release 2 19 url of the endpoint navigated from the authorisation pay page in case of cancel global setting for all payments payment fail introduced in release 2 19 url of the endpoint navigated from the authorisation pay page in case of fail global setting for all payments payment success introduced in release 2 19 url of the endpoint navigated from the authorisation pay page in case of success global setting for all payments use custom auth image introduced in release 2 20 use your own image for the authorisation button see details here for using your own image https //payonomy freshdesk com/a/solutions/articles/43000688889#update