Creating and Processing Authorizations
You can create an authorization and then apply it to an account, or create an authorization directly from an account.
We recommend that you create and edit authorizations from the account page with which they are associated.
Creating an Authorization
- Navigate to the detail page for the Account that you want to create an authorization for.
- Click New Authorisation.
- Follow the instructions in the Asperato documentation to create and process the authorization.
- Once processed, the status of the authorization is "In Force".
- To configure a customer account for Asperato payments and set the default authorization, see Creating Payment Integration Methods.
Processing an Authorization
Select one of the following options to process an authorization for a customer account:
- Copy and send the link displayed in the eCommerce URL field to the customer. This link enables the customer to enter their card or bank details and submit them to Asperato. For more information on authorizing payment routes, see the Asperato website.
- Click Process Authorisation. This option is recommended for "customer not present" or Mail Order Telephone Order (MOTO) authorizations. For example, the customer might want to provide their card or bank details over the telephone.
Once authorized, the status of the authorization is "In Force". Authorized payments can be collected from the customer account with which the authorization is associated.
Authorizing Vendor Accounts
You must create and process an authorization for each vendor account that you want to pay using the Asperato payment method in Payments Plus. To be able to pay a vendor in multiple currencies, you must create and process an authorization for each of the vendor currencies. You can select multiple authorizations and process them as a single batch.
To process an authorization for a vendor account:
- Navigate to the Authorisations tab.
- Select the applicable authorisation.
- Click the Submit for verification button.
The vendor account authorization involves mapping the payment fields between the Account object in FinancialForce Accounting and the Authorisation object in Asperato ONE. This table shows the field mapping between those objects.
Field Mapping for Vendor Payment Authorization between FinancialForce Accounting and Asperato ONE
Key: * – Mandatory field; A - Populated automatically by Asperato
| Authorisation Object Field Name |
|
Account Object Field Name |
|---|---|---|
|
Account Lookup |
* |
Account Name |
|
Account Name |
* |
Bank Account Name |
|
Account Reference |
* |
Bank Account Number |
|
Account Routing Value |
* |
Bank Sort Code |
|
Asperato Repeat Token |
A |
— |
|
Authorisation Number |
A |
— |
|
Bank Country |
* |
Bank Country |
|
Bank IBAN Number |
* |
Bank IBAN Number |
|
Bank Name |
* |
Bank Name |
|
Bank Swift Code |
* |
Bank SWIFT Number |
|
Batch Identifier |
A |
— |
|
Billing Address City |
* |
Billing City |
|
Billing Address Country |
* |
Billing Country |
|
Billing Address PostalCode |
* |
Billing Postal Code |
|
Billing Address State |
* |
Billing State |
|
Billing Address Street |
* |
Billing Street |
|
Card Type |
|
— |
|
Company Name |
* |
Account Name |
|
Currency |
* |
Account Trading Currency |
|
First Name |
|
— |
|
Is Domestic |
* |
— |
|
Is International |
* |
— |
|
Is Outbound Payment Bank Details |
* |
— |
|
Last Name |
|
— |
|
Local Clearing System |
* |
Based on the payment country or region and on the payment currency. |
|
Merchant Group |
* |
Based on the Accounting Company Name. |
|
Payment Service Provider Repeat Token |
|
— |
|
Record Type |
* |
— |
|
Status |
* |
— |
|
Status Description |
* |
— |
For more information about the Authorisation object in Asperato, see the Asperato Help.
For more information about vendor payments, see