Authorisation records are used when you want to collect and save a payment method from one of your customers. The authorisation object in Salesforce is used to store a saved payment method that can authorise payments in the future. An authorisation can be created for any payment route aside from Paypal.
Saved payment method details, such as card or account number are always tokenised to protect you and your customer from fraud, don’t accept anything less.
Your customer can register multiple authorisations with you, so you could have both a card payment method on record as well as a Direct Debit mandate in place.
Asperato will always maintain these records, updating Salesforce with any state changes that you need to be aware of (such as if your customer cancels a direct debit.) 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.|
|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|
|Payment Route Selected||Tells you which type of payment method has been granted by the customer.|
Autorisations have to be ‘In Force’ before they can be used to collect payments.