Authorisation records are used when you want to collect and save a payment method from one of your customers. An authorisation can consist of saved card details, a Direct Debit mandate or ACH authoristaion.
Saved payment method details such as card or account number are always tokenised to protect you and your customer from fraud. Your customer can register multiple authorisations with you, so a single customer could have both a card payment method on record as well as a Direct Debit mandate in place.
Asperato ONE will always maintain these records, feeding into Salesforce any state changes that you need to be aware of. For example, if your customer cancels a direct debit, Asperato will update the appropriate authorisation to a cancelled state within Salesforce. Acting on these state changes is something you can do via Salesforce automation.
Key fields include:
|Authorisation URL||This is the link you provide to your customer to enable them to provide authority to save a payment method.|
|Status||Tells you if the Authorisation is ready to use or not. Autorisations have to be ‘In Force’ before they can be used to collect payments.|
|Status description||A descriptive text showing the reason related to the current status. Might contain the reason for cancellation or failure for example.|
|Payment Route Options||Allows you to choose which Authorisation routes are available to your customer to use. E.g. Card, Direct Debit or ACH|