---
title: Import Authorisations
slug: payments/import-authorisations
docTags: 
createdAt: 2026-07-17T02:00:29.166Z
---

Import existing authorisations from your PSP into Salesforce. This process involves transferring PSP data into Salesforce and preparing it for use with Unaric Payments.

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@unaric.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 Unaric Payments 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

::::WorkflowBlock
:::WorkflowBlockItem
**Export data from your PSP**

Retrieve customer and token information from your PSP. This process varies from PSP to PSP.  
:::

:::WorkflowBlockItem
**Prepare the data**

Format and map the data to the **Authorisation** object fields.
:::

:::WorkflowBlockItem
**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.
:::

:::WorkflowBlockItem
**Link authorisations**

Connect the imported records to related Salesforce objects. 
:::

:::WorkflowBlockItem
**Export for Unaric Payments**

Once you have created all the Authorisation rows and ensured that the fields **Unaric Payments 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 Unaric Payments support team, who will sanity-check the object content and import relevant data to the application database.
:::
::::

## Prepare the data

:::hint{type="warning"}
This section is for guidance only. Contact the Unaric Payments 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 Unaric Payments customer ID (found in **Unaric Payments settings** or provided by Unaric Payments).
    - `-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 **Unaric Payments Settings**. In multi-merchant setups, you may need to hard-code this value—contact Unaric Payments 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

:::hint{type="warning"}
For persistent issues during this process, refer to [Salesforce Data Import documentation](https://help.salesforce.com/s/articleView?id=xcloud.importing.htm\&type=5) or contact Unaric Payments 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 **Unaric Payments 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 Unaric Payments' specifications before submission.