Import Authorisations
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 [email protected] 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
Export data from your PSP
Retrieve customer and token information from your PSP. This process varies from PSP to PSP.
Prepare the data
Format and map the data to the Authorisation object fields.
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.
Link authorisations
Connect the imported records to related Salesforce objects.
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
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
For persistent issues during this process, refer to Salesforce Data Import documentation 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.